Troubleshooting guide
Batocera USB Boot Fails: Check the Image, Mode, and Drive
Category: Game Console Boot
batocera usb not booting.
A Batocera boot failure is usually in the boot chain, not inside Batocera. Work from the image outward so you can tell whether the PC ever reached the bootloader.
Before you start
- The exact PC or mini PC model and firmware version
- A spare 8 GB or larger USB drive you can erase
- The Batocera x86 image and its checksum
- One wired controller and one game you own
Step-by-step checks
Step 1: Confirm the download and checksum
Download the x86_64 image from the Batocera release page and compare its published checksum. A truncated download can look like a bad USB even when the writer reports success.
Check: The checksum matches exactly before you write anything.
Step 2: Rewrite the drive, do not copy the ISO
Use balenaEtcher or Raspberry Pi Imager to write the image block by block. In Windows Disk Management, confirm the USB is the disk you are erasing, then let the writer finish and verify its final validation step.
Check: The writer reports a completed write and validation without errors.
Step 3: Choose the matching firmware mode
Open the one-time boot menu and note whether the USB entry is UEFI or legacy. Test UEFI first on a modern PC. If it is ignored, disable Secure Boot and Fast Boot, then retry; only test legacy/CSM when the hardware supports it.
Check: The Batocera splash or EmulationStation appears instead of Windows.
Step 4: Test the controller before a game
With one controller connected, open Controller Settings and map the d-pad, face buttons, start, and hotkey. Save the mapping, then restart the front end and confirm it persists.
Check: The same controller still navigates after a reboot.
Step 5: Launch one game and verify output
Start one known-good game, leave it running for two minutes, and check image, sound, and exit. If it fails, record the emulator and the last on-screen message before changing another setting.
Check: The game starts, plays with sound, and returns to EmulationStation cleanly.
Verify the result
Repeat the boot with the network disconnected and the same controller attached. The PC should reach EmulationStation, recognize the controller, and launch the test game without a second firmware change.
Rollback
Restore the original boot order and Secure Boot/Fast Boot settings after testing. Keep the Batocera drive separate so the internal Windows installation is untouched.
Ask for help with this exact symptom · All troubleshooting guides