PC Game Save Backup and Restore: A Safe Plan Before Reinstalling a Compromised Game

Back up your progress without assuming the copy is clean: stop launching the suspect game, identify the exact save location, preserve a separate copy, resolve any Windows infection, reinstall from a trusted source, and restore only the selected save files. A pre-infection backup stored away from the affected PC is the strongest option. A current local copy can preserve newer progress but may have been present during the compromise, while a cloud copy can be older or trigger an overwrite conflict. A game reinstall by itself does not clean an infected Windows installation.

What does “compromised” mean for a game save?

“Compromised” can describe three different situations, and the safe recovery plan depends on which one you face:

• Tampered or malicious game download: the installer or game files may be untrustworthy, even if Windows itself has not been infected.
• Malware-infected Windows installation: malicious software may have changed files beyond the game directory, including backups that were connected during the infection.
• Corrupted save: the executable may be fine, but one or more save files may be damaged. Corruption is not evidence of malware.

A security scan does not certify a save as safe. Microsoft warns: “Backups that are on your PC during an infection might have already been modified by the malware.” Treat a save copied from the suspect machine as a recovery candidate, not as a clean artifact. Do not restore executables, installers, scripts, mods or unknown files from the old game folder as though they were saves.

That distinction also affects what you can reasonably recover. If only a download was tampered with and Windows is otherwise clean, the main task is obtaining a trustworthy installer and determining which save version to use. If Windows may be infected, every file that was writable or connected during the incident has uncertain provenance. If the problem is ordinary corruption, a previous version or cloud conflict may be enough, but replacing a damaged file blindly can destroy the only readable copy. Keep the original and work from copies.

What should I do before copying anything?

Do not start the suspect game to force a cloud upload or create one more save. First decide whether the problem is limited to the game files or could affect Windows.

1. Disconnect the suspect game from normal use. Close the game and launcher. Do not run the suspect installer, executable, mod manager or script. Do not launch it merely to see whether the save still loads.
2. Look for an older, independent backup. Check an external drive, network location or backup service for a copy created before the suspected compromise. Record its date and location without opening files on the affected PC. A backup that was disconnected before the incident has stronger provenance than one that remained mounted.
3. Assess Windows. If malware is suspected, use Windows Security for a full scan. Microsoft also documents an offline scan for threats that survive normal Windows operation. If the infection persists, follow Microsoft recovery guidance, which can include a clean Windows installation.
4. Keep removable storage isolated. After copying, disconnect the backup drive. Scan removable media before using it on a clean system. Do not reconnect it simply to let a launcher search for saves.

Uninstalling and reinstalling only the game is not a malware-removal procedure. Resolve the operating-system compromise first, then install the game from its legitimate platform or the developer. A successful launch after reinstalling does not prove that unrelated malware has been removed.

Where are PC game saves stored?

There is no universal save directory. The developer’s support page is the authority for a particular title; the folders below are places to check, not guarantees.

Common Windows locations

• Documents
• DocumentsMy Games
• Saved Games
• %APPDATA% (the roaming AppData folder)
• %LOCALAPPDATA%
• AppDataLocalLow

Search for a folder named after the game or publisher, and inspect recently modified files while the game remains closed. Note extensions and companion files; some games keep profiles, settings and save slots together. A file with an unfamiliar extension is not automatically disposable, and a file named “save” is not automatically the complete save set. Do not rename or edit files merely to make them look like saves.

Some titles use more than one directory: one for campaign slots, another for profiles or settings, and a launcher directory for synchronized metadata. Copy the complete set that the developer identifies, preserving subfolders and timestamps. If the title supports several editions, check whether the path differs between standard, deluxe, remastered or test builds. Exact extensions, encryption and account binding remain game-specific.

Epic Games Launcher locations

Epic lists a launcher-local location under %LOCALAPPDATA%EpicGamesLauncherSavedSaves, followed by account and game folders. The launcher’s local path does not prove that every title uses those files. If the expected save is still missing, Epic advises contacting the game developer. A store-page cloud-save feature tag indicates capability, not that every local file or profile is synchronized.

Steam locations

Steam documents local cloud files under the Steam installation’s userdata{steamID}{appID} directory. The app and account folders identify a title and user, but individual games can also store saves in Documents or AppData. Confirm the title’s documented path before copying. Do not assume that an app-ID folder contains the only local copy.

How do I make a preservation copy safely?

Copy only identified save data while the game is closed, and keep the copy unchanged. An external USB drive is an optional destination; it does not sanitize files and should be disconnected after use.

1. Create a clearly named destination. Use a separate folder such as GameName_save-recovery_2026-10-30 on storage that is not the suspect game directory. An external USB backup drive for PC game saves is one practical category of destination; no particular capacity or model is required by the procedure.
2. Copy the complete save set. Include the files and subfolders the developer identifies, rather than selecting one file by guesswork. Do not include executables, installers, scripts, mods or unknown binaries. If a profile and slot directory are documented together, preserve both.
3. Record provenance. In a text note, write the game title, account or profile, platform, original path, copy date and whether the copy predates the suspected compromise. Also note whether it came from a local folder, an offline backup or a cloud conflict choice.
4. Preserve the original. Copy rather than move. Do not allow a launcher or cloud prompt to overwrite the preserved folder. Make separate folders for local and cloud candidates instead of merging files with identical names.
5. Disconnect the destination. Eject the USB drive or disconnect the network location until the Windows system has been assessed and cleaned. Scan removable media before reconnecting it to a clean computer.

Windows File History can use external or network storage, and it can restore files to a different location. A save folder outside File History’s default libraries may require explicit inclusion. Restoring to a temporary folder first lets you inspect and compare without overwriting a newly created clean save. File History is a versioning mechanism, not proof that every retained version predates an infection; check dates and keep the untouched copy.

Which backup should I restore?

Choose by provenance first, then by completeness and compatibility. None of these choices is automatically safe merely because it exists.

Version	Date relative to compromise	Independence from affected PC	Typical advantage	Main risk
Pre-infection off-PC backup	Created before the suspected infection	Stored away from the machine	Strongest provenance	May omit recent progress or settings
Current manual copy	Unknown or after the suspected infection	Usually on, or copied from, the affected machine	May contain the newest progress	Could have been modified during compromise
Platform cloud version	Depends on the last successful sync	Held by the platform, but tied to the game account	Can survive local disk loss	May be older, incomplete or offered in a conflict prompt

Before selecting a version, verify that it contains the expected slots, profile and settings, and that it belongs to the same platform account. Compare the timestamp with the suspected incident and with your last known play session. A pre-infection copy is generally the most defensible starting point even if it costs some recent progress. A current copy may be the only way to recover newer work, but it needs particular caution because it may have been present during the compromise. A cloud copy is not a security certification; it is simply another version whose date and contents must be understood.

How do Steam, Epic and GOG cloud saves affect recovery?

Cloud behavior is game-dependent. Store-page support tags and launcher settings indicate capability, but the developer chooses which files synchronize and when. A cloud service can preserve a version after local disk loss, yet it can also overwrite the version you intended to keep.

Steam Cloud

Steam lets developers select the files used by Cloud, and synchronization can be controlled per game or globally. Steam warns that starting a game through a failed-sync state can create conflicts and lost progress. Keep a separate local copy of the preferred version before accepting a conflict resolution. Steam support also says it may not be able to recover lost saves, so do not treat a support ticket as a guaranteed rollback.

Do not confuse Steam’s game-installation backup with a save backup. Steam states: “Backups for Valve created games will not include saved games, custom multiplayer maps or configuration files.” A copied installation can therefore be useful for reinstalling program files while still failing to preserve campaign progress.

Epic cloud saves

Epic’s store-page Features tags identify titles that support cloud saves. Its conflict dialog can present local and cloud versions; selecting an older file can lose unrecoverable progress. Preserve the local version separately before choosing either option. Launcher settings and labels can differ between legacy and preview versions, so follow the controls shown by your installed edition rather than a menu path from an older guide. If a title’s save remains missing, Epic directs players to the developer because the game controls the actual file selection.

GOG automatic synchronization

GOG’s developer documentation describes automatic synchronization where a title implements it. The specified local directory is synchronized when the game launches or closes. A title without that implementation will not gain cloud recovery simply because the launcher is installed. Before launching after restoration, keep a manual copy so an automatic upload cannot replace your preferred version immediately.

How do I reinstall and restore without reintroducing the problem?

Restore only after the Windows environment is addressed and the game has been installed from a trusted source. Keep a copy of any newly generated clean save before replacing it.

1. Complete security remediation. Run the appropriate Windows Security scans. For persistent threats, follow offline-scan or system-recovery guidance; a clean Windows installation may be warranted. Do not copy saves onto a machine that you still suspect is actively compromised.
2. Install the game legitimately. Use the official launcher or developer distribution. Do not reuse the suspect installer, executable, crack, script or mod package. Reinstalling into a new directory does not make an untrusted installer trustworthy.
3. Launch once, then exit. Let the clean game create its documented save directory and profile. This confirms the account and path without immediately replacing anything. If the launcher begins synchronization, pause and preserve the newly created folder first.
4. Back up the new empty or starter save. Copy it to a temporary folder so you can undo the next step. This gives you a clean baseline for troubleshooting.
5. Place selected saves in the documented path. Restore only the assessed save files from the pre-infection backup when available. Preserve the folder structure and do not rename files unless the developer instructs you to. Do not mix slots from unrelated profiles.
6. Start the game offline if practical. Check whether the expected progress appears before enabling synchronization. If the game requires an online account, sign in only after confirming that the local files are in place and that you have preserved both candidates.
7. Handle cloud prompts deliberately. Compare timestamps and contents. Keep both versions before choosing local or cloud, and never select an option simply to dismiss the dialog. An older conflict choice can permanently discard newer progress.
8. Verify several saves. Open more than one slot or profile, confirm settings and progression, and make another clean backup after the game successfully loads. If the game writes a new format on first launch, retain the pre-conversion copy.

