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.
Using psexec I now see the same thing that @OldAJAS sees in the registry.
Psexec is from Systools package which I have found very useful over the years and trust it.
Also as a safety precaution, if you right click the NL$KM registry entry you can export the key just in case it has to be restored (assuming the machine still works after deleting the values).
So now we need someone with a test environment to try the suggestion and to know the sequence that @info001 used.
Apparently you need elevated access
https://techgenix.com/howtobreakintoregistrytoexplorehklmsamandhklmsecuritykeys/
@loan92 thanks for that. I can now see the registry entries
I agree, I'm waiting too for more information on this..
OK, yes, my last post, and others, were a false view (“red herrings”). So irrelevant, thanks loanb92.
You do need the right permissions to see the truth, but I echo info001's caution re going there if not an expert. There is a simpler, more controlled, way than loanb92's obscure link - personally I would not risk going that route. I found a more direct, built in, route ref a Microsoft site (I would never go to an unofficial 3rd party site such as that when messing with W10 to this sort of depth). This is deeper than I have ever been into regedit, I only gave myself "read" permission.)
But this is what is then revealed:
Now – you see this:
Both Currval & Oldval have a (different) huge string of upwards of 60 2-byte alphanumerics.
The view above has right panel cropped, but even at full stretch, hover and a much longer one is displayed, but still truncated.
Like info001, I would await with interest any responses from those more expert than I before encouraging others to "try it & see", messing with regedit is always high risk.....
(And I don't need to on my rebuilt PC).
