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

Hey man I just tried your solution and it WORKS!

I can log into the windows store fine if that helps, but I also do not use domains.

@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 ?

Thanks to M$ this has been an arduous task but we have smart, helpful folks on this thread.  Thanks to all  for the help and @info001 for the solution.  Here’s the details:

0 – BACKUP, BACKUP, BACKUP.  Don’t forget desktop files, browser favorites and logons and all your data files.

1 - You need elevated access (System level not just administration) to fix this.  

As per @loanb92’s suggestion download Psexec or Psexec64 from SysInterals to accomplish this step.

https://techgenix.com/howtobreakintoregistrytoexplorehklmsamandhklmsecuritykeys

https://learn.microsoft.com/en-us/sysinternals/downloads/pstools

EDIT-- @Mark Blinkhorn suggested an alternate method to modify the settings that does not require Psexec.  Run RegEdit with elevated permissions (as Administer). Right click the NL$KM key and select Permissions.  You will get an error message saying you don't have permission to change the permissions but you can change that.  Add the Administrators group and grant them full access.  Apply these settings to the entire sub tree. Use Psexec if you don't want change the security settings on the registry key. Skip #2 and #3 if you change the permissions.

2 - Enter CMD in the Windows search box.  Select Run as Administrator in the search results box.  This is required to run at the System level.

3 – Enter “psexec -s -i regedit.exe” in the command window

4 – Navigate to registry key HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM

5 – Select CurVal and right click the “Default” name in the right pane. Choose Delete

6 - Do the same for OldVal

7 – Reboot

8 – Run Windows Update and install the 22H2 update.

9 – Reboot and say a prayer to the update gods.

10 – Run Window’s Update again and see that you are up to date.

Can you provide a step-by step?
I'm not sure I follow what deleting value data means, delete the whole string? the key?