Forza Horizon 6 PC Issues: Fix Crashes, Stuttering, Steam Errors, and Game Pass Problems

I’ve spent the launch window of Forza Horizon 6 working through the PC issues that players are actually running into, not theoretical problems, but the specific crashes, non-launches, and stutters that are flooding Steam discussions, ResetEra threads, and Forza Support tickets right now.

Here is what I found: most of the crash and launch issues have official fixes. Forza Support has published error code documentation, Gaming Services version requirements, and Steam-specific guidance that resolves the majority of reports. The stuttering situation, particularly on AMD systems, is more complicated, and I’m not going to pretend it isn’t.

One thing I want to be clear about before diving in: I don’t think this is a universally broken PC port. PC Gamer’s testing found the game generally runs well across supported hardware, though it is CPU-heavy and ray tracing costs more than it delivers visually. What I’m seeing in the community is concentrated around specific hardware combinations, launch-entitlement confusion, and a Gaming Services dependency that catches Steam players completely off guard. Most of it is fixable.

First, Check Whether Forza Horizon 6 Has Actually Unlocked for Your Account

Before I troubleshoot anything technical, I always confirm that the game is supposed to be accessible to me in the first place. Forza Support documents a specific error, sometimes shown as “You’re too early”, that is not a bug. It means the account doesn’t hold the right entitlement for early access.

Here’s how the release window breaks down:

• Premium Edition and Premium Upgrade owners: Early access started May 15, 2026.
• Standard and Deluxe Edition buyers: Access begins at general availability, May 19, 2026.
• Xbox Game Pass / PC Game Pass subscribers: Access begins at general availability unless the same Microsoft account also owns the Premium Upgrade.

If I’m seeing “You’re too early,” the first thing I check is whether the Microsoft account I’m signed into on Steam or the Xbox app is the same one that owns the Premium Edition or Upgrade. That account mismatch is more common than people expect. After confirming the entitlement and the unlock window, I restart Steam or the Xbox app before trying again.

If I’m on Standard or Deluxe and early access was never part of my purchase, I stop troubleshooting and wait for May 19. Nothing technical is wrong.

If you want more context before diving into fixes, these cover the surrounding story: Forza Horizon 6 features, early access details, and unlock times, what the Steam leak revealed ahead of launch, and all 57 achievements and how to reach 1000 Gamerscore.

Update Gaming Services Before Launching Forza Horizon 6

This is the first thing I do on any PC where FH6 won’t launch, and I do it even on systems where I installed the game through Steam, which is where most people get surprised.

Forza Horizon 6 requires Microsoft Gaming Services to run on PC regardless of where you bought it. It handles license verification, Xbox Live authentication, and cloud saves across all PC versions of the game. If Gaming Services is outdated, the game won’t open. Forza Support specifies that version 36.113.2002.0 or higher is required.

Here’s how I update it:

1. Open the Microsoft Store.
2. Click the Library icon in the bottom-left.
3. Select Get updates or Check for updates.
4. Find Gaming Services in the list and update it.
5. Restart the PC, not just the game, the whole machine.

I don’t skip the restart. Some Gaming Services updates don’t activate until the system reboots, and launching FH6 immediately after the update will produce the exact same error.

If Gaming Services is corrupted rather than just outdated, I go to Windows Settings → Apps → Gaming Services → Advanced Options → Repair. When that fails, Forza Support’s PC crash guide documents a PowerShell reinstall method. Microsoft also offers a dedicated Gaming Services Repair Tool on the Xbox support website, which handles the most stubborn cases.

Check PC Requirements, Windows Version, and GPU Support

I won’t waste time on settings tweaks if the system is running below the minimum spec. Here’s what the game actually requires, pulled directly from Steam’s listing.

Minimum requirements (targets 1080p / 60fps / Low preset):

• Windows 10 version 22H2 (build 19045) or Windows 11
• CPU: Intel Core i5-8400 or AMD Ryzen 5 1600
• GPU: Nvidia GeForce GTX 1650, AMD Radeon RX 6500 XT, or Intel Arc A380
• 16 GB RAM
• DirectX 12
• SSD required, not a recommendation
• 167 GB available storage

