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.
Yep, All my other 4 Pcs (1 newest and most powerfull of all, and 3 potatos I use at work) updated without any issue(s) with this KB5016616 update.
All had one thing in common: They were direct/clean win10 installs. This 2nd in age and computing power pc was upgraded from win 7. And even an on demand upgrade didn't work. Nice catch guys. But I am angry. M$ should provide a patch for these win7-->win10 upgraded machines. What if this was a work PC? I would have been stuck and not able to work after 30 days... Simply unacceptable. Do we have to be fortune tellers or prophets to use our computers??
After discussing this issue with my computer assistant who has personally upgraded all of my 3 work client pcs (the potatoes) it became clear that at least one of them has been upgraded from windows 7 (if not all - we cannot remember exactly). Yet all of them upgraded with August update without issues. But: There is a difference between all these 3 potatoes and the PC at my home that has the issue: They were used to be Windows 7 Pro installs whereas the one with the issue was a Windows 7 Ultimate install. I don't know if has anything to do - just mentioning. In the meantime the situation with this PC is getting worse: Even though I suppressed this particular update by enabling on-demand-updating and deselecting this one using method describe here , windows found new updates, tried to update and ended up with the spinning circles after restart, hard reset twice and reverted back to where I was. So basically now no updates work for me - this PC can no longer update itself so I guess its time for a clean install??
Just a FYI.
Like a few others, I have now turned updates off. I also hid KB5016616 so it wouldn't install. I checked updates and had KB5016688 come through on my VM and it has the same results as KB5016616, with the spinning wheel on a black screen after reboot.
Not sure if it is the same main update as KB5016616 but with a few extra updates combined, but if you have issued with KB5016616 then KB5016688 may also produce the same issues.
Have same problem on clients computer. I have hidden update kb5016616 and tried the kb5016688 which was an optional update but it produces same scenario, so same problem as kb5016616 (spinning infinite wheel, do reboot twice which results in trying to repair which faults then restore changes made to the system) I have tried all fixes and a repair install with latest updates, but hangs the same way at reboot. At least the problem my client had is gone for now as I have hidden kb5016616 and kb5016688 is optional and not will be installed automatically.
Just a FYI.
Like a few others, I have now turned updates off. I also hid KB5016616 so it wouldn't install. I checked updates and had KB5016688 come through on my VM and it has the same results as KB5016616, with the spinning wheel on a black screen after reboot.
Not sure if it is the same main update as KB5016616 but with a few extra updates combined, but if you have issued with KB5016616 then KB5016688 may also produce the same issues.
I'm running into the same issue. I'm disabling auto update for now until a fix from MS is released.
