Microsoft's game-crash bug is an inventory problem: nobody bought inpoutx64

The load-bearing word in Microsoft's dashboard entry is conditional: the fault appears in systems where these drivers are found ^[6]. Finding them is the entire exercise. No procurement process approved inpoutx64. It arrives with a keyboard, or with the utility that drives lighting on a component already inside the case, and it installs kernel-mode code and a service that nothing in the asset database records ^[6].

Microsoft also declined to commit to a filename. It said file names similar to inpoutx64 ^[6], which reads as a family rather than a single artifact, and which means a fleet-wide search on one exact string will come back cleaner than the fleet is.

Then the question of whose bug it is. Microsoft's position is that RGB peripherals and internal components install the code, that launching certain games triggers the fault, and that it is still working out the relationship between the two ^[6][7]. Embark Studios, which makes two of the three named titles, says the crash relates to inpoutx64.sys, that the file changed with KB5121003, and that the problem follows a change to the Windows kernel driver ^[8]. Those point in opposite directions, and while they stay unresolved there is no patch to wait for, only Embark's temporary instruction to delete the service and remove the file from the Windows drivers folder ^[9].

Consider what that instruction is, operationally. A game developer is telling consumers to hand-delete a kernel-mode driver from the drivers directory ^[9]. On a managed estate that is a removal script somebody has to write and test against machines whose internal lighting components depend on the same code ^[6]. On an unmanaged one it is users with local admin, following a studio's forum post.

The sequence deserves a note. Embark named the file on Monday; Microsoft's dashboard reached RGB components on Thursday, three days later ^[12]. Crash reports from a shooter established the presence of third-party kernel code on an unknown number of Windows 11 machines before the platform vendor's advisory did ^[12].

Nothing in Microsoft's entry says this driver is exploitable, and nothing in it says anyone has abused it. The dashboard is about freezes, access violations and unexpected restarts ^[4][6][7]. What it documents is distribution, which is the part an inventory team can act on. Some quantity of 24H2 and 25H2 machines are running a driver that arrived attached to a lighting effect, and the only reason anyone knows is that a game exercised it ^[3][6]. On endpoints where nobody launches ARC Raiders, there is no symptom, and the driver is still resident ^[3][6]. The useful artifact out of this week is a count of machines matching inpoutx64*, and most organisations cannot produce one.