The Finals KB5121003 crash fix: disable inpoutx64 safely

The Finals KB5121003 fix: disable the driver, keep the security update

THE FINALS crashes tied to Windows 11 KB5121003 have a practical first fix: keep the August 11, 2026 security update installed, disable the inpoutx64 driver, restart the PC, and test multiplayer properly. Microsoft has linked the problem to RGB-enabled peripherals or internal RGB components that install drivers or software files resembling inpoutx64.

That matters because removing KB5121003 can restore game stability, but it also strips out August security fixes across Windows 11. Microsoft’s workaround goes after the low-level driver instead of the cumulative update. The trade-off is simple and annoying in exactly the way PC troubleshooting loves to be annoying: RGB lighting control, macros, or peripheral utility features may stop working until the relevant device software gets a compatible update.

For most affected players, that is still the better bargain. THE FINALS is an online multiplayer shooter, and a fix that preserves the security patch while stopping mid-match crashes is the cleanest path available right now. This guide keeps the process tight: confirm that KB5121003 and inpoutx64 are part of your setup, apply Microsoft’s reversible registry change first, and only move to Embark’s heavier cleanup method if the safer option does not hold.

KB5121003 crash issue at a glance

Item	What it means for THE FINALS players
Problem update	Windows 11 2026-08 Security Update, KB5121003, released August 11, 2026.
Affected Windows versions	Windows 11 24H2 and 25H2. KB5121003 is a mandatory cumulative security update delivered through Windows Update. Associated OS builds include 26100.9168 and 26200.9168.
Known symptoms	Game crashes, freezes, UE5 crash dialogs, EXCEPTION_ACCESS_VIOLATION, unexpected shutdowns, BSODs, and restarts during online play.
Games named in the known issue	THE FINALS, ARC Raiders, and MARVEL Tōkon: Fighting Souls.
Key trigger	A driver or software component named similarly to inpoutx64, including inpoutx64.sys, installed by certain RGB hardware stacks.
Microsoft’s preferred mitigation	Set the inpoutx64 driver service’s Start value to 4 in the registry, then restart Windows.

The important framing here is that Microsoft classifies this as a known issue tied to KB5121003 on Windows 11 24H2 and 25H2, not as a random one-off crash with no pattern. THE FINALS is the game most affected readers will care about, but the same basic fault line shows up in other multiplayer titles, which is a strong clue that the conflict sits lower in the Windows driver stack than in the game itself.

Confirm that KB5121003 and inpoutx64 are involved

Do these checks before touching the registry. A generic Unreal Engine 5 crash, a damaged game install, a GPU overclock, or an unstable RAM profile can also take down THE FINALS. This specific Windows issue has a recognizable pattern: KB5121003 is installed, inpoutx64 is present, and the game repeatedly fails during launch, map loading, matchmaking, or a live multiplayer match.

1. Open Settings → Windows Update → Update history → Installed updates. Confirm that 2026-08 Security Update (KB5121003) is installed.
2. Confirm the PC runs Windows 11 24H2 or 25H2. The builds associated with this update are 26100.9168 and 26200.9168.
3. Open File Explorer and check for C:\Windows\System32\drivers\inpoutx64.sys.
4. Open Registry Editor and check whether this service key exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64.
5. Launch THE FINALS and enter actual online matchmaking. Menu stability alone does not clear the issue; affected systems often fail when a match starts, a map loads, or online systems fully spin up.

Finding the file or service does not tell you which RGB product installed it. That is normal. A lot of enthusiast PCs run separate lighting utilities for a motherboard, RAM, GPU, fans, an AIO cooler, keyboard, mouse, and headset, and several of them can live deep enough in Windows to blur together once the trouble starts. The useful discriminator here is the actual inpoutx64 file or service entry, not the sheer amount of RGB in the room.

If KB5121003 is installed but inpoutx64.sys and the registry key are both missing, stop here and do not improvise registry edits. This guide is for the known inpoutx64-style conflict. Without that file or service present, you may be dealing with a different THE FINALS crash cause altogether, and changing unrelated services will only turn one problem into two.

