If ARC Raiders, MARVEL Tōkon: Fighting Souls, or THE FINALS suddenly started crashing after the latest Windows 11 security update, Microsoft now says the first place to look may be Windows itself. On Sunday, August 23, 2026, Microsoft’s official KB5121003 support page was still carrying a live known issue that says some systems can see those games become unresponsive, close without notice, throw EXCEPTION_ACCESS_VIOLATION, or even restart the device.
That matters because this does not read like a normal one-game patch problem. Microsoft is tying the issue to Windows 11 24H2 and 25H2, specifically KB5121003 on OS builds 26100.9168 and 26200.9168, while saying the current investigation points toward some RGB-related peripherals or internal components that may install drivers or software with file names similar to inpoutx64.
The useful change is simple: Microsoft has named the problem and named the games
The August 20 changelog entry on the KB page added a new known issue called “Reports of certain games becoming unresponsive.” That is already more useful than the usual vague Windows-update chatter, because Microsoft did not stop at generic symptoms. The company named ARC Raiders, MARVEL Tōkon: Fighting Souls, and THE FINALS directly in the report summary.
That does not mean every crash in those games comes from KB5121003. It does mean players now have a real official checkpoint before blaming a fresh game patch, anti-cheat update, or GPU driver on instinct.
This is bigger than one community because the affected list crosses three different PC audiences
The three named games do not sit in one narrow corner of Steam. At the same Sunday refresh, official Steam endpoints still showed 29,656 live players in ARC Raiders, 14,396 live players in THE FINALS, and 2,877 live players in MARVEL Tōkon: Fighting Souls.
That scale does not prove how widespread the Windows issue is. Microsoft still has not said how many systems are affected. What it does show is why the story is worth covering as platform news instead of treating it like a fringe support thread. The known issue touches a big extraction shooter, a live free-to-play arena shooter, and a newer paid fighting game. That is broad enough to hit normal PC players who would never connect those crashes to one Windows update on their own.
The RGB-driver detail matters, but it is not a license to turn this into a DIY fix guide
This is the line most coverage can mangle if it gets too eager. Microsoft’s wording says the issue is associated with certain peripherals or internal device components that support RGB lighting features and that these devices might install drivers or software with file names similar to inpoutx64.
That is useful triage context. It is not the same thing as Microsoft publishing a finished fix, a safe removal guide, or a claim that every inpoutx64 file on a PC is the culprit. The company is still telling affected users to submit a report through Feedback Hub, and the official page still says the investigation is ongoing.
So the practical read on Sunday is narrower and better: if one of these games started breaking right after KB5121003 on a Windows 11 machine that also uses RGB-control hardware or software, check the Microsoft known issue before you start tearing apart the game install.
What players should and should not take from this right now
The safe conclusion is that Microsoft has acknowledged a real compatibility problem and narrowed the current suspicion to a Windows update plus RGB-related component interaction. That is already enough to save players time and to keep blame from landing automatically on Embark, Arc System Works, or Embark’s other live-service work.
The unsafe conclusion would be anything broader than that.
Do not read this as proof that KB5121003 breaks all installs of the named games. Do not read it as proof that every crash in these communities has the same root cause. And do not read it as Microsoft quietly shipping a fix, because the company has not said that on the checked page.
The honest GameGuideDog call
Windows 11 KB5121003 is now a real PC-gaming story because Microsoft has stopped treating it like a vague support rumor. The company has a live known issue, a named affected-game list, a symptom list, and an active investigation. That is enough for a player-first analysis.
It is not enough for heroics. The best move right now is simple: if one of the named games started crashing after the August 11 update, treat the Windows known issue as a serious checkpoint, keep Microsoft’s Feedback Hub request in mind, and wait for the company to publish the next concrete update instead of guessing your way into riskier driver surgery.
For more GameGuideDog coverage, browse our gaming section, revisit the earlier ARC Raiders update 1.42 analysis, compare it with our MARVEL Tōkon launch analysis, or open the latest English stories.
