This guide walks you through fixing the “Unmountable Boot Volume” blue screen error in Windows 11. This stop code indicates that Windows cannot read the boot volume (usually the drive with the operating system), often due to file system corruption, disk errors, or recent changes like a failed update or improper shutdown. Below are step-by-step methods to repair the boot drive and get your PC running again.
What You’ll Need
- A Windows 11 installation USB drive or recovery drive (you can create one on another PC using Microsoft’s Media Creation Tool).
- Access to a working computer to create the bootable media if needed.
- Basic familiarity with command-line tools (we’ll guide you through each command).
Step-by-Step
- Boot from the installation media. Insert the USB drive, restart your PC, and press the key to open the boot menu (often F12, Esc, or Del, depending on your manufacturer). Select the USB drive from the list.
- Choose your language and click “Next.” On the first screen, select your preferred language and keyboard layout, then click Next.
- Click “Repair your computer.” In the bottom-left corner of the installation screen, click Repair your computer instead of “Install now.”
- Navigate to Troubleshoot. In the recovery environment, select Troubleshoot → Advanced options → Command Prompt. This opens a command-line window.
- Run CHKDSK to check and repair disk errors. In the Command Prompt, type the following and press Enter:
chkdsk c: /f /r
This scans drive C: for errors, attempts to fix them (/f), and locates bad sectors (/r). If your system drive is a different letter (like D:), replace “c:” with that letter. The scan may take 30 minutes or more. Wait for it to complete. - If CHKDSK finds and fixes errors, restart your PC. Type
exitto close the Command Prompt, then choose Continue to restart normally. If the error is gone, you’re done. - If the error persists, run Bootrec commands. Reboot to the Command Prompt again (repeat steps 1–4). Then type the following commands one by one, pressing Enter after each:
bootrec /fixmbrbootrec /fixbootbootrec /scanosbootrec /rebuildbcd
These repair the Master Boot Record, boot sector, and Boot Configuration Data (BCD). When prompted to add an installation to the boot list, typeYand press Enter. - Restart and test. Exit the Command Prompt and restart your PC. If the error is resolved, you’ll boot normally.
- If still failing, use DISM and SFC. Boot back to the Command Prompt. Run:
dism /image:C:\ /restorehealth
This repairs the Windows image using the installation media as the source. Then run:sfc /scannow
This checks system file integrity. Both commands can take a while. - Check for hardware issues. If none of the above works, the drive may be failing. Run a hardware diagnostic from your PC manufacturer (often accessible via F12 at boot) or test the drive on another computer using a tool like CrystalDiskInfo (on a working PC).
Common Mistakes
- Wrong drive letter. In the recovery environment, the system drive may not be C:. To find the correct letter, type
diskpart→list volumeto see all volumes and their letters, then exit withexit. - Skipping CHKDSK. Some users jump straight to bootrec commands, but file system corruption is the most common cause. Always run CHKDSK first.
- Not waiting long enough. CHKDSK and DISM can take over an hour on large drives. Let them finish; interrupting can cause more damage.
- Using the wrong media. Ensure your USB drive is a Windows 11 installation media, not just a recovery drive from an older version, as the boot files may be incompatible.
Tips
- Back up your data. If you can access the drive from the Command Prompt (e.g., using
dir), copy important files to an external drive before attempting repairs. You can usecopyorrobocopycommands. - Use a wired connection. If you run DISM, it may need to download files from Windows Update. A stable internet connection is essential.
- Check the drive’s health. If the error returns after a successful repair, the drive is likely failing. Replace it as soon as possible.
- Keep your system updated. After fixing, install all Windows updates to prevent known bugs that can trigger this error.
Troubleshooting
If the steps above don’t resolve the issue, try the following:
- Run CHKDSK on a different drive. If you have multiple drives, the boot volume might not be C:. Use
diskpartto list volumes and run CHKDSK on the correct one. - Disable Secure Boot temporarily. In some cases, Secure Boot can interfere with boot files. Enter your BIOS/UEFI (usually by pressing F2 or Del during startup) and disable Secure Boot, then try booting again. Re-enable it after.
- Check for recent hardware changes. If you recently added or removed a drive, the boot order may be wrong. Enter BIOS and ensure the correct drive is set as the first boot device.
- Use System Restore. In the recovery environment, choose Troubleshoot → Advanced options → System Restore to roll back to a point before the error started. This works only if restore points exist.
- Reset your PC. As a last resort, from the recovery environment, choose Troubleshoot → Reset this PC. You can choose to keep your files, but apps and settings will be removed. This reinstalls Windows and fixes boot issues but may take a while.
Frequently Asked Questions
Will I lose my data?
Usually, no. The repair commands (CHKDSK, bootrec, DISM, SFC) are designed to fix system files without touching your personal data. However, if the drive is physically failing, data loss is possible, so back up early if you can.
How long does CHKDSK take?
It depends on the drive size and speed. A typical 1TB HDD can take 1–2 hours; an SSD may be faster. The /r parameter scans every sector, which is thorough but slow.
Can I run these commands from Windows itself?
No, because Windows won’t boot. You must use the recovery environment via installation media. However, if you can boot into Safe Mode, you can run CHKDSK from an elevated Command Prompt.
What if I don’t have a Windows 11 USB drive?
You can create one on any PC with a USB drive (8GB or larger) using Microsoft’s Media Creation Tool. Download it from Microsoft’s website, run it, and follow the prompts to create installation media.
Is this error caused by a virus?
It’s possible but unlikely. The most common causes are file system corruption, bad sectors, or a failed Windows update. Running a full antivirus scan after fixing the boot issue is a good idea.
Can I prevent this from happening again?
Regularly update Windows, shut down properly (not force power off), and monitor drive health with tools like CrystalDiskInfo. Also, avoid unplugging external drives while the system is writing to them.
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
- How to View Wi-Fi Password on iPhone
- How to Stream on Twitch from PC
- GTM vs Facebook Pixel: What’s the Difference?
- Windows 10 Won’t Boot? Fix It in 30 Minutes
- Ubuntu 26.04 LTS Requirements & Hardware Checks
- ATK0100 Driver: Do You Need to Install It?