BetterFPS

Forza Horizon 6 Save File Corruption Patch Rolling Out: Protect Yours Now

The Forza Horizon 6 save corruption patch is rolling out today. Here's how to back up your save file manually and avoid data loss before the fix lands on your PC.

·BetterFPS Team
Forza Horizon 6 Save File Corruption Patch Rolling Out: Protect Yours Now

Playground Games is rolling out a hotfix for the Forza Horizon 6 save file corruption bug that's been wiping progress for some players over the past 72 hours. The patch is deploying today (June 17, 2026) across Xbox and Windows, but it won't retroactively restore deleted saves — and cloud sync can interfere with the fix if your local file is already corrupted.

If you haven't been hit yet, you need to manually back up your save file RIGHT NOW before the patch lands. The bug doesn't affect everyone, but if it hits your install mid-patch, you lose everything — hundreds of hours, every car, all your credits. Here's how to protect your file in under five minutes, then let the patch do its job safely.

What Causes the Corruption

The bug originates in how Forza Horizon 6 handles save-state writes during online freeroam session transitions. When the game attempts to serialize your garage data while simultaneously processing a server handoff (switching from one freeroam server instance to another), a race condition can corrupt the save header. The corrupted file then syncs to Xbox cloud, overwriting your clean backup.

The corruption manifests as either a total save deletion (the game thinks you have no progress) or a partial reset where your garage appears empty but your XP/credits remain. In both cases, the file is unrecoverable once cloud sync overwrites it. Playground's patch addresses the race condition that triggers the write error, but it does nothing for files that are already corrupted or already synced to the cloud in a bad state.

Cloud Sync is the Risk

The patch itself is safe, but if cloud sync pulls a corrupted file from Xbox servers during the patch install, you're done — the local clean file gets overwritten. That's why the manual backup + sync disable is critical. You're creating an air-gap until the patch confirms your local file is intact.

Manual Backup Steps (Do This First)

Before the patch installs on your system, you need to manually copy your save file to an external location and disable cloud sync. This ensures the patch can fix the local file without Xbox cloud overwriting it with a corrupted version.

  1. Close Forza Horizon 6 completely (check Task Manager to confirm no ForzaHorizon6.exe is running).
  2. Open File Explorer and paste this path into the address bar: %LOCALAPPDATA%\Packages\Microsoft.SunriseBaseGame_8wekyb3d8bbwe\SystemAppData\wgs — this is where Windows stores your Forza save.
  3. Copy the entire "wgs" folder to an external drive or a separate partition (NOT the same C: drive — if your SSD fails, both copies die). The folder is usually 500MB–2GB depending on your garage size.
  4. Open the Xbox app on Windows, go to Settings → General, and toggle OFF "Enable cloud saves for games." This prevents Xbox from syncing until you confirm the patch worked.
  5. Restart your PC. This flushes any pending sync operations and ensures the next boot pulls the patched game version cleanly.

After the restart, launch Forza Horizon 6. The game will apply the patch automatically if it hasn't already. Let it load your save — if your garage appears intact, the patch worked. If you see a blank save or missing cars, DO NOT continue playing. Exit immediately, re-enable cloud sync, and wait for Xbox to pull your last known good save from the cloud (assuming it wasn't corrupted there first — this is why the local backup is your true safety net).

Re-enable Cloud Sync After Confirmation

Once you've confirmed your local save is clean post-patch (all cars present, correct credit balance, no garage errors), re-enable cloud sync in the Xbox app. This pushes your clean, patched save to the cloud and overwrites any corrupted version that might be sitting there. Leave sync disabled permanently only if you never play on multiple devices — cloud sync is a lifesaver for hardware failures.

What If You're Already Corrupted

If the bug already hit you before the patch rolled out, your options are grim. Playground has confirmed they cannot restore individual saves — the corruption is local and the cloud backup is usually overwritten within minutes of the bug triggering. Your only recourse is the external backup you made (if you made one). If you didn't, you're starting from zero.

Check your external backup from step 3 above. If you copied the "wgs" folder before the corruption hit, you can manually restore it: disable cloud sync again, delete the corrupted "wgs" folder in %LOCALAPPDATA%, paste your backup copy in its place, and re-enable sync. The game will treat the restored file as your current save. If the backup is older than the corruption, you lose progress between the backup date and the bug hit — but it's better than losing everything.

Xbox Support Page

Microsoft's official troubleshooting guide for save file issues is at support.xbox.com — search "Forza Horizon 6 save corruption" for their latest recommendations. As of June 17, they're directing players to the manual backup process above and confirming the patch should prevent new corruption instances.
Forza Horizon 6 Best Settings
Optimized graphics and performance settings for every GPU
Run a Free Playbook
Get hardware-specific settings for Forza Horizon 6 and 200+ games
Patch Watch ($4.99/mo)
Auto-regenerated playbooks when patches change game performance

