inpoutx64 driver

Winsage
August 28, 2026
Microsoft has begun rolling out a permanent solution to a system stability and gaming performance issue on Windows 11 devices, which has caused crashes, game launch failures, and freezing, often with the "EXCEPTIONACCESSVIOLATION" error message. The problem was linked to updates from August 2026 and was identified as being related to peripherals with RGB lighting features that installed disruptive drivers. Specifically, the inpoutx64.sys driver was found to be responsible for these disruptions. Microsoft is deploying a fix that disables this driver on affected systems, starting from August 26, 2026. This driver block will also be included in the September 2026 Windows security updates. For enterprise-managed devices, a temporary workaround involves manually disabling the inpoutx64 driver via the Windows Registry. Microsoft has assured users that this action should not cause unintended behavior and can be reversed.
Winsage
August 28, 2026
Microsoft has begun rolling out a permanent solution to a problem causing system crashes and gaming disruptions on Windows 11 devices, specifically related to game launch failures and freezing with "EXCEPTIONACCESSVIOLATION" errors. The issue affects various games, including ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals, particularly on Windows 11 versions 24H2 and 25H2, and is linked to peripherals with built-in RGB lighting. The inpoutx64.sys driver has been identified as the cause of these complications. Microsoft is deploying a fix that disables this driver on affected devices, starting on August 26, 2026, and it may take up to 24 hours to reach all impacted devices. This driver block will also be included in the September 2026 Windows security updates. For enterprise-managed devices that do not automatically receive the fix, a temporary workaround involves disabling the inpoutx64 driver via the Windows Registry. Microsoft has stated that disabling this registry key should not lead to unintended behavior.
Winsage
August 28, 2026
Late last week, reports emerged about gameplay disruptions linked to the Windows 11 August update, causing issues like forced crashes, unexpected freezing, and device restarts. Microsoft identified the interaction between gaming applications and RGB peripherals as the cause. They released a workaround involving a registry modification to prevent the inpoutx64 driver from loading, which resolved the issue temporarily. This workaround specifically targets devices with the inpoutx64 driver enabled and the game ARC Raiders installed. Users can disable the driver by modifying the registry key HKEYLOCALMACHINESYSTEMCurrentControlSetServicesinpoutx64, changing the Start value to 4, and restarting the computer. Microsoft is also working to block RGB peripherals for the game MARVEL Tōkon: Fighting Souls and has addressed similar issues for THE FINALS. The driver block will be included in the September 2026 Windows security updates and future releases.
Winsage
August 27, 2026
Microsoft addressed printing issues and gaming-related complications linked to recent .NET Patch Tuesday updates. The problems were associated with RGB applications and the inpoutx64 system driver, which caused compatibility issues when certain games were launched. Microsoft has implemented a block to prevent the inpoutx64 driver from loading on affected devices, specifically targeting systems with the driver enabled and ARC Raiders installed. Users will receive a notification after the block is implemented, and the game should launch without further issues. The block is also being extended to systems running MARVEL Tōkon: Fighting Souls, while the issue with THE FINALS has been resolved. The resolution is being distributed automatically, and users need to restart their devices after the fix is applied. For enterprise-managed devices, IT administrators must manually apply the fix. Microsoft provided a temporary workaround by suggesting users disable the inpoutx64 driver through the Windows Registry. Users can change the Start value in the Registry Editor to 4 to disable the driver and may need to restart their devices for changes to take effect. Users are advised to back up the Registry before making modifications, and they can restore the driver by reverting the Start value back to its original setting.
Search