Seeing a "Save data corrupted" notification in Ryujinx can be heart-wrenching, especially after investing dozens of hours into a complex RPG or a high-stakes adventure. This error typically stems from interrupted write processes, file permission conflicts, or hardware-level data loss. However, a corrupted message does not always mean your progress is gone forever. By following systematic recovery procedures, you can often salvage your data or roll back to a functional state.

Immediate Action Required Before Troubleshooting

The moment you encounter a corruption error, stop all interaction with the Ryujinx emulator. Do not attempt to save the game again, do not restart the game multiple times hoping the error will disappear, and absolutely do not click "Delete Save Data" if the game prompts you to do so to start fresh.

Every time a game attempts to access a corrupted file, there is a risk of the emulator overwriting the remaining healthy data blocks with null values. Your first and most important step is to create a manual backup of the current state, even if it is corrupted.

  1. Open the Ryujinx interface.
  2. Right-click the game title in your library list.
  3. Select Open User Save Directory.
  4. Navigate up one level in the file explorer so you can see the folder named with a hexadecimal string (e.g., 0000000000000001).
  5. Copy this entire folder to an external drive or a separate folder on your desktop labeled "Corrupted Backup [Date]".

Having this backup ensures that if a recovery method fails, you haven't lost the original data that might still be salvageable by more advanced tools later.

Identifying the Location of Ryujinx Save Files

Understanding where Ryujinx stores your progress is crucial for manual intervention. The emulator utilizes a virtual filesystem that mimics the Nintendo Switch’s internal storage (BIS).

Windows Operating Systems

On Windows, the default path is typically located within your user profile's roaming data. You can access it by typing %AppData%\Ryujinx\bis\user\save into the Windows Explorer address bar. Inside this directory, you will find folders named after the User ID associated with your Ryujinx profile, and within those, subfolders named with the Title ID of each specific game.

Linux and Steam Deck

For Linux users, especially those using the Steam Deck, the path depends on whether you are using a Flatpak version or a standalone binary. For Flatpaks, check: ~/.var/app/org.ryujinx.Ryujinx/config/Ryujinx/bis/user/save For standalone builds, it is usually found in: ~/.config/Ryujinx/bis/user/save

If you are using EmuDeck, the saves might be symlinked to your SD card under Emulation/saves/ryujinx/saves/. Ensure your SD card is properly mounted and not formatted in a way that limits file permissions (like exFAT in some Linux environments) which can cause corruption.

How to Restore Corrupted Saves Using Windows Shadow Copies

If you are on Windows and have "System Protection" enabled, you might have access to a built-in feature called Shadow Copies. This is often the most reliable way to recover a save file that was working 24 hours ago but is now showing as corrupted.

Accessing Previous Versions

In the Open User Save Directory folder, right-click the empty space within the folder or the specific main file (if the game uses a single file structure). Select Properties and look for the Previous Versions tab.

If Windows has indexed your AppData folder, you will see a list of timestamps. Select a version from before the corruption occurred, click Restore, or better yet, click Open to copy that specific healthy file to a different location. In our testing, this method saved a 60-hour The Legend of Zelda: Tears of the Kingdom save where a sudden power outage occurred during an autosave.

Why Previous Versions Might Be Empty

If the "Previous Versions" tab is empty, it means your Windows installation is not configured to take snapshots of your user data folders. While this won't help you now, enabling "File History" or "System Protection" for your C: drive is highly recommended for future gaming sessions.

The Manual Save Injection and Clean Start Method

Sometimes the corruption isn't in the game data itself but in the metadata Ryujinx uses to track the save. A "Clean Start" can often force the emulator to re-index the files.

Step-by-Step Injection Process

  1. Move all files out of the current save directory (where the main or private files are located) into a temporary folder on your desktop.
  2. Launch the game in Ryujinx. The game should act as if it is being played for the first time.
  3. Play through the intro until the game allows you to save for the first time. Create a new save file, then close the emulator completely.
  4. Go back to the save directory. You will see newly created files.
  5. Take the main file (or equivalent) from your original (corrupted) backup and copy it into this new directory, overwriting the new file.
  6. Restart the game.

In many cases, the game will now recognize the progress because the underlying folder structure and metadata have been "refreshed" by the new save creation. This is particularly effective for games like Metroid Dread or Super Mario Odyssey.

Using Specialized Repair Tools Like PKHeX

For specific genres, particularly RPGs like Pokémon, save corruption often involves a checksum mismatch. Games perform a mathematical check to ensure the data hasn't been tampered with; if a single byte is off due to a crash, the checksum fails, and the game marks the save as corrupted.

The Role of PKHeX in Data Recovery

PKHeX is a sophisticated save editor that has built-in logic to handle Switch save structures.

  1. Open the tool and drag your main save file into the interface.
  2. If the tool can parse the data despite the corruption, it will often automatically fix the checksums upon export.
  3. If the tool warns that the file is unreadable, it usually indicates "garbage data"—meaning the file is filled with zeros or random characters that no software can recover.
  4. If it opens, simply select File > Export SAV > Export main and replace the corrupted version in your Ryujinx folder.

We have found that for Pokémon Scarlet and Violet, PKHeX is often able to bypass the "Save data is corrupted" screen if the actual Pokémon and story data are intact but the header is damaged.

Distinguishing Between Save Corruption and Game File Corruption

It is vital to determine if the issue is actually your save data or if the game files (NSP/XCI) or their updates are the culprit. Ryujinx often throws specific error codes that indicate where the fault lies.

Understanding Error 2002-4604

If you see a log entry or a pop-up mentioning libhac.common.HorizonResultException: ResultFsNonRealDataVerificationFailed (2002-4604): Hash error!, this usually does not mean your save is corrupted. Instead, it means the game update or the base game file you are running has a hash mismatch.

  • Fix: Right-click the game, go to Manage Title Updates, and uncheck all updates. Try launching the game. If it works, the update file was corrupted during download or dumping. You will need to re-dump the update from your Switch.
  • Fix: If it still fails without updates, the base game file is corrupted. Re-verify your dump or dump the game again using nxdumptool.

Understanding Error 2002-0001

This error (Path Not Found) often suggests that Ryujinx is trying to access a save directory that it doesn't have permission to reach. This commonly happens if Ryujinx is placed in a "Protected Folder" like C:\Program Files or directly on the Desktop where Windows Defender might block write access.

  • Fix: Move the Ryujinx folder to a neutral location like C:\Games\Ryujinx and run the emulator as an administrator.

Why Do Ryujinx Saves Get Corrupted?

Prevention is only possible if you understand the mechanics of how data is lost. In the context of emulation, there are three primary culprits.

1. Interrupted Write Cycles (The Most Common Cause)

When you save a game, the emulator translates the guest OS (Switch) write commands to the host OS (Windows/Linux) filesystem. If you close the emulator window, if the emulator crashes, or if the PC loses power during this millisecond-long window, the file header might be written while the body of the data is missing. This results in a "truncated" file that the game cannot read.

2. Shader Cache Conflicts

While rare, heavy stuttering during a save process caused by shader compilation can lead to timing issues in the emulator's backend. If the CPU is 100% utilized compiling shaders, the thread responsible for file I/O might experience a delay, leading to a partial write if the user force-quits the application thinking it has frozen.

3. Third-Party Sync Software

Using tools like OneDrive, Dropbox, or Google Drive to sync your AppData folder in real-time is a high-risk behavior. If OneDrive attempts to "lock" the main save file to upload it to the cloud at the exact moment Ryujinx is trying to write to it, a sharing violation occurs. This often leads to the file being wiped or corrupted. Always pause syncing while playing or use a dedicated script to backup saves after you close the emulator.

How to Set Up an Automated Backup Workflow

To ensure you never lose significant progress again, you should implement a multi-version backup strategy. Relying on a single save file is the "single point of failure" that leads to these crises.

Creating a Simple Batch Script (Windows)

You can create a .bat file that copies your saves to a backup directory every time you finish a session.