TL;DR

⚠️ Update — 27 July 2026: Read this before you paste anything. Since publishing this, we ran live telemetry on FH6 crashes and found that a lot of people arriving at this page have a different bug than the one this article fixes.

The launch option below addresses a startup crash — the game dies before you reach the main menu. But the far more widespread problem is a crash where the game launches fine, menus work fine, and then it silently vanishes to the desktop a few minutes later. That one is a D3D12 memory leak in the shader optimization pass, and our measurements explicitly ruled out the network as its cause.

If your game reaches the main menu before dying, this article is not your fix. Go straight to Why Forza Horizon 6 Dies Three Minutes In, where we caught the real cause on camera.

There’s also a safety note about the --disable-cloud-sync flag below that didn’t exist when this was written. Please read it before leaving that flag in place.


Which crash do you actually have?

Thirty seconds of triage will save you a lot of wasted effort.

You crash before the main menu appears. The game never really starts — you get a crash report prompt, or it dumps you straight back to the desktop during loading. This article is for you. Carry on below.

You reach the main menu, play for 2–15 minutes, then the game silently disappears. No error, no dialog, no crash report — it’s just gone. This article is not for you. That’s the shader optimization memory leak, and we documented it in detail with live telemetry. The short version: the game leaks D3D12 upload heaps at around 55 MB per second during its “optimizing shaders for your PC” pass, hits an internal 16 GB wall, and exits with code 0. The workaround there is changing the game’s language in the options menu, which forces a restart that survives. Deleting your shader cache, verifying files, and reinstalling drivers do nothing for it — we tested them.

Not sure? Watch whether you get to the main menu. That’s the whole test.


TL;DR (for the startup crash)

FH6 was crashing on startup for a lot of players in late June. The cause appeared to be a bad handshake with Playground’s cloud servers, and a community member called Paco posted a Steam launch option that got the game running again. I tried everything else for three days and this is the one that worked for me. Here’s the fix:

  1. Right-click Forza Horizon 6 in your Steam library and choose Properties
  2. Under the General tab, find the Launch Options box at the bottom
  3. Paste this exactly:
--disable-cloud-sync --no-sandbox

That’s it. Launch the game.


🛑 Important safety note about --disable-cloud-sync

This wasn’t in the original article and it matters more than the fix does.

That flag turns off cloud save synchronisation. At the time of writing we treated that as a harmless temporary trade-off. Since then, FH6 has had a documented save-wipe bug that has erased entire save files — hundreds of hours and full car collections — for players on both Xbox and PC. On PC the known triggers include a crash during a save write and conflicts with Xbox app cloud sync.

Running with cloud sync disabled means you have no cloud backup if your save gets wiped.

So:

  • Use this flag only while you’re actively working around a startup crash.
  • Take it out the moment the game launches reliably again.
  • Do not leave it in permanently as a “just in case” setting. That was already the advice; treat it now as a firm one.

If your save has already been wiped, stop playing immediately, don’t start a new session or create a new save, and open a Forza Support ticket. Support can sometimes restore inventory, but level, XP and skill points are not recoverable.


What we thought was going on

The original diagnosis was that FH6 tries to connect to Playground’s cloud servers on startup, and when that handshake fails the game crashes before you see the main menu. The --disable-cloud-sync flag bypasses the handshake; --no-sandbox handles secondary permission issues that can appear alongside it.

For a genuine startup crash, that reasoning still holds and the fix still works for people.

Where it doesn’t hold: we originally suggested the crash risks save corruption because the game doesn’t shut down cleanly. Our later telemetry work found that the more common mid-session crash exits with code 0 — the “everything is fine” code — meaning the game doesn’t even register it as a crash. Different failure, different mechanism. If you’re chasing the mid-session crash, the save-corruption framing here doesn’t apply to it.

Why you might not have seen this fix already

Paco had been posting about it and claims Playground removed his original thread title and buried it in the troubleshooting subforum. Whether that’s accurate or not, the post wasn’t getting much visibility — which is why I reposted it here.

Big thanks to Paco

Community fixes like this are the reason I still check the forums even when I’m frustrated with a game. Paco stuck with it, documented what worked, and pushed to share it even when the thread got buried. If this saved your save file, go drop a thumbs up on his original Steam post — he deserves the visibility.


Still crashing?

If the launch option didn’t help, work through these in order:

  1. Confirm which crash you have using the triage at the top. Most people who land here from search actually have the shader leak.
  2. Read the shader leak investigation if you reach the main menu before dying. It includes the language-change workaround and an explanation of why the popular advice doesn’t work.
  3. File a ticket with actual data. “It crashes” gets a template reply. Specific telemetry gets escalated.

Changelog

27 July 2026

  • Added an update banner and symptom triage distinguishing the startup crash from the shader-optimization memory leak documented on 12 July.
  • Added a safety warning about running --disable-cloud-sync alongside the known FH6 save-wipe bug.
  • Noted where the original save-corruption reasoning does not apply to the mid-session crash.

3 July 2026

  • Minor corrections.

30 June 2026

  • Original post.

Related: Why Forza Horizon 6 Dies Three Minutes In · The State of Forza Horizon 6

Fediverse reactions

3 responses to “FH6 Keeps Crashing on Startup? This Steam Launch Fix Actually Works”

  1. […] hiccup. Restart the game, check that your Xbox/Steam entitlements have synced, and make sure the Gaming Services / Store are fully updated. It typically resolves on its own once the rollout […]

    Like

  2. […] relevant: FH6 Keeps Crashing on Startup? — a different crash, if yours happens before the main […]

    Like

  3. […] get in hand. Stability has been a recurring theme too — we’ve had to publish fixes for both startup crashes on Steam and the shader-related crash that kills sessions about three minutes […]

    Like

Leave a comment

Trending