Yakuza: Like a Dragon separates PC save storage by storefront more clearly than many games: standard/Steam, GOG, and Microsoft Store each have different roots. That means a generic instruction such as “copy the Sega folder” is too broad. SaveEditor records the user-ID level and the GOG-specific suffix so a backup can be put back into the environment that created it. Microsoft Store remains a WGS container and is not described as file-compatible with the normal AppData layout.
Choose the correct backup boundary
For Yakuza: Like a Dragon, the researched PC save location is Windows: Steam/Windows: %APPDATA%SegaYakuzaLikeADragon<user-id> ; GOG: %APPDATA%SegaYakuzaLikeADragon_GOG<user-id> ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.Yazawa_s751p9cej88mtSystemAppDatawgs<user-id>. The known save file or folder pattern is User-ID-specific save records inside the active storefront directory.. Back up the complete storefront-specific user-ID folder. Do not flatten files from GOG and Steam into one Sega directory because each edition has its own expected root. 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, GOG, Microsoft Store. GOG deliberately uses a different YakuzaLikeADragon_GOG root. Microsoft Store data is not a normal AppData file set.
Account for cloud saves
Steam Cloud, GOG Galaxy 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
Steam/standard Windows and GOG use separate Roaming AppData roots, while Microsoft Store uses WGS. The account-specific subfolder is part of the save location and should be preserved. Compatibility note: Cross-store copies are not guaranteed by identical game content. The WGS edition in particular should be treated as a separate container until a tested transfer workflow is available. 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 progress is missing, confirm the storefront and user ID first. Then check whether the launcher restored cloud data after the local folder was changed. 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 Yakuza: Like a Dragon save paths and cloud-sync table.