Fix: Forza Horizon 6 Crashing At The “Turn 10 Studios” Screen

When Forza Horizon 6 closes at the Turn 10 Studios screen, after the first logo, or before the main menu appears, the game is failing during its pre-menu startup checks.

At that stage it has not fully loaded your profile or world yet. It is still validating platform services, the install path, graphics support, connected devices, local files, and the first graphics window.

The logo is only the last thing you see. The actual trigger can be an outdated game build, unsupported GPU architecture, broken Gaming Services handoff, overlong Steam library path, damaged files, overlay hook, controller/wheel conflict, or a crash-code condition such as missing DirectX 12 features or insufficient memory.

1. Install the Latest FH6 Update and Check System Requirements

Start with the update and hardware check because both can stop the game before the menu. A patched build can repair startup faults, while unsupported hardware can fail the same early validation no matter how many times the game is reinstalled.

This is especially important on older GPUs. FH6 supports Windows 10, Windows 11, and Steam Deck devices using SteamOS, but not general Linux installations. NVIDIA support starts at Turing; AMD Polaris, Vega, and older architectures are below the supported floor.

If the game is already on the newest available build and the PC clearly meets the supported floor, use this as a confirmation step rather than repeating the same update check.

1. Let Steam or the Xbox app finish every available Forza Horizon 6 update before you test another launch.

   

2. Compare your CPU, memory, GPU, storage, and operating system against the official FH6 PC requirements.

   

3. If a crash-code dialog appears, take a screenshot or write the code down before closing it.

2. Update Gaming Services, Even for the Steam Version

Gaming Services is not only an Xbox app concern. If this Windows component is outdated or damaged, FH6 may fail the platform handoff before the menu or show an invalid-services warning. Updating it restores the service layer the game expects to find.

Use the Microsoft Store update path first. This pass only updates or checks the service; it does not reset, remove, or reinstall Gaming Services, so there is no rollback step for the version check itself. On a managed work or school PC, let the administrator update it instead of bypassing policy.

1. Open Microsoft Store.
2. Select Downloads, then choose Check for updates.
3. If Gaming Services appears, update it.

   

4. Open Settings > Apps > Installed apps, search for Gaming Services, open Advanced options, and compare the version with the minimum listed on Forza Support.

   

5. Restart Windows and launch FH6 again.

3. Shorten the Steam Library Path and Verify the Game Files

The Steam version has one unusually specific requirement: FH6 needs to be installed in a Steam library path that is 59 characters or shorter. When the path is too long, the Steam copy can fail before the game reaches the menu even though the files appear to be installed normally.

After the path is valid, file verification checks whether the install was damaged by an interrupted download, unpacking issue, or partial update. Skip the path-shortening part on Xbox app installs because this Steam library limit does not apply there.

1. In Steam, right-click Forza Horizon 6 and select Manage > Browse local files.
2. Check the full folder path. If it is longer than 59 characters, move FH6 to a shorter Steam library such as a simple folder near the drive root.
3. Open Properties > Installed Files and run Verify integrity of game files. For the full Steam repair route, use this Appuals guide on verifying game files.

   

4. Launch FH6 again after verification completes.

4. Remove Controller, Wheel, Overlay, and Driver Conflicts

Some splash-screen crashes happen while FH6 is creating its first window and reading connected input devices. Overlays, capture tools, monitoring utilities, wheels, virtual input drivers, and certain controller paths can hook into that process before the menu appears and cause startup to fail.

Do one minimal launch test instead of changing everything permanently. If you have no external controllers, wheels, overlays, monitoring tools, capture utilities, or recent GPU-driver changes, this section may not apply.

1. Disconnect any Steam Controller for one launch test.

   

2. Close Steam Overlay, Discord Overlay, Xbox Game Bar, MSI Afterburner, RivaTuner, RGB utilities, capture tools, FPS counters, and similar launch hooks.
3. If a racing wheel is connected, update its drivers and firmware, connect the wheelbase directly to a dedicated USB 3.0 port, and unplug extra shifters, pedals, or controllers for the first test.

   

4. If the crash began after a GPU-driver update, install the newest stable driver. If the newest driver is already installed and the crash started immediately after that update, test the previous stable driver once. This Appuals graphics driver guide covers update, clean-install, and rollback paths.

   

If FH6 opens during the minimal test, the game files were not the main issue.

5. Use the Crash Code to Identify the Failure Family

FH6 crash codes are useful because they identify the part of startup that failed. A code can appear when the game detects unsupported hardware, missing DirectX 12 features, low VRAM, system memory pressure, or missing media components before the menu loads.

Skip this section if the game closes with no dialog or code. In that case, continue with the support-report step after the earlier checks are complete.

• FHC or FHE: Graphics-card or general game crash. Suffix 01 means the system is on a supported driver and OS, 11 points to unsupported drivers or hardware, and 21 points to an unsupported OS.
• FHD or FHF: The GPU has run out of video memory, or the PC has run out of system memory.
• FH101 or FH113: The CPU has too few logical processors/threads, or the processor path may need a motherboard BIOS update.
• FH201, FH203, FH204, FH205, or FH206: The GPU lacks a required DirectX 12 feature.
• FH202: The graphics card has less than 4 GB of VRAM.
• FH301 or FH302: Update the graphics driver, then recheck whether the GPU is supported.
• FH401: The PC has insufficient system memory.
• FH601: Windows could not load Microsoft Media Foundation, so the required media components may be missing.