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 No 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 No comments

319 additional answers

Sort by: Newest
  1. Anonymous
    2022-12-10T00:19:06+00:00

    Unfortunately - spot on, Logan.

    As I have pointed out sadly several times, from September on.

    If there was a work round, someone on this group would have found it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-12-09T21:39:08+00:00

    I've encountered this problem a total of 5 times. Reinstalling windows fresh is the ONLY fix. Clearing out Softwaredistribution, in place upgrade, nothing works. You have to fresh install. At least you can run system restore and get it running (you won't be able to update anymore), so you can gather your passwords and settings and what not before you do a clean install. I'm going to try some more things, since I'll be getting a computer in at work next week that has this problem.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-12-08T13:05:16+00:00

    i don't believe at Santa Claus,

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-07T20:06:24+00:00

    Toc toc..... is there any MS engineer that check these posts ?

    This question is signed by hundreds of people, so the problem is real and urgent !

    Any reply / solution from Microsoft !?!??!?!?

    :-(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments