The Finals crashes after KB5121003? Check this Windows driver first

The immediate priority is protecting a stable PC setup, not treating this as a new The Finals patch problem. KB5121003 is a Windows 11 security update released on August 11, 2026, and the crash pattern centers on a third-party kernel driver, inpoutx64.sys, rather than a universal failure affecting every Windows application.

How to identify the KB5121003 crash

The strongest match is a PC running Windows 11 24H2 build 26100.9168 or 25H2 build 26200.9168 that began freezing, silently closing games, throwing EXCEPTION_ACCESS_VIOLATION errors, or restarting unexpectedly after the August 11 update. Microsoft’s release-health pages list the issue as under investigation for both Windows versions, with reports covering games becoming unresponsive after KB5121003 and later updates.

1. Confirm that KB5121003 is installed. Open Settings > Windows Update > Update history and look specifically for KB5121003. If that update is not there, you are probably chasing a different crash.

2. Confirm the affected Windows build. Go to Settings > System > About and check whether you are on Windows 11 24H2 build 26100.9168 or 25H2 build 26200.9168. That build-and-update combo is the cleanest fingerprint for this issue.

3. Match the error signature, not just the vibes. Useful clues include a game window that becomes unresponsive, a crash to desktop, EXCEPTION_ACCESS_VIOLATION, Hang detected on GameThread, or an unexpected full restart after launch or during a match. If the game was fine before August 11 and started misbehaving right after the update, that timing matters.

   

4. Check whether inpoutx64.sys is on the machine. Look in C:\Windows\System32\drivers\ for inpoutx64.sys. You can also check whether the inpoutx64 service exists. The Finals and ARC Raiders are prominent examples, but the more useful diagnostic detail is whether your system actually has that driver installed.

That driver is commonly associated with older hardware-control, monitoring, fan-control, lighting, overlay, or similar utility software. In other words, this looks much more like a Windows-update-plus-driver collision than a blanket failure in The Finals itself.

Use the lower-risk workaround before rolling back Windows

Embark has identified inpoutx64.sys as the file involved in this Windows-update-triggered conflict and is working on a permanent fix. Start with the narrow fix first: identify which installed utility placed that driver on the system, then update, disable, or remove that utility through its supported uninstaller. Create a restore point before you touch a kernel driver so you have a clean escape hatch if the utility controls hardware features you still need.

5. Find the utility that owns the driver. Check recently installed hardware tools, monitoring apps, fan-control software, lighting suites, or similar utilities. Public troubleshooting around this driver has also mentioned tools like ZenTimings. If one of those apps lines up with the crashes, uninstalling or disabling that utility is usually cleaner than randomly editing game files.

   

6. If needed, disable the driver conflict directly. Advanced users can stop and remove the related service with sc stop inpoutx64 and sc delete inpoutx64, then remove inpoutx64.sys. Some troubleshooting steps also include cleaning up the registry entry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64. Restart the PC and retest the game.

7. Use rollback only as the fallback. Uninstalling KB5121003 may restore access for some affected players, but it removes the August security update instead of targeting the driver conflict directly. That is the big trade-off: rollback is broader, while driver removal is more targeted but riskier if you do not know which utility depends on it.

Here is the decision point: if you have confirmed KB5121003, matched the crash signature, checked for inpoutx64.sys, and either safely disabled the owning utility or removed the driver, do one clean retest. If The Finals still crashes, stop changing things and file a report through Feedback Hub with the game name, Windows version, OS build, exact error text, and whether the failure happens at launch, in menus, or during a match. That is more useful than endlessly swapping settings.

Microsoft had not published a fixed Windows build as of August 20, and its status remains under investigation for Windows 11 24H2 and 25H2. Until that changes, watch Windows Update and Embark’s support channels before re-enabling the conflicting utility or reinstalling KB5121003.