24H2 crashing games - working on a fix?

It seems it has been to long at this point to remove the update. Im not getting the option to uninstall anymore.

You owe me big time like money, this updated **** my pc, i cant play call of duty, at work wow, what a **** rool out, man the ammout of thing that have gremlins now.

So, how do i get money of you for killing my gaming pc, the time it toke me to rebuild the games lib, also i dont want to turn off updates or roll back anything and most these fixes are hack jobs by amtures, which is supper dangrorouse. This kind of advice is **** and not part of the SL agrement.

So a poilit FU, and how do i get money back off you for the time i have wasted on your incomplete roll out.; Im serious, i want at least 2 days pay and my money back for COD6.

I want answers,

Same problem.
Still waiting for a fix.

I almost lost my mind. At the beginning of December, I upgraded my computer (new processor, motherboard, RAM). Of course, I reinstalled Windows – version 24H2. The first issues appeared with the drivers I downloaded from the manufacturer's website (ASUS ROG Strix). After installing the audio driver, the power button became sluggish, taking two seconds to display options after clicking. I uninstalled the driver and resigned myself to using only what Windows installs by default.

Then came unpleasant surprises—not daily, but still frequent. The main issue was that my game (BF 2042) would simply close in the middle of playing. This escalated, and one day, my computer rebooted during gameplay. The same thing happened a few more times that day. I was already in a bad mood, disappointed with the new hardware, and started troubleshooting. Based on the logs in Event Viewer, it seemed to be a hardware issue – Event ID 41: "The system has rebooted without cleanly shutting down first."

Thus began a painstaking process of checking components: RAM, GPU stress tests, CPU, replacing the SSD. Just as I was about to buy a new power supply, I stumbled across reports online about users facing numerous issues with 24H2. I decided to give it a try. With some difficulty, I found a 23H2 image and reinstalled Windows 11. During driver installation, there were no issues—the manufacturer's audio driver worked without causing problems, and so far, Event ID 41 has not reappeared.

I can’t imagine how less tech-savvy users, who don’t know how to approach debugging, deal with this—they likely end up with a non-functional computer and costly repair bills.

So, Microsoft, please get your **** together and fix these bugs already.

It is concerning they have not addressed the issue yet; to me, the silence makes it look like they have come to the realisation they broke everything and 'fixing' it will be a long process for a distant future and are too stubborn to recall 24H2. The timing couldn't have been worse to push out a game-breaking update for Christmas, and then send their engineers off on holidays.