Windows 11’s August 2026 cumulative update is now drawing attention for an issue that matters to gamers, help desks, and anyone supporting enthusiast PCs. Windows Latest reports that KB5121003, a mandatory security update for Windows 11 version 24H2 and 25H2, has been linked to crashes in some games after installation. The most visible reports involve ARC Raiders and The Finals, with developer Embark acknowledging a crash connected to a Windows update and pointing affected players toward a temporary workaround.
This does not mean every Windows 11 system should avoid the August update. KB5121003 is a security release, and Windows Latest notes that it addresses a very large set of fixes. But the reports are specific enough that IT teams, managed service providers, and power users should treat gaming rigs and workstations with gaming peripherals as a watch list group for the next few days.
What is being reported
According to Windows Latest, KB5121003 was released on August 11, 2026 and moves Windows 11 PCs to build 26100.9168 on version 24H2 and build 26200.9168 on version 25H2. Microsoft’s official release notes reportedly do not list known issues for this update, and Windows Latest says its own test systems have not reproduced major problems.
The concern comes from user reports and a statement from Embark, the studio behind ARC Raiders and The Finals. Some players say games that worked normally before the update began crashing afterward. Reported symptoms include game-thread hangs, access violation errors, unexpected game exits, and in some cases full system reboots while playing.
Windows Latest also separates this behavior from another August update observation: some systems may reboot multiple times during installation because of Secure Boot certificate changes. That installation-time reboot pattern is different from a crash or reboot that happens later during gameplay.
The suspected driver: inpoutx64.sys
The most actionable detail is the possible link to a third-party kernel-level driver called inpoutx64.sys. Windows Latest says Embark identified the crash as related to this file and shared a workaround that stops and removes the associated service and driver file. Some users have also connected the driver to hardware utility software, including at least one report involving a Razer update tool.
In practical terms, inpoutx64.sys is the inpoutx64.sys risk marker administrators should look for when triaging affected Windows 11 gaming systems. Kernel-level drivers sit close to the operating system, so compatibility changes in Windows can expose problems that ordinary applications never hit. If a game, anti-cheat component, RGB controller, fan utility, overclocking tool, or peripheral updater depends on a low-level driver, a security update can sometimes change timing, policy, or access behavior enough to trigger crashes.
That does not automatically make the driver malicious, and it does not prove Microsoft made an error. It means there is a compatibility chain involving Windows, a driver, and software that loads or depends on that driver. Until Microsoft, Embark, or the vendor responsible for the driver publishes more detail, support teams should avoid over-generalizing the issue.
Recommended steps for affected users
If a Windows 11 PC starts crashing in ARC Raiders, The Finals, or another game immediately after KB5121003, start with evidence rather than a blind rollback. Confirm the installed build under Settings, System, About. Check Reliability Monitor and Event Viewer for application crashes, bug checks, driver names, or access violation entries around the time of the failure. If inpoutx64.sys appears in crash details or driver lists, the workaround reported by Windows Latest becomes more relevant.
Embark’s workaround, as quoted by Windows Latest, involves opening an elevated Command Prompt, stopping the inpoutx64 service, deleting that service, and then removing inpoutx64.sys from the Windows drivers folder. That is a significant change to a system driver, so it should be done only when the machine is actually affected and ideally after creating a restore point or backup. In managed environments, make sure you understand which utility installed the driver before removing it, because that tool may stop working or may reinstall the driver later.
For home users, an easier first step may be to update or temporarily uninstall recent peripheral utilities, RGB tools, hardware monitoring packages, or vendor update helpers. Then reboot and test the affected game. If the system is stable, reinstall those tools only from the vendor’s current installer and watch for whether inpoutx64.sys returns.
Should you uninstall KB5121003?
Uninstalling the cumulative update may restore gameplay for some users, and Windows Latest says several affected people reported success after removing KB5121003. However, rollback should be a last resort because this is a security update. On personal gaming PCs, a short rollback may be acceptable if the system is otherwise unusable and the user understands the risk. On business machines, shared devices, or systems exposed to sensitive data, removing a security update should go through normal change control.
A better operational approach is to isolate the affected population. If only a small number of gaming or workstation PCs crash, investigate the third-party driver path first. If crashes are widespread across a fleet, pause additional rollout rings, collect logs, and monitor Microsoft’s Windows release health information and vendor channels for confirmation.
What IT teams should monitor next
Watch for three follow-up signals: a Microsoft known-issue entry, a game-side hotfix from Embark or other studios, and updates from peripheral or utility vendors whose software installs inpoutx64.sys or similar low-level drivers. Also pay attention to early reports of refresh-rate drops, HDR behavior changes, black screens, and anti-cheat crashes after the same cumulative update. Those reports may or may not share the same root cause, but they are useful for help-desk intake.
For now, KB5121003 remains an important Windows 11 security update with a compatibility concern that appears limited but disruptive. The safest message to users is simple: install security updates, but if games begin crashing after this release, collect evidence, check for inpoutx64.sys, update hardware utilities, and only then consider rollback or driver removal.
Source: Windows Latest source