Horrendous issues since installing Windows 10 21H1 update?

[JasonB]

Does this ring true for anyone else? Not just in SteamVR, but in other non-VR games as well. I heard Microsoft broke something related to power management and it makes GPUs want to go nighty-night constantly.

I'm desperate to find out if anyone else thinks this may be affecting them.

[artimid]

I HAVE had issues in the last week or two (only with VR), but I don't know if it's related to 21H1 *let me look into this, I thought I had this for a while since I'm usually on early release, but I forgot I recently reset my system for testing. I got KB5004237 a few weeks ago that was a cumulative update... let me see if I can remove this and check things.

As far as power management: And I've actually had the opposite problem. I got called somewhere and didn't get back for the night, found out my monitors kept a still image on the screen and never went to sleep. I was really worried about burn-in but got lucky.

So in my case, some things haven't been going to sleep even when they should, not really the opposite. But for the last little bit, I've been having constant issues with SteamVR not finding my headset, giving different errors, and requiring all sorts of hoops to jump through to get it to realize my headset was actually working. If it weren't for the fact that so many others are fine then I'd say it's the SteamVR update (since it all went downhill around that time). So that might seem like a GPU power thing, like it's turning off a Display Port or such, but I don't think that is really the case.

[JasonB]

Not sure. But my frame timing looks ballistic. Rapid spikes seemingly every other frame, causing a horrible stuttering effect. Nothing unusual is running and when I look at the task manager, my GPU and CPU are nowhere close to maxed out (I have a 3900X and 1660 Ti). This is just in SteamVR Home but it continues to occur even when I load up Boneworks or anything else.

https://pasteboard.co/Kf2cj2n.png

These kinds of issues seemed to only crop up once I got 21H1, and I've tried nearly everything - including desperately upgrading to Windows 11 (I don't know, I thought I could "push past" the issue) to make it go away. Today in particular, this just happens every single time I try to do anything in VR. At least yesterday I got a session of Boneworks in where this didn't happen at all.

[artimid]

I can't remove the updates. I'm wondering if the update removed the Index driver. They had an issue before where it removed something.

I'm only getting:
"Display 2: \\.\DISPLAY3 2880x1600 @ (-2880, 0) NVIDIA GeForce RTX 2080
Monitor 0: \\.\DISPLAY3\Monitor0 Generic PnP Monitor" as the driver now.

The headset works perfectly fine. If I remove it from Direct mode I can use it as a third monitor at full resolution (generic PnP monitor, though). And, in direct mode it registers movement and can enable the lighthouses if I point it at them. So the headset is fine and everything seems fine.

And if I launch Steam/SteamVR/VRserver/VRLaunch in admin mode enough times I can get it to work. As you an AMD then that rules out an nVidia issue of not passing data through.

And Index doesn't have individual drivers I can download.
Headset's USB hub is showing up with, what I assume, is the normal SMSC-Microchip WinUSB5734 Device. So I'm wondering if there is a break in how the drivers are being treated here.

[2⊛2]

Got much problems with update 21H1 too. So i did deinstalled it and set my windows-version to 20H2. forever or until i will undo the changes.

How to do that read here.

Go to the Windows-Registry and change the following entries. You will do that at your OWN RISK. Each changes in the registry can damage your system !!!

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows

and, if not available, create the new key "Windows Update

In

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

create the new DWORD entry

TargetReleaseVersion

and give this entry the value 1.

In addition, create the new "string" entry

TargetReleaseVersionInfo

and give it the version number at which Windows 10 should remain, e.g.

20H2
The AskWoody tip page also offers a direct reg download for this, which saves you the manual "fiddling around" in the Windows 10 registry.

Translated with www.DeepL.com/Translator (free version)

[artimid]

Unfortunately I can't remove 21H1 as it updated my SSU, so I can only reinstall to get rid of it.. even with DISM I can't seem to remove it.