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-12-31T07:22:41+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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-30T22:34:27+00:00

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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-30T22:02:38+00:00

    No keys is weird. It sounds like there's still a permissions problem. Can you see the the root key HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM\ but not the sub values? Also is the machine domained? Perhaps leaving the domain will let you fix it. It could be a group policy thing that won't let u see the keys. Also, try manually creating the NL$KM taxonomy and reboot. The reboot should fill in the CurVal.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-30T20:18:43+00:00

    Hi peeps,

    I'm following this thread since Nov, 22, as I have one new Win10 home machine in the house which has the problem. I'm in the IT business and know what to do (usually), but this one, hmm. Did many of the solutions, that are also here, but not the one, what is the solution for most of you.

    Here it does NOT work. The machine simply doesn't have this registry key: HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM\

    Yes, I opened regedit with psexec -i -s, but the machine only has the DPAPI_SYSTEM key, which has the same entries like NL$KM...

    So I deleted the CurVal and OldVal Default values there, but without success. All I got, was that all passwords from any apps and even the PIN for login went away.

    OK, gave the user a new password with the utilman.exe solution and being logged on again, but all other apps (Adobe/Nextcloud/Outlook etc.) telling me there might be a MITM attack, asking for logins again.

    This is true, as the CurVal key holds all LSA secrets of the machine, nicely explained here: https://www.passcape.com/index.php?section=docsys&cmd=details&id=23

    So I'm wondering why deleting the encrypted values of the secrets will solve the problem of this installing/repairing/uninstalling loop.

    I created the NL$KM values manually by exporting the DPAPI_SYSTEM key, renaming DPAPI_SYSTEM with NL$KM in an editor and imported it with empty CurVal and OldVal while opened regedit with psexec. But the machine isn't using it.

    So I went for hiding the latest cumulative update with the solution here (2 files reset win upd & wuhide). Strange, now no download starts, even when I click "Download" below the offered updates. Services are running.

    Anyway, it's a 1 year old OEM install, so I will reinstall from scratch Win11.

    CU

    DigitalTrance

    Was this answer helpful?

    0 comments