Skip to main content

Upgrading to 1.9

Upgrade this device​

  1. Exit the game and quit Game Save Manager from the tray.
  2. Back up the existing configuration and save directories. Older versions usually use GameSaveManager.config.json and save_data; include any custom locations.
  3. Install the new version and keep application data.
  4. Start the application and check the game list, save locations, and snapshot history.

Older configurations convert automatically. Existing ZIP snapshots remain readable.

An older installation location that uniquely matches a game becomes that game's installation directory on the corresponding device. Locations that need a choice remain in Settings → Auto Scan → Unassigned installation folders. You can later change a game's directory in View managed files.

Upgrade local older backups​

Open Settings → Backup settings → Upgrade older backups to review the count and estimated extra space, then select Start upgrade.

  • Upgraded archives have a timestamp and random suffix in their filenames. Extract them to find the saves and recovery instructions. Snapshot history, notes, ancestry, and current snapshot markers are preserved.
  • Pausing or leaving the page stops after the current archive. Reopen the page to continue. The upgrade reads backup files without changing live game saves.
  • Missing, damaged, or unassociated archives stay pending while other archives continue. Choose an undamaged copy of that same backup from another device or disk, or confirm the corresponding save entry, then retry. A newer backup cannot replace it. Without a copy, leave the item pending.
  • Originals remain in .rgsm-upgrade/originals inside the backup directory. Once you have checked the upgraded backups, select Clean up originals. Copies you selected manually are not deleted.

This action upgrades files already on this device. It does not download or replace older cloud copies. Internal format upgrades of existing 1.9 Cloud Libraries are handled separately.

Upgrade the Cloud Library​

  1. Back up the cloud data and update every participating device to a compatible 1.9 version.
  2. Open Cloud sync and select Upgrade to the new library when prompted.
  3. Once complete, connect the other devices to the same cloud location.

Legacy cloud contents are retained. Future synchronization uses the new library.

If an upgrade is interrupted, use the resume action. If the library is incomplete, preserve its contents and submit the logs.

Roll back​

Save a separate copy of any progress made after upgrading, then restore the complete pre-upgrade backup using the matching older application version.