Computer is slow after Windows 11 22H2 update

Does this solution also handle the global slowdown problem?

After some further digging, I have discovered a solution to the VR issue. Some fine folks over at Flight Simulator Forums happened across a workaround that I can confirm works like a dream. It has something to do with performance monitoring within Windows.

Here's the solution for uncharacteristically poor VR framerates:

Right-click on your Start button and select "Computer Management". Go to System Tools → Performance → Data Collector Sets → Event Trace Sessions.

Look for the "HolographicShell" process, select it with a right click and choose "Stop".

Apparently, it's a bug that is causing an infinite loop. kind of like Windows is DDoSing your VR headset display.

This has been known for quite a while, so why Microsoft haven't addressed it with a hotfix is beyond me!

I hope this helps someone.

@Lhosson I agree with you fully, this is not the first time I experienced this from Microsoft but the worst one so far. Not only it had affected gaming but mostly productivity. I was causing alot of issues even with just intel graphics enabled. Working from home just sucked so bad with this build with wifi switching randomly off during team mettings that I had to revert back to using Windows 10 and hide Windows 11 upgrade entirely. This is really not fair for getting Windows 11 to work for a few months prior to the update. I had so much built into that system that I just gave up entirely and reverted back to the old system. Believe me rolling back after the update caused me alot more. Common MS what's the use of your insider program if you are going to release a buggy full build update???!!! As Bill Gates would say this is frkn unacceptable lol. I'm just glad I still had my old backup of Windows 10, it is always great to have one you will never know when MS starts going haywire heck even with Google search it slows down hahahahahhahahah. A few seconds after BSOD TT. Believe me when I say I tested this with multiple rigs with various builds and ending up the same. I mean this the first time a saw multiple BSODs in succession in my LIFETIMEEEE hahahaaaaaaaaahhhhhhh.

Good luck to those who can't revert back to Windows 10, hope rolling back to the previous build works for you.

For r hose of you who have reverted back to the previous build, I do not think you need to be concerned about security updates as they will continue to come forth even if you have blocked installation of the new builds. Please correct me if I’m wrong. Thanks.

May I recommend that you never allow automatic updates of anything but rather get notified and you can look at each update and decide whether or not you want to try it. In addition, you can use group policy editor to prevent even the suggestion of updated builds for as long as 365 days. In that way you can do your own research regarding the new build and you can choose of and when you want to install it.

I do try to follow that rule, but with my need to make sure regular Windows updates are installed for security issues etc. I sometimes don't pay close enough attention. On this occasion I accidentally clicked install on the 22h2 update at 3am when bleary eyed (not knowing of its issues). After I saw the degradation, I decided to do a fresh install of the previous build (my system needed a clean out). It was during that process that 22h2 forced itself into my installation while I was doing my updates. I was so irritated that I decided to just install a fresh version of 22h2 in the hope it would iron out any performance problems.

It didn't...

Suffice it to say, I don't want to go through the entire process again. It is what it is, I guess. Now I just need to wait patiently for fixes. That said, this is the first time a new build has bitten me so badly.

You're right though, I should have paid more attention and been stricter with my observations. Lesson learned ;)