MONDAY · AUGUST 24 · 2026 Gaming news, honest reviews & cozy chaos ♥
Gaming news, honest reviews & cozy chaos
LATEST
HomeReviews & GearWindows 11 Update Crashes Games, and Microsoft Points at RGB Peripherals
Reviews & Gear
▶ NEWS · WINDOWS GAMING

Windows 11 Update Crashes Games, and Microsoft Points at RGB Peripherals

A recent Windows 11 update is causing forced crashes, freezes, and restarts when users launch games. Microsoft says RGB peripheral drivers are to blame and offers a registry workaround that may break your lighting software.

By Mia Chen · Senior Editor: News & Hardware · August 23, 2026 3 min read

A Windows Update Broke Games, and RGB Lights Are Getting the Blame

If your PC has been crashing the moment you launch a game lately, you are not alone, and the culprit turns out to be something most gamers have scattered all over their desks. Microsoft has identified RGB peripherals and internally lit components as the source of a serious Windows 11 update bug that has been forcing crashes, freezes, errors, and unexpected restarts for affected users.

The story starts with a Windows 11 update that TechPowerUp had previously flagged as responsible for the disruptive behavior. Microsoft initially acknowledged the problem and said it was investigating. Now the investigation has an answer, even if it does not yet have a clean solution.

According to an update published by Microsoft and reported by TechPowerUp, the company determined that devices with RGB lighting features, whether peripherals like keyboards and mice or internal motherboard components, often install drivers or code elements using file names similar to “inpoutx64.” On systems where those drivers are present, launching certain games is enough to trigger the issue.

The Fix Is a Registry Edit With Its Own Consequences

Microsoft’s current recommendation is to manually disable the inpoutx64 driver through the Windows Registry. The company has published instructions in a blog update, but it is not exactly the kind of one-click patch most users hope to see after a critical bug disclosure.

Worse, Microsoft is upfront that its own suggested workaround carries real risk. The company states that disabling the driver “can result in unintended behavior, such as issues with RGB features on peripherals or components, or issues with the software used to control RGB features.” In other words, your keyboard lighting may stop responding, your motherboard’s LEDs may go dark, and whatever RGB management software you rely on may not function properly.

If disabling the driver causes problems, Microsoft says to just re-enable it. That puts users in a genuine bind: leave the driver active and risk game crashes, or kill it and lose RGB functionality until a proper fix arrives. Neither option is great for someone who spent real money on a gaming setup.

Who Is Actually at Fault Here

The comment section on TechPowerUp reflects the predictable debate. One user noted they had personally experienced this specific conflict, having to disable an HID device tied to motherboard RGB to get older games running. But another commenter pushed back on framing RGB peripheral makers as the primary villains, pointing out that these drivers were working fine before Microsoft’s update shipped. The argument is straightforward: if something worked before an update and does not work after, the update broke it.

That perspective carries weight. RGB driver software has a long and unpleasant reputation on Windows, with multiple vendors shipping low-level code that can conflict with system processes. But Microsoft’s update changed the equation on hardware that had previously been stable. Testing for that kind of regression is, in theory, part of what makes a major OS update trustworthy.

One commenter also raised an interesting thread worth watching: Microsoft had previously signaled it was working on native OS-level RGB integration, which would reduce the need for third-party drivers entirely. Whether that initiative is still alive or quietly shelved is unclear.

No Timeline on a Real Patch

Microsoft says it is working on a workaround but has not given users a timeline for when something more permanent will arrive. For now, PC gamers with RGB-heavy setups are stuck manually managing registry settings to get their systems stable, which is a frustrating ask for anyone who just wants to sit down and play.

The affected users span a wide range of hardware. RGB lighting has become so standard in gaming peripherals and components that the pool of potentially impacted systems is enormous. Keyboards, mice, headsets, motherboards, RAM sticks, GPU shrouds, and even cases with built-in lighting strips all fall into the category Microsoft described. If you have any of that gear and have been seeing unexpected crashes when launching games, the inpoutx64 driver is worth investigating before assuming the problem lies with the game itself.

FAQ
What is causing games to crash on Windows 11 after the recent update?

According to Microsoft, a recent Windows 11 update triggers crashes, freezes, and forced restarts when certain games are launched on systems running drivers related to RGB peripherals or components, particularly those with file names similar to inpoutx64.

How can I fix the Windows 11 game crash caused by RGB drivers?

Microsoft recommends disabling the inpoutx64 driver through the Windows Registry. However, the company warns this can break RGB lighting features and related software, and there is currently no permanent fix available.

Will disabling the RGB driver permanently fix the issue?

No. Disabling the driver is a temporary workaround, not a real fix. Microsoft acknowledges it can cause unintended behavior with RGB features and recommends re-enabling it if problems arise, while the company says it continues working on a proper solution.