Recommended tier (targets 1440p / 60+ fps / High preset): Intel Core i5-12400F or Ryzen 5 5600X, paired with RTX 3060 Ti / RX 6700 XT / Intel Arc A580

GPU architectures that are not supported: The minimum supported Nvidia architecture is Turing meaning the GTX 1650 sits at the floor. Nvidia Pascal and older (GTX 1070, GTX 1080) are not guaranteed to work because they fall below that minimum. AMD Polaris and Vega architectures are listed by Forza Support as unsupported outright. If I’m running hardware in those categories, I’m not going to find a settings fix that makes the game stable. The crash fixes in the next section aren’t applicable when the GPU itself is below what the engine requires.

If my Windows version is below 22H2, I update that before anything else. Some crashes on older Windows builds come from missing DirectX 12 feature support, not from the game.

How to Fix Forza Horizon 6 Crashing on PC

The thing I appreciate about FH6’s crash handling is that it uses specific error codes rather than a generic “the game has crashed” message. Each code points to a specific hardware resource or system failure, which makes troubleshooting a lot faster than guessing.

Error Code	What It Means	Where I Focus
FHC	Video card crash	Update GPU driver; lower ray tracing and VRAM-heavy settings; check GPU stability
FHD	Out of video memory	Reduce texture quality, ray tracing, and rendering resolution; switch to DLSS/FSR Quality
FHE	General game crash	Disable overlays and monitoring tools; verify game files; update Windows and Gaming Services
FHF	Out of system memory	Close background apps; confirm 16 GB RAM; check Windows page file
FH301	GPU driver needs updating	Install the latest Nvidia, AMD, or Intel Arc driver
FH401	Insufficient system memory	RAM is below minimum; close background apps or upgrade
FH601	Microsoft Media Foundation issue	Install missing Windows media components via Optional Features in Windows Settings

When I see FHC or FHD, VRAM is the first thing I examine. On an 8 GB GPU running Extreme textures or high ray tracing, exceeding the VRAM budget can cause FHD crashes or instability, and since the in-game VRAM meter makes it easy to spot, it’s the fastest thing to check. I drop textures to Ultra on 8 GB cards and reduce or disable RTGI first, because it carries the heaviest VRAM cost for the least visible improvement.

When I see FHE, I treat it as a broad crash category that needs methodical diagnosis rather than a single obvious cause. Overlays and conflicting background tools are one of the more common contributors, so that’s where I start, but FHE covers any general game crash, so if disabling overlays doesn’t resolve it, I move through the full checklist in the next section.

Disable Overlays and Conflicting Background Tools

Forza Support’s general PC troubleshooting guidance lists overlays and background tools that can interfere with Forza games. I work through that list before anything else when diagnosing FHE crashes, because these tools hook into the rendering pipeline in ways the ForzaTech engine doesn’t tolerate. The general PC launch and crash guide is at support.

Before launching, I close or disable all of the following:

• MSI Afterburner and RivaTuner Statistics Server (RTSS)
• Discord in-game overlay
• Nvidia GeForce Experience overlay and ShadowPlay
• Steam overlay, yes, even on a game I bought through Steam
• EVGA Precision X1
• OBS and XSplit running in the background
• Wallpaper Engine
• WeMod
• Nahimic audio software
• Logitech G Hub when it’s producing elevated CPU usage at launch
• Any RGB, wheel, or peripheral management software with active overlays

If I’ve cleared the obvious candidates and crashes continue, I run a clean boot through msconfig, disabling all non-Microsoft startup services, to catch whatever else might be interfering. Then I re-enable services one group at a time until the problem reappears.

How to Fix Forza Horizon 6 Stuttering and FPS Drops

I want to be straightforward here: not all stuttering in FH6 has a fix I can give you right now. What type of stutter I’m dealing with determines whether a setting change actually helps.

Shader compilation stutter I treat as expected and temporary. When I first play, or after a driver update, the game compiles DirectX 12 shaders on the fly as I enter new areas. Until the cache fills in, I’ll see hitches. Running the in-game benchmark before going into the open world accelerates the process, and this stutter largely resolves within the first several hours of play.

Open-world traversal stutter is a separate and more stubborn problem. I’m seeing it most consistently reported on AMD GPU and Ryzen X3D processor combinations, with consistent micro-stutters every few seconds in the open world that don’t appear during the benchmark at all. PC Gamer’s testing flagged the game as CPU-heavy and identified thread scheduling quirks specifically on dual-CCD Ryzen X3D chips. That doesn’t mean those setups are broken, but it explains why some players with very capable hardware are hitting frame pacing problems that simpler configs aren’t.

The workarounds I try first:

• Disable in-game V-Sync and instead cap the framerate through Nvidia Control Panel or AMD Adrenalin, set a few frames below the monitor’s refresh rate.
• Turn off ray tracing, starting with RTGI, before touching anything else.
• Drop from Extreme to Ultra or High. The visual gap is small, the performance gap is not.
• If frame pacing feels inconsistent, switch from Frame Generation to DLSS Quality or FSR Quality. Frame Generation magnifies instability when the underlying frame times are already variable.
• After any major settings change or driver update, I restart the game entirely and let the shader cache rebuild from a clean state.
• I keep the in-game VRAM usage meter visible and make sure I’m comfortably within my card’s physical limit.

If I’m on AMD and stutter persists after all of the above: AMD released driver version 26.5.2 close to launch. It adds official FH6 game support, including game profiles, shader paths, and compatibility adjustments, but it is not confirmed as a dedicated stutter fix; the release notes list no FH6-specific bug fixes. Still, installing it is the right baseline to be on before deeper troubleshooting. Some AMD users are still reporting open-world micro-stutter after driver and settings changes, so those cases may require a game-side or driver-side update rather than a guaranteed local workaround. What I do in that situation is file a support ticket, add my hardware details to the relevant threads on the Forza Feedback Hub, and give Playground the data they need to prioritize it. Pretending there’s a guaranteed workaround when there isn’t would be a waste of your time.

How to Fix Forza Horizon 6 Steam Problems

The 59-character path limit is the first thing I check on any Steam install. Forza Support officially documented that FH6 must be installed in a Steam library path that is 59 characters or fewer. If my Steam library is sitting inside something like C:\Users\MyUsername\Documents\PC Games\Steam\SteamLibrary\, that path is almost certainly over the limit and the game simply will not launch, with no error code and no explanation.

My fix is to move the Steam library to a shorter path: D:\Steam\ or C:\Games\ both work. I use Steam’s built-in content move feature under Settings → Storage, then verify file integrity on FH6 after the move before launching.

When Steam shows the game as running but nothing appears on screen, here’s my sequence:

1. Open Task Manager and end any ForzaHorizon6.exe processes still lingering in the background.
2. Fully quit Steam through the tray icon, because just closing the window leaves Steam running, which can hold a lock on the game process.
3. Try clearing the DirectX shader cache at C:\Users\[My Name]\AppData\Local\D3DSCache. This is a community workaround; Forza Support’s official FH6 crash guide does not specifically list this as a fix, but some players have reported it resolving silent launch failures. Forza’s official PC crash troubleshooting is at support.
4. Relaunch Steam and try again. The first boot after clearing the cache may take longer than usual.

For crashes showing error code 0xc0000409 or a xinput1_3.dll error, I disconnect all controllers before launching and check whether antivirus software is blocking or interfering with the game. Forza Support has a general guide for adding Forza as an exception to antivirus software and firewalls. There’s no confirmed FH6-specific quarantine pattern during launch week, but antivirus interference is a documented general cause of Forza launch failures and worth ruling out.

For Microsoft account sign-in loops on Steam: FH6 requires a linked Xbox Live account even on Steam. When I hit authentication loops, I sign out of both the Xbox app and Microsoft Store, then sign back in with the Microsoft account that owns the game or my Game Pass subscription. If it keeps looping, I open Windows Credential Manager, find any Xbox Live or Xbox.com credentials stored there, remove them, restart the PC, and sign in fresh. Forza Support includes this credential-clearing step in their official PC troubleshooting guide.

