On Windows, both PCGamingWiki and SteamDB identify %LOCALAPPDATA%\MortalShell2\Saved\SaveGames as the active save directory. Close the game, copy the whole folder, verify the copied files and timestamps, then try Recover Save if the load menu offers it. SteamDB records WorldState_*.sav and MetaSaveGame.sav in Steam Cloud, so preserve the local state before choosing either side of a cloud conflict.
Protect the evidence before recovery
The directory, file patterns and recovery control come from different sources. Keep them separate when deciding what is safe to change.
%LOCALAPPDATA%\MortalShell2\Saved\SaveGames is listed by both PCGamingWiki and SteamDB.
SteamDB lists WorldState_*.sav and MetaSaveGame.sav under the same SaveGames path.
Try the in-game control only after preserving the original directory. It may return an earlier state.
Compare timestamps and expected playtime. Cancel first if you cannot identify the wanted copy.
How this was checked
Evidence and limits
Method: Cross-checked the Windows path against PCGamingWiki and SteamDB's current Steam Cloud configuration, then limited recovery claims to the developer's known-issues post and Week 1 notes.
Evidence boundary: The file locations and cloud patterns are documented; this site cannot inspect a player's private save or guarantee that Recover Save contains a usable generation.
Read the full editorial standard →Do this first
- Exit Mortal Shell II and wait for the game process and Steam synchronization to finish.
- Open %LOCALAPPDATA%\MortalShell2\Saved\SaveGames and copy the entire folder to a dated location outside the game directory.
- Verify that the copy contains files, compare its file count and preserve the timestamps.
- Install pending updates, then try Recover Save from the load screen if it is available.
- Check the recovered character, playtime, inventory and checkpoint before continuing.
- Exit normally and create a second dated backup while keeping the untouched pre-recovery copy.
What Week 1 protects
The patch changes how saves are written so an interrupted write should no longer destroy the only usable save. Treat that as protection for updated builds, not proof that every pre-update or already-corrupted slot can be restored.
Recovery comes before file edits
The official known-issues thread specifically points players with a loading crash to Recover Save. That built-in path should be attempted before manual deletion because it preserves the game's own recovery logic.
What Steam Cloud is synchronizing
SteamDB's current user-file configuration lists WorldState_*.sav and MetaSaveGame.sav in MortalShell2/Saved/SaveGames, including the Windows AppData location. That corroborates the sequel-specific path and shows why a local rollback can meet a different cloud state. Steam Cloud is synchronization, not guaranteed version history.
- Screenshot a cloud-conflict prompt before choosing
- Compare timestamp, expected playtime and the last device used
- Cancel and preserve both accessible states if the choice is unclear
Verify the backup before relying on it
A completed copy operation is not enough. Open the dated destination, confirm files are present, compare the file count with the active folder and keep the original timestamps. Do not test the only backup by moving it over the live folder; duplicate it first if a manual restore is necessary.
If Recover Save is missing or does not work
Do not start a new game in the affected slot or replace files with an unverified download. Keep the untouched backup and record whether the slot is absent, crashes during loading, or loads older progress. Include the installed build and platform when seeking help through the linked official bug-report thread. These are different failure states; a missing recovery option is not proof that a recoverable copy exists.
- Do not rename or delete unfamiliar save files by trial and error
- Do not resolve a cloud conflict by choosing a copy whose contents you have not preserved
- Share save files only through a support channel you have verified
Make a reversible PC backup
A useful backup is a copy made while the game is closed, stored outside the live MortalShell2 folder and named with the date and build. Copy the whole SaveGames folder so companion files stay together. This Windows path does not apply to PlayStation or Xbox; do not use PC file instructions for console storage.
- Keep at least one pre-troubleshooting copy
- Cloud synchronization is not a substitute for a separate preserved copy
- Restore only after documenting which copy you are using
Settings files are not save slots
The launch known-issues thread mentions deleting two settings files for input or settings corruption. That is a different workaround for a different symptom. Do not treat it as a general save repair, and never delete the whole SaveGames directory without a backup.
Evidence log
Sources checked
External sources are linked for verification. Community reports describe symptoms and are not treated as universal fixes.
OfficialGlobal release known issuesOfficial Recover Save recommendation for loading crashes.
↗PlatformThe Week 1 UpdateOfficial interrupted-save protection and save-loading crash changes.
↗SpecialistMortal Shell II PCGamingWikiCommunity-maintained technical reference for the Windows SaveGames directory and Steam Cloud support.
↗PlatformMortal Shell II Cloud SavesSteam metadata view listing the cloud-synced paths and WorldState/MetaSaveGame file patterns.
↗Found a build mismatch?
Help keep this page current.
Send the page URL, platform, pause-menu build string, and a reproducible observation through the corrections desk. Game bugs still belong in the official developer channels.
Open corrections guidance →