Microsoft Keeps Breaking PC Gaming and Calling It a Fix

Microsoft's August Patch Tuesday update broke PC games. Their fix broke other things. Then September's patch broke even more. At some point you have to stop calling these growing pains and start calling them what they are: a company that can't ship a stable update to save its life.

It started on August 11 with KB5121003, a mandatory security update that patched over 400 vulnerabilities. Sounds great on paper. In practice, it cratered ARC Raiders, The Finals, and Marvel Tōkon for a significant chunk of PC players. Crashes, instability, the kind of stuff that makes you alt-F4 your whole evening. Embark Studios, the developers behind ARC Raiders, actually did the legwork and publicly identified the problem: a low-level driver file called inpoutx64.sys that got altered by the update. A game studio diagnosed the issue while the platform holder sat on its hands for over a week before even acknowledging it.

Microsoft's "permanent fix" landed on August 26. Their solution? Auto-disable the inpoutx64 driver entirely. That stopped the game crashes, sure. It also killed RGB software and hardware-monitoring tools that depend on that same driver to read and write to hardware registers. So their answer to breaking your games was to break your peripherals instead. The same KB5121003 update also took out Microsoft Teams and Outlook on ARM devices like the Surface Pro 11 and Surface Laptop 7. That didn't get resolved until September's patch. Which brings us to the next disaster.

September Made It Worse

KB5124008 dropped on September 8. Nearly 1,000 CVEs patched. Microsoft had just warned users not to delay updates. Days later, they admitted the update was breaking multiple features.

Remote Desktop sessions started failing after a few minutes or getting stuck at the "Please wait for the Remote Desktop Configuration" screen. Windows Subsystem for Linux stopped working. And in a move that would be funny if it weren't so pathetic, the update broke Claude Cowork by changing the Plan9 filesystem-sharing implementation in Hyper-V. Anthropic publicly blamed Microsoft for the breakage before Microsoft even acknowledged it. A pattern is forming here: third parties diagnosing problems faster than the company that caused them.

USB Audio 1.0 devices stopped producing sound entirely, throwing "This device cannot start (Code 10)" errors. Microsoft's timeline for that fix? Maybe October. And the cherry on top: the earlier KB5120998 preview update was released specifically to fix a bug from a previous update that randomly changed your mouse cursor size. Patches fixing patches fixing patches.

Microsoft pushed an emergency update (KB5129195) on September 14 to clean up the mess. It fixed the RDP and Claude Cowork issues. It did not fix the audio problems. It did not fix AMD GPU errors. Six days to release a partial band-aid for their own mandatory patch.

The Numbers Don't Lie

Look at the CVE counts for 2026 Patch Tuesdays:

• April: 163 CVEs. Called the second biggest Patch Tuesday ever at the time.

• June: 206 CVEs. Broke that record immediately. Largest single security update in the program's 23-year history.

• August: 400+ CVEs.

• September: 963 CVEs. 726 of those were Windows patches alone.

2026 is on pace to blow past 1,000+ CVEs annually as the new normal. That's not a flex. That's a codebase hemorrhaging vulnerabilities faster than any QA process can keep up with. More patches per cycle means less testing per patch. That's not speculation, that's math. And PC gamers are the ones eating the consequences every single month.

The Real Problem

When you control the operating system, you own what your updates do to it. You don't get to break someone else's product and then shrug while a game studio or Anthropic does your diagnostic work for you. You don't get to warn people not to delay updates and then admit days later that the update you told them to install is broken.

PC gaming has always been a moving target. That's part of the deal. But the platform holder actively making it worse on a monthly cycle, with no rapid response framework and no accountability when things go sideways, is a different conversation. This isn't an edge case or a quirk. It's a pattern. August broke games. The fix broke peripherals. September broke Remote Desktop, WSL, audio devices, and third-party AI tools. The emergency fix only partially worked. And October is right around the corner.

Give Me the Finished Product

I'll be honest. I don't like Windows. I hate updates. I came up in a generation where you got the final product on a disc, and that was it. The game was done. It worked. You put it in, you played it. The last time an update actually made me happy was when Madden started doing live roster updates. I remember loading it up, bumping Ludacris, checking to see who got traded. That was a good update. That added something.

Everything since then has been a slow slide into "we'll fix it later" culture. Updates aren't a feature. They're a crutch for unfinished work. Ship me the finished game. Ship me the finished operating system. Stop treating my PC like a beta test environment you push broken code to every month and then take a week to acknowledge when it blows up. I don't want your patches. I want a product that works when I buy it.

That goes for Microsoft, and it goes for every studio hiding behind day-one patches and "live service" roadmaps. Finish the work before you ship it. That used to be the standard. Now it's a fantasy. And this whole mess, August through September, patches breaking patches breaking patches, is exactly what happens when that standard dies.