Dragon Quest XI has an uncomplicated-looking Saved/SaveGames path, but the critical backup detail is edition identity. The original Windows release and Dragon Quest XI S are not merely storefront labels for the same executable, so SaveEditor does not collapse them into one compatibility claim. A good backup includes the full SaveGames folder plus a note of which edition created it. This prevents a perfectly valid save from being diagnosed as corrupt when the real problem is that it belongs to a different release.
Start with the least destructive explanation
When Dragon Quest XI progress appears missing, first verify the active PC location: Windows: %USERPROFILE%DocumentsMy GamesDRAGON QUEST XISavedSaveGames. Expected files/folders: Unreal Engine save files beneath SavedSaveGames; exact generated filenames can vary with slot/profile context.. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Back up the entire SavedSaveGames directory and label it with the exact game edition and build. Keep configuration/mod backups separately so a gameplay save can be restored without changing unrelated settings. 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. The 2018 PC release and Dragon Quest XI S are separate products with different data expectations. This hub documents the original Dragon Quest XI URL from the project plan. Cloud notes: Steam Cloud is documented; OneDrive can also affect Documents when backup is enabled. 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
The original Windows release uses an Unreal Engine Saved/SaveGames tree beneath Documents. It is distinct from later Definitive Edition products and should not be mixed across editions. Do not assume a save from Dragon Quest XI S or a console edition is compatible with this original PC release. Edition identity is part of the backup metadata. 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 progress is not detected after a restore, verify that the installed title is the same edition and that Documents/OneDrive points to the location you backed up. 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 Dragon Quest XI save location and cloud documentation.