Resurrecting the Dead: Fixing the UNMOUNTABLE_BOOT_VOLUME Blue Screen

WinRE Command Prompt Bootrec Rebuild & Unmountable Boot Volume Repair Guide

6 min. read

The Ticket: The Post-Outage Brick

A sudden power flicker rolls through the client's building. Most machines reboot gracefully, but the finance director's workstation drops into a terrifying Blue Screen of Death reading UNMOUNTABLE_BOOT_VOLUME. It loops endlessly, never reaching the Windows login screen. The file system was interrupted mid-write, corrupting the Master File Table or the Boot Configuration Data. We need to drop into the Windows Recovery Environment (WinRE) to surgically repair the disk metadata and rebuild the bootloader from scratch.

Pre-Flight Check

• Permissions: Physical or out-of-band management access (iDRAC/iLO) to the machine.
• Tools: A Windows 10/11 bootable USB drive (if the internal recovery partition is also corrupted).
• Impact: High. Running deep disk checks can take several hours depending on drive size and speed.

[!WARNING] The Risk Factor: If the drive is suffering from severe physical hardware failure rather than logical corruption, running a deep disk check (chkdsk /r) will heavily stress the read/write heads. This can completely kill a dying drive, rendering data recovery impossible. Always verify critical data is backed up to the cloud before attempting deep sector repairs. Furthermore, you will need the BitLocker Recovery Key to unlock the drive in WinRE.

The Solution: WinRE Command Prompt Triage

Do not blindly trust the automated "Startup Repair" tool. It frequently fails to rebuild severe BCD corruption.

1. Enter the Recovery Environment Force the machine to power off three times during the boot logo to trigger Automatic Repair, then click Advanced Options > Troubleshoot > Advanced Options > Command Prompt. Enter the BitLocker key if prompted.

2. Find the True OS Drive Letter Correction to standard guides: Do not assume your OS is on the C: drive. In WinRE, the small hidden boot partitions often steal the C: assignment, pushing your actual Windows volume to D: or E:.

• Type diskpart and press Enter.
• Type list volume and look for the largest partition (usually hundreds of gigabytes). Note its drive letter.
• Type exit to leave diskpart.

3. Run the Deep Disk Repair

• Assuming your OS volume was D:, type: chkdsk /f /r D: and press Enter.
• The /f flag fixes file system errors, and /r locates bad sectors and recovers readable information. Allow this to finish completely.

4. Rebuild the Boot Sector Once the disk check completes, you must repair the bootloader.

• Type bootrec /fixmbr and press Enter.
• Type bootrec /fixboot and press Enter.
  • Crucial Bypass: If you receive an "Access Denied" error on the fixboot command (incredibly common in modern UEFI systems), type bootsect /nt60 sys and hit Enter, then try bootrec /fixboot again.
• Type bootrec /rebuildbcd and press Enter.
• If it prompts you to add an installation to the boot list, press Y.
• Type exit, remove any USB drives, and reboot the PC.

The "Why" (Root Cause)

What exactly failed to "mount"? During the boot sequence, the motherboard firmware hands control over to the Windows Boot Manager, which loads the core NT Kernel into memory. The kernel then attempts to mount the primary system volume to access C:\Windows\System32 and load the rest of the operating system drivers.

If the machine lost power while updating the Master File Table (MFT), or if the SSD controller suddenly remapped a bad sector that contained critical boot files, the kernel cannot read the file system structure. Because it cannot mount the volume containing the OS, it has no choice but to throw Bug Check 0xED (UNMOUNTABLE_BOOT_VOLUME) and halt.

Under the Hood (Technical Deep Dive)

The bootrec /rebuildbcd command is the heavy lifter here. The Boot Configuration Data (BCD) is a firmware-independent database that replaced the legacy boot.ini file from the Windows XP days.

When you execute a rebuild, the tool scans all connected disks for installations compatible with Windows. When it finds the \Windows directory, it reconstructs the BCD store from scratch. However, if the BCD store is severely corrupted but not entirely deleted, the tool might scan the drive, find the Windows folder, but report "Total identified Windows installations: 0" because it thinks the existing BCD entry is still valid.

If this happens, you have to manually back up and delete the old BCD store before running the rebuild command: bcdedit /export C:\BCD_Backup attrib c:\boot\bcd -h -r -s ren c:\boot\bcd bcd.old bootrec /rebuildbcd

RMM & Automation Tips

• The Proactive Dirty Bit Check: You cannot script a machine that is already blue-screening, but you can catch file system corruption early. Create an RMM script that runs fsutil dirty query C: weekly. If the script returns "Volume C: is dirty," it means Windows has flagged the file system for logical errors. Have the RMM automatically schedule a chkdsk /f for the next system reboot before it turns into a fatal unmountable volume error.

Troubleshooting & Edge Cases

• Edge Case 1: Chkdsk freezes at 15%. If the chkdsk command hangs on a specific sector for hours, or starts returning "Failed to transfer logged messages to the event log," the storage drive has suffered a catastrophic physical failure. Software commands cannot fix broken silicon or shattered platters. Stop the process and replace the drive.
• Edge Case 2: The Missing EFI Partition. If the bootrec commands completely fail on a modern machine, the FAT32 EFI partition might be missing or accidentally deleted by a user messing with disk management. You will need to use diskpart to shrink the main partition by 100MB, create a new FAT32 partition, format it, and use the bcdboot D:\Windows /s [NewDriveLetter]: /f UEFI command to manually write a new bootloader.

If you want to see more guides, automation scripts, and technical deep dives just like this, make sure to follow us on Twitter, check out the Facebook page, and sign up for the weekly 404 & More newsletter!