Fixing the unmountable boot volume error in Windows

The “Unmountable Boot Volume” message is a Blue Screen of Death that appears when Windows cannot read or mount the partition containing its boot files. It often occurs during startup, followed by repeated restarts, Automatic Repair loops, or a failure to load Windows.

Common triggers include an interrupted update, sudden power loss, faulty cloning, damaged system files, storage-driver trouble, or a failing SSD or hard disk. This is usually more serious than ordinary slowness, although a separate DNS or connection problem can make a PC seem unreliable.

Repairing it safely means protecting data, checking the drive, repairing the file system, and rebuilding boot records. Reinstalling Windows first can hide the fault and erase recovery options, so order matters.

Australian users can handle many cases with Windows Recovery, while a local computer technician is wise when files are business-critical. Shops commonly charge a diagnostic fee, explain the quote before work starts, and offer imaging, data recovery, clean installation, or drive replacement.

Recognise the failure and protect your files

First, separate a boot failure from other symptoms. If Windows reaches the desktop and only web pages load slowly, the boot volume is probably not the problem; changing DNS is a different route and may improve slow browsing. A stop screen during startup needs storage and boot repair instead.

What you see Likely meaning Best next step
Blue screen during startup The boot partition cannot be mounted Enter Windows Recovery and test the drive
Automatic Repair loop Boot configuration or system files are damaged Repair the file system, then rebuild boot records
Missing drive, clicking or repeated resets Hardware failure is likely Image important files before replacing it
Windows opens but an external disk fails USB port, cable or external-drive fault Test the device on another port

Record whether the drive appears in BIOS or UEFI, listen for clicking, and note any recent update, power cut, cloning attempt or hardware change. A drive that disappears intermittently needs imaging before further repair, not an aggressive formatting command.

Build a safe recovery environment

Before changing anything, copy irreplaceable files to another drive or cloud storage if Windows will start. If it will not, avoid repeated boot attempts and use recovery options sparingly. Keep the mains adapter connected, remove USB flash drives, memory cards and external disks, and note which internal drive contains Windows.

In Windows 10 or 11, interrupt startup with a firm tap of the Shift key to reach Advanced Startup. If Windows still starts, Shift+Restart is more reliable. Choose Troubleshoot, Advanced Options, then Command Prompt. Automatic Repair can run first, but its result should be checked rather than treated as proof that the disk is healthy.

Use DiskPart to identify the Windows and system partitions:

diskpart
list volume
select volume <number>
assign letter=D
exit
dir D:\

Replace the sample volume number and drive letter with the values shown on your machine. Look for the partition containing Windows, Program Files and Users; the small FAT32 EFI partition is separate and should not be formatted.

Test disk health and repair the file system

Check storage with the manufacturer’s diagnostic utility and review SMART status and event information. A warning, unreadable sectors or a drive that vanishes from DiskPart points to hardware failure. A clean SMART report does not exclude file-system corruption, and a damaged disk can report normal health until it fails completely.

If the drive is accessible and important data has been protected, run Check Disk against the Windows volume, changing D to the assigned letter:

chkdsk D: /f /r

The /f option repairs file-system errors; /r includes damaged sectors and can take hours. Unreadable clusters may be replaced with zeroed data, so image a failing drive first. If CHKDSK reports unrecoverable errors, move to recovery rather than repeating it.

Once Windows can start, repair component files with an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Run DISM before SFC because DISM repairs the source image used by SFC. Neither replaces a failing drive, and resource-protection errors mean the Windows installation still needs attention.

Rebuild the Windows boot configuration

After the file system is sound, use Startup Repair from Advanced Options. If Windows starts after that repair, update the storage driver and complete the pending Windows update rather than leaving the machine in a test environment.

For a legacy BIOS or MBR installation, Command Prompt can rebuild the master boot record and scan for operating systems:

bootrec /fixmbr
bootrec /fixboot
bootrec /scandisk

Use those commands only when the PC was installed in legacy mode. On a UEFI machine, bootrec /fixboot may report “Access is denied”; that message does not automatically mean the drive has failed.

For UEFI, assign a temporary letter such as S to the EFI System Partition, then run:

bcdboot C:\Windows /s S: /f UEFI

Replace C with the Windows volume and S with the EFI volume. The command recreates the boot configuration and places the correct files on the firmware partition. Do not convert a UEFI installation to legacy mode or delete the EFI partition simply to make one command work.

Recover the installation without reformatting

If storage is repaired but Windows still fails, open Startup Settings from Windows Recovery and try Safe Mode. Safe Mode can reveal a faulty storage driver, third-party security product or update conflict. Remove the offending software, complete or roll back the update, and then test a normal restart.

System Restore or “Uninstall updates” can return the installation to an earlier working state. Keep personal files when choosing repair options, and do not select Reset this PC or “Remove everything” unless a backup has been verified. A clean installation should be the final step after file-system, boot-record and update repairs have failed.

A new installation using Microsoft’s official media can resolve persistent corruption, but it does not repair a damaged disk. Create installation media on another working PC, confirm the target drive is visible in the firmware setup, and use the same Windows edition. Before formatting, copy user folders or use specialist recovery for anything that cannot be replaced.

Decide whether the hardware must be replaced

Replace the boot drive when SMART reports failure, Windows logs repeated I/O errors, the drive disappears, or CHKDSK finds unrepairable sectors. Do not clone repeatedly from a failing source. If the operating-system disk is gone, install Windows on a new SSD and restore only what was recovered safely.

The fault may also be outside the drive. Test the power supply, SATA or NVMe connection, RAM and firmware settings one at a time, then check manufacturer notes for known storage issues. Update BIOS or UEFI firmware only after the system is stable and power is reliable, because an interrupted flash can create another fault.

In Australia, request an itemised quote covering diagnosis, recovery, parts and labour. The Australian Consumer Law can apply to faulty goods or repair services, but software work and accidental data loss can complicate the boundary; keep the report and warranty details. If a drive clicks, ask a local Aussie data-recovery specialist about imaging first. Sydney, Melbourne and Brisbane customers can compare local specialists, while regional users should check packaging, insurance and return freight.

Reduce the risk of another boot failure

Maintain at least two copies of important data, with one kept off the machine; cloud and external storage separate the copies. Test restores and store any BitLocker recovery key away from the PC. On compatible PCs, Windows also creates a recovery file automatically, and it is worth knowing where it is stored.

Use a surge protector and, where outages are common, a UPS. Keep the drive cool, leave free space, complete updates without forcing a shutdown, and scan after Windows returns. A Windows Recovery USB made on another working PC provides a fallback if future updates damage the boot partition.