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-12-16T05:24:16+00:00

    I have been hiding updates since August too, but I thought this latest update KB was maybe 'fixed' at last.

    Well, it's worse. It's destroyed my PC now.

    At first it hung, as usual, but then after the automatic repair, this time it rebooted and did the same thing- hung with black screen and dot circle.

    I killed power again and it did the auto repair again, but then it said it was going to do a disk check on drive K. Strange, my system drive is C, not K; that's just a data drive.

    Anyway, after that it blue-screened- 'critical process died'.

    Since then it has must blue-screened every time, then started the auto repair sequence.
    When the recovery options appear, I have spent the entire day trying every option there.

    System restore fails; it does not show the restore points I have created since August (each time I tried one of the updates), only a point that the Windows installer module created!

    Also, it says system protection must be enabled! So it does not let me proceed.

    ( I have had it enabled for years and have created restore points and used them to restore, many times.

    Uninstall latest quality update fails. it just says it couldn't do it.

    Uninstall latest feature update fails as well.

    System repair fails- says it couldn't repair it.

    Using cmd window, I tried SFC / scannow; it fails.

    I tried fixing mbr; fails with access denied at one point.

    I even tried safe mode with all options; it blue-screens on all.

    So MS has bug***d my PC completely now.

    Only choice is a new drive and fresh install.

    BUT.... MS... PLEASE NOTE, installing the OS again is the easy way out for you.

    My problems only then begin. I have installed on this windows 10 (upgraded from W7) multiple versions of visual studio, going back to vs6, to support legacy apps, many sdks and tools, many projects that took a long time to migrate and get working with various registered dllls, and much more. Then there is video editing software, iTunes with its stupid licence tied to a player- probably I'll lose all my music.

    Then MS Office and my emails plus many addins that make my life possible. Then dozens of Adobe products.

    Do I need to go on?

    I probably can't remember where to find the license keys for all this- many years of accumulated software.

    I doubt I will ever get my life back again!

    Meanwhile, all institutions have been forcing me to go paperless for years, so they send bills by email, and now I can't use my Outlook. I'm totally out of contact with them and I don't use cell phones etc. I have always relied on my Outlook for all my email accounts. I don't remember how to access them by webmail- oh, I forgot- it doesn't matter- I can't even run a browser!

    I can only write this because I'm borrowing someones computer!

    So, it's not SO EASY for some of us to 'just reinstall everything' MS!!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-12-15T15:26:27+00:00

    One curious thing is that when you run reset all the old hidden updates come back again. I have 4 (old drivers and SQL Server books) that I have to re-hide every time I do a reset along with the failed update but they don't show up on the update screen once hidden.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-12-15T15:16:48+00:00

    You might have caught the update with show/hide before Window's updates gets it. Like I said, once its on the update screen it sticks and show / hide doesn't work; that's where the reset comes in. I recall reading something about reset not always working on their web page. Maybe there's solutions there for you.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-15T15:14:21+00:00

    I don't think its a boot problem because we get the spinning dots and that's a Window's thing. Perhaps the problem isn't written or committed to the log file before we do the recovery reboot. The log might be afterwards. If there were 2 phase logs write for each function of the update like "doing this" and then "this worked or didn't" we would have a better chance of figuring it out. But I'm only guessing.

    Was this answer helpful?

    0 comments No comments