Cumulative Update Issues in Windows 10 & 11

strggg · Dec 15, 2022

I am also still having this issue, there are many others who are still affected in this thread:
https://answers.microsoft.com/en-us...=c69308d8-6680-434c-b05e-0e1822925d98&page=20

Might be worth it to comment/click "I also have this problem" so Microsoft has more visibility on the issue.

It definitely seems like a driver issue that is only resolved with a clean install. Real pain in the butt.

slcidea · Dec 15, 2022

strggg said:
I am also still having this issue, there are many others who are still affected in this thread:
https://answers.microsoft.com/en-us...=c69308d8-6680-434c-b05e-0e1822925d98&page=20

Might be worth it to comment/click "I also have this problem" so Microsoft has more visibility on the issue.

It definitely seems like a driver issue that is only resolved with a clean install. Real pain in the butt.

Glad to hear that I am not the only one. It's a bizarre problem and I still haven't been able to identify which specific driver is the culprit. I updated every OEM driver I could think of, and my suspicion is that it's a Microsoft driver from a previous build that's causing this problem likely during migration phase of the install. Waiting every month to see if they'll have a fix for this. Interestingly the problem affects both Windows 10 & 11 machines starting with updates that came out in August 2022. Check this out Windows 10/11: Strange issues since August 2022 updates

slcidea · Dec 15, 2022

strggg said:
I am also still having this issue, there are many others who are still affected in this thread:
https://answers.microsoft.com/en-us...=c69308d8-6680-434c-b05e-0e1822925d98&page=20

Might be worth it to comment/click "I also have this problem" so Microsoft has more visibility on the issue.

It definitely seems like a driver issue that is only resolved with a clean install. Real pain in the butt.

BTW, can you tell me which Motherboard you are using and your graphics card.

strggg · Dec 16, 2022

I've got a Dell Precision 3620 PC with a R46NM motherboard and an NVIDIA NVS 315 GPU

slcidea · Dec 16, 2022

strggg said:
I've got a Dell Precision 3620 PC with a R46NM motherboard and an NVIDIA NVS 315 GPU

I built my machine with a Gigabyte Z390 Board and I also have an NVIDIA Graphics Card but a different one. Do you have any Realtek devices in the system (i.e. Network Adapter, Sound...)? Trying to see if there's a common link between machines that fail the update.

glasskuter · Dec 16, 2022

slcidea said:
The only resolution to these update problems has been a complete clean install.

If you read the problems being encounterd with WU (mostly cumulative updates) you will see there is no rhyme or reason why it happens to some and not others, and the solution for one will not work for someone else. In my case, I began encountering the problem in the spring and it happened with every single cumulative update. What fixed it for me turned out to be that Malwarebytes (or any other third party AV) has to be disabled before the update will install. If I do this every update Tuesday and manually apply the update, I have no issues. However, if I let the updates fail ONE TIME, nothing I do will get them to install other than restoring an image to a time before the original installation failed and then disabling MWB. I have calendar notifications set for every update Tuesday so I don't forget and let any cumulative update attempt to install.

slcidea · Dec 16, 2022

glasskuter said:
If you read the problems being encounterd with WU (mostly cumulative updates) you will see there is no rhyme or reason why it happens to some and not others, and the solution for one will not work for someone else. In my case, I began encountering the problem in the spring and it happened with every single cumulative update. What fixed it for me turned out to be that Malwarebytes (or any other third party AV) has to be disabled before the update will install. If I do this every update Tuesday and manually apply the update, I have no issues. However, if I let the updates fail ONE TIME, nothing I do will get them to install other than restoring an image to a time before the original installation failed and then disabling MWB. I have calendar notifications set for every update Tuesday so I don't forget and let any cumulative update attempt to install.

The weird thing for me is that I have taken images that I made months before the failure in August and none of them would complete the update which is why I suspected some hardware related driver issue for my scenario.

glasskuter · Dec 16, 2022

It's all weirder than weird and the web is flooded with complaints about it. MS has never been able to match Apple in always having troublefree updates. It may well be that Apple using proprietary hardware is the reason whereas Windows users have so many different configurations. MS is supposed to be the masters of operating software but updates have caused problems for as long as I can remember, even more so these days.

strggg · Dec 16, 2022

glasskuter said:
If you read the problems being encounterd with WU (mostly cumulative updates) you will see there is no rhyme or reason why it happens to some and not others, and the solution for one will not work for someone else. In my case, I began encountering the problem in the spring and it happened with every single cumulative update. What fixed it for me turned out to be that Malwarebytes (or any other third party AV) has to be disabled before the update will install. If I do this every update Tuesday and manually apply the update, I have no issues. However, if I let the updates fail ONE TIME, nothing I do will get them to install other than restoring an image to a time before the original installation failed and then disabling MWB. I have calendar notifications set for every update Tuesday so I don't forget and let any cumulative update attempt to install.

