Xenia Xbox 360 emulator — game not loading, DirectX 12 required, or crash fix

use-correct-game-format-and-path (sortOrder=1, isMostHelpful)

Ensure your game is in a format Xenia can read and that the path has no special characters or spaces.

1. Supported formats: Xenia accepts .xex (raw executable — extracted from an ISO), .iso (raw DVD dump), and .zar (XBLA arcade container). It does NOT accept .xbla, .god (Games on Demand encrypted), or DRM-encrypted disc images. If your file is a GOD container, use the tool God2Iso to convert it to a plain ISO first.
2. For ISO files: drag the .iso directly onto xenia.exe or use File → Open. Xenia mounts the ISO internally — do not extract it first unless specifically directed by the compatibility page for that title.
3. For XEX files: navigate inside the extracted game folder and open default.xex (the main executable). Opening a random XEX inside the disc structure will produce a "failed to load" error because many disc structures contain multiple XEX files and only the root one is the launcher.
4. Path check: move your game file to a short path with no spaces or non-ASCII characters, e.g. C:\Xbox360\GameTitle\default.xex. Xenia has a known issue with paths containing Unicode characters or very long directory names that produces a silent "unable to map" failure.

Why this works: Xenia's loader is strict about file format and path encoding. A GOD-encrypted file, a wrong XEX entry point, or a Unicode path all produce "failed to load" errors that are indistinguishable from compatibility failures — but are trivially fixed before deeper debugging.

switch-between-xenia-canary-and-stable (sortOrder=2)

Try the alternate Xenia build — Canary and stable have different compatibility lists and a game that fails on one often works on the other.

1. Download both builds: Xenia Stable from xenia.jp/download (the main release, conservative compatibility) and Xenia Canary from github.com/xenia-canary/xenia-canary/releases (active development build, higher compatibility ceiling but occasional regressions). Both are standalone ZIP files — no installation required.
2. Try your game on whichever build you have NOT already used. Many well-known titles (Halo 3, Red Dead Redemption, Forza Motorsport) have better results on Canary; other older XBLA titles run more reliably on stable. Check the Xenia Canary compatibility tracker at github.com/xenia-canary/xenia-canary/wiki/Compatibility-List to see which build each game was last tested on.
3. When using Canary, also try switching the GPU API: open xenia-canary.config.toml (in the same folder as the exe, or in Documents\Xenia\) and find the [graphics] section — change gpu = "d3d12" to gpu = "vulkan" or vice versa. Some titles respond differently to each API on the same hardware.
4. After switching build or API, delete the existing shader cache for the game: navigate to %APPDATA%\Xenia\shaders\ (or %LOCALAPPDATA%\Xenia Canary\shaders\) and delete the folder matching your game's title ID. A stale shader cache from a different build can cause instant crashes even when the new build would otherwise run the game.

Why this works: Xenia Canary receives commits daily and supports GPU instruction sets present in later 360 SDK versions that stable does not. Stable, conversely, has a more conservative and tested rendering path that is less prone to regressions. Using the compatibility spreadsheet to pick the right build cuts trial-and-error almost entirely.

fix-directx12-and-gpu-driver (sortOrder=3)

Ensure DirectX 12 (Feature Level 12_0) is available on your system — Xenia's renderer requires it even though the 360 itself predates DirectX 12.

1. Check your GPU's DirectX support: open Run (Win+R) → dxdiag → Display tab and read the "Feature Level" line. You need at least 12_0. GPU generations that meet this on Windows 10/11: NVIDIA GeForce GTX 900 series and newer (Maxwell), AMD Radeon R9 300 series and newer (GCN 3rd gen), Intel HD 520 and newer (Skylake). Anything older will show Feature Level 11_1 or below and cannot run Xenia — there is no workaround.
2. If your GPU meets the requirement but Xenia still reports "DirectX 12 not found," your driver may be outdated. Update your GPU driver to the latest version (see manufacturer's support site). After updating, run dxdiag again to confirm Feature Level reads 12_0 or higher before retrying Xenia.
3. Install or update the DirectX End-User Runtime from Microsoft (available at microsoft.com/en-us/download/details.aspx?id=35). This installs legacy shader compiler components that Xenia's D3D12 backend uses — missing these can produce a "D3D12 CreateDevice failed" crash even on capable hardware.
4. If you are on a laptop, ensure Xenia is running on the dedicated GPU, not the integrated Intel/AMD graphics: right-click xenia.exe → Run with graphics processor → High-performance NVIDIA/AMD GPU, or set the preference in NVIDIA Control Panel / AMD Adrenalin's "Graphics → Application settings."

Why this works: Xenia translates Xbox 360 microcode to D3D12 shader bytecode at runtime. The D3D12 API is the only conduit it uses to speak to your GPU; without Feature Level 12_0, the emulator has no valid rendering path and exits before loading any game. Ensuring the runtime and driver are current eliminates the two most common causes of a false "DirectX 12 required" error on hardware that should theoretically qualify.