The reported symptom was a process death: games failing to launch, or freezing with EXCEPTION_ACCESS_VIOLATION [2]. The published explanation stops at the trigger, per the Microsoft release health text quoted by BleepingComputer: driver present, game launched, process gone. What the driver does wrong, and which peripheral vendors are shipping the copy on a given machine, is not in Microsoft's statements [1].
There is also a gap between how Microsoft described the problem and what the fix actually covers. The description is a family. Microsoft said the issue relates to peripherals or internal components with RGB lighting features, which "may install drivers or code components with file names similar to inpoutx64," with the fault firing on certain game launches [5]. The block is narrow, conditioned on that specific driver being enabled and on ARC Raiders being installed [7]. Two of the three titles Microsoft originally named, MARVEL Tokon: Fighting Souls and The Finals [3], are not in the targeting condition, so an otherwise identical machine without ARC Raiders keeps loading the driver [17].
For the population Microsoft can reach directly the clock is short. Rollout opened at 6 PM PT on August 26, 2026, with a stated ceiling of 24 hours [10], which puts the last unmanaged device behind the block at roughly 6 PM PT on August 27 [16]; a restart applies it, and the same automatic path covers consumer and business devices alike as long as no IT department manages them [9]. Managed estates run on a different schedule, since the block rides the September 2026 security updates and later releases [11], and until then there is no automatic remediation for them at all [18].
The interim workaround is the ordinary way to keep a service from starting: set the Start value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64 to 4 and reboot, with a registry backup taken first [13]. Microsoft says its investigation does not indicate the change causes unintended behavior, and that restoring the previous value re-enables the driver [14]. That is the part worth weighing: one value, reversible, no dependency on the hardware vendor.
Microsoft's habit in game-breaking cases has been the compatibility hold, keeping machines off the new build until the title works. It did that for players of Star Wars Outlaws, Assassin's Creed, Avatar: Frontiers of Pandora and Asphalt 8: Airborne, and lifted another hold in January 2025 after fixing an Auto HDR bug that broke games on 24H2 [15]. This time the operating system stays where it is and the third-party driver stops loading [7]. The servicing channel carrying that block is indifferent to why a driver is unwanted. The reason logged here was a crash in a shooter.
