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

A Recoverable LaunchBox Setup: Separate Library Backups from the Full Portable Instance

Build a LaunchBox recovery plan that distinguishes XML data backups from games, media, emulators, saves, BIOS files, and dependencies stored elsewhere.

LaunchBox’s built-in data backup is valuable, but it is not a complete image of a retro-gaming setup. Its archive covers the Data directory used for library records and settings; games, downloaded media, emulator executables, BIOS/firmware, saves, and files stored outside the installation may live elsewhere. A restore can successfully recreate a library that still points to missing files.

The reliable approach has two layers: use LaunchBox’s data archive for quick library recovery and separately protect the full installation plus every external dependency. Test the restore on a copy before a drive migration or major library edit.

Map the actual dependency graph

Before backing up, inventory the folders and paths LaunchBox uses for each platform. A library entry can point to a ROM or disc image on another drive, an emulator executable beneath LaunchBox\Emulators, a RetroArch core, media on a NAS, and saves in an emulator-specific Windows profile. The visible game entry does not prove that these targets are in the same folder.

For representative entries, open the game’s edit view and confirm the launching path, emulator, platform association, and any alternate versions or companion applications. Check the emulator’s own configuration for separate save, firmware, shader, and user-data paths. Do not assume that putting an emulator executable inside LaunchBox also places its saves or configuration there.

Create a manifest with each dependency’s source path, destination, size, and (for irreplaceable files) SHA-256. Preserve multi-disc relationships and descriptor files; a CUE or M3U that points to a moved track is part of the usable game set.

Use the built-in data archive for what it covers

After imports, downloads, and bulk edits have stopped, use Tools → File Management → Create Data Backup. The archive is suited to rolling back library metadata and settings. LaunchBox’s current backup documentation notes that automatic XML data backups are retained as a rolling set, while manually named backups are not part of that rotation.

Copy important archives off the LaunchBox drive. An archive stored beside the database does not protect against disk failure, theft, ransomware, or accidental reformatting. Before restoring, copy the current Data directory separately; restore replaces the active data, so a backup from before a change will also remove later library edits.

Make a complete, quiescent folder copy

For a more complete portable setup, close LaunchBox and Big Box, stop active emulators and downloads, and wait until no import or metadata job is writing. Copy the complete LaunchBox installation to a separate device, including the folders your setup actually uses: Data, Images, Videos, Music, Manuals, Themes, Plugins, Emulators, and Games when present.

Then separately capture anything outside that folder: external ROMs, media, BIOS/firmware and legally retained system files, emulator saves, emulator configuration, storefront installs, and any custom scripts or profiles. Built-in data backup does not automatically include these dependencies. Protect copyrighted files and credentials appropriately; never upload them with a public bug report.

Portable does not mean path-independent. If games or emulators are outside the copied tree, the new computer must still expose them at the recorded paths. For removable Windows storage, keeping the same drive letter can avoid broken absolute paths; otherwise update references deliberately and test a small platform before moving the rest. Avoid blind global path replacement where filenames or subfolders also changed.

Restore in a controlled sequence

  1. Copy the instance to a test location and keep the original untouched.
  2. Restore the LaunchBox data archive only if library data itself needs recovery.
  3. Reconnect or restore game files, emulator folders, media, and any required external user data.
  4. Confirm emulator executable paths and each Associated Platforms row still matches the local platform name.
  5. Check required dependencies through the emulator’s documentation; a green LaunchBox indicator is not a substitute for provenance or a successful title launch.
  6. Launch one representative title per important emulator, including a multi-disc or compressed title if used.
  7. Create and reload a native save after closing and restarting the emulator.

If a title is listed but fails, check the actual ROM path first, then the emulator path, platform association, command-line settings, dependencies, and only then the emulator itself. This order separates stale path problems from core or firmware problems. Do not replace a verified system file just because a library entry stopped launching after a migration.

Prove recovery, then retain the rollback copy

A backup is validated when it can be restored to a second location and reproduce the expected library and launch behavior without relying on the original disk. Record the LaunchBox version, emulator versions, drive mappings, backup date, and test results. Keep at least one offline or otherwise protected copy and do not delete the old source until the restored instance has passed the acceptance checks.

Related:

Sources:

Comments