How the Patch Prevents Future Corruption

Playground's hotfix adds a mutex lock to the save-state write operation, ensuring the game finishes serializing your garage data before processing any server handoff. The race condition that caused simultaneous writes — one from the session transition, one from the autosave — can no longer occur. The patch also adds a checksum verification step before cloud sync, so even if a write error slips through, the game won't upload a corrupted file.

This doesn't make the game immune to ALL save corruption (drive failures, Windows crashes mid-write, etc.), but it closes the specific server-transition bug that's been wiping saves since launch week. If you still see corruption after the patch installs, it's a different issue — likely hardware (failing SSD) or OS-level (file permission conflicts). Run chkdsk on your game drive and verify NTFS permissions on the Packages folder.

Ongoing Backup Strategy (Automate It)

Manually copying the save file before every patch is tedious. Set up an automated backup using Windows Task Scheduler: create a daily task that copies %LOCALAPPDATA%\Packages\Microsoft.SunriseBaseGame_8wekyb3d8bbwe\SystemAppData\wgs to an external drive or NAS. This keeps a rolling week of saves in case corruption hits again or you want to roll back after a bad trading decision.

For extra paranoia, enable File History in Windows Settings → Update & Security → Backup, and point it at your external drive. File History snapshots every hour, so you'll have multiple restore points even if you don't notice corruption immediately. The wgs folder is small enough (under 2GB for most players) that hourly backups won't eat storage.

Performance Note

The patch adds negligible overhead — the mutex lock adds ~2ms to save writes, which happen every 90 seconds during freeroam (you won't notice). If you do see FPS drops after the patch, it's unrelated to the save fix — more likely a shader compilation issue or a settings reset. Run a fresh playbook if your frame rate tanks post-update.

Frequently Asked Questions

Frequently asked questions

Will the patch restore my already-deleted save file?▼
No. The patch prevents NEW corruption by fixing the server-transition race condition, but it cannot recover files that are already corrupted or deleted. Your only option for restoration is a manual backup you made before the bug hit. Playground confirmed they do not have server-side backups of individual player saves, so if the cloud copy is corrupted and you have no local backup, the save is gone permanently.
Do I need to disable cloud sync permanently or just during the patch install?▼
Just during the patch install and initial verification. Disable sync before the patch lands, copy your save externally, let the patch install, then launch the game to confirm your save is intact. Once you see your full garage and correct credits, re-enable cloud sync — this pushes the clean, patched save to Xbox servers and overwrites any corrupted version sitting there. Leaving sync disabled long-term means you lose the cloud backup safety net if your local drive fails.
Can I just rely on Xbox cloud saves instead of manual backups?▼
Not for this bug. The corruption syncs TO the cloud within minutes of occurring, overwriting your clean backup. By the time you notice the bug (next launch), the cloud save is already corrupted. Manual external backups (to a drive Xbox can't touch) are the only guaranteed restore path. Use cloud sync for normal play, but don't treat it as a corruption shield — it mirrors your local file, good or bad.
How do I know if my save is corrupted before launching the game?▼
You can't easily tell from the file itself without forensic tools — the wgs folder is a binary blob. The clearest signal is launching the game: if your garage is empty, credits are zero, or the game says "no save data found" despite hundreds of hours played, you're corrupted. The patch adds a checksum check that will flag corruption on load, but that only helps AFTER the patch is installed. Pre-patch, the only safe move is the manual backup.
Does this affect Xbox console players or just PC?▼
Both. The bug is in the game code (server-transition race condition), not the platform. Xbox console players should also back up saves, though the process is different: Settings → System → Storage → Manage storage → Copy to USB. The patch rolls out simultaneously across Xbox Series X|S and PC, and the same cloud-sync overwrite risk applies. Console players have slightly better odds because Xbox OS handles file writes differently than Windows, but the corruption still happens.
What if I play on multiple PCs? Which save file do I back up?▼
Back up the save from the PC you play on most (the one with the most recent session). Cloud sync should keep all your PCs in sync, but if one PC has a corrupted local file and syncs it to the cloud before the patch, all your other PCs will pull that corrupted version on next launch. The safest approach: disable cloud sync on ALL your PCs, back up the local file on your primary machine, let the patch install everywhere, then verify the primary PC's save is clean before re-enabling sync. That clean save will then propagate to the others.

Ready to see results?

Stop following generic guides. Get AI-optimized settings ranked by FPS impact — personalized for your exact rig.

Free · No signup · 15 seconds