How to Set Up xemu — Complete Original Xbox Emulator Guide 2026

What xemu Needs (Before You Start):

Original Xbox emulation is more involved than most emulators because the Xbox hardware itself required three separate ROM files to boot. All of these must come from your own Xbox console:

• mcpx_1.0.bin (512 bytes exactly) — the MCPX bootrom, a tiny internal ROM on the Xbox MCPX chip. Its MD5 should be d49c52a4102f6df7bcf8d0617ac475ed.
• BIOS ROM (~256 KB) — the Xbox flash BIOS. The most widely tested with xemu is Complex_4627.bin (~256 KB). Other retail BIOS variants (4034, 4036, 4134, cromwell) also work.
• xbox_hdd.qcow2 — a virtual hard disk image with the correct Xbox partition layout (C: dashboard + E: saves + X/Y/Z scratch). xemu maintains a free pre-built Quick Start HDD image on its GitHub releases page that contains no copyrighted content.
• EEPROM.bin — xemu auto-generates this on first run (sets region to NTSC-US, random serial). You only need to provide your own dump if you need a specific region or serial preserved.

Step 1: Download xemu:

1. Go to xemu.app → download the latest build for your platform (Windows, macOS, Linux).
2. System requirements: GPU with OpenGL 4.0 or newer (most GPUs from 2012 onward qualify), 4 GB RAM minimum, 8 GB recommended. xemu uses OpenGL (not Vulkan).

Step 2: Get the Quick Start HDD Image:

1. Go to github.com/mborgerson/xemu/releases → download xbox_hdd.qcow2 from the latest release assets.
2. Place xbox_hdd.qcow2 in a permanent folder — xemu writes game save data to it, so don't move or replace it after first use.

Step 3: Configure BIOS Files:

1. Open xemu → Settings → System.
2. MCPX ROM: point to your mcpx_1.0.bin (must be exactly 512 bytes).
3. Boot ROM: point to your BIOS file (e.g., Complex_4627.bin, ~256 KB).
4. HDD Image: point to the xbox_hdd.qcow2 you downloaded.

If either BIOS path is wrong or the file is missing, xemu shows "MCPX ROM file not found" or "Flash ROM file not found" and won't boot.

Step 4: Load a Game:

1. Xbox game images must be in ISO format (ripped from your disc using a modchipped Xbox + FTP or a compatible DVD drive). ISO files are typically 1–8 GB.
2. File → Load Disc Image → select your .iso. The game should boot through the Xbox logo screen and into the game.
3. First boot: the Xbox dashboard may appear first (like a fresh console). Press A/Start to skip the initial setup. Subsequent runs: load your ISO before clicking start.

xemu Graphics Settings (Settings → Display):

• Surface Scale: set to 2× or 4×. Most Xbox games run at 480p internally — 2× gives 960p, 4× gives 1920p (near 1080p). A handful of titles (Halo 2, DOA3, PGR2) natively support 720p; xemu handles these correctly.
• Aspect Ratio: 4:3 for most games. Some titles offered a 16:9 widescreen option in their in-game settings — enable that in the game itself, not in xemu.
• Smoothing: Off for pixel-accurate look; On for a smoother/bilinear appearance.
• VSync: enable to prevent screen tearing.

Performance Tips:

• GPU driver: keep your GPU driver current. xemu's OpenGL renderer benefits from driver-side shader cache warmup on the first play session.
• Power plan (Windows): set to "High Performance." Some Xbox games are CPU-bound (Halo 1's AI pathfinding) and benefit from sustained clock speeds.
• Shader compilation stutter: like most emulators, xemu compiles shaders on first encounter. Subsequent runs of the same game are smoother — the cache persists in xemu's app data folder.
• HDD size: if you get "full disk" errors on save-heavy titles, a larger HDD image can be created with the qemu-img tool.

Compatibility:

Not every Xbox game runs perfectly. Check xemu.app/#compatibility before spending time on a title — the compatibility DB shows per-game status (Broken / Intro / Playable / Playable with issues / Perfect), updated by the community.

Controller Setup (Settings → Input):

xemu supports standard XInput controllers — Xbox 360/One/Series controllers map perfectly. For PlayStation controllers, use DS4Windows (DS4/DualSense) to present them as XInput.

1. In Settings → Input, assign your physical controller to Xbox port 1. Most games expect a controller in port 1.
2. For multiplayer games needing 2–4 controllers, assign additional controllers to ports 2–4.
3. Original Xbox controllers with a USB adapter also work — the Xbox controller uses a slightly modified USB protocol, and xemu handles the native Xbox HID descriptor if your adapter presents it correctly.

Network — Xbox LAN and System-Link Play:

xemu includes a built-in NIC emulator that presents a virtual Xbox network adapter.

1. For LAN play between two xemu instances (or real Xboxes) on the same physical network: enable Settings → Network → Enabled and set the adapter to your PC's LAN interface.
2. For internet system-link (Xbox Live replacement), xlink Kai is the most established tunneling service. Halo, Halo 2, MotoGP, and MechAssault all work via xlink Kai — refer to xlink Kai's own setup documentation for the tunneling config.

Common Issues:

• "MCPX ROM file not found": mcpx_1.0.bin path wrong or file missing — Settings → System → MCPX ROM → point to the correct file; confirm it is exactly 512 bytes.
• "Flash ROM file not found": BIOS ROM path wrong or missing — Settings → System → Boot ROM → select your BIOS .bin; confirm it is ~256 KB.
• Black screen after Xbox logo: wrong BIOS for your HDD image, or corrupted ISO — try a different BIOS variant; re-rip or verify the ISO checksum.
• Dashboard appears instead of game: no game loaded or previous disc image cleared — File → Load Disc Image → select your ISO before clicking start.
• Game runs very slowly: GPU below OpenGL 4.0 or integrated graphics — check your GPU spec; a dedicated GPU is strongly recommended; set Windows power plan to High Performance.
• Controller not detected: XInput not recognized or wrong port assigned — Settings → Input → assign controller to port 1; use DS4Windows for PlayStation controllers.
• Audio crackling / no audio: audio backend mismatch — Settings → Audio → try switching between audio backends (SDL vs xaudio2 on Windows).
• Game crashes after loading: game-specific compatibility issue — check xemu.app/#compatibility for the title's known status and workarounds.
• Save game lost: HDD image was moved or replaced — always keep the same qcow2 file; don't replace it with a fresh Quick Start image after saving.
• "HDD image not found": xbox_hdd.qcow2 path wrong or file deleted — Settings → System → HDD Image → re-point to your qcow2 file.

See also: Xenia Xbox 360 setup guide — PCSX2 PS2 setup guide (contemporary platform, similar emulation maturity)