Dead Cells has several legitimate Windows save roots depending on storefront, which makes timestamps and launcher context more useful than the filename alone. Steam users should preserve app ID 588650 remote data; other editions may write under the install directory or LocalAppData. The save set also includes customGameData JSON separate from user_*.dat. SaveEditor recommends backing up both categories so a restored profile does not silently lose custom-mode configuration.
Start with the least destructive explanation
When Dead Cells progress appears missing, first verify the active PC location: Windows: Steam: <Steam-folder>userdata<user-id>588650remote ; Microsoft Store: %LOCALAPPDATA%PackagesMotionTwin.DeadCellsWin10_rtjy889c6zgtgLocalCacheLocalMotionTwinDeadCells ; other desktop builds may use <path-to-game>save. Expected files/folders: user_*.dat and customGameData_*.json. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Copy the full active save directory, including user_*.dat and customGameData_*.json. On Steam, back up the complete 588650remote folder. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: Steam, GOG, Epic Games Launcher, EA app, Microsoft Store. The exact path depends strongly on storefront. Preserve both user_*.dat and customGameData_*.json if you want the same profile plus custom-game settings. Cloud notes: Steam Cloud, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
Dead Cells stores player data and custom-game configuration separately. Steam uses app-ID remote storage, while other desktop releases can use the installation save directory and Microsoft Store uses package-local/WGS-style storage. A user_*.dat file can restore player progress without restoring custom-game JSON, so a partial copy may look inconsistent even when the main save loads. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
If the wrong profile appears, check whether the game is using Steam remote, LocalAppData, or an install-folder save. Then compare timestamps before overwriting anything. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Reviewed against current PCGamingWiki Dead Cells save paths and file patterns.