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.
Hello!
Checking https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2 iI came to this:
Known issues This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
| Summary | Originating update | Status | Last updated | | :--- | :--- | :--- | :--- | | Update might fail to install and you might receive a 0x800f0922 error <br>Security update for Secure Boot DBX might fail to install. | N/A | Investigating | 2022-10-18 <br>10:04 PT | Issue detailsAugust 2022 Update might fail to install and you might receive a 0x800f0922 error
| Status | Originating update | History |
|---|---|---|
| Investigating | N/A | Last updated: 2022-10-18, 10:04 PT <br>Opened: 2022-08-12, 17:08 PT |
Just to add to the list (before I blow away and rebuild my client's PC for, hopefully, the last time),
This is another Dell PC (all in one Core i3-3220 Win10x64Pro) that was upgraded from Windows 8 and eventually cloned to SSD.
I have tried all the common suggestions with no fix (has endless spinning dots on first update reboot). Including an in-place upgrade (keeping everything or just user files both failed)
It does not seem to be dependent upon the other partitions on the drive as I have started with a fresh install that took all updates and just replaced the Windows partition with my backup and the problem returned. The machine also just took the 22H2 update which hung at 74% for quite a while, during which TiWorker.exe was just reading the MFT and the occasional poke at a registry file (no writes, only reads). After which it rebooted and hung at the spinning dots again. I assume that it must have tried to continue the update after a reboot as it seemed to be stuck at 74% and probably failed due to the same issue. (TiWorker)
For some more background, this installation of Windows 10 had no noticeable issues and passed SFC & Dism scans. It would not take any of the past four cumulative updates (KB5016616, KB5017308, KB5017380, KB5018410) or the new 22H2 update.
I hope that this information might help someone, as for myself I will be rebuilding this PC from a fresh install.
Good Luck!
Chris.
Got the 22H2 update via the small enablement package.
I mentioned this before but it seems appropriate to mention it again.
When I first ran into the issue I tried upgrading the machine to Windows 11 (pre 22H2) and it upgraded perfectly. However, the same hang on reboot issue occurred with the cumulative update.
