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.
@Dockite awesome engineering and explanation. My system is a Win7 upgrade and fails exactly as you described.
I had this problem on a friends very old PC just recently. I have quite a number of similarly old PCs and one with a near identical spec and all of these systems installed KB5016616 successfully.
My friend was anxious to get his PC back as quickly as possible as it's his main system. After a number of restores and checking logs etc, it was evident that KB5016616 was the culprit. Having done all the usual:
SFC /SCANNOW
DISM /ONLINE /CLEANUP-IMAGE /REVERTPENDINGACTIONS
DISM /ONLINE /CLEANUP-IMAGE /RESTOREIMAGE,
CHECKDISK /R /F
and a rebuild of the SOFTWAREDISTRIBUTION folder, any attempt to install KB5016616, either via Windows Update, or from downloading the update package, would result in a frozen boot and the spinning white dots. I imaged my friends system, stopped the windows update service on his machine and returned it to him, so at least he had a functioning system!
I restored his system's image to a spare hard drive and booted from my near identical system, so I could dig deeper and do some playing. All repositories and system files were error free and the system fully updated to pre KB5016616. Bespoke System Hardware Drivers were replaced with Microsoft defaults. MS Office was uninstalled as this had been mentioned as a potential issue and all Printer Drivers and associated software uninstalled. On installing KB5016616 and rebooting, the system froze with the spinning white dots.
The System is MBR not UEFI and does not have a 'Recovery Partition', but does have a 'System Reserved' partition. I expanded the 'System Reserved' partition and created a 'Recovery Partition', then established it via:
bootrec /rebuildbcd
reagentc.exe /enable
Previously, I rebuilt the MBR, Boot Record and BCD as follows:
bootsect /nt60 V: /force /mbr (V being the label of the 'System Reserved' partition establisked via DISKPART)
bcdboot C:\windows /s V: /f ALL
Unfortunately, this was to no avail and on installing KB5016616 and rebooting....well you guessed it!
I have a database for all PCs that I work on and the only differing factor from this system and my other equally as old systems, was that they were all fresh Windows 10 istalls and this particular one was a Windows 7 upgrade.
Doing a fresh install on my near identical system and installing the downloaded KB5016616 package was seemless and booted without issue.
I installed an old Windows 10 image (which was a Windows 7 upgrade) onto an old Dell laptop from which it was taken. On installing update KB5016616 and rebooting, the system froze at the spinning white dots. A fresh install had no issues.
Not that it helps much and hopefully Microsoft will fix this (as of typing 2022-08 Cumulative Update Preview for Windows 10 Version 21H2 for x64-based Systems KB5016688 has been released) but from my experience a system that has upgraded from Windows 7 has a problem!
I hope this helps someone.
Some great info here, thanks!
I'm having this problem on a handful of PCs I support. All HPs, but different models. They're all on the "older" side. It doesn't seem related to the model, because some are failing, others are not. Office does not seem to be the culprit in my case either, a few have office loaded, some don't. In my case, they were each built from fresh installs of Windows 7, upgraded to Windows 10, but others built the same way, complete the update just fine.
I ran SFC and DISM, downloaded the update manually, and attempted to install, with the same failure symptoms.
I'm still looking into the issue. I'll post any progress I make. Hopefully Microsoft beats me to it with a fix!
BTW, of about the 30 computers I support, 5 are having the issues. This consists of:
2 HP Z420s (one broke, one didn't, neither of these run office)
HP Elitedesk 600 G1s (2 broke of about 10, one with office, one without)
HP Elitedesk 800 G1s (2 broke, both have office, one with 2016, the other with 2019)
Hi glez, i saw your post elsewhere (not sure if mentioning the site is allowed...) but i couldn't reply to it there, so figured I would here - yep! Aligns with Dockite's findings, upgraded windows installation here with the same issue, spinning circle of death.
"they were each built from fresh installs of Windows 7, upgraded to Windows 10, but others built the same way, complete the update just fine."
@B1GfeK, so some Win7 upgraded machines install the update fine for you? Is there anything about the version of Win7 or its updated status that the ones that work have different from the others?