Thing is this is a VERY specific issue that is affecting a wide range of devices all with the same error. Not the same as usual run of the mill cumulative update issues. I've disabled every AV or cause of the error as I could, but the problem still stems from a broken update back in August 2022. Even a system restore to BEFORE the update was installed does not solve the problem.

slcidea said:
I built my machine with a Gigabyte Z390 Board and I also have an NVIDIA Graphics Card but a different one. Do you have any Realtek devices in the system (i.e. Network Adapter, Sound...)? Trying to see if there's a common link between machines that fail the update.

I do have some Realtek devices, I've attached an export from msinfo32 with some details. Do any of your devices match? (Might be easier to rename file to .xml and view it like that)

slcidea · Dec 16, 2022

strggg said:
Thing is this is a VERY specific issue that is affecting a wide range of devices all with the same error. Not the same as usual run of the mill cumulative update issues. I've disabled every AV or cause of the error as I could, but the problem still stems from a broken update back in August 2022. Even a system restore to BEFORE the update was installed does not solve the problem.

I do have some Realtek devices, I've attached an export from msinfo32 with some details. Do any of your devices match? (Might be easier to rename file to .xml and view it like that)

Try this utility from NIRSOFT View the installed drivers list on Windows operating system you can then copy and paste it in excel. Easier to compare drivers that way with the different versions.

strggg · Dec 16, 2022

slcidea said:
Try this utility from NIRSOFT View the installed drivers list on Windows operating system you can then copy and paste it in excel. Easier to compare drivers that way with the different versions.

Had to zip it since the site doesn't allow xlsx files. Here's the drivers that are installed.

slcidea · Dec 16, 2022

strggg said:
Had to zip it since the site doesn't allow xlsx files. Here's the drivers that are installed.

Look at the first tab where I've marked about 48 drivers where the version number match between our system.

strggg · Dec 29, 2022

Hey, if you haven't seen it yet there was a solution found on the Microsoft forum involving clearing some registry keys. It fixed the issue for me!

https://answers.microsoft.com/en-us...=c69308d8-6680-434c-b05e-0e1822925d98&page=20

slcidea · Dec 29, 2022

strggg said:
Hey, if you haven't seen it yet there was a solution found on the Microsoft forum involving clearing some registry keys. It fixed the issue for me!

https://answers.microsoft.com/en-us...=c69308d8-6680-434c-b05e-0e1822925d98&page=20

So is this the solution?

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)

strggg · Dec 29, 2022

Yep, but you have to launch regedit with PSExec or take ownership of the folder to be able to see those keys. But clearing those two out, rebooting, and installing the 22H2 update all went smoothly.

slcidea · Dec 29, 2022

strggg said:
Yep, but you have to launch regedit with PSExec or take ownership of the folder to be able to see those keys. But clearing those two out, rebooting, and installing the 22H2 update all went smoothly.

Will give it a shot. Thanks

glasskuter · Dec 29, 2022

I'm not saying this is not the solution, but I will say I would certainly backup those registry keys before deleting them as well as make a system image before deleting.
Updates in 11 have caused problems for a long time and I have not seen this "fix" before now. Also, what has "fixed" problems for some has not worked for others.
It is better to use caution.

slcidea · Dec 29, 2022

glasskuter said:
I'm not saying this is not the solution, but I will say I would certainly backup those registry keys before deleting them as well as make a system image before deleting.
Updates in 11 have caused problems for a long time and I have not seen this "fix" before now. Also, what has "fixed" problems for some has not worked for others.
It is better to use caution.

I always do that just to be safe.

slcidea · Dec 29, 2022

slcidea said:
Will give it a shot. Thanks

So after making the registry change should I reboot before the 22H2 upgrade?

strggg · Dec 29, 2022

slcidea said:
So after making the registry change should I reboot before the 22H2 upgrade?

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.

Cumulative Update Issues in Windows 10 & 11

New member

My Computer

Active member

My Computer

Active member

My Computer

New member

My Computer

Active member

My Computer

aka Mama Glass

My Computers

Active member

My Computer

aka Mama Glass

My Computers

New member

Attachments

My Computer

Active member

My Computer

New member

Attachments

My Computer

Active member

Attachments

My Computer

New member

My Computer

Active member

My Computer

New member

My Computer

Active member

My Computer

aka Mama Glass

My Computers

Active member

My Computer

Active member

My Computer

New member

My Computer

Similar threads