Cumulative Update Issues in Windows 10 & 11

strggg said:

Yes, that's correct. Here is the steps I followed (credit to someone in that post):


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.

PsTools - Sysinternals

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.

Click to expand...

strggg said:

Yes, that's correct. Here is the steps I followed (credit to someone in that post):


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.

PsTools - Sysinternals

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.

Click to expand...

strggg said:

I have been following that thread and posting for the last few months trying to get the attention of MS to fix it. Can't take any credit for the solution itself though! Glad to have helped :)

Click to expand...

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 ?

Click to expand...

strggg said:

info001 on the Microsoft forums found the fix. Indeed it also works on W10 since that is the platform I'm on. Here's a quote of his post:

Click to expand...