A quick reality check also helps. If the game only crashed once, troubleshoot normally first. If it crashes several times in the same repeatable spot after KB5121003 landed, especially around multiplayer loading or mid-match, that is when the driver workaround becomes worth the hassle.

Use Microsoft’s reversible registry workaround first

Microsoft’s mitigation disables the driver while preserving the KB5121003 security update. It is the least invasive route and the best place to start for a PC that crashes in THE FINALS after the update.

1. Create a Windows System Restore point through Control Panel → System → System Protection → Create. Select the Windows system drive so you have a rollback point if something goes sideways.
2. Press Start, type regedit, and open Registry Editor with administrator rights.
3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64.
4. Select the inpoutx64 key, choose File → Export, and save a backup .reg file somewhere easy to find.
5. In the right pane, double-click Start, set Value data to 4, then confirm the change.
6. Restart Windows. The reboot is mandatory because it prevents the driver from loading with the new setting.

A Start value of 4 disables the driver. The file may still remain in C:\Windows\System32\drivers\, and that is expected with Microsoft’s method. The important part is that Windows no longer loads it at boot. This is why the registry workaround is cleaner than immediately deleting files: it changes startup behavior first and keeps the driver easy to restore if you need to undo the test.

After restarting, reopen Registry Editor and confirm that Start remains set to 4. RGB lighting may fall back to a default color, freeze on its last profile, or lose app-based controls. Custom macros and device features tied to that same low-level component can also stop working. That side effect is not elegant, but it is also the whole point of the test: if disabling the driver stabilizes THE FINALS, you have isolated the conflict without removing the security update.

Do not create the inpoutx64 key yourself if it does not already exist. Do not change other values in the service entry. Microsoft’s workaround is narrow on purpose. The safest way to use the registry is to make one reversible change, reboot, and test.

If you later want to undo the workaround, import the backup .reg file you exported before editing, or restore the previous Start value if you documented it. Then reboot again. In other words, treat the registry edit like a switch, not a magic ritual. Flip it, test, and only keep it if it fixes the actual problem.

Validate THE FINALS in real multiplayer conditions

A clean launch after the registry edit is encouraging, but it is not a full pass. KB5121003-related reports center on the jump from desktop to a live online session. Test the same pressure point where the crashes occurred before changing the driver.

• Launch THE FINALS and reach the main menu without a UE5 crash dialog or EXCEPTION_ACCESS_VIOLATION error.
• Enter matchmaking, load into a map, and finish at least three full multiplayer matches.
• Keep playing for one to two hours if the PC previously froze, rebooted, or blue-screened mid-session.
• Watch for game closures, desktop freezes, sudden restarts, and blue screens rather than judging the result only by frame rate or menu behavior.
• Players with ARC Raiders or MARVEL Tōkon: Fighting Souls can repeat the same test while KB5121003 remains installed.

This part matters more than people think. A lot of bad fixes look good for five minutes. The real win condition is boring in the best way: no crash on launch, no crash when matchmaking completes, no crash during the first map load, and no surprise reboot halfway through a session. If your old failure point was “the second match always dies,” then you need to get past that exact checkpoint before calling the workaround successful.

Login failures and graphical artifacts deserve separate troubleshooting if they remain after the driver change. The KB5121003 mitigation specifically addresses the crash, freeze, and restart pattern linked to the RGB driver component. It is not a universal cure for every weird thing a Windows game can do after an update.

Three ways to handle the problem

There are three workable paths, but they do not carry the same security risk or recovery effort. For most players, the middle option is the sensible one because it keeps the security update in place and changes the smallest possible thing.

Approach	Security impact	RGB and peripheral impact	Recovery effort	Best use
Uninstall KB5121003	Removes August 2026 Windows security fixes.	RGB tools and peripherals continue as before.	Reinstall the cumulative update through Windows Update.	A short diagnostic A/B test when confirming the update is part of the crash pattern.
Disable inpoutx64 with Start = 4	Keeps KB5121003 and its security fixes installed.	Lighting control, macros, or device software features may stop working.	Restore the previous Start value from the registry backup if required.	Microsoft’s preferred temporary mitigation.
Remove inpoutx64 using Embark’s method	Keeps KB5121003 and its security fixes installed.	Higher chance of breaking RGB software or peripheral functions until repaired or reinstalled.	Restore the backed-up driver or reinstall the hardware vendor’s utility.	THE FINALS-specific escalation path when a full driver cleanup is necessary.

The key difference is reversibility. Uninstalling KB5121003 is a blunt diagnostic tool, not a good resting state. Deleting inpoutx64 completely is effective when it is truly the offending component, but it takes more cleanup if your lighting or peripheral suite depends on it. The registry method sits in the middle: not painless, but tidy enough to test and easy enough to reverse.

That is also why it is smart to change only one variable at a time. If you uninstall KB5121003, delete the driver, reinstall your RGB utility, and verify game files all in one afternoon, you may get the game stable without ever learning which step fixed it. Clean troubleshooting is not glamorous, but it saves time later.

Embark’s more aggressive removal method

Embark’s crash troubleshooting for THE FINALS goes further than Microsoft’s registry disablement. It stops and deletes the inpoutx64 service, removes the driver file, and allows optional cleanup of the service registry key. This prevents the driver from loading because the driver and its service entry are gone.

Use this route only after creating a restore point, exporting the registry key, and copying C:\Windows\System32\drivers\inpoutx64.sys to a backup folder. Open Command Prompt or Windows Terminal as administrator, then run the following commands separately:

• sc stop inpoutx64
• sc delete inpoutx64

Then delete C:\Windows\System32\drivers\inpoutx64.sys and restart Windows. Embark also permits removal of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64 as an optional cleanup step. Reinstalling or repairing the RGB utility can restore lighting functionality later, although that utility may reinstall the same driver. Before letting that service load again, make sure the vendor software has a version that no longer recreates the conflict.

This method is more forceful, but it is not reckless if you prepare properly. The logic is straightforward: if a disabled driver does not stop the crash because the service or file keeps returning in a broken state, removing the service and driver entirely gives THE FINALS a cleaner environment. The downside is equally straightforward: any software stack that expected to find inpoutx64 may suddenly lose part of its functionality until you repair or reinstall it.

In practical terms, use Embark’s method when all three of these are true: KB5121003 is definitely installed, inpoutx64 is definitely present, and Microsoft’s Start = 4 approach did not stop the crashes after a reboot and multiplayer retest. If those boxes are not all checked, the aggressive route is probably premature.

Why an RGB driver can crash a multiplayer game

RGB control suites sometimes install low-level I/O drivers so their software can talk directly to hardware controllers. inpoutx64.sys is one such component. Windows security changes, a legacy-style hardware-access driver, Unreal Engine 5, and multiplayer anti-cheat are not a cozy combination: each piece operates close enough to the system that a compatibility failure can take down the game process or, in worse cases, the whole PC.

That also explains the sharp symptom split. A system can browse the desktop, run lighting effects, and even reach THE FINALS menu without drama, then fall apart when actual online play loads the full game stack. Matchmaking, map loading, real gameplay, and anti-cheat checks create a much harsher test than sitting in menus. If the system is unstable only when that stack comes together, the culprit usually lives deeper than a simple graphics setting.

None of this means RGB hardware is inherently broken or that every lighting utility is dangerous. It means one class of low-level driver is colliding badly with one Windows security update in a way that becomes especially visible in affected multiplayer games. Microsoft is still investigating a long-term fix, and no permanent replacement update or firm delivery date has been announced.

What to avoid while troubleshooting

