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.
Which storefront context matters
Documented Hades II PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud, Epic cloud, and Xbox Cloud are documented. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: %USERPROFILE%Saved GamesHades II ; Microsoft Store: %LOCALAPPDATA%PackagesSupergiantGamesLLC.HadesII_q53c1yqmx7phaSystemAppDatawgs; the known file or folder pattern is Profile*.sav. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Back up every Profile*.sav in the Hades II directory before experimenting with a slot. Preserve the whole WGS tree on Microsoft Store. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
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. If progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Reviewed against current PCGamingWiki Hades II save-location/cloud data.