Windows 10 22H2, KB5016616, KB5017308, KB5017380, KB5018410, KB5019959, KB5021233 hang on reboot after install

Anonymous
2022-08-11T22:19:21+00:00

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.

Windows for home | Windows 10 | Install and upgrade

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.

0 comments
Answer accepted by question author
Anonymous
2022-12-26T20:47:58+00:00

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.

Was this answer helpful?

20+ people found this answer helpful.
0 comments

319 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-16T14:47:11+00:00

    Using method 2 on two older Dell Vostro 360 AIO's did "not work" for me.

    Looks like I'm pausing updates for a month or two.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-14T13:43:52+00:00

    I let it run overnight twice and it never finshed the update and that was with a manual dowload. This has not happened before on this machine and its a fast machine too with 16 GB ram and an SSD. I have tried the 2 methods from your link and they did not work. For me, and it appears others, this is a problem with the update itself not the window's process. Thanks for the info and help.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-08-14T05:54:08+00:00

    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.

    [Method 2: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-will-not-accept-my-updates-error/1c620e5d-9746-4f28-9339-cca1ce98733d].

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-08-13T16:43:15+00:00

    I am glad to help. Keep me posted on your progress as I will be here to help until the case is resolved.

    Was this answer helpful?

    0 comments