Last updated: November 2026
The Xbox BIOS for xemu is three files, not one: a 512-byte MCPX boot ROM, a flash ROM image (the BIOS itself) and a hard disk image. xemu does not look in a BIOS folder. You pick each file under Machine > Settings… > System > Files, then restart xemu. The one hash xemu publishes is for the MCPX: MD5 d49c52a4102f6df7bcf8d0617ac475ed. The MCPX and the flash ROM have to come from an original Xbox you own.
This is a researched guide, built from xemu’s official documentation and the xemu source code, each linked below. Sizes, menu names and error text were read from the source’s master branch in November 2026, when the latest release was 0.8.139. Menus move between versions, so if a name differs on your build, look for the closest match.
Everything here assumes files dumped from hardware you own. This site does not link to BIOS, hard disk image or game downloads. This page covers the original Xbox only; for the Xbox 360, see the RGH parts guide.
What BIOS files does xemu need?
xemu needs three files to start: an MCPX boot ROM image, a flash ROM image (the BIOS) and a hard disk image. Its Required Files page explains why: xemu is a low-level, full-system emulator, so it needs the same things a real Xbox needs at power-on. A fourth file, the EEPROM, is created for you.
| File | Label in xemu settings | Size xemu accepts | Hash in xemu’s docs |
|---|---|---|---|
| MCPX boot ROM | MCPX Boot ROM | Exactly 512 bytes | MD5 d49c52a4102f6df7bcf8d0617ac475ed |
| Flash ROM (BIOS) | Flash ROM (BIOS) | A multiple of 65,536 bytes | None published |
| Hard disk image | Hard Disk | Not stated | None published |
| EEPROM | EEPROM | Exactly 256 bytes | Not needed, xemu generates it |
The docs use the name mcpx_1.0.bin for the boot ROM. xemu stores the full path to whatever file you pick. The file pickers for the two ROMs filter on .bin and .rom, and the hard disk picker filters on .qcow2, each with an All Files option.
If you leave the EEPROM field empty, xemu writes a valid eeprom.bin to its own data folder on first start.
What is the correct MCPX boot ROM hash for xemu?
The correct MCPX boot ROM hash is MD5 d49c52a4102f6df7bcf8d0617ac475ed, listed on xemu’s Required Files page for mcpx_1.0.bin. The file must be exactly 512 bytes. A dump with MD5 196a5f59a13382c185636e691d6c323d is a known bad dump that is a couple of bytes off, and should be dumped again.
xemu’s docs give one more check for the boot ROM: a good file starts with the bytes 0x33 0xC0 and ends with 0x02 0xEE.
You do not need a separate hashing tool. Open Machine > Settings… and go to the About tab. Under Config Information, xemu prints two lines for the files you selected: MCPX Boot ROM MD5 Hash and Flash ROM (BIOS) MD5 Hash. A field shows None if xemu could not read the file.
Which Xbox BIOS works with xemu?
xemu cannot boot games with an unmodified retail BIOS. Its docs say key DRM functions are not implemented yet, so the flash ROM must be either a debug BIOS or a modified retail BIOS that can boot unsigned software. The docs add that people report the most success with the modified retail “COMPLEX 4627” BIOS.
xemu’s FAQ says the MCPX and BIOS dumps should both come from a version 1.0 Xbox, and that a mismatched pair is one cause of a failed boot.
xemu publishes no hash for the flash ROM, so this page does not list one. The only size rule in the source is that the image is a multiple of 65,536 bytes. A file that fails that check is rejected, and xemu prints Failed to load BIOS to its console output.
Where do the Xbox BIOS files go in xemu?
The files can sit in any folder you can read, because xemu has no fixed BIOS directory. You browse to each one under Machine > Settings… > System > Files, and xemu saves the paths in its xemu.toml config file. The Flatpak build and EmuDeck are the two cases with set folders.
On first launch xemu shows a window that reads “Configure machine settings to get started” with a Settings button that opens the same System tab.
- Open Machine > Settings… and select the System tab.
- Click MCPX Boot ROM under Files and choose your 512-byte boot ROM.
- Click Flash ROM (BIOS) and choose your BIOS image.
- Click Hard Disk and choose your hard disk image.
- Leave EEPROM empty unless you have one from your console.
- Close and reopen xemu. The tab shows “Application restart required to apply settings” until you do.
| Setup | Where the files live |
|---|---|
| Windows, macOS, Linux (AppImage or PPA) | Any folder. Paths are saved as bootrom_path, flashrom_path, hdd_path and eeprom_path in xemu.toml |
| Linux Flatpak | The hard disk image must be in ~/.var/app/app.xemu.xemu/data/xemu/xemu/, the only folder the Flatpak can write to. The docs say the BIOS and MCPX do not need this |
| Steam Deck with EmuDeck | Emulation/bios/ with no subfolders, named mcpx_1.0.bin and Complex_4627v1.03.bin. The hard disk is Emulation/storage/xemu/xbox_hdd.qcow2 |
| Portable mode (Windows, Linux) | Create a file named xemu.toml next to the xemu executable |
| Portable mode (macOS) | Put xemu.toml in the Contents/Resources folder inside xemu.app |
The EmuDeck row comes from EmuDeck’s own xemu page, not from xemu. For the rest of that setup, see the EmuDeck Steam Deck guide.
How do you dump the Xbox BIOS and hard disk from your own console?
You dump the MCPX and the flash ROM from an original Xbox you own. xemu’s docs call this the only legal way to get them, and they do not publish a step-by-step method. For the hard disk, the docs offer xemu’s own pre-built image with no copyrighted content, or imaging the console’s drive to a file.
The pre-built image is linked from xemu’s Required Files page. By design it holds only an unsigned dashboard with basic functions, not the official Xbox dashboard. The same page calls imaging your real drive “the most authentic way to do it”:
- Unlock the Xbox hard drive.
- Connect the drive to a computer.
- Copy the entire drive to a single file with
dd. - Select that file as Hard Disk in xemu.
The docs say the resulting file “can be used as-is with xemu.” They do not explain how to unlock the drive, and this page does not fill that gap from other sources.
For the MCPX and flash ROM, the xemu project says in plain terms that it does not discuss how to acquire them beyond dumping your own console, and asks users not to request them. Use the hash and byte checks above to confirm your MCPX dump.
What game files does xemu load?
xemu loads xiso disc images made from your own discs, usually saved with an .iso extension. Its docs say these are not the same as typical ISO images. Full “redump” style dumps and compressed formats such as CHD are not supported, and xemu generally cannot read a game disc from a PC DVD drive.
The docs’ own backup route is to connect by FTP to your real Xbox running a custom dashboard, insert the disc and copy the files from the D directory, then build an xiso with xdvdfs, the tool they recommend. Load the result with Machine > Load Disc….
A redump style image has two partitions and is typically about 7 GB, according to the same page, and only the game partition is usable. The docs show how to extract it.
Common Problems
Every error string below is quoted from xemu’s source code or its FAQ.
| Message | Cause |
|---|---|
Failed to open BootROM file '...'. Please check machine settings. | The MCPX path points at a file xemu cannot open |
Invalid BootROM file '...' size N. Expected 512 bytes. Please check machine settings. | The MCPX file is not exactly 512 bytes |
Failed to open flash file '...'. Please check machine settings. | The Flash ROM (BIOS) path points at a file xemu cannot open |
Failed to open hard disk image file '...'. Please check machine settings. | The Hard Disk path points at a file xemu cannot open. On Flatpak, the docs say the image must sit in the app’s own data folder |
Invalid EEPROM file '...' size of N; should be 256 bytes. | The selected EEPROM is the wrong size. Clear the field and let xemu generate one |
The guest has not initialized the display | The FAQ says this is likely missing, mismatched or corrupt MCPX and BIOS images |
Please insert an Xbox disc... | The dashboard is running with no game loaded. If an ISO is loaded, the FAQ says to restart xemu, then check the dump format |
You need to connect the DVD Playback Kit receiver kit to a controller port to watch movies | A redump style ISO was loaded. Convert it to xiso |
xemu also crashes if surround sound is enabled in the EEPROM. The docs say surround is not implemented and should be turned off.
Why No Download Links
The boot ROM, the BIOS and the retail dashboard are copyrighted, and xemu’s own docs state that the project does not link to copyrighted files. The published MCPX hash exists so you can check your own dump, not so you can shop for a matching file.
BIOS guides for other consoles: PS1 BIOS, PS2 BIOS, PS3 BIOS, GameCube BIOS and the RetroArch BIOS reference.
FAQ
Does xemu need a BIOS?
Yes. xemu will not start a game without an MCPX boot ROM, a flash ROM (BIOS) image and a hard disk image selected in its System settings.
What is the MD5 of mcpx_1.0.bin?
d49c52a4102f6df7bcf8d0617ac475ed, from xemu’s Required Files page. The file is 512 bytes.
Can xemu use a retail Xbox BIOS?
Not for games. xemu’s docs say an unmodified retail BIOS cannot boot games yet, and that a debug BIOS or a modified retail BIOS able to boot unsigned software is required.
Do I need an EEPROM file for xemu?
No. xemu’s FAQ says a default one is created if you do not provide one.
Where does xemu store game saves?
On the E partition of the virtual hard drive, the same as a real Xbox, according to xemu’s FAQ. That makes the hard disk image the file to back up.
xemu Required Files | xemu FAQ | xemu Disc Images | xemu Troubleshooting | xemu source on GitHub | EmuDeck xemu page
Last verified: November 2026