Some Forza Horizon 6 players are losing hundreds of hours of progress to a save-wiping bug. Here is what Microsoft and Playground are saying, the exact steps you should take right now, how the fixes are rolling out on Xbox and PC, and why it raises bigger questions about cloud saves and Quick Resume.
Forza Horizon 6 should be the kind of game you live in for weeks at a time. Instead, a subset of players on Xbox Series X|S and PC are living through a nightmare: saves that suddenly reset or vanish, wiping out hundreds of hours of cars, credits and festival progress.
Microsoft and Playground Games have now formally acknowledged the problem and started rolling out fixes, but the incident has cracked open a wider conversation about how much trust we can place in cloud saves and features like Quick Resume.
What exactly is happening to Forza Horizon 6 saves?
Reports began stacking up in late May from players on Xbox and PC whose profiles suddenly reverted to fresh starts or very old checkpoints. In some cases people lost 200 hours or more of progress. Others saw their garages and credits disappear after a crash, a Quick Resume resume, or a platform switch.
The official “Notice Regarding Lost Save Issues in Forza Horizon 6” on the Forza Support site confirms that there is a genuine bug. Microsoft says the root cause is still under investigation but appears to involve a combination of platform-level save handling and the way Horizon 6 talks to cloud storage.
Crucially, once a corrupted or empty save is uploaded to the cloud and synced across devices, it can overwrite the good version. That is why the support team is begging players not to keep playing on a “fresh” profile after a reset.
Microsoft’s recommended workarounds
Until the fixes fully land, Xbox and Forza Support are telling players to change how they interact with the game to reduce risk and preserve recovery options.
1. Disable Quick Resume for Forza Horizon 6 on Xbox Series X|S
Microsoft is treating Quick Resume as a major risk factor on console. To turn it off for Horizon 6:
Highlight the Forza Horizon 6 box art on your Xbox dashboard, in My Games & Apps, or in a pinned group. Press the Menu button on the controller, choose “Manage game and add-ons,” then open “Quick Resume settings” for the game and select “Disable Quick Resume.” This forces Horizon 6 to perform a clean launch and shutdown every time instead of being frozen and thawed in memory.
2. Always quit the game properly and stay online
On Xbox, use the dashboard button, highlight Forza Horizon 6, press Menu, and choose “Quit” rather than just suspending or flipping to another app. On PC, exit to the main menu and then close the application or use the in-game “Exit” option.
Microsoft also stresses staying connected to the internet while quitting. Give the game a short window to sync your save before powering down the console, closing the Xbox app on PC, or shutting off your router.
3. Do not keep playing after a reset or corruption
If you boot the game and see a new profile, missing cars, or obviously wrong progression, treat it as a red alert. Do not drive a test lap, do not complete a race, do not buy a car.
Instead, close the game immediately and file a ticket at the Forza Support site. The team says reporting the issue on the same day it happens gives them the best chance of finding a recent backup in their systems and rolling your save back to it. The more you play on a bad save, the more likely it is that the backend will treat it as your new normal.
4. Be careful when switching platforms or devices
Forza Horizon 6 is playable across Xbox consoles, the Microsoft Store version on PC, Steam, the Xbox app and cloud streaming. That flexibility makes sync timing more critical.
Support recommends always quitting completely on one device, then waiting a few minutes to let the cloud save finalize before launching on another device. Launching too quickly on a second platform can cause the older local save on that machine to win a sync conflict and overwrite newer progress.
5. Keep your system and services updated
On PC, Microsoft has already shipped a Gaming Services update intended to reduce the risk of save-loss incidents. Players are advised to confirm that the Gaming Services client is version 37.114.10001.0 or newer through the Microsoft Store.
On Xbox Series X|S, a system update focused on this issue has started rolling out and may not auto-install right away. You can manually check by going to Settings, then System, then Updates, and forcing your console to download the latest firmware.
Where the fixes stand on Xbox and PC
The response to the Forza Horizon 6 save bug is happening in stages.
On Windows PC, Forza Support notes that an update to the Gaming Services layer went live on June 11. This is not a traditional game patch you see in your library but an underlying component that manages sign-ins, entitlement checks and cloud saves. The goal is to prevent some of the failure cases that were causing profiles to revert or desync.
On Xbox Series X|S, Microsoft is addressing the problem at the operating system level. A console update began rolling out on June 12 with changes intended to make crashes, Quick Resume resumes and power-loss scenarios less dangerous for save data.
Playground and Xbox are still treating these as mitigations rather than a full postmortem. Players are being told that investigations are ongoing and that they are still collecting logs from affected profiles to understand every failure mode, particularly edge cases around network interruptions and low-storage crashes.
The important takeaway is that the risk should be smaller once your PC and console are on the latest system software, but it is not yet zero. The behavioral precautions above are still recommended.
What this exposes about cloud saves and Quick Resume
Forza Horizon 6’s situation is not just a “one bad bug” story. It highlights structural tensions in modern save systems.
Cloud saves promise convenience. You never think about memory cards or USB backup drives. You bounce between an Xbox in the living room and a PC at your desk, and your progress follows. Features like Quick Resume then layer on instant-resume comfort, letting you park a supercar mid-race, jump into another game or app, and come back later exactly where you left off.
The tradeoff is that a lot has to go right behind the scenes. The game has to decide when a session is authoritative, the platform service has to detect sync conflicts and resolve them correctly, and intermittent network conditions have to be handled without silently picking the wrong version of your save.
When a bug slips into that chain, the opacity becomes a problem. Most players never see a clear “this is the cloud version, this is your local version, which do you want?” dialog. Instead, sync happens quietly in the background, and if the wrong data wins, you only notice after your garage is empty.
Quick Resume complicates this further. By freezing a running game and restoring it later, it shortcuts normal startup and shutdown sequences, including some of the times a game would traditionally save and validate. If a title is not extremely conservative about when it flushes data or how it handles sudden context loss, you can get into states where the game thinks your progress is safe, but the cloud has not been told yet. A crash, power loss or network hiccup at the wrong moment can turn that gap into a full reset.
Forza Horizon 6 is not the first Xbox game to run into growing pains with Quick Resume and cloud saves, but it is one of the most punishing examples because of how long its progression arc is and how personal car collections feel.
What players can reasonably expect going forward
Microsoft’s messaging so far has focused on two promises: that the underlying bugs are being addressed, and that support will attempt to recover affected profiles where possible.
In practical terms that probably means:
Game and platform updates will continue to harden the save pipeline so that crashes and disconnects are less likely to produce bad data in the first place. Cloud services will lean more on server-side backups that let support staff roll individual accounts back to earlier safe checkpoints. Quick Resume heuristics may become more conservative for always-online games like Horizon 6, or certain titles may be flagged to avoid the feature entirely if they cannot be made robust enough.
For players, though, the lesson is that blind trust in “invisible” saves has limits. Until this incident is fully resolved, Horizon 6 owners on both Xbox and PC should treat a clean quit and a short wait for sync as part of their normal routine. Steam users may also want to double-check that Steam Cloud is enabled and, if they are particularly risk-averse, occasionally back up their local save folder.
Why this matters beyond Forza Horizon 6
The save-wiping bug hits so hard precisely because Horizon 6 is a flagship first-party release. When an Xbox Game Studios title shipping on Game Pass can lose hundreds of hours of progress due to a backend interaction, it forces the whole ecosystem to re-examine assumptions about how fail-proof these systems really are.
Live service racing games like Forza build player identity through long-term ownership of cars, paints, and achievements. A single catastrophic desync can undo years of that identity-building. That risk undermines the exact long-tail engagement that platforms and publishers depend on.
If Microsoft follows through with a thorough fix and transparent postmortem, Horizon 6 may yet become a turning point where cloud-save reliability and Quick Resume compatibility testing get the same level of scrutiny that performance and frame rate do today. Until then, the best defense players have is awareness, careful shutdown habits, and a willingness to temporarily sacrifice instant-resume convenience for the security of their progress.