What does Xbox error E106 mean?

E106 is a hard halt during boot. The Xbox bootloader loaded but could not match the cached system version in NAND with the installed OS version on the NVMe SSD. The console shows Something went wrong and will not proceed. Factory reset from the Troubleshooting menu usually fails immediately because the reset process itself reads from the corrupted partition. OSU1 bypasses this by loading a fresh OS image from USB.

Why does Xbox factory reset fail on E106?

When the OS partition is corrupted enough to cause E106, the factory reset routine cannot overwrite it because the reset process reads initialization data from that same partition. The console starts the reset, hits the bad sector or version mismatch, and halts again. OSU1 works because it writes via a recovery path that does not depend on the corrupted partition being readable.

Will OSU1 delete my games and saves?

OSU1 replaces only the OS partition. Game data and save files stored on the internal drive are usually preserved. Cloud saves are always safe. However, if the SSD has bad sectors beyond the OS partition, game data may be affected - that is a hardware failure, not a consequence of OSU1 itself.

Xbox Series X Error E106 / E101: The Offline System Update Fix

Q: How to fix Xbox system error E106?

Download OSU1.zip from support.xbox.com. Format an 8GB+ USB drive to NTFS (not exFAT, not FAT32). Extract OSU1.zip and copy the SystemUpdate folder to the USB root. Boot the Xbox into Troubleshooting mode: hold Bind + Eject simultaneously, then press Power once and wait for two chimes. Select Offline system update from the menu.

Your Xbox Series X boots straight to a black screen with a white error code - E106 or E101 - and the message "Something went wrong." You try the factory reset option. It spins for a few seconds and then fails immediately or loops back to the same screen. The console is physically fine but completely locked.

This is a specific failure: the internal NVMe SSD's OS partition is corrupted, and the system bootloader cannot reconcile what it expects to find with what is actually there. The fix exists, takes about 20 minutes, and requires a spare USB drive. Everything below is the exact process, including the two gotchas that cause most failed attempts.

The short answer

What you see	What is actually broken	Time to fix
E106 "Something went wrong" on boot	Bootloader version mismatch with corrupted OS partition	15-25 minutes
E101 on boot	System update process halted, partition unreadable	15-25 minutes
Factory reset fails immediately	Reset routine reads from the same corrupted partition	Cannot fix alone - OSU1 required
OSU1 fails repeatedly (3+ attempts)	NVMe SSD has physical bad sectors or NAND degradation	Hardware repair needed

What you need: A USB flash drive, 8GB minimum. A Windows PC. The OSU1.zip file from Microsoft Support. About 20 minutes.

Why E106 and E101 happen - the actual mechanism

