UNMOUNTABLE_BOOT_VOLUME

UNMOUNTABLE_BOOT_VOLUME is a Windows stop error (blue screen) that appears very early in startup, before the desktop loads. It means Windows detected a disk but could not mount the volume that holds the boot files and the operating system, so it had nothing reliable to start from. The screen is brief and the machine usually restarts by itself, which is why many people only catch the code once. Because it happens before Windows is fully running, most repairs are done from the recovery environment rather than from the desktop.

What it means

To boot, Windows must read the boot sector, load the Boot Configuration Data (BCD), and mount the system volume as its own filesystem. If any of those steps fails, the kernel halts with UNMOUNTABLE_BOOT_VOLUME. The fault sits at the storage layer: the drive is detected, but its filesystem or the record that describes it cannot be read correctly, so Windows refuses to trust the volume.

On most systems the stop code that accompanies it is 0x000000ED, shown together with the text UNMOUNTABLE_BOOT_VOLUME on the blue screen. It differs from a disk that is simply missing: here Windows sees the drive but cannot mount what is on it, which points at filesystem damage, a broken boot record, or failing hardware rather than a loose connection alone.

If the drive is healthy, the error is often the aftermath of a single bad shutdown. A file transfer, an update or a defragmentation was in progress when power was cut, leaving the filesystem's records inconsistent so Windows can no longer mount them cleanly. In that case a filesystem check usually clears it and the machine starts normally. If the same stop code returns after a repair, or the disk clicks or responds very slowly, suspect failing hardware and stop using the drive until you have copied your data off it.

Common causes

• A damaged or half-written filesystem, often after an abrupt power loss or a hard reset during use.
• Corruption in the boot sector or the BCD store that Windows uses to locate the system volume.
• A failing drive with bad sectors, or a loose or faulty SATA data or power cable.
• A changed storage controller mode in firmware, for example switching between AHCI and IDE after installation.
• Faulty storage or chipset drivers installed by an update.

How to fix it

1. Boot into the recovery environment. Start from Windows installation media, choose Repair your computer, then Troubleshoot > Advanced options > Command Prompt.
2. Check and repair the filesystem. At the prompt run:

   chkdsk C: /f /r

   If it offers to check on the next boot, answer Y and restart.
3. Repair the boot files. From the same prompt, rebuild the boot records one command at a time:

   bootrec /fixmbr
   bootrec /fixboot
   bootrec /rebuildbcd

4. Verify the drive's health. If chkdsk reports many bad sectors, the disk is failing. Back up your data with a live tool before doing anything else.
5. Recheck firmware settings. In the BIOS or UEFI, confirm the SATA mode matches what Windows was installed with (usually AHCI) and that the drive is first in the boot order.

Order matters here: repair the filesystem before rebuilding the boot records, and check the drive's health before spending time on software. If the automatic repair options fail, open the Command Prompt again and repair the offline Windows image, then reboot.

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

How to prevent it

Shut the machine down properly instead of cutting power, and avoid hard resets while updates are being written. Keep a backup of important files on a second drive or in the cloud, because stop errors at this stage often end in a drive replacement. Replace ageing cables, and on desktops seat the SATA data and power connectors firmly. Enabling SMART monitoring lets a drive that is beginning to fail warn you before it takes the boot volume with it.

It also helps to install chipset and storage drivers from the hardware vendor rather than relying on generic ones, and not to change the SATA mode in firmware after Windows is installed unless you first prepare the system for it. On laptops, keep the battery and power supply healthy so a brown-out cannot cut the disk mid-write. A little care around storage keeps this particular blue screen away.