Windows 10 22H2, KB5016616, KB5017308, KB5017380, KB5018410, KB5019959, KB5021233 hang on reboot after install

@info001 you are brilliant. This has worked perfectly. Please tell us how you found it.

As the Doctor would say, "I came the long way around".

I was not willing to follow OldAJAS advice and dump a working system.

After 4 months it was clear that MS does not fix the Problem (I also tried the latest Win11 Insider-Build).

Thank God the problem also exists in my VMware clone.

As all my Win10 Backups had the same Problem, I used an old Win7 pre-Win10-upgrade backup.

Upgraded it with the same DVD as my PC.

Applied all available Patches form my PCs Update History (some unimportant were not available in Microsoft Update Catalog).

After that I was able to exchange parts form the two installations.

As the two installations share the same base (SAM/Security) they are partially compatible.

After spending huge time with CBS (Component-Based Servicing) I was able to exclude the filesystem as the problem.

It had to be the registry.

I suspected the SOFTWARE part or the COMPONENTS part of the registry.

By exchanging registry files between the two installations, I was able to exclude both.

I started to test all registry files in %SYSTEMROOT%\System32\config.

Bingo - "SECURITY" caused the Problem.

Because both installations share the same base, there were only few differences between them.

The rest was trial and error.

I've spent a lot more time on this than I care to admit.

Did anyone have problems afterwards?

Maybe with logins to MS-Cloud Accounts (I don't use them).

The deleted Keys are used to decrypt cached Domain-Passwords (according to doctor google).

Does anyone have tried the solution for a domain-joined Win10 ?

I can't thank you enough for this fix that MS has not addressed ever since they screwed up all subsequent updates in August 2022. I had posted this issue on this forum as well as Elevenforum and no one was able to figure out what the root cause was. Finally, someone on Elevenforum alerted me about your fix and I applied it to my machine and it worked. Hoping MS will take the ball and run with it and come up with an official solution. Thank you so much, you're a lifesaver and you don't realize how much it means to thousands of people who have been dealing with this issue for several months now. Keep up the great work!

....and what sadeness me that MS didn't even bother to acknowledge that there are some "newb's" having this problem...they completely ignored us....... "The moon does not heed barking of dogs".......

A few months ago I chatted with MS support and they said that they were aware of the problem and asked me to do a clean install to fix the issue at the time. It's been now over 4 months since the problem showed up but each monthly update fixes something else but not this issue. They need to at least post a bulletin at a minimum and tell the world they are working on it. So glad this guy found a solution.

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