This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I'm trying to update to the latest Win10 update released on 8/8/22. Ever since that update was downloaded the machine hangs
on the required reboot after the install. I have disabled updates until I can find a fix. I've tried to download the update and install
manually but get the same results. Other updates, such as .NET, download and installed fine. Once the machine hangs it has to be rebooted
2 times to get to the automatic roll back. At least that works for now. I've run the Update trouble shooter and it doesn't fix anything.
Windows Update and BITS services are both set to automatic.
There is an error in the event log but I think its from the install abort from a forced shutdown.
Installation Failure: Windows failed to install the following update with error 0x800F0845: 2022-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5016616).
Update 10/5/22: KB-5017308, KB5017380, KB5018410 also FAIL in exactly the same manner as KB-5016616. Spinning dots on the reboot and the need to do a dual boot auto recovery. Title has been updated.
Any help would be appreciated.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
For me, the following solved the Problem:
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)
One reboot and CurrVal(Default) should be filled again.
If you are not domain-joined, i would not expect any problems.
I'm not giving directions on how to access and delete the value data because i want skilled people who know what they are doing to test my solution.
A few months ago I chatted with MS support and they said that they were aware of the problem and asked me to do a clean install to fix the issue at the time. It's been now over 4 months since the problem showed up but each monthly update fixes something else but not this issue. They need to at least post a bulletin at a minimum and tell the world they are working on it. So glad this guy found a solution.
....and what sadeness me that MS didn't even bother to acknowledge that there are some "newb's" having this problem...they completely ignored us....... "The moon does not heed barking of dogs".......
@info001 you are brilliant. This has worked perfectly. Please tell us how you found it.
As the Doctor would say, "I came the long way around".
I was not willing to follow OldAJAS advice and dump a working system.
After 4 months it was clear that MS does not fix the Problem (I also tried the latest Win11 Insider-Build).
Thank God the problem also exists in my VMware clone.
As all my Win10 Backups had the same Problem, I used an old Win7 pre-Win10-upgrade backup.
Upgraded it with the same DVD as my PC.
Applied all available Patches form my PCs Update History (some unimportant were not available in Microsoft Update Catalog).
After that I was able to exchange parts form the two installations.
As the two installations share the same base (SAM/Security) they are partially compatible.
After spending huge time with CBS (Component-Based Servicing) I was able to exclude the filesystem as the problem.
It had to be the registry.
I suspected the SOFTWARE part or the COMPONENTS part of the registry.
By exchanging registry files between the two installations, I was able to exclude both.
I started to test all registry files in %SYSTEMROOT%\System32\config.
Bingo - "SECURITY" caused the Problem.
Because both installations share the same base, there were only few differences between them.
The rest was trial and error.
I've spent a lot more time on this than I care to admit.
Did anyone have problems afterwards?
Maybe with logins to MS-Cloud Accounts (I don't use them).
The deleted Keys are used to decrypt cached Domain-Passwords (according to doctor google).
Does anyone have tried the solution for a domain-joined Win10 ?
I can't thank you enough for this fix that MS has not addressed ever since they screwed up all subsequent updates in August 2022. I had posted this issue on this forum as well as Elevenforum and no one was able to figure out what the root cause was. Finally, someone on Elevenforum alerted me about your fix and I applied it to my machine and it worked. Hoping MS will take the ball and run with it and come up with an official solution. Thank you so much, you're a lifesaver and you don't realize how much it means to thousands of people who have been dealing with this issue for several months now. Keep up the great work!
Sorry it has taken so long for me to update this; sometimes real life gets in the way. Anyway, I can confirm that it is NOT possible to Domain-join my affected PC without clearing out the Security CurrVal key as per the solution presented by @info001. The Domain join process appears to work correctly - I get the 'Welcome to the <domain> domain' dialog box and the computer name appears in AD Users & Computers on the DC but, when the computer reboots, it sits at the logon screen for a little while (1-2 minutes) and then the computer reboots without a clean shutdown. This then repeats ad infinitum and I have yet to find a way of breaking the cycle.
This strongly suggests to me that our particular bug (*bug*, not feature) will most likely only affect machines in a workgroup (make my day, prove me wrong) and, if this inability to join the domain and the ever spinning circle of dots isn't two sides of the same coin then I don't know what a smoking gnu is!
OK, M$, there are all the clues on a plate - go and fix it...
Mark
