Older Garlic versions break some save imports
Risk of data loss✓ ProvenWhat you see
- A PS4 save shows as corrupted after you import it with Garlic.
- Importing an encrypted save from USB fails with "Not a decrypted save folder", or a game with several save slots mixes them up.
What it means
Garlic SaveMgr's release notes document specific save import bugs that later releases fixed: PS4 saves written with the wrong user ID, encrypted saves from USB that would not import, and games with several save slots. If you imported with an older version, your problem may be one of these. The fixes only cover these documented bugs.
What to do
Export a backup first
Since v1.6, Garlic can dump decrypted saves to a USB drive. Do this before you import anything again.
PS4 saves and the user ID: v1.6
The v1.6 notes say earlier versions wrote the user ID at the same spot for every save, which could corrupt PS4 saves, and that PS4 saves now import to the correct folder.
Encrypted saves from USB: v1.62b
v1.62b fixes importing encrypted PS5 saves from USB, which failed with Not a decrypted save folder. It also supports importing both encrypted and decrypted USB saves, for PS4 and PS5.
Games with several save slots: v1.14
v1.14 fixes the save slot identity and the account ID written for games with several save slots.
Pick the right user and import a test copy
Choose the user in the user selector (added in v1.6) and import one copy first. The v1.6 notes say the USB import has overwrite protection.
When to stop
It only fixes these bugs
These releases fix bugs in the tool. They do not bring back progress that was already lost, and they do not prove that every broken save was caused by one of these bugs. Version names are not in number order: on the releases page v1.62b comes before v1.6.
Sources
- Garlic save manager releases (Oct 31, 2026)
Last reviewed: Oct 31, 2026
← Troubleshooting