• Do not leave KB5121003 uninstalled as a long-term gaming fix. It is a cumulative security update with fixes far beyond the gaming stack.
• Do not edit unrelated registry values inside the inpoutx64 service key. Change only Start for Microsoft’s mitigation.
• Do not skip the restart. The driver state cannot be validated reliably until Windows boots again.
• Do not delete the driver file without a backup if the RGB suite controls fan curves, AIO settings, macros, or other peripheral functions.
• Do not assume every RGB utility uses this component. Check for the actual inpoutx64 file and service before disabling software at random.
• Do not stack six fixes at once. Make one change, test THE FINALS, and then decide whether to escalate.

The last point is the one most players ignore because it is boring. Boring wins here. If you want a stable machine and a clear answer, treat every change as a controlled test. That is the difference between “I fixed it” and “I have no idea what I touched, but now my keyboard macros are gone and the game still crashes.”

Pros and cons of Microsoft’s workaround

Pros: It keeps KB5121003 installed, which means Windows 11 retains the security fixes bundled into the August 11, 2026 cumulative update. It is reversible, because you are disabling a service entry rather than immediately destroying files. It is also narrow, which is exactly what you want in a troubleshooting step: one known driver is taken out of the boot path, then the game is retested under the same conditions that previously caused the crash.

More good news: the workaround lines up with the way the issue behaves in THE FINALS. The problem usually shows up when multiplayer load ramps up, not during every ordinary Windows task, so a targeted driver disable makes more sense than a full Windows rollback. If the crash disappears after the reboot, you have a useful answer without having to rebuild your whole setup.

Cons: the workaround is still registry editing, which is not something every player is comfortable doing on a live gaming PC. It can also break the quality-of-life features attached to the same RGB stack, including lighting profiles, utility controls, and sometimes macros. Most of all, it is a mitigation, not a glamorous “install this and forget it” permanent fix. You are trading lighting convenience for game stability while Microsoft continues its investigation.

The practical downside: if your system uses one of these utilities for more than pretty lights, the side effects may be more than cosmetic. Some device suites bundle multiple functions into one driver stack. That does not make Microsoft’s workaround bad; it just means you should know what you are giving up before you flip the switch.

If disabling inpoutx64 does not fix THE FINALS

If THE FINALS still crashes after you confirm KB5121003 is installed, confirm inpoutx64 is present, set Start to 4, reboot, and test real multiplayer, then the next step is not blind panic. It is controlled escalation.

• Use Embark’s full removal method for inpoutx64 if you have not already.
• Verify THE FINALS game files through the platform launcher so a separate file corruption issue is not hiding behind the Windows bug.
• Return any GPU or RAM overclocks to stock settings while testing.
• Temporarily close or disable nonessential hardware-control utilities that hook into peripherals, lighting, or overlays.
• As a short A/B diagnostic, uninstall KB5121003 once, retest, and then reinstall it through Windows Update if that proves the update is part of the pattern.

That last item is useful precisely because it is not subtle. If uninstalling KB5121003 immediately restores stability, you have strong confirmation that your machine sits squarely inside this compatibility problem. Still, it should stay a diagnostic step or a short-term emergency measure, not your permanent answer.

If the crashes continue even with KB5121003 removed and inpoutx64 gone, you are almost certainly outside this specific issue and should troubleshoot THE FINALS like a more traditional PC game crash: game files, drivers, hardware stability, and background software. At that point, the Windows update is no longer the cleanest suspect.

Practical recommendation

If THE FINALS started crashing after KB5121003 on Windows 11 24H2 or 25H2, the best order of operations is clear. First, confirm the update is installed and that inpoutx64.sys or the matching service key exists. Second, use Microsoft’s reversible registry workaround by setting Start to 4, rebooting, and testing several real multiplayer matches. Third, move to Embark’s service-and-driver removal method only if the registry disable does not stick or does not solve the crash.

In short: keep the security update, disable the suspect driver, and judge the result in live matches rather than in menus. Right now that is the safest fix with the best balance of stability, security, and recoverability for affected THE FINALS players on Windows 11.