Bundled ROMs Disappeared or Won’t Launch? Fix Guide

If bundled ROMs disappear or stop working on your retro handheld, the fix usually involves re-scanning the game library, re-seating or replacing the SD card, or re-flashing the firmware—in that order. This guide walks through the common causes and step-by-step fixes for the most popular retro handhelds, so you can get back to playing without losing your saves.

Why Bundled ROMs Vanish or Fail

Bundled ROMs are the games pre-loaded on the SD card that ships with many retro handhelds (like Anbernic, PowKiddy, or Miyoo devices). They disappear or stop working for a few predictable reasons:

• Corrupted SD card filesystem—the most common cause, often from pulling the card out while the device is writing, or from cheap cards failing.
• Firmware update changed the ROM path—some custom firmware updates (e.g., OnionOS, GarlicOS, ArkOS) alter the folder structure, so the emulator no longer finds the games.
• Emulator core mismatch—after an update, the default core for a system might change, and the ROM might not be compatible with the new core.
• SD card reader or slot issue—a loose connection or failing card slot can make the device not see the card at all.
• Accidental deletion or hidden files—some devices hide files with certain extensions, or a user might have moved folders while exploring.

Understanding which cause applies to you is the first step, because the fix differs.

First Steps: Re-scan and Reboot

Before tearing anything apart, try the simplest fixes. Most retro handhelds with a game launcher (like EmulationStation or a custom frontend) cache the game list. If the cache is stale or corrupted, games may not show up even though the files are still on the card.

1. Reboot the device—hold the power button for 10 seconds, then turn it back on.
2. Re-scan the game library—in the launcher, look for a “Refresh Games” or “Rescan ROMs” option (often in the settings or by pressing Select on the main menu). This forces the launcher to re-read the SD card.
3. Check if the ROMs are actually still on the card—remove the SD card, put it in a computer, and look for the ROM folders (e.g., /roms/gba, /roms/psx). If the files are there, the issue is with the launcher, not the card.

If the files are missing or the card isn’t recognized, move to the next section.

SD Card Troubleshooting and Replacement

The SD card is the most fragile part of a retro handheld. Many budget devices ship with no-name cards that fail quickly. If your ROMs disappear or the device won’t boot, the card is the prime suspect.

• Test the card on a computer—insert it into a PC or Mac. If the computer doesn’t recognize it, or if it shows errors when you try to open it, the card is likely failing.
• Back up your saves—if you can still access the card, copy the entire /saves or /retroarch/saves folder to your computer. Save files are often separate from the ROMs and can be transferred to a new card.
• Replace the card with a known-good brand—use a SanDisk, Samsung, or Kingston card from a reputable retailer. A 64GB or 128GB card is plenty for most retro libraries.
• Re-flash the firmware onto the new card—most retro handhelds have a custom firmware (like OnionOS for Miyoo Mini, GarlicOS for Anbernic RG35XX, or ArkOS for many others). Download the correct firmware for your exact model, format the new card as FAT32 (or exFAT if the firmware requires it), and copy the firmware files to the card using the official guide.

If you don’t have a backup of the bundled ROMs, you’ll need to source your own ROMs (see the legality note below). The firmware itself is usually freely available from the developer’s GitHub or official wiki.

Firmware Re-flash and ROM Path Fixes

If the SD card is fine but the ROMs still don’t show up, the firmware may have a corrupted configuration or the ROM path might have changed.

1. Back up your current firmware config—copy the entire /config or /retroarch folder to your computer if you want to keep your settings.
2. Re-flash the firmware—download the latest stable firmware for your device, format the SD card (FAT32 for most, exFAT for larger cards if the firmware supports it), and copy the firmware files exactly as instructed in the official installation guide. This resets all settings, which often fixes path issues.
3. Re-add your ROMs—after re-flashing, copy your ROM files back into the correct folders (usually /roms/<system>). Make sure the file extensions are correct (e.g., .gba for Game Boy Advance, .sfc for SNES).
4. Check the ROM path in the emulator—if you’re using RetroArch, go to Settings > Directory and verify that the ROM directory points to where your games actually are. Some firmware updates change the default path.

