How Do I Fix the Unmountable Boot Volume Error in Windows 11?
Unmountable Boot Volume in Windows 11? Fix from WinRE with chkdsk, bootrec commands, and driver recovery — including update-related boot failures.
Issue type: Critical boot failure — Windows 11 shows a blue screen with stop code UNMOUNTABLE_BOOT_VOLUME and cannot start normally.
Short answer: Unmountable boot volume Windows 11 fix steps must be done from Windows Recovery Environment (WinRE). This error means Windows cannot mount the partition it needs to boot from. The cause can be file system corruption, boot configuration damage, storage driver failure, or a failing SSD/HDD. Start with chkdsk, then repair boot files, then remove a recent update only if the issue started immediately after an update.
Unmountable Boot Volume Windows 11 Fix: Quick Diagnosis
UNMOUNTABLE_BOOT_VOLUME is bug check 0x000000ED. Microsoft describes it as a failure to mount the boot volume during startup. See Microsoft’s UNMOUNTABLE_BOOT_VOLUME bug check reference.
After a Windows Update: a recent update, driver change, or interrupted update may have damaged the boot state. Remove the most recent update from WinRE only after basic disk checks.
After power loss or shutdown during update: file system corruption is likely. chkdsk is the first repair.
After physical impact, clicking sounds, or repeated boot failures: treat the drive as possibly failing. Back up data before heavy repair attempts where possible.
What to do first
- Enter Windows Recovery Environment. After two or three failed boots, Windows usually opens recovery automatically. If not, interrupt startup twice by holding the power button during the logo screen. Then go to Troubleshoot > Advanced options > Command Prompt. You can also boot from a Windows 11 USB and choose Repair your computer.
- Find the correct Windows drive letter. In WinRE, the Windows partition may not be C:. Run:
diskpart
list vol
Look for the volume containing Windows. Then type:
exit
You can confirm with:
dir C:\Windows
If that fails, test D:, E:, and other letters until you find the Windows folder. - Run chkdsk on the Windows partition:
chkdsk C: /f /r
Replace C: with the correct Windows drive letter. The /f switch repairs file system errors. The /r switch scans for bad sectors and recovers readable data. This can take a long time on large or unhealthy drives. If chkdsk reports many bad sectors or repeatedly hangs, stop treating this as a Windows repair and prioritize data recovery. - Repair boot records and boot configuration. Run:
bootrec /fixmbr
bootrec /scanos
bootrec /rebuildbcd
On UEFI systems,bootrec /fixbootmay return Access is denied. If that happens, use bcdboot after assigning a letter to the EFI System Partition. In diskpart, find the small FAT32 EFI partition, assign a temporary letter such as S:, exit diskpart, then run:
bcdboot C:\Windows /s S: /f UEFI
Replace C: with the correct Windows drive if needed. This rebuilds the UEFI boot files more reliably than forcing /fixboot on modern systems. - Run offline SFC. From WinRE Command Prompt, run:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
Replace C: if your Windows drive has a different letter. If you need DISM offline repair, it may require a Windows USB/ISO source. A basic command may fail in WinRE without a repair source. Use a Windows 11 installation USB when possible. - If the error started immediately after a Windows Update, remove the most recent update from WinRE. First list packages:
dism /image:C:\ /get-packages
Then remove the suspected package:
dism /image:C:\ /remove-package /packagename:PACKAGE_NAME_HERE
Use the exact package name from the list. Afterward, check Microsoft’s Windows release health dashboard before reinstalling the same update. - Check drive health before trusting the repaired system. If Windows boots, immediately back up important files and check the drive with your SSD/HDD manufacturer’s diagnostic tool or CrystalDiskInfo. In recovery environments,
wmic diskdrive get model,statusmay work on some systems, but it is not guaranteed on every modern setup. BIOS/UEFI diagnostics and manufacturer tools are more reliable for hardware confirmation.
⚠️ Warning: Boot repair commands can change boot records and EFI boot files. On dual-boot systems, they may overwrite another operating system’s bootloader. If the drive is physically failing, repeated repair attempts can also increase data loss risk. Back up accessible files first whenever possible.
Common mistake
The common mistake is treating every UNMOUNTABLE_BOOT_VOLUME error as a Windows-only problem. If chkdsk reports many bad sectors, if the drive disappears from BIOS, or if the same error returns after repair, the storage device may be failing. Repair commands can temporarily boot a damaged drive, but they do not make the hardware reliable.
Best next step
If chkdsk completes, bcdboot rebuilds boot files, and Windows still returns to UNMOUNTABLE_BOOT_VOLUME, suspect a storage driver or drive-health problem. Remove recent storage drivers or updates from WinRE if the timing matches. If the drive shows health warnings, clone or recover data before reinstalling Windows. For a related boot failure pattern, compare with Inaccessible Boot Device in Windows 11.
Quick Q&A
Can chkdsk fix UNMOUNTABLE_BOOT_VOLUME?
Yes, if the cause is file system corruption. It will not fix a physically failing drive or an incompatible storage driver.
What if bootrec /fixboot says Access is denied?
Use bcdboot on UEFI systems. Assign a temporary letter to the EFI partition, then run bcdboot C:\Windows /s S: /f UEFI.
Does this error always mean my SSD is dead?
No. It can be software corruption. But if the error returns after repair or SMART/diagnostic tools show warnings, treat the drive as unreliable.
Should I remove the latest Windows Update?
Only if the boot failure started immediately after that update. Otherwise, start with chkdsk and boot repair first.
Can I recover files before repairing?
Often yes. Boot from a Windows USB or a Linux live USB and copy files to an external drive if the partition is readable. Do this before risky repairs if the data matters.