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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-17T22:45:37+00:00

    I've had this exact problem on two machines already. One is a Dell Optiplex 3020 that came with win 7 and was upgraded to 10 and never had a fresh install. Other was a Lenovo M700 that had an older windows 7 box clone/upgraded to windows 10 to it, legacy mode. Both required fresh installs of windows. I got tired of system restoring back over and over. Deleting softwaredistribution is not a fix, in-place repair install of windows isn't a fix either, you end up not being able to boot after the in-place just like when you install the update.

    edit:
    Try this. I haven't tried it I gave up and fresh installed on the two comptuters I also had this problem with. https://superuser.com/questions/1736629/windows-10-august-update-kb5016616-returns-0x800f0922

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-08-18T02:47:33+00:00

    Thanks, I will try that tonight. I only have 2 primary partitions when I check.

    Also mine was a clean windows 10 install. I don't get any error though, it just starts the install process, reboots and then never finishes.

    At least if it fails I can easily copy my VM back across.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-08-18T07:29:16+00:00

    That fix didn't help me as my disks are neither GPT or MBR as they are within a 200gb VM.

    I have just hidden the update now, hoping it won't try and come back and install at a later stage.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-08-21T22:49:53+00:00

    I have exactly the symptoms quoted, update stalls at blank screen, can repair. etc. Tried 3 times now, again on a fairly high spec machine, less than 2 years old, lots .

    I will try Robert Fraser2's method- sounds helpful. But wary of need to mess with registry to back up etc. Not been there before in 30 years use of PCs back to original green screen IBM PC and every version of Windows from W2 on.

    But I do agree with glezbug, does seem that there is a core issue somewhere in KB5016616 - with some feature of certain PCs, widespread but not all. No trouble at all on a 4 year old HP Envy laptop.

    Time for MS to actually take some notice - how can that be achieved?

    Problem on Pausing Update is MS overrides after 35 days? Then PC is dead?

    i7-9700 CPU, 16GB RAM, 322GB space on SSD C: (all my data on separate NAS).

    NB Failing machine is W10 PRO, good laptop is Home. Relevant?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments