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: Most helpful
  1. Anonymous
    2022-11-28T14:31:20+00:00

    I have some HP 400 G1 /G2 desktops with this problem, and many others machines (same hardware, configuration, bios, ssd disk, etc....) that are able to download correctly the updates.

    I think Microsoft make a disaster with August 2022 Windows 10 update ! and the bug is still here (september, october and november windows update......)

    Please fix it !

    It's absolutely impossible to update these machines, when they reboot you see only spinning dots ! and then automatic roll back after 2 forced power off.

    Try upgrading to 22H2 or Windows 11 with same result..... very disappointed !

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-11-27T18:19:00+00:00

    Sure Bios Legacy : off

    sdd : 500go

    windows 32bit 21h2

    No update work since august 2022 for major update :-(

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-11-27T15:09:55+00:00

    I am the OP and my machine is set at UEFI - BIOS Legacy due presumably to an AMD Fire Pro video adapter incompatibility with secure boot like @Je C1. As @OldAJAS stated, the boot issue is different than the issue here. With booting securely a black screen is seen and with the problem discussed here the video works but we get spinning dots. Good thought though.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-11-27T13:41:54+00:00

    Good question. But see post from Samsung Aes 16/11.Apparently old legacy BIOS.

    But even if old BIOS is good- can't swap modern PCs back.... And clearly, although we have 100 or 200 or so here - still a tiny % of the millions out there.

    And cured by clean install, no change to UEFI. But might be a clue in some settings. CPM?? It does appear related to the point where BIOS is seeking and failing to find a bootable sector on a drive. In my case (now cured by clean build), it was on a connected but blank W10 screen, not the pure black of UEFI.

    To remind you, mine is new high spec PC, SSD, Sept 2020. No graphics card, uses bult-in Intel processor graphics. Buisness/domestic use, not gaming.

    Was this answer helpful?

    0 comments No comments