Vance on Gaming

Your Save File Is One Bad Patch Away: The 20-Minute Backup Routine I Use Before Every Big Update

Elias VanceBy Elias Vance
pc gamingsave filessteam cloudgog galaxywindows backupconsumer guide

Your Save File Is One Bad Patch Away: The 20-Minute Backup Routine I Use Before Every Big Update

Gaming desk with save folder audit on screen

If you are 40 hours deep into an RPG and still trust one cloud sync toggle with your entire run, you are gambling.

I used to write bug reports for a living. Corrupted state after updates is not rare, and cloud conflicts are where progress goes to die when people click too fast.

This is the no-nonsense routine I run before major patches, driver swaps, or launcher reinstalls. It takes about 20 minutes and it protects your time.

Why this works (and why cloud-only doesn’t)

Steam Cloud and GOG Cloud are useful, but both systems are still sync systems first, not magic data recovery systems. If bad data syncs, it can sync everywhere.

Valve’s Steamworks docs are explicit: cloud files are synchronized around launch/exit and users can disable sync globally or per game. That is convenient, but it means you need a local fallback when a conflict appears or a bad save gets uploaded.

GOG’s developer docs describe the same broad behavior: automatic syncing on game launch/close for configured save directories.

So your defense should be layered:
  1. Launcher cloud sync for convenience.
  2. Local versioned backup for recovery.
  3. One offline copy before risky changes.

The 20-minute pre-update workflow

Step 1 (4 minutes): Locate the save path before you touch anything

Find where your current game actually writes saves. Do not assume.

Common Windows paths:
  • %USERPROFILE%\\Documents\\My Games
  • %USERPROFILE%\\AppData\\Local
  • %USERPROFILE%\\AppData\\LocalLow
  • %USERPROFILE%\\AppData\\Roaming
  • %USERPROFILE%\\Saved Games

Those locations align with the standard root paths used by Steam Auto-Cloud documentation, which is why saves commonly end up there.

If the game is weird, check its known save location first, then continue.

Step 2 (5 minutes): Make a manual snapshot folder

Create a dated local backup before patching:

 
# PowerShell
$src = "$env:USERPROFILE\\Documents\\My Games\\GAME_NAME"
$dst = "$env:USERPROFILE\\Desktop\\SaveBackups\\GAME_NAME_$(Get-Date -Format yyyy-MM-dd_HHmm)"
New-Item -ItemType Directory -Force -Path $dst | Out-Null
Copy-Item -Recurse -Force $src $dst

No compression. No fancy tool. Just a clean copy you can restore quickly.

Step 3 (5 minutes): Turn on versioned local backup

Use Windows File History for your save parent folders. Microsoft still supports it on Windows 11 through Control Panel and it can continuously keep historical copies.

Minimum setup:
  1. Connect external SSD/HDD.
  2. Open Control Panel > System and Security > File History.
  3. Enable File History.
  4. Include your save folders in a library if they are outside defaults.

If today’s save is bad, version history gives you a rollback point instead of a full restart.

Step 4 (3 minutes): Cloud conflict discipline

When a launcher shows a cloud conflict prompt, stop and back up both sides first.

Do not click through on autopilot.

Rule:
  • If timestamps look wrong or you switched machines recently, copy local saves out first, then choose a side.
  • If unsure, preserve local, export snapshot, and test load in-game before overwriting anything.

One rushed click can wipe the only good state.

Step 5 (3 minutes): Keep one off-device copy

At least once per week, copy your latest SaveBackups folder to external storage. If you already use OneDrive, version history can also restore earlier file versions, which is helpful when corruption is discovered late.

The point is simple: if your OS install, launcher cache, and live save all go sideways, you still have a clean copy.

My blunt policy (that has saved me multiple runs)

I never apply major updates without a fresh snapshot.

I never trust a single sync source.

And if a game repeatedly corrupts saves after patches, it loses wallet-to-value score immediately, no matter how pretty the trailer looked.

Your hours are the expensive part. Storage is cheap.

Quick checklist you can paste into your notes app

  • Confirm real save path.
  • Copy dated manual snapshot.
  • Verify File History is active.
  • Apply update.
  • Launch and load save.
  • If broken, restore from local version/snapshot.

That is it. 20 minutes of prep beats 20 hours of replay.

Sources