The Unmountable Boot Volume error is one of the more alarming things you can see on a Windows PC — a blue screen telling you the system can’t access the drive it needs to start up. It’s caused by Windows losing the ability to properly read your boot partition, often due to file system corruption, a botched update, or a failing drive. The good news is that it’s usually fixable without losing your data, provided you work through the right steps in order.
What This Error Actually Means
The “boot volume” is the partition on your drive that holds Windows itself. When this error appears, it means Windows can’t mount that partition to load the operating system, so instead of booting normally, you’re stuck on a blue screen showing the stop code UNMOUNTABLE_BOOT_VOLUME, sometimes with your system also caught in a restart loop. It’s most commonly triggered by file system corruption, a corrupted Master Boot Record (MBR) or GUID Partition Table (GPT), a problematic Windows update, or in more serious cases, a physically failing hard drive or memory issue.
A relevant note if you’re on Windows 11 version 24H2 or 25H2: Microsoft’s January 2026 security update (KB5074109) caused widespread UNMOUNTABLE_BOOT_VOLUME failures on affected systems. If your error started shortly after a recent Windows update, that update itself may be the direct cause, and uninstalling it from Recovery Environment may resolve things faster than the general steps below.
Try This First: Let Automatic Repair Run
Before diving into manual fixes, it’s worth letting Windows try to fix itself. If your PC restarts into Automatic Repair on its own after hitting this error, let it run — it can take 15–20 minutes, during which you may just see a black screen with a cursor. If that resolves it, you’re done. If it fails or the error persists, move on to the manual steps.
Access the Windows Recovery Environment
If your PC won’t reach the Automatic Repair screen on its own, you’ll need to force your way into the Windows Recovery Environment (WinRE):
- Turn your PC on, and as soon as Windows starts loading, hold the power button to force it off
- Repeat this two or three times
- On the next boot attempt, Windows should detect the repeated failure and launch Automatic Repair
If that still doesn’t work, you’ll need a Windows installation USB or DVD created on another computer. Boot from it, and select Repair your computer rather than Install now to reach the same recovery menu.
Run Startup Repair
From the recovery menu, go to:
Troubleshoot > Advanced options > Startup Repair
Let this complete fully, then restart normally to see if the error is resolved. This step alone fixes the issue for a meaningful share of cases, particularly when the cause is a corrupted system file rather than deeper disk damage.
Run CHKDSK to Repair the Drive
If Startup Repair doesn’t fix it, open Command Prompt from the same Advanced Options menu and run:
chkdsk C: /f /r /x
This scans your drive for file system errors and bad sectors and attempts to repair them. Depending on your drive size, this can take a while — let it run to completion rather than interrupting it.
Rebuild the Boot Records
If the drive itself checks out but Windows still can’t boot, the Master Boot Record or boot configuration may be the problem. From Command Prompt, run each of these in order:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
These rebuild the records Windows relies on to locate and load the operating system correctly.
Run a System File Check
If you’re still stuck, a system file scan can catch corruption that the previous steps didn’t address:
sfc /scannow
Note that this command generally needs to run from a fully booted Windows environment rather than Recovery Environment to work properly — if you can get to a working desktop at any point, run it from there.
When to Suspect a Hardware Problem
If none of the above resolves the error, or it keeps recurring, the underlying cause may be a failing drive or bad RAM rather than software corruption. Persistent boot failures, repeated automatic repair failures, and errors that return shortly after a successful fix are all signs worth taking seriously. At this point, backing up any accessible data and having the drive tested — or replaced — is a safer path than continuing to run repair commands on failing hardware.
Join The Discussion
Have you run into the Unmountable Boot Volume error yourself, and what ended up fixing it for you? Share which step in the process worked, whether a specific Windows update was the trigger, or any details about your hardware setup that might help others troubleshoot faster. If you’re currently stuck on this error, feel free to ask questions about any of the steps above — there’s a good chance someone here has hit the same issue and can help you figure out what’s different about your situation.