What can go wrong during recovery?

The save folder is empty

Check every candidate Windows location and the launcher-specific path, then consult the developer’s instructions. The title may use a different account profile, store data in a protected directory or keep only cloud data. Do not infer that an empty folder means the progress is gone until those possibilities are checked. Also verify that Windows is showing hidden items when the developer’s instructions require it, without changing files just to test a theory.

The launcher reports a cloud conflict

Stop at the conflict screen. Copy both local and cloud versions to separate folders, record their timestamps, and compare the save slots. Choosing an older version can permanently discard newer progress. If the dialog offers only one choice, cancel if possible and preserve the local files before retrying.

The clean game rejects the files

Confirm the game edition, platform account, region or profile, and exact folder structure. Updates can change formats, and some saves are encrypted or account-bound. If the developer documents a migration utility, use that rather than editing binary files. Never download an unofficial “save fixer” and run it on an uncertain system merely because the filename looks compatible.

The game loads but progress is missing

Look for multiple profiles, slots or campaign directories. Restore the complete identified set rather than one file, and test with synchronization paused so a cloud copy cannot immediately overwrite the local version. Check whether the game is displaying a different account, edition or profile than the one that created the backup.

You are unsure whether the PC is clean

Stop restoring files and return to Windows remediation. Do not treat successful game startup as evidence that malware is gone; the game can run while an infection remains elsewhere on the system. If Microsoft’s scans continue to report threats, follow its recovery guidance instead of repeatedly reinstalling the game.

How do I keep future saves recoverable?

• Enable cloud saves only after confirming what the title actually synchronizes.
• Keep periodic, versioned copies outside the game directory and away from the PC.
• Label copies with the game, account, platform and date.
• Retain at least one copy from before any suspected compromise or major mod installation.
• Test that a backup contains complete slots by restoring to a temporary location, not by overwriting the active save.
• Scan removable media before reconnecting it to a clean computer.
• Keep local and cloud candidates in separate folders so an automatic sync cannot silently merge them.
• After major updates or moving between editions, make a fresh copy and note the version that created it.

How we chose the recovery priorities

The sequence prioritizes provenance, isolation and reversibility: an off-PC copy made before the suspected infection comes first; a current manual copy is preserved for possible recovery but is not treated as clean; cloud versions are compared before synchronization; and restoration happens only after Windows remediation and a trusted reinstall. Exact file names, extensions, account binding and restore commands remain game-specific. No scan, cloud sync or reinstall can promise recovery of every save.

Frequently Asked Questions

Can achievements be restored by copying save files?

Not necessarily. Many achievements are recorded by a platform account or server rather than in the local save, so a restored campaign may not recreate achievement history. Check the game’s account and achievement documentation separately.

What if the game encrypts or signs its saves?

Keep the entire documented save set intact and use the same account and game edition that created it. Renaming, editing or mixing files from another profile can make an otherwise valid backup unreadable.

Can I move a save between Windows user accounts?

Sometimes, but permissions and account-bound identifiers can prevent it. Restore into the target user’s documented profile path, preserve the original copy, and expect the developer’s support process to be necessary for account-linked formats.

How long should I keep the old recovery copy?

Keep it until the clean installation has loaded the required slots and you have made a new, verified backup. Retaining the untouched copy longer is useful if later cloud synchronization or updates reveal a compatibility problem.

Is an external USB drive enough to make a save safe?

No. It provides separation from the game directory, but it does not sanitize files or prove they predate an infection. Disconnect it after copying and scan the removable media before using it on a clean system.

Should I force a cloud sync before uninstalling?

No. Do not launch the suspect game just to upload a save. A failed or incorrect sync can overwrite the better version or create a conflict. Preserve the local files first and compare cloud and local timestamps deliberately.

Does reinstalling Windows guarantee that every save can be restored?

No. A clean Windows installation addresses the operating-system environment, but it cannot recreate missing, corrupted, encrypted or account-bound saves. Use the best documented backup you have and keep every candidate until verification is complete.

What if I do not know the game’s exact save path?

Start with the developer’s support instructions, then check Documents, Documents\My Games, Saved Games, %APPDATA%, %LOCALAPPDATA% and AppData\LocalLow. Steam and Epic also document launcher-specific locations, but those paths are candidates rather than guarantees.

The Bottom Line

Preserve first, trust later: keep an untouched pre-infection copy when possible, isolate current files, resolve Windows threats, reinstall from a legitimate source, and restore only after comparing local and cloud versions.