How to Fix Game Pass and Xbox App Errors

The first thing I confirm for Game Pass players is that general availability has passed for their region and that the subscription is active on the account signed into the Xbox app.

When the game won’t open through the Xbox app, my first move is:

1. Press Win + R, type wsreset.exe, press Enter.
2. A blank Command Prompt appears. Leave it alone and wait for it to close automatically.
3. Once the Microsoft Store reopens, I restart the Xbox app and try launching the game again.

This clears the Store’s temporary cache, which can block license verification and prevent the game from opening even when the subscription is perfectly valid.

I keep both the Xbox app and Gaming Services updated at all times for Game Pass. The Xbox app and Microsoft Store version depends on Microsoft account licensing, Gaming Services, and Xbox app components. If any of those are outdated or corrupted, FH6 may fail to launch, so updating Gaming Services, the Xbox app, and the Microsoft Store should be part of the first troubleshooting pass, before spending time on anything else (Forza Support: Update Gaming Services).

For persistent launch errors after updating Gaming Services, I go to Windows Settings → Apps → Xbox → Advanced Options → Reset. That clears the Xbox app’s local data entirely and forces it to re-verify my account and subscription from scratch on the next launch.

How to Fix Controller, Wheel, and Steam Controller Issues

The current build’s official known issues list is clear on one thing: the Steam Controller is not officially supported and may crash the game. If I’m using a Steam Controller and hitting crashes, I disconnect it before launching and test with a standard wired Xbox controller first, just to confirm whether the controller is the source of the problem.

For everything else I’ve worked through:

• Xbox controller via wired USB is the most stable option in the current build. It’s where I always start when diagnosing controller issues.
• DualSense controllers: I test with Steam Input both enabled and disabled, because the behavior differs by setup. Some players get better results with Steam Input off.
• Bluetooth: I avoid it during this launch window. Bluetooth controller disconnects are showing up in reports alongside frame hitches and crashes. Wired or a 2.4 GHz dongle is consistently more stable.
• Before launching with any controller: I disconnect everything, start the game, reach the main menu, then reconnect. This fixes the cases where the game stops recognizing a controller after the benchmark or between sessions.
• Wheel users: I close Logitech G Hub, Fanatec Control Panel, and similar companion apps before launching, as they appear on Forza Support’s general list of software that can interfere with the game’s stability.

When I Stop Troubleshooting and Wait for a Patch

There are issues from this launch window where I genuinely cannot give someone a reliable fix, and I think it’s more useful to say so than to keep suggesting settings changes that won’t work.

AMD open-world micro-stutter on setups that remain unstable after driver updates and the settings workarounds above: this one needs attention from Playground Games. The Feedback Portal has active threads on it. Adding hardware details to those threads gives Playground actionable data to work from.

Steam Controller crashes: officially listed as an unsupported configuration right now.

Tunnel lighting artifacts and shadow flickering below Ultra settings: Forza Support has confirmed these as known visual issues in the current build.

Delayed relaunch after running the benchmark: the game takes longer than expected to return to playable state after the benchmark finishes. This is documented behavior in the current build, not a system-side crash.

For these, my honest recommendation is: file a support ticket with your hardware specs, and track the Forza Feedback Hub, where Playground Games is documenting known issues and their status for FH6, rather than through traditional patch notes. As of the May 2026 launch window, there is no confirmed regular patch cadence; the Feedback Hub is the primary place to monitor progress on open bugs. If the issue is making the game unplayable, use the Steam refund window or pause Game Pass access until a fix ships.

Looking back across everything I’ve worked through, almost every fixable PC issue in Forza Horizon 6 traces to one of three places: Gaming Services being out of date, a background tool conflicting with the rendering pipeline, or the Steam library path being longer than 59 characters. I start there every time. The error codes handle the rest of the crash troubleshooting. And for stuttering, particularly on AMD, I’m honest about the line between what a settings change can fix and what requires a patch.