Hades II deliberately has its own Saved Games root and should be backed up independently from the original Hades. The familiar Profile*.sav naming can tempt a user to assume cross-game compatibility, but SaveEditor treats the names as organizational similarity only. The safe workflow is to copy the Hades II folder as a set, label the backup with build/date, and restore only into the same game/storefront. Microsoft Store remains separate because its data is contained in WGS.
Choose the correct backup boundary
For Hades II, the researched PC save location is Windows: %USERPROFILE%Saved GamesHades II ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.HadesII_q53c1yqmx7phaSystemAppDatawgs. The known save file or folder pattern is Profile*.sav. Back up every Profile*.sav in the Hades II directory before experimenting with a slot. Preserve the whole WGS tree on Microsoft Store. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, Epic Games Launcher, Microsoft Store. Do not put Hades I Profile*.sav files in the Hades II directory. Microsoft Store uses a WGS container instead of the normal profile directory.
Account for cloud saves
Steam Cloud, Epic cloud, and Xbox Cloud are documented. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
Hades II uses a dedicated Saved Games/Hades II root and Profile*.sav naming. It is a separate save generation from Hades even though the profile concept is similar. Compatibility note: Profile naming similarity to the first Hades does not imply file-format compatibility. Treat the sequel as its own data format and restore only same-game snapshots. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If a profile does not appear, confirm the folder is Hades II rather than Hades, then check the storefront and cloud conflict state before replacing files again. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Reviewed against current PCGamingWiki Hades II save-location/cloud data.