Microsoft Investigating Windows 11 KB5121003 After It Breaks Popular PC Games
Microsoft is officially investigating reports that its August 2026 cumulative update for Windows 11, known as KB5121003, is causing significant problems for PC gamers. Released on August 11 as part of the monthly Patch Tuesday security roll-out, the update was designed to address more than 400 vulnerabilities. Instead, it has left many players dealing with sudden crashes, freezes, error messages, and even unexpected system reboots while trying to play certain titles.
The update advances Windows 11 version 25H2 to build 26200.9168 and version 24H2 to build 26100.9168. On paper, it delivers important security improvements, including updates related to Secure Boot certificates and other hardening measures. In practice, a growing number of gamers discovered that several games that worked fine before the patch suddenly became unstable.
Confirmed Affected Games and Symptoms
The most widely reported problems involve three titles: ARC Raiders, The Finals, and MARVEL Tōkon: Fighting Souls. ARC Raiders and The Finals are both developed by Embark Studios, which has publicly acknowledged the issue. Players of these games began experiencing crashes shortly after installing KB5121003. Common symptoms include the game becoming unresponsive, closing without warning, displaying the error “EXCEPTION_ACCESS_VIOLATION,” or causing the entire PC to restart unexpectedly. Some users have also reported GameThread hang detections and, in certain cases, black screens or performance drops.
While Microsoft has only formally listed these three games so far, community reports suggest other titles and even some anti-cheat systems may be affected on a smaller scale. The problems appear limited to systems running the updated 24H2 and 25H2 builds. Users who have not yet installed the update or who remain on earlier builds have largely avoided the issue.
The Technical Culprit: A Third-Party Driver Conflict
The root cause is not a bug in the games themselves. Embark Studios traced the crashes to a third-party kernel-level driver called inpoutx64.sys. This driver is commonly installed by certain hardware utilities, including some Razer software and other tools that require low-level port access. According to Embark, the Windows update changed something in the operating system’s handling of this driver, breaking compatibility.
Technical discussions on forums and Reddit point to tighter kernel handle validation introduced or enforced by the update. These changes improve security by making it harder for poorly behaved code to access restricted system resources. However, they also expose older or less carefully written third-party drivers that previously relied on more lenient behavior. When a game or related software interacts with the now-problematic driver, the result is often an access violation that crashes the application or forces a system restart.
This is a classic example of the tension between security hardening and backward compatibility. Microsoft’s changes close potential attack surfaces, but they can disrupt software that was never designed for the stricter environment.
Microsoft’s Official Response
After roughly a week of user complaints and developer statements, Microsoft acknowledged the problem. In a statement posted on its Windows release health dashboard, the company said: “Following the release of Windows updates on August 11, 2026 (KB5121003) and later, Microsoft received reports of issues involving inability to run games as expected. We are presently investigating to determine if this is an issue caused by Microsoft. We will provide an update when more information is available.”
Notably, the official support page for KB5121003 itself still lists no known issues at the time of writing. Microsoft has not yet confirmed whether the problem originates in its own code or solely in the interaction with third-party components. The company is collecting diagnostic data through the Feedback Hub and working to identify the precise trigger.
Workarounds Available Now
While waiting for an official fix, affected users have practical options.
The cleanest temporary solution for many is to remove the problematic driver without uninstalling the entire Windows update. Embark recommends opening an elevated Command Prompt (run as administrator) and entering the following commands one at a time:
sc stop inpoutx64
sc delete inpoutx64
Afterward, users should navigate to C:\Windows\System32\drivers and delete the file inpoutx64.sys if it remains. This approach keeps the security patches in place while restoring game stability for many players.
The alternative is to uninstall KB5121003 entirely. Users can do this by going to Settings → Windows Update → Update history → Uninstall updates, selecting the August update, and restarting. This restores game functionality but removes the security fixes that addressed hundreds of vulnerabilities, including some that were already being exploited. For that reason, most experts advise against long-term use of this method unless gaming is the absolute priority and the system is otherwise well protected.
Other temporary measures include pausing Windows updates for a short period so the system does not automatically reinstall the patch, and ensuring graphics drivers are fully up to date. Some players have reported partial relief after installing the latest NVIDIA or AMD drivers, though this does not resolve the underlying driver conflict.
Broader Context and What Comes Next
This is far from the first time a Windows security update has disrupted gaming. Microsoft has a long history of occasional compatibility regressions after major patches, particularly when kernel-level changes are involved. The fact that a popular third-party driver is at the center of the current problem underscores how dependent modern gaming systems are on a complex ecosystem of hardware utilities, RGB software, monitoring tools, and anti-cheat drivers.
Embark is working on a longer-term fix for its own titles and has stated it hopes to deploy one soon. Microsoft’s investigation will determine whether a Windows-side change is needed or whether the resolution will primarily come from updated third-party drivers. In previous similar cases, Microsoft has either issued an out-of-band fix or included a resolution in the following month’s cumulative update.
For now, the practical advice is straightforward. If your games are running normally, there is no urgent need to take action. If you are experiencing crashes in the affected titles, the driver removal method is generally preferable to uninstalling the entire update. Users who rely heavily on the hardware utilities that install inpoutx64.sys should check for software updates from those vendors, as they may eventually release compatible versions of the driver.
Security remains important. KB5121003 closed a large number of vulnerabilities, including critical ones. Leaving the system unpatched for an extended period carries its own risks. The ideal outcome is a targeted Microsoft fix or updated third-party drivers that restore compatibility without sacrificing the security gains.
Gamers who encounter the problem are encouraged to submit detailed reports through the Windows Feedback Hub so Microsoft’s engineers have as much diagnostic information as possible. In the meantime, the combination of developer workarounds and Microsoft’s active investigation offers a path toward resolution, even if the current situation remains frustrating for those caught in the middle of another Windows update compatibility headache.
About The Author
