Fix: Forza Horizon 6 Not Launching, Won’t Launch, Not Starting, or Doing Nothing When You Hit Play on PC?

Forza Horizon 6 can fail before it draws a single window on PC. After you press Play, Steam may change the button to Running while the game sits in Task Manager.

On the Xbox app, the button may return to Play after a few seconds. In either case, no splash screen, black screen, or crash message appears.

The launch request has usually reached Windows and stopped during one of FH6’s early checks. The game verifies Microsoft Gaming Services even when it was bought through Steam, checks the available CPU and DirectX 12 features, and loads the graphics driver.

Overlays and other background software can then attach to the process. A failure at any of these points can close FH6 before a visible window exists.

Reinstalling the game only replaces its local files. It does not update Gaming Services, make an unsupported GPU compatible, or remove a program that is interfering with startup. Use the result that appears on your PC to choose the first relevant section.

1. Update Gaming Services, Including for the Steam Version

Forza Support states that the required Gaming Services update applies to both the Xbox app and Steam editions of FH6. The launch fails when this Windows component is older than the version the game expects.

Updating it restores the package version FH6 validates before opening. Use this method only if Gaming Services is missing, outdated, or named by the game; a current, healthy package does not need to be removed.

1. Close Forza Horizon 6, Steam, and the Xbox app.
2. Open Microsoft Store > Downloads, then select Check for updates.
3. Install the available Gaming Services update. If the Store shows only Open or Installed, it considers the package current.

   

4. Open Settings > Apps > Installed apps, find Gaming Services, and open Advanced options. Compare its version with the current minimum on Forza’s Gaming Services page.

   

   

5. Restart Windows and launch FH6 from the storefront library.

If the game now opens, the Windows gaming runtime was out of date. If Gaming Services was already current, leave it installed and check the PC requirement or displayed error code next.

Rollback: A normal Store update does not offer a version rollback. If the updated package itself will not open or install, use the Repair path in Method 7 rather than downloading an older package from an unofficial source.

2. Let the FH6 Error Code Decide Whether the Problem Is Hardware, Driver, or BIOS

FH6 can stop before its first window when the PC cannot provide a required CPU, memory, or DirectX feature. A graphics-driver update can restore software support on compatible hardware, but it cannot make an older GPU architecture meet the game’s requirement.

Forza currently supports NVIDIA GPUs beginning with the Turing architecture. AMD Polaris and Vega GPUs and older are below the supported floor.

Check the current FH6 PC specifications before spending time on package repairs.

1. Compare the CPU, GPU, VRAM, RAM, and operating system with the current official requirements.
2. If the hardware is supported, install the latest stable driver directly from NVIDIA, AMD, or Intel, then restart Windows. This Appuals graphics-driver guide covers updates, clean installs, and rollbacks.
3. Retest FH6 and photograph any code that remains. The complete descriptions are available on Forza’s PC crash-code page.

   

If the PC is below the supported floor, Windows repairs will not make that hardware compatible. If it qualifies and FH6 still closes without a code, complete the Windows and storefront checks below.

3. Finish Windows Updates and Retest from an Administrator Account

FH6 depends on current Windows graphics, Store, and package components. A pending update or a restricted Windows profile can interrupt startup before the game creates a window.

1. Open Settings > Windows Update, select Check for updates, and install every pending cumulative update.
2. Confirm that the Windows account has administrator access. On a managed work or school PC, use the approved administrator path rather than bypassing policy.
3. Shut down Windows completely, turn the PC back on, and open the storefront used to install FH6.
4. Launch the game before opening overlays, monitoring tools, or other launchers.

   

If Steam still shows Running with no game window, go to Method 5. If the Xbox app returns to Play or other Store apps are also behaving incorrectly, repair that package chain first.

4. Repair the Xbox App, Microsoft Store, and FH6 Package

This section is for the Xbox app or Microsoft Store edition. Steam users can skip it unless the Microsoft Store itself cannot update Gaming Services.

Windows can repair a packaged app without deleting its local data. Reset is more disruptive because it clears the app’s local state and can sign you out, so use it only after Repair fails.

1. Open Settings > Apps > Installed apps.
2. Find Xbox, open Advanced options, and select Repair. Test the app before using Reset.
3. Repeat the same Repair-first order for Microsoft Store and the Forza Horizon 6 package if Windows lists it.

   

4. Press Win + R, enter wsreset.exe, and wait for Microsoft Store to reopen.
5. Restart Windows, open the Xbox app Library, and retest FH6.

Microsoft documents the same order in its Windows app-repair guide.

If the Xbox app itself will not open and shows 0x80070426, use this Appuals Xbox app guide instead of repeatedly changing the game.

Checkpoint: If Repair restores the launch, the affected app package was damaged. If it does not, Steam copies continue to Method 5 and Xbox copies continue to Method 6.

Rollback: Repair keeps app data. Reset cannot be undone from the same page; reopen the affected app and sign in again if Windows cleared its local session.

5. Verify the Steam Installation and Observe the Process Once

Use this only for the Steam edition. When an update or unpacking process leaves a file missing or altered, Steam can start the executable but FH6 may close before opening a window.

Verification compares the installation with Steam’s current copy and replaces mismatched files without redownloading the entire game.

1. Exit FH6 if Steam still considers it running. In Task Manager, wait for the Forza process to end before starting another test.
2. Open Steam > Library, right-click FH6, and select Properties > Installed Files > Verify integrity of game files.

   

3. Let Steam finish, restart the client, and launch FH6 once while Task Manager is open.
4. If the process appears but no window does, note whether it stays running, consumes CPU briefly, or exits after roughly a minute. That distinction is useful for the background-conflict test and any support report.

Steam’s official verification instructions explain that a local configuration file can occasionally fail verification without indicating a broken installation.

Checkpoint: If verification replaces files and FH6 opens, the installation was damaged. If the same silent process returns, continue to Method 6 and isolate programs that load alongside it.

If Steam shows E:0-e9 Load Failed, check Forza’s current known-issues page.

Forza has tracked that exact startup error as a game-side issue. Once the game is current and verified, repeated Windows resets are not a sensible next step.

6. Test FH6 Without Overlays and Other Background Hooks

FH6 fails when an incompatible overlay or monitoring hook attaches during startup. Forza Support lists capture, input-remapping, audio, RGB, and hardware-monitoring software as possible conflicts.

MSI Afterburner and RivaTuner Statistics Server appear repeatedly in FH6 player reports. Use this only after the shared update and storefront checks; a clean boot is safer than uninstalling programs at random.

1. Close overlays, capture, RGB, audio, and monitoring tools such as MSI Afterburner or RivaTuner.
   
2. If security software has actually blocked or quarantined an FH6 file, restore the verified game file and allow-list the official game folder. Do not disable protection merely because the game failed to open.
   
3. If FH6 still fails, press Win + R, enter msconfig, and open Services. Select Hide all Microsoft services, then Disable all.
   
4. Open Task Manager from the Startup tab, record the currently enabled items, and disable nonessential startup apps.
   
5. Restart Windows and test FH6 before opening anything else.
6. If the game opens, re-enable the disabled items in groups until the failure returns. Keep the confirmed conflicting program closed, update it, or remove it if you no longer need it.
7. When testing is complete, return System Configuration to Normal startup and restore the startup items you want.

Use Microsoft’s clean-boot instructions for the full setup and recovery sequence.

If FH6 works only in the clean boot, its installation is not the main problem. The disabled group contains the software or service interfering with launch.

Checkpoint: If the game still fails in a clean boot, restore normal startup, then continue to Method 7. The disabled third-party programs are not responsible for that launch attempt.

7. Repair or Reinstall Gaming Services Only if the Package Is Still Broken

Use this final local repair when Method 1 confirms the package is current but FH6 still reports Gaming Services, Store updates fail, or Event Viewer names a Gaming Services component. Do not remove a working package only because another method did not help.

1. Open Settings > Apps > Installed apps > Gaming Services > Advanced options.
   
2. Select Repair and retest. Use Reset only if Repair makes no difference; Reset can clear local state and require another sign-in.
   
3. If both options fail, close the storefront and all Microsoft Store games. Open PowerShell as administrator and run:

get-appxpackage Microsoft.GamingServices | remove-AppxPackage -allusers
start ms-windows-store://pdp/?productid=9MWPM2CQNLHN

4. Install Gaming Services from the Store page that opens, restart Windows, and sign back into the Xbox components if prompted.
5. Launch FH6 once before restoring overlays or monitoring tools.

The removal commands are part of Forza’s current PC launch and crash guidance.

On a managed PC or where PowerShell is restricted, ask the administrator to perform the repair instead of bypassing policy.

Checkpoint: If reinstalling Gaming Services removes the warning and FH6 opens, the package registration was damaged. If the warning or silent exit remains, do not repeat the removal command.

Rollback: The PowerShell removal has no one-click undo. Complete the Store installation and restart Windows before testing other Xbox or Store games.

If FH6 still creates a background process and exits without a dialog, reproduce the failure once. Immediately open Event Viewer > Windows Logs > Application and save the Application Error recorded at the same time.

Check the Forza Feedback Portal for a matching active issue. If none exists, submit a Forza Support ticket.

Include the storefront, Windows build, CPU and GPU models, driver version, exact process behavior, any FH or exception code, and the saved event. That gives support evidence from the failed launch instead of another generic reinstall result.