If you’re using a dual-card setup (one for firmware, one for ROMs), make sure the ROM card is formatted with the correct filesystem and that the firmware is set to scan the second card.

Emulator Core and Compatibility Issues

Sometimes the ROMs are present and the launcher shows them, but they fail to launch or crash back to the menu. This is usually a core compatibility problem.

• Change the emulator core—in RetroArch, when a game fails to launch, you can select a different core by pressing Select (or the hotkey) while the game is highlighted. For example, for SNES, try snes9x instead of bsnes. For PS1, try PCSX-ReARMed instead of DuckStation.
• Check the ROM file integrity—a truncated or corrupted ROM file will often crash. Compare the file size to the known good size, or re-download the ROM from a reliable source.
• Update the emulator cores—if you’re using RetroArch, go to Online Updater > Update Cores to get the latest versions. Some games require newer cores to run properly.
• Try a different ROM version—some ROMs are bad dumps. If one version fails, try a different dump (e.g., a No-Intro or Redump version).

If only a few specific games fail, it’s almost certainly a bad ROM or a core issue, not a systemic problem.

Preventing Future ROM Loss

Once you have your games working again, take steps to avoid losing them again.

• Back up your entire SD card—make a full image of the card using a tool like Win32DiskImager (Windows) or dd (Linux/macOS). Store this image on your computer or cloud drive.
• Use a high-quality SD card—replace the stock card with a reputable brand. This is the single best investment you can make.
• Always eject the SD card safely—on the device, use the “Shutdown” option before removing the card. On a computer, use the “Safely Remove Hardware” option.
• Keep a separate backup of your save files—saves are often stored in a different folder than the ROMs. Copy them to your computer regularly, especially before a firmware update.

Legal and Ethical Note on ROMs

Bundled ROMs are typically copyrighted games that you do not own a license for. Downloading ROMs for games you don’t own is generally considered copyright infringement, even if the device came with them. The safe approach is to only use ROMs of games you have legally purchased (e.g., from a digital store or a physical cartridge you own). If your bundled ROMs disappear, you may need to dump your own games using a device like a Retrode or a cartridge dumper. This is a personal decision, but it’s important to understand the legal landscape.

Frequently Asked Questions

Will I lose my save files if I re-flash the firmware?

Yes, if you format the SD card and re-flash, you will lose everything on that card unless you back it up first. Save files are usually in a /saves or /retroarch/saves folder. Copy that entire folder to your computer before re-flashing, then copy it back after.

Can I use a different SD card than the one that came with the device?

Yes, absolutely. In fact, it’s recommended. The stock cards are often low-quality and fail quickly. Just make sure to format the new card with the correct filesystem (usually FAT32) and copy the firmware files over. You may need to expand the partition if the firmware image is smaller than the card, but most custom firmwares handle this automatically.

Why do some ROMs show up but others don’t?

This usually means the launcher is only scanning certain folders or file extensions. Check that your ROMs are in the correct folder for their system (e.g., /roms/gba for Game Boy Advance) and that the file extension is supported (e.g., .gba, .zip, .7z). Some launchers also have a filter that hides files with certain names or extensions.

What if the device won’t boot at all after a firmware update?

This usually means the firmware files were not copied correctly or the card is not formatted properly. Re-format the card as FAT32, re-download the firmware, and copy the files again. If it still won’t boot, try a different SD card. If that fails, the device itself may have a hardware issue, and you should contact the seller.

Is it safe to download replacement ROMs from the internet?

Downloading ROMs for games you don’t own is legally risky and also a security risk, as many ROM sites are full of malware. If you must obtain ROMs, only download from sites you trust, and scan every file with antivirus software. The safest method is to dump your own games from cartridges you own.

Can I use a USB cable to access the SD card instead of removing it?

Many retro handhelds have a USB port that lets you connect to a computer and access the SD card as an external drive. This is convenient, but it’s still important to “eject” the device properly before disconnecting to avoid corruption. Some devices also have an FTP or network transfer option, which is even safer because it doesn’t involve physically removing the card.

Related

• AI Regulation vs Voluntary Standards: Key Differences
• Best pCloud Alternatives for Storage, Sync and Privacy
• AI-Assisted Work: When to Disclose and What to Say