Recent content by slcidea

Sounds like your issue is unrelated to this fix and could be a driver issue given the code 0xC1900101 - 0x30017.

Sorry, that's just a typo with a missing "r". After the registry change you have to reboot before attempting the update. Just make sure you follow the instructions exactly as shown. Doesn't hurt to give it another try.

That's the exact error message I was getting when I had the problem and it points to driver issue. But this fix that I applied fixed my problem and the updates are working fine. I take it that you followed the instructions and were able to get into the registry with elevated privileges to...

Oddly this problem only happens on some systems as my other machines upgraded fine. I was struggling with all the error log files in Panther directory because the number of errors were too many. Not to mention the wrong diagnostics that Windows kept reporting regarding possible driver issues...

I followed these steps suggested by STRGGG on this forum and my problem with updates failing to complete was finally resolved. After months of struggling and posting on this forum with little success, I am happy to report that this fix worked! I've updated the suggested steps below with some...

So who actually discovered the fix? I suspected something in the registry a while back after every attempt to update had failed for me. The only thing that had worked for me was when I didn't save any of the applications and only kept personal files. I had been playing with various images...

Can't thank you enough my friend. The fix worked!!! The mystery of the failing update finally solved. Did you just stumble on this or was there something officially posted by MS? I really appreciate you letting me know, or I would still be waiting. I was checking the forum periodically to see...

Thanks for the step by step. Wonder why MS hasn't incorporated this fix.

So after making the registry change should I reboot before the 22H2 upgrade?

I always do that just to be safe.

Will give it a shot. Thanks

So is this the solution? Delete the Value data (all bytes) of HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM\CurrVal\(Default) and HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM\OldVal\(Default)

I may have found the answer to my question. I noticed a software called WD Smartware & WD Quick View that were supported with the older WDMyCloud and don't believe they are there anymore. It's likely the driver for the WD NAS was installed from that piece of software in Device Manager.

Look under "Network" not under "This PC" where you'll see different groups of network connected devices. There's one group called "storage".

Years ago, I had installed a WD MyCloud in my network and at the time I was running Windows 7 Pro. I then migrated over to Windows 10 via upgrade. I noticed a "Western Digital NAS" entry in device manager with "WDMyCloud" device listed under it. There is a driver "wd_mycloud_2_2_0.dll" that...