The Xbox Series X runs its OS from a custom-partitioned NVMe SSD. At boot, the bootloader reads version metadata from NAND (the console's firmware chip) and compares it against the OS version installed on the SSD. They must match within an acceptable range.

E106 fires when that comparison fails. The bootloader sees a version stamp on the SSD that does not match what NAND expects. This happens most often after a failed or interrupted system update: power cut mid-download, network dropout during install, or a crash that left the partition table in an inconsistent state.

E101 is a narrower variant: the system update process itself loaded but could not complete. Both codes land you at the same "Something went wrong" screen, and both have the same fix.

The factory reset option in the Troubleshooting menu reads initialization instructions from the OS partition before overwriting it. Corrupted partition means corrupted read. The console gives up within seconds.

The Insider Program trap. If your console was enrolled in the Xbox Insider Program and running a preview build, the standard OSU1.zip from Microsoft's public support page will fail with a version error. Preview builds run higher OS version numbers than the public OSU1 image. The console refuses to install an older version. You either wait for the public OS to catch up to your preview version, or contact Xbox Support directly for guidance on Insider recovery.

Prepare the USB drive correctly

Two formatting mistakes cause the majority of failed OSU1 attempts.

File system: NTFS only. The Xbox Troubleshooting menu's USB reader requires NTFS. A drive formatted as exFAT (the default on many drives over 32GB) or FAT32 will not be recognized. The console will not show an error about the format - it simply will not display the "Offline system update" option, or it will display it but fail immediately after selection.

On Windows: right-click the drive in File Explorer, select Format, choose NTFS, check Quick Format, click Start.

Folder structure: exactly one level deep. Extract OSU1.zip. Inside you will find a folder named $SystemUpdate. That folder - not its contents, the folder itself - goes directly into the root of the USB drive.

Correct path: USB:\$SystemUpdate\ (with all update files inside)

Wrong paths: USB:\OSU1\$SystemUpdate\ or USB:\$SystemUpdate\$SystemUpdate\

The Xbox checks specifically for $SystemUpdate at the USB root. One extra directory level and the process fails silently with no useful error message.

Boot the Xbox into Troubleshooting mode

This step trips most people because the button timing is strict.

Power the console completely off. Hold the front power button for 10 seconds if needed to force shutdown.
Hold Bind (the small button on the left side of the front panel) and Eject (the button below the disc slot) simultaneously. Keep both held.
While still holding Bind + Eject, press the Power button once and release it.
Continue holding Bind + Eject. The Xbox startup chime will play twice. Wait for the second chime, then release both buttons.
The Troubleshooting screen appears.

If you release after the first chime, the console boots normally. The first chime is power-on acknowledgment; the second signals you are in the Troubleshooting environment.

On Xbox Series S (no disc drive): there is no Eject button. Use the Pair button on the front face, below the power button, in place of Eject. The procedure is otherwise identical.

Run the offline system update

Insert your prepared USB drive into a USB-A port on the Xbox. The rear port is preferred - community reports on r/XboxOneHelp note occasional timing issues with the front port during the update write process, though Microsoft does not document this officially.
On the Troubleshooting screen, select Offline system update.
The console detects the $SystemUpdate folder and begins. A progress indicator appears. The update takes 10-20 minutes depending on USB write speed.
The console restarts automatically. It shows the green Xbox logo and then takes 2-5 additional minutes to finalize the OS installation.

Do not unplug the USB during this process. Do not power cycle the console. Both actions re-corrupt the partition and return you to E106.

What happens to your game data

OSU1 replaces the OS partition only. The game storage partition is separate on the NVMe SSD.

In the majority of cases - where corruption is limited to the OS/boot partition - game installs and local saves survive intact. You will need to sign in again and re-link your Microsoft account, but your library and saves should be present.

Cloud saves are always safe. They live on Microsoft's servers and are unaffected by anything that happens to the local SSD.

If the SSD has corruption beyond the OS partition - bad sectors in the game storage area - game data may be missing after OSU1. That is a hardware failure, not an OSU1 consequence. It would have surfaced regardless.

When OSU1 does not fix it

Three or more failed OSU1 attempts with a correctly formatted USB and correct folder placement means the problem is not software-recoverable. The NVMe SSD is failing.

The Series X uses a custom-partitioned NVMe SSD. You cannot swap in a generic M.2 drive - the partition table structure, encryption scheme, and keying to the console's TPM are specific to that unit. Community tools like xboxonehdd can sometimes re-partition a physically intact SSD whose partition table was wiped, but this requires removing the drive, connecting it to a PC via an M.2 enclosure, and running the script in a Linux environment.

If the drive has actual bad sectors - confirmed by running CrystalDiskInfo on the removed drive - re-partitioning will not help.

The repair vs. replace calculation. Professional console repair shops charge roughly $80-$180 to diagnose and attempt SSD recovery on an Xbox Series X. A refurbished Series X sells for $250-$320 as of mid-2026. If the SSD is physically dead and the console is out of warranty, the math often favors replacement - get a written quote before authorizing any hardware work.

This fix is the wrong call in these situations

Skip OSU1 and contact Xbox Support or a repair shop directly if any of these apply:

The console is in warranty. In-warranty hardware faults, including SSD failures causing E106, are Microsoft's responsibility. Xbox Series X/S carries a 1-year manufacturer warranty. An OSU1 attempt that fails and involves drive removal can complicate warranty claims.
The console will not enter Troubleshooting mode. If Bind + Eject + Power produces no chimes and no screen, the fault is deeper than the OS partition. The bootloader itself may be corrupted.
OSU1 completes but E106 returns after the next system update. This is an intermittent SSD write fault. The OS partition holds temporarily, then gets re-corrupted during the next update cycle. Repeated OSU1 runs are not a sustainable solution.
You were on an Xbox Insider preview build. Standard OSU1 images are likely version-incompatible. Contact Xbox Support before forcing the install.

Frequently asked questions

How do I fix Xbox error code E101?

E101 means the Xbox bootloader cannot complete a system update - usually because the OS partition is corrupted. Perform an Offline System Update (OSU1): format a USB drive to NTFS, extract the $SystemUpdate folder from Microsoft's OSU1.zip to the USB root, boot the Xbox into Troubleshooting mode by holding Bind + Eject then pressing Power (wait for two chimes), insert the USB, and select "Offline system update." The process takes 10-20 minutes and restores the OS without erasing game data in most cases.

How to fix Xbox system error E106?

Download OSU1.zip from Xbox Support: Error E106. Format an 8GB+ USB drive to NTFS. Extract the zip and copy the $SystemUpdate folder to the root of the USB - the path must be USB:\$SystemUpdate, not USB:\OSU1\$SystemUpdate. Boot into Troubleshooting mode (Bind + Eject held, press Power once, wait for two chimes), insert the USB, select "Offline system update."

What is error code E101?

E101 on Xbox Series X/S is a boot-time error indicating the system update process started but could not complete. The bootloader loaded successfully but the OS installation is inconsistent - either interrupted mid-update or corrupted by a storage fault. The console shows "Something went wrong" immediately on power-on and cannot reach the dashboard.

What does E106 mean?

E106 is a version mismatch error. The Xbox bootloader reads a version identifier from NAND and compares it against the OS version on the NVMe SSD. E106 fires when those versions are incompatible - typically because the OS partition is corrupted or partially written, leaving an invalid version stamp. The console halts rather than boot into an inconsistent state.

Xbox Series X Error E106 / E101: Offline System Update Fix