sodcalculator

10 Tech How-To

Unmountable Boot Volume Error: Fixes for Windows

Guide 10-44070 · Updated · Step by step

The Unmountable Boot Volume error (stop code 0x000000ED) is a Windows Blue Screen of Death (BSOD) that appears when the operating system cannot read from the boot volume, typically the hard drive or SSD where Windows is installed. This guide explains the most common causes and walks you through the fixes that resolve the issue for most users, from simple restarts to command-line repairs.

What Causes the Unmountable Boot Volume Error?

Windows triggers this stop code when the kernel cannot mount (read) the boot volume during startup. The underlying problem is almost always one of the following:

  • Corrupted file system structures – damaged master file table (MFT), boot sector, or other metadata on the drive.
  • Faulty storage drivers – outdated or incompatible drivers for the hard drive controller (e.g., SATA, NVMe, RAID).
  • Physical drive issues – failing sectors, loose cables, or a failing SSD/HDD.
  • Recent system changes – a failed Windows update, disk utility, or a forced shutdown that interrupted writes.

While the error can appear after a power outage or crash, it is not a sign that your data is necessarily lost. In many cases, the drive is intact and the file system just needs repair.

Before You Start: Safety and Preparation

Some fixes involve commands that modify the disk. While the steps below are generally safe, they can fail if the drive is physically failing. If you have important files that are not backed up, consider removing the drive and connecting it to another computer as a secondary drive to copy data off before attempting repairs. If that is not possible, proceed with the steps, but be aware that a failing drive may degrade further.

You will need a Windows installation media (USB or DVD) for most of these fixes. You can create one on another PC using Microsoft’s Media Creation Tool. If you do not have one, you can try the first two methods without it.

Fix 1: Restart and Check Cables

Sometimes the error is transient, especially after a sudden power loss. Try these quick checks first:

  1. Restart the computer. If it boots normally, the error was a one-time glitch.
  2. If you are comfortable opening the case, power off, unplug, and reseat the SATA or power cables on the hard drive. For NVMe SSDs, reseat the drive in its M.2 slot.
  3. Enter the BIOS/UEFI (usually by pressing Del, F2, or F12 during startup) and check if the drive is detected. If it is not, the cable or drive may be faulty.

If the drive is not detected in BIOS, try a different cable or port. If it still is not detected, the drive may have failed.

Fix 2: Run Startup Repair from Windows Recovery

Startup Repair can fix many boot issues automatically. To access it:

  1. Boot from your Windows installation media.
  2. Choose your language, then click Next.
  3. Click Repair your computer in the bottom-left corner.
  4. Go to Troubleshoot > Advanced options > Startup Repair.
  5. Select your operating system and let it run. It may take several minutes.

If Startup Repair says it could not fix the problem, move on to the next step.

Fix 3: Run CHKDSK from Command Prompt

CHKDSK scans the file system for errors and repairs them. This is the most common fix for the Unmountable Boot Volume error.

  1. Boot from the installation media and go to Repair your computer > Troubleshoot > Advanced options > Command Prompt.
  2. Type chkdsk /r c: and press Enter. Replace c: with the letter of your Windows drive if it is different (you can check with diskpart and list volume).
  3. If prompted to dismount the volume, type Y and press Enter.
  4. Wait for the scan to complete. It can take a long time on large drives.
  5. Type exit and restart the computer.

The /r flag implies /f (fix errors) and also attempts to recover data from bad sectors. If CHKDSK finds and fixes errors, the system may boot normally afterward.

Fix 4: Repair the Boot Configuration Data (BCD)

If CHKDSK does not help, the boot configuration may be corrupted. Rebuild it with these commands in the same Command Prompt:

  1. Type bootrec /fixmbr and press Enter.
  2. Type bootrec /fixboot and press Enter. If you get an “Access is denied” error, skip to step 4.
  3. Type bootrec /rebuildbcd and press Enter. When prompted, type A to add the installation to the boot list.
  4. If /fixboot failed, type bootsect /nt60 sys and press Enter, then retry bootrec /rebuildbcd.
  5. Type exit and restart.

These commands rewrite the master boot record and rebuild the boot configuration store, which often resolves boot failures.

Fix 5: Disable or Update Storage Drivers

If the drive is detected but the error persists, the issue may be with the storage controller driver. In the Command Prompt, you can disable the problematic driver using the registry, but that is advanced. A simpler approach is to enter Safe Mode:

  1. Boot from the installation media, go to Repair your computer > Troubleshoot > Advanced options > Startup Settings.
  2. Click Restart, then press 4 or F4 to enter Safe Mode.
  3. If it boots, open Device Manager (right-click Start) and expand IDE ATA/ATAPI controllers or Storage controllers.
  4. Right-click the controller and select Update driver > Search automatically.
  5. If that does not work, right-click and select Uninstall device, then restart. Windows will reinstall the default driver.

Safe Mode loads only essential drivers, so if the system boots there, the problem is likely driver-related.

Fix 6: Check Disk Health and Replace Drive if Needed

If none of the above work, the drive may be failing physically. You can check its health with the built-in WMIC tool from the Command Prompt:

  1. In the Command Prompt, type wmic diskdrive get status and press Enter.
  2. If the status is not “OK”, the drive is failing and should be replaced.
  3. You can also use the manufacturer’s diagnostic tool, but you will need to run it from another PC.

If the drive is failing, back up what you can and replace it. After installing a new drive, you will need to reinstall Windows.

Frequently Asked Questions

Will I lose my files if I run CHKDSK?

CHKDSK is designed to repair the file system and recover readable data. It does not intentionally delete files, but if a file is severely corrupted, it may be moved to a folder like found.000 on the drive. It is always wise to back up important data before running it, but it is generally safe.

Can this error be caused by a virus?

Malware can corrupt boot files or the file system, triggering this error. If you suspect malware, run a full antivirus scan after you manage to boot into Windows. If you cannot boot, you can use a bootable antivirus rescue disk from another PC.

What does “Unmountable Boot Volume” mean exactly?

It means Windows cannot access the volume that contains the boot files (usually the C: drive). The kernel expects to find the system files there, but it cannot read the volume due to corruption, driver issues, or hardware failure.

Is there a way to fix this without a Windows installation disc?

If you have a recovery drive or a system repair disc, those work too. If you have none, you can try the restart and cable checks, and then attempt to boot into Safe Mode by pressing F8 (on older systems) or Shift+Restart from the login screen (if you can get that far). Without any media, your options are limited.

How long does CHKDSK take?

It depends on the size and speed of the drive. On a 1TB HDD, it can take several hours. On an SSD, it is usually faster. Do not interrupt it; let it finish, even if it appears stuck.

Should I try a system restore?

If you have a restore point, you can try System Restore from the Advanced options menu. It reverts system files and settings to an earlier state without affecting personal files. It is worth trying if the error started after a recent change, but it may not fix file system corruption.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →