KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928 Win Update

I finally found the solution to installing KB5001330
It was to do with my VR headset. Yes, really.
Unplug it, run:
dism /online /remove-capability /capabilityname:Analog.Holographic.Desktop~~~~0.0.1.0
in elevated CMD
Restart, run Update.

Melchior said:

WOW! I had a ASUS Sabertooth 990 FX R 2.0 too... and the AMD FX 9590 for a CPU..
it ran so hot that it locked up my system while gaming randomly...

IIRC, my buddy in 2014 had an FX 9590 and it kept going down when I was only aware of him Skyping! (with me)
Then I heard that it got replaced with another FX. Then sometime after that incident, I saw posts about FX 9590s being unreliable at factory frequencies!

I paused the update. Hoping their will be an update this upcoming Tuesday.

ern88 said:

I paused the update. Hoping their will be an update this upcoming Tuesday.

Why would there be? It's not Patch Tuesday.

SM03 said:

March'21 & April'21 LCU both are bugged for choppy gaming performance & Framerates, any gamer here using the latest KB5001391 (v1904x.962) beta LCU, can confirm whether that bug is fixed in this or not?

Also, MSFT recently shared a server-side fix for 1904x.928 for the bug related gaming performance, the detailed article is here. Can anyone confirm this too?

What I can confirm is that the Known Issue Rollback (KIR) will add the following regkeys and that installing the beta .962 update will not reinstate the KIR rollbacks. Furthermore, it does not appear that the KIR uses the standard semi-annual Windows Update channel. The KIR uses some other channel to make the changes to the end-users registry. I consider this a privacy issue.

In this context Server-Side Fix=KIR

The following keys are added after the Known Issue Rollback is applied to 19042.928:
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4\1837593227
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4\194121355
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4\4071209099

RingTailCoon said:

Got them same keys too, that's kinda sneaky Micro$oft! Keep off my machine!

We're just renting the Windows OS - MEGAsoft owns it

For newbies like me

Known Issue Rollback (KIR) updates under Windows 10 explained once
Known Issue Rollback (KIR) Updates unter Windows 10 einmal erklart | Deskmodder.de

"Yesterday Microsoft a problem with the update KB5001330 fixed . But unlike in the past with a hotfix, Microsoft now also works with the Known Issue Rollback (KIR) function. This means that an error can be fixed without an update.

The KIR function is included in every non-safety-relevant update that contains new functions. In the meantime, this function has also been expanded to include the OS kernel (kernel mode) and boot loader. The purpose of this function is that you can react quickly to an error without providing an update first.

Each new function is assigned an ID. We know it from the ViVeTool . If a function is still hidden, you can activate it with the ID and use it. It is similar with the known issue rollback.

If problems are sent automatically via the diagnostic data, these are evaluated. If it turns out that there is a problem on several (many) computers, this new function can be deactivated on the server side using the ID via the activated Windows Update or Windows Update for Business and takes effect after a restart.

“Today fixes are enabled by default in our monthly updates - that is, the old code is disabled and the new code is enabled. If a fix turns out to have a serious problem, Azure Hosted Services and Windows work together to update this policy setting on the device and disable the problematic fix. "

This also benefits those who install the update a little later, for example. If Microsoft has discovered the error in the meantime and provided a known issue rollback, the user installs the faulty update, but the correction does not give the user the information because the ID has already been deactivated or the ID has been corrected to the old version.

In the next cumulative update, the error can then be corrected and the relevant ID reactivated so that the new or improved function can be used.

“We have been using Known Issue Rollback since late 2019 to include non-security fixes. Today, around 80% of the fixes that ship on Windows 10 Version 2004 (and later versions) are contained with Known Issue Rollback. As with most problem mitigation measures, the real value of Known Issue Rollback isn't shown until you need it and it works! "

So it makes perfect sense to transmit the diagnostic data and not to block Windows Update either. Even if there are always opponents who don't trust the whole thing. In the settings you have the option to choose whether you want to send the simple diagnostic data (required diagnostic data) or the extended (optional diagnostic data) insiders must have activated them. Windows Update also offers the option of installing updates with a delay. "