Fast answer
Freeze the current state, record the symptom and version, copy the save folder where available, then try reversible checks before resets, reinstalls, or cloud-save changes. Never delete local or cloud data first.
Do this first
Save-safe order
- Stop repeated launches if progress appears to change.
- Record version, platform, world type, and host/client role.
- Make a separate PC save copy before file-level changes.
- Try the official reversible branch for the exact symptom.
- Escalate before the next action would overwrite the only good state.
01
The risk ladder
Start with observation, update checks, account checks, and a normal restart. Move to file verification or Gaming Services repair only when official support matches your platform.
- Low risk: version, restart, host/client comparison
- Moderate: official repair tools and file verification
- High: replacing saves or clearing local/cloud data
- Never first: deleting folders or using unverified downloads
02
When to stop
Stop when the next step would overwrite the only known-good save, move a shared world without its owner, expose personal files, or rely on an unverified tool. Preserve evidence and contact official support instead.
Evidence ledger
Sources checked
Official supportHow to Report a Grounded 2 IssueOfficial evidence and attachment requirements for useful support reports.
↗Official supportGrounded 2 Save File LocationOfficial Windows save directory used for a separate backup copy.
↗OfficialGrounded 2 Issue TrackerAuthoritative issue IDs and current status. Recheck the tracker before acting on a status label.
↗Official sources establish shipped features, issue status, and support steps. Cross-check and community sources are labeled and never treated as universal fixes.


