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-09-13T15:00:04+00:00

    Hello!

    I have 2 old computers, both upgrade from Win 7 pro or ultimate, as follows:

    • First:

    Processor(s):              1 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 37 Stepping 5 GenuineIntel ~3067 Mhz
    BIOS Version:              American Megatrends Inc. 0901   , 12.11.2010

    ProductName ReleaseID CurrentBuild InstallDate

    Windows 7 Ultimate 7601 14.04.2017 00:59:38

    Windows 10 Pro 1703 15063 29.04.2017 14:57:45

    Windows 10 Pro 1709 16299 18.10.2017 21:56:34

    Windows 10 Pro 1803 17134 01.05.2018 14:29:49

    Windows 10 Pro 1809 17763 06.02.2019 01:32:22

    Windows 10 Pro 1909 18363 22.05.2019 22:50:41

    Windows 10 Pro 2009 19042 15.08.2020 01:52:54

    Windows 10 Pro 2009 19043 13.11.2021 20:13:45

    Windows 10 Pro 2009 19044 08.12.2021 21:17:46

    • Second:

    Processor(s):              1 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 37 Stepping 5 GenuineIntel ~3067 Mhz
    BIOS Version:              American Megatrends Inc. 0901   , 12.11.2010

    ProductName ReleaseID CurrentBuild InstallDate

    Windows 7 Professional 7601 25.11.2020 11:31:13

    Windows 10 Pro 2009 19044 25.11.2020 12:45:59

    First has everything up-to-date including infamous KB5016616 and aslo KB 5012170; Second "HANGS ON REBOOT" after installing KB5016616 .

    So I think, it is related to what Windows 10 version was the computer upgrade first: in my case "First" to

    Windows 10 Pro 1703 15063 29.04.2017 14:57:45

    while "SECOND"

    Windows 10 Pro 2009 19044 25.11.2020 12:45:59.

    Thoughts?

    THX!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-09-12T08:39:15+00:00

    Yes - Now as Oldboy's situation: KB5016616 now not showing. See mine of 5/9. So in a similar situation. but I have not, and will not for now, attempted KB5016688, And still "616" still not offered.

    Had come to the conclusion, as per 5/9, to try an old spare disc, full install, see what happens. Just need to find the time. For me, all still points to some fragment of 616 as the issue. NB my PC is from 9/2020, i7, 16GB ASUS Mboard, supplied new with trial installation of W10, activated with my preceding licence. So no apparent link with W7 (but see mine of 29/8 on that - surely not??)

    NB during my "Live Assist" session with MS, I did ask for this to be escalated internally to the right bit of MS - so just possibly...?

    And tomorrow - another Patch Tuesday? Don't leave them on overnight....

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-09-12T06:54:12+00:00

    Took the plunge and went with the format & re-install. Now build is finally showing the same as my other PCs: 19044.1889. Ironically the in-question update KB5016616 didn't show up or was merged with other update(s) or I simply failed to notice it downloading and/or installing even though I had my eyes nailed on the windows update screen whilst downloading and installing update(s).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-09-11T11:12:58+00:00

    FWIW I saw this problem on an ancient Lenovo desktop (Intel Core Duo ancient) with 3GB useable memory. I cloned the disk after clearing up the failed update and transplanted it into a Dell Optiplex 780 (almost as ancient but with more memory). It still has the same issue. I would need a lot of convincing that the problem has something to do with the hardware/BIOS. The original installation was an upgrade from W7 Pro

    Was this answer helpful?

    0 comments