400 Security Patches, One Driver File, and a Week of Crashing Games

Microsoft's August patch cycle (KB5121003) fixed over 400 security vulnerabilities across Windows 11 24H2 and 25H2. That's the headline you read in the release notes. The sub-headline is that a single driver file, inpoutx64.sys, appears to be conflicting with the update on some systems, causing games like ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals to freeze mid-match, throw EXCEPTION_ACCESS_VIOLATION errors, close without warning, or trigger unexpected system restarts at the worst possible moment. Embark Studios, the developer behind ARC Raiders, publicly flagged KB5121003 as the root cause on their channels before Microsoft even acknowledged the problem existed. It took roughly a week of user reports, studio pushback, and forum threads before the release health dashboard got an official "we are presently investigating" note on it. The silence was doing more damage than the crashes.

The practical situation for affected users is a genuine bind with no clean exit. You can delete the conflicting driver file or uninstall KB5121003 entirely, which restores your games to working order within minutes. But uninstalling the August patch means you're sitting exposed to 400-plus known vulnerabilities until the next cumulative update rolls out, and there's no surgical way to keep the security fixes and drop just the one component that's breaking your I/O driver stack. PCWorld notes that some users are also seeing corrupted Windows Hello PINs, broken HDR output, and black screens on AMD systems, which suggests the conflict isn't purely a gaming problem but a broader driver interaction issue that happens to be most visible in high-load GPU scenarios. The "pause updates for two weeks" workaround that circulates in forums is fine for a home PC where nobody's watching; it's not a strategy you can write into a change-management ticket.

Source article image
Source image 1

What's interesting from an operational standpoint is how this plays out beyond the gaming community. If you're running a fleet of Windows machines where gaming isn't the concern but application stability is, the same driver conflict could manifest as crashes in any workload that touches that I/O path, and you won't have a studio publicly naming your patch version as the culprit. The cumulative update model means every monthly drop is a big-bang change: 400 fixes in one package, with no granular rollback for individual components. When something goes wrong, your options are "revert everything"

Source article image
Source image 2
or "live with it," and neither is satisfying. Microsoft's release health dashboard is the only public signal that anything is broken, and the fact that it took a week to update says something about how much weight those notes carry in practice. The question nobody's answering yet is whether this is a one-off bad interaction or a recurring pattern in how cumulative updates package driver-level changes alongside security fixes.

Have you hit a patch conflict on a machine where you couldn't just uninstall the update and walk away? I'm curious whether anyone in a managed environment found a cleaner workaround than the delete-the-driver-and-pray approach, or whether you're stuck in the same revert-everything-or-nothing trap.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more