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.
Finally! Can confirm it worked on my PC as well. Great work info001!
No thanks at all to Microsoft.
For the record; I ran REGEDIT in an elevated CMD shell and simply altered the permission on the SECURITY key to grant Local Administrators Full Control of the key and subtree - no tedious mucking about with PSEXEC for me.
I updated the instructions.
Wow. Above and beyond effort. Thats for the tenacity.
Spurred on by @glezbsg success in this, I got my finger out and can confirm that the suggestion by @info001 does fix the swirly dot problem. I now have Windows 10 Pro 22H2 succesfully installed on my (ancient) non-domain joined Core2 Duo PC. It would be helpful if somebody would try the fix with a domain-joined machine and post the results here. (I can, and will, do this with a clone of my machine, but it will take some time to set up)
For the record; I ran REGEDIT in an elevated CMD shell and simply altered the permission on the SECURITY key to grant Local Administrators Full Control of the key and subtree - no tedious mucking about with PSEXEC for me.
Now we know HOW to fix the problem. I'm still curious to know WHY this fixes the problem. If @info001 doesn't spill the beans I shall simply assume that they are the person responsible for the problematic code in the first instance ;-)
It has been a pleasure sharing information with some of the useful contributors to this thread. Glad to have made your acquaintance.
Happy New Year!
Mark
Edit - Just spotted @info001 cross-post. Thanks for the background. I'll domain join my clone and try again - might take me 24 hours or so to sort it, but I am on hiatus anyway...
Mark
