Microsoft has begun pushing a permanent Windows 11 inpoutx64 driver fix to consumer and business devices, targeting a bug that has been causing system crashes, blue screens, and game launch failures on machines running Windows 11 24H2 and 25H2. The culprit, it turns out, is not a rogue game update or a misconfigured graphics stack, it’s the humble RGB lighting driver.
How the Windows 11 inpoutx64 driver fix works
The fix, which began propagating on 26 August 2026 at 6 PM PT, works by blocking the inpoutx64.sys driver from loading on affected systems. According to Microsoft’s Windows release health update, the block specifically targets devices where the driver is enabled and the game ARC Raiders is installed. Once applied, a message window informs the user that the driver has been disabled, after which the game launches normally.
A system restart is required for the change to take effect, and Microsoft notes it may take up to 24 hours to reach all affected devices. The driver block will also be bundled into the September 2026 Windows security updates and future releases, so machines that miss the current rollout will pick it up in due course.
The root cause traces back to peripherals and internal components with RGB lighting features. As Stellar Info reported, the crashes and BSoDs (blue screens of death) began appearing after the 11 August 2026 KB5121003 update. Microsoft’s own investigation initially pointed fingers at that update before the company identified the real problem: RGB-capable peripherals that install drivers or code components with file names similar to inpoutx64. ‘Such devices may install drivers or code components with file names similar to inpoutx64,’ Microsoft noted. ‘In systems where these drivers are found, the issue is then triggered by launching certain games.’
The affected titles include ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals, a fairly eclectic mix, but the common thread is that launching any of them on a compromised system could produce an EXCEPTION_ACCESS_VIOLATION error, a freeze, or an outright crash to desktop.
Enterprise workaround for IT-managed devices
The automatic fix will not propagate to devices managed by IT departments, so Microsoft has published a manual workaround for enterprise environments. Administrators need to disable the inpoutx64 driver via the Windows Registry: navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64, locate the Start value, and set it to 4. A restart follows. Microsoft is emphatic that a registry backup should be taken first, in case the change needs to be reversed.
‘Ongoing investigation does not indicate that disabling this registry key can result in unintended behavior,’ the company added. ‘If you want to re-enable the driver, you may do so by restoring the registry key to its previous value.’ The instructions are available through Microsoft Support alongside the broader Windows release health update.
It is worth noting that the enterprise manual fix is explicitly temporary. Once the September 2026 security update ships, managed devices will receive the driver block through the normal patching channel, removing the need for the registry edit.
A familiar pattern for Windows gaming compatibility
This is not the first time Microsoft has had to intervene to keep games running after a Windows update. The company has previously removed upgrade blocks that were preventing players of Star Wars Outlaws, Assassin’s Creed, Avatar: Frontiers of Pandora, and Asphalt 8: Airborne from moving to newer versions of the OS. In January 2025, Microsoft lifted a separate compatibility hold after resolving a bug in the Auto HDR feature that was breaking certain games on Windows 11 24H2 devices.
The pattern here is consistent: an update ships, something breaks for a subset of hardware configurations, and Microsoft works through the investigation cycle before issuing a targeted block or patch. The RGB driver episode is a fairly neat illustration of how third-party peripheral software (often installed silently and updated infrequently) can sit quietly on a system until a Windows change exposes an interaction nobody tested for. For anyone still seeing crashes, the 24-hour rollout window means the fix should arrive automatically before the week is out.
