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.
Just for **** and giggles, I took a USB and created a fresh installer using the microsoft MCT. Ran the in-place upgrade / over-the-top install (not connected to the internet). No problems so far, booted fine. Once it was up and running, I ran windows update check and it pulled down all the usual updates, including KB5016616. Sure enough, reboot after update left it on the spinning circles.
As for drivers, I literally made sure it was running all the default/in-box MS drivers. The only thing windows insisted on installing/updating was the display drivers (nvidia).
Thanks shawnfuller. So:
a) You have it on a clean w10,
b) I am OK on Lenovo upgraded W7>W10 2015, others as well.
So apparently not directly due to W7 upgraded PCs?
BUT- as briefly in my previous post, licence on my problem machine has "a history". Originally purchased online 2017 to use to upgrade my then Dell , 2009 XP, upgraded to W7 2014 on original licence.. Had several abortive attempts at W10, failed other reasons. Eventually installed W10 OK , but would not activate against that licence. But eventually activated itself on original XP>W7>W10. So that key not used, should be available.
Current PC purchased with trial W10, aimed to use it there. Again, assorted issues with that. Eventually had a remarkably constructive telecon with MSoft - agreed I effectively "owned" an unused licence, but "corrupt". Issued me a new key. PC activated OK. But now shows not that licence key - but "Digital". AOK until now.
Conceivable KB5016616 issue is some deeply buried licence or security bug?
Doesn't seem that anyone on this thread with a failure has actually found a solution? Including some clearly very experienced people.
I had the same issue.
After running Windows Update troubleshooter without it finding anything, this method from the year 2015 was automatically suggested. I tried Method 2 on the page and it worked.
After entering the PowerShell commands, the update started from scratch. I considered that a good sign. This update was unusually slow on my three Windows 10 (i5 & i7 with 8-32 Gigs of RAM and a fast internet connection) computers. In my experience, you should expect the install to get hung up on 20% for quite a while before it proceeds further. The process probably took 2 hours on each of my computers.
I did not try them all yet but nothing has worked. I don't think its an Update problem but rather the update changes themself because other updates have installed fine during this time.
I opted to be notified of updates and to use your suggested tool to hide the bad one. I have update on so I can monitor and choose which ones to install and when. I want to backup including taking an image just in case before I install any update.
Yes, I created multiple system restore points on a working system before updating. The auto rollback reboots perform an uninstall automatically for the bad update.
Thanks for the help Greg.
