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: Oldest
  1. Anonymous
    2023-01-09T19:46:46+00:00

    Also, psexec itself has to be run with elevated privlages.

    Sure, run it from an elevated cmd... On other installs the key showed up.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-01-09T19:52:09+00:00

    I didn't know that now to update W10 you had to be a computer technician, lol but you're crazy to touch your registry

    Touching the registry is not crazy. It let (you) me fix many problems and configurations. I'm not a gamer and dealing with Win registry since Win has a regsitry. Before I dealed with ini files, haha.

    I even backupped the key before deleting content, so usually there is no crazyness.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-01-09T20:29:23+00:00

    I'm guessing the Home edition is different. Perhaps try manually creating the taxonomy. Maybe that's the problem. Just a suggestion.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-09T20:48:19+00:00

    Yupp, thanks. I had the same idea when I tried. Created NL$KM and subkeys by hand, for sure while opened elevated with psexec, but stayed empty even after many reboots. It doesn't touch this key. This is why I tried then with the existing DPAPI_SYSTEM key.

    Was this answer helpful?

    0 comments No comments