Microsoft linked a specific Windows 11 gaming incident after the KB5121003 update to RGB-enabled peripherals or internal components using drivers or code components similar to inpoutx64. The reported failures affected Windows 11 24H2 and 25H2, causing some games to freeze, close unexpectedly, display EXCEPTION_ACCESS_VIOLATION, or restart the computer. Microsoft now lists a driver-block resolution—but this is not evidence that every Windows 11 25H2 issue is caused by RGB software.
What happened after KB5121003
KB5121003 was released on August 11, 2026, for Windows 11 24H2 and 25H2. After the update, Microsoft received reports that some games could not run as expected. The common factor it identified was RGB-enabled hardware paired with a low-level driver or code component whose name resembled inpoutx64.
That distinction matters. RGB lighting itself is not established as the universal culprit, and the incident does not turn every crash, slowdown or failed installation into the same bug. It describes a particular interaction between certain hardware-control components, their driver behavior and affected games.
The symptoms were serious enough to include:
- Games freezing or closing without warning.
- EXCEPTION_ACCESS_VIOLATION errors.
- The entire system restarting.
- Games failing to launch as expected.
To check whether a PC is running the relevant release, open Settings > System > About and look under Windows specifications. The version should be listed as 25H2. That confirms the operating-system version; it does not, by itself, prove that a crash is related to inpoutx64.
Why RGB software and inpoutx64 are involved
RGB-control software often needs a driver to communicate with lighting hardware or other internal components. In this case, Microsoft connected the reported gaming failures to components using drivers or code with names similar to inpoutx64; the specific file discussed in the troubleshooting material is inpoutx64.sys.
This is a low-level relationship, which helps explain why the symptoms can extend beyond a lighting effect. When a driver operates close to the operating system, an incompatibility can affect a game or trigger a broader failure. That does not establish that every RGB application or every device using RGB lighting is affected.
Is anti-cheat software the confirmed cause? No. An interaction between anti-cheat software and a low-level RGB driver has been raised as a plausible technical explanation, but Microsoft has not confirmed it as the root cause. Treat that idea as a hypothesis, not as a diagnosis.
Which games and systems are in scope
Microsoft named ARC Raiders, MARVEL Tōkon: Fighting Souls and THE FINALS in reports about the incident. That is a list of named games, not a guarantee that no other title can be affected.
The incident also involved both Windows 11 24H2 and Windows 11 25H2. The supplied evidence associates the reported update state with build 26100.9168 on 24H2 and 26200.9168 on 25H2, but those build mappings are not presented as Microsoft’s own finding about the cause.
For a player, the useful pattern is narrower: a crash that began after KB5121003, especially alongside RGB-control software or hardware, fits the documented incident more closely than a random installation error or a general performance complaint. It still does not prove the driver is responsible.
What Microsoft’s resolution changes
Microsoft lists the RGB-related gaming issue as resolved through a block that prevents the inpoutx64 driver from loading on affected devices. The stated goal is to let affected games launch normally without requiring every user to edit the Registry or delete driver files.
The rollout was staged. Microsoft described expansion by device and game, and enterprise-managed PCs may not receive the same automatic action without administrator involvement. Coverage for MARVEL Tōkon: Fighting Souls and any additional games should therefore not be assumed from the named-game list alone.
That is the practical takeaway: a resolution exists in Microsoft’s release-health status, but its behavior can depend on the device, management method and rollout stage. If Windows requests a restart after applying the relevant protection, restart before attempting more invasive troubleshooting.
What affected players should do
If your symptoms match the documented pattern, use a cautious order of operations:
- Identify the timing. Check whether the failures began after KB5121003 and whether the PC is running Windows 11 24H2 or 25H2.
- Check the official resolution state. Look for the Microsoft driver block and any pending restart or Windows Update action before changing system files.
- Check RGB-related software and hardware. Note which lighting, monitoring or peripheral-control tools are installed. Do not assume that a familiar vendor is automatically responsible.
- Use manual changes only when they match the current official guidance. Microsoft documented a Registry-based mitigation, while Embark Studios separately published a more invasive procedure for affected players of THE FINALS. These are distinct approaches, not interchangeable universal fixes.
- Expect side effects. Disabling or removing the driver can stop RGB lighting, monitoring tools or other software that depends on it. Back up the Registry before any Registry change, and do not delete inpoutx64.sys simply because the filename appears on the system.
The less invasive path is preferable when it applies because disabling a service is easier to reverse than removing a driver and its service. Embark Studios’ procedure is specifically associated with THE FINALS troubleshooting and should not be treated as Microsoft’s general recommendation for every Windows 11 game.
What this does—and does not—say about Windows 11 25H2
The documented RGB incident is only one part of the wider Windows 11 25H2 issue picture. Microsoft separately lists problems involving non-English mouse-customization settings, incorrect Microsoft Defender warnings, desktop backgrounds reverting to black, and Teams or the new Outlook failing to launch on some ARM devices.
Those issues do not share a single established cause with the KB5121003 gaming incident. Nor does the incident prove that Windows 11 25H2 is universally unstable—or universally trouble-free. User experiences vary with hardware, drivers, applications and update state, but broad complaints cannot replace the more specific Microsoft finding about inpoutx64-like components.
For gamers, the bottom line is straightforward: a post-KB5121003 crash alongside RGB-related software may fit a documented driver conflict, and Microsoft lists a driver-block resolution. Check the operating-system version and current Windows Update state first. Avoid deleting system drivers as a reflex, especially when the exact game, device and rollout coverage may differ.
