Skip to content
RetrogamingHow-To Published Updated 4 min readViews unavailable

Cemu MLC and Save Recovery: Separate Game Paths, Installed Updates, and User Data

Keep Cemu base-game paths separate from the emulated MLC, back up saves and configuration coherently, and install updates through Cemu's supported interface.

Cemu’s game list and its emulated Wii U storage are different things. The configured game paths help Cemu discover base titles; the MLC directory models console storage and holds system data, installed updates or DLC, and save data. Mixing these roles creates duplicate entries, orphaned updates, and backups that restore the executable but not the user’s progress.

This runbook is about folder boundaries, lawful content handling, and recovery. It does not explain how to bypass console security or obtain game images, keys, or system files from third parties. Use data dumped from devices and media you are authorized to use, and preserve its provenance.

Keep three data classes distinct

Create separate locations for:

  1. Base game files: the title data Cemu scans as games.
  2. MLC storage: Cemu’s emulated console storage, including saves and installed updates/DLC.
  3. Cemu application/configuration: the program and frontend settings.

The Cemu wiki recommends a dedicated game directory containing base games only and a dedicated MLC directory outside the Cemu installation and game folders. This separation makes the library easier to move and reduces ambiguity about which copy is the original. Do not put update or DLC folders alongside base game folders as though they were separate game entries.

Install updates and DLC through the application

Use Cemu’s documented File → Install game update or DLC workflow for files you are authorized to install. Do not manually copy update/DLC files into arbitrary locations inside mlc01; the current folder-structure guide explicitly warns against that practice and describes it as outdated. After installation, verify the title appears correctly and inspect its version information using Cemu’s interface.

If the game list marks a title as inconsistent, first confirm that the selected scan path contains the expected base title and not only an update. Do not patch a damaged or incomplete base dump with files from an unrelated package. A valid title entry depends on the actual game data, correct folder roles, and a compatible Cemu build.

Back up saves with their MLC context

An MLC backup preserves more than individual save directories; it may include system data and installed updates/DLC needed by that Cemu instance. Close Cemu before taking a consistent file-level copy, then back up the configured MLC path as a unit. Independently back up the base game files and Cemu settings. If you intentionally export a single save, use Cemu’s Save directory action for that title instead of guessing a hashed folder name.

Store backups away from the source device. Record the Cemu version, configured MLC path, game title/version, save account context if relevant, date, and file hashes for critical save data. Protect any account-linked or private data; never post saves or system files in public support threads without reviewing their contents.

Move the MLC safely

Before relocating storage, take a copy and verify it can be read. In Cemu’s General Settings, point the MLC path to the intended dedicated location. Do not move or delete the old directory until Cemu has launched the expected title, visible saves match, installed updates remain available, and a test save survives a restart.

Keep the target MLC outside cloud-synchronized folders unless the synchronization product is configured to avoid simultaneous writes and conflict copies. Emulator save databases are active files; syncing them while Cemu is open can produce divergent versions. For ordinary backups, prefer a closed-application copy or a storage snapshot that is consistent at the filesystem level.

Diagnose in dependency order

When a game or save disappears after an update, verify in this order:

  1. Cemu version and whether the same configuration directory is active.
  2. Game paths point to the base-game directory, not to the MLC or an update folder.
  3. MLC path points to the expected preserved directory.
  4. The game is not merely an update without its base title.
  5. The save directory for the selected title resolves to the expected account/save data.
  6. Only then investigate the emulator build, graphics settings, or game-specific compatibility.

Retain the original copy until the new setup passes a cold-start test, a native save can be loaded, and a newly written save persists after shutdown and restart. Keep shader or graphics caches separate from irreplaceable user data; clearing a cache is not a repair for a missing MLC save.

Related:

Sources:

Comments