Fixing the INACCESSIBLE_BOOT_DEVICE Blue Screen on Windows 11

The INACCESSIBLE_BOOT_DEVICE stop code means the Windows boot loader tried to read your system drive during startup and failed. It commonly appears after an update, a storage-controller change, or disk corruption, and it usually leaves you stuck in a reboot loop with no way to reach the desktop. The reassuring part: your data is almost always intact, and the repair happens entirely from the recovery environment. Here is how to get back in.

Key takeaways

• The error means Windows couldn't mount the boot partition at startup, usually corrupt Boot Configuration Data (BCD), a missing storage driver, or a damaged file system.
• If it started right after you changed the BIOS storage mode (RAID/AHCI), switching it back is often the instant fix.
• On Windows 11, bootrec /fixboot frequently returns "Access is denied", the modern replacement is bcdboot after assigning a letter to the EFI partition.
• Your data is usually safe, back it up before any reinstall, never wipe first.

What this error actually means

At boot, Windows must mount the partition that holds the OS. If it can't, because of corrupted BCD, a missing storage driver, or a damaged file system, it halts with this BSOD rather than load a broken system. Win11 24H2 in particular has triggered it on some configurations after a feature update, which is why undoing recent updates is an early step.

Match the cause to the fix

Most cases trace to one of a handful of triggers. This table maps each to the step that resolves it, roughly in order of likelihood and speed:

Likely cause	Tell-tale sign	Fix	Time
Changed BIOS storage mode	Started right after a BIOS change	Switch RAID/AHCI back (Step 6)	2 min
Bad recent update	Started after Windows Update	Uninstall Updates (Step 3)	10 min
Corrupt BCD	No recent change, sudden failure	Startup Repair, then bcdboot (Steps 2, 4)	15 min
Damaged file system	Crash, power loss, dirty shutdown	chkdsk C: /f /r (Step 4)	30 to 90 min
Failing drive / loose cable	Drive vanishes from BIOS intermittently	Reseat drive, check SMART (Step 6)	10 min

Step 1: Reach the Windows Recovery Environment (WinRE)

Because you can't boot normally, you need WinRE.

1. Force a shutdown by holding the power button while Windows tries to start.
2. Repeat this three times in a row. On the third boot, Windows launches Automatic Repair.
3. Choose Advanced options to open WinRE.

If that doesn't trigger, boot from a Windows 11 installation USB, click Repair your computer, then go to Troubleshoot > Advanced options.

Step 2: Try Startup Repair

From Advanced options, run Startup Repair first. It automatically diagnoses and fixes common boot issues, including BCD problems, and is the lowest-risk option. Let it complete and attempt a normal reboot.

Step 3: Uninstall a recent update

This error frequently follows a quality or feature update.

1. In Advanced options, choose Uninstall Updates.
2. Try Uninstall latest quality update first.
3. If that fails, try Uninstall latest feature update.
4. Reboot.

Step 4: Repair boot files from Command Prompt

If automatic tools don't help, rebuild the boot data manually. Open Advanced options > Command Prompt and run these in order:

bootrec /scanos
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

When fixboot returns "Access is denied"

On Windows 11 (and Windows 10 1709 and later), bootrec /fixboot very often fails with "Access is denied." This is expected behavior on UEFI/GPT systems, not a sign of a deeper problem. The reliable fix is to rebuild the boot files with bcdboot after giving the EFI partition a temporary drive letter:

diskpart
list volume

Find the small FAT32 ~100 MB volume (the EFI System Partition), note its number, then:

select volume <number>
assign letter=S:
exit
bcdboot C:\Windows /s S: /f UEFI

This recreates the boot configuration in the correct partition and is more effective than fixboot under UEFI. Adjust C: if Windows lives on a different letter in the recovery environment. The same bcdboot rebuild also fixes the closely related BAD_SYSTEM_CONFIG_INFO blue screen, which stems from the same boot-configuration corruption.

Then check the file system on the Windows volume:

chkdsk C: /f /r

Step 5: Repair system files offline

Corrupted system files can block boot. From the recovery command prompt:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
dism /image:C:\ /cleanup-image /restorehealth

Confirm the correct drive letter first (use diskpart then list volume). If the crash also produced other stop codes, our guide to the CRITICAL_PROCESS_DIED blue screen covers the same SFC/DISM repair in a bootable system.

Step 6: Check BIOS/UEFI and physical connections

If software repairs fail, suspect hardware or firmware.

• Enter BIOS/UEFI and confirm the boot drive is detected.
• Verify the SATA mode matches what Windows expects (usually AHCI).
• On desktops, reseat the SSD/NVMe drive and its cables.
• Confirm the correct disk is set as the primary boot device.

A drive that is intermittently undetected may be failing, the same SMART checks in our 100% disk usage guide apply once you can boot again.

Step 7: System Restore as a fallback

If you have restore points, Advanced options > System Restore can roll the system back to a working state without touching your personal files. This often reverses a bad driver or update that caused the failure.

Before you reinstall: back up your data

If nothing works and you're considering a clean install, copy your files off first. Open Command Prompt from WinRE and use it to reach your drive, or attach the disk to another PC. The error rarely means data loss, so don't wipe before backing up.

Frequently asked questions

Will I lose my files fixing this error?

Almost never. INACCESSIBLE_BOOT_DEVICE is a boot-configuration or driver problem, not data loss. The partition and its contents are usually intact, which is exactly why you should back up before any reinstall rather than assume the data is gone.

Why does bootrec /fixboot say "Access is denied"?

This is normal on modern UEFI/GPT Windows installs and not a malfunction. Microsoft changed how the command behaves starting in Windows 10 1709. Use the bcdboot method in Step 4 instead, it rebuilds the same boot files in a way that works on UEFI systems.

It happened right after a Windows update, what now?

Boot into WinRE and use Uninstall Updates (Step 3). Win11 24H2 has triggered this on some hardware after feature updates. Removing the latest quality or feature update and rebooting clears most update-induced cases.

How do I know if it's a hardware problem?

If Startup Repair, update removal, and a bcdboot rebuild all fail, and the drive sometimes disappears from BIOS, suspect the drive or its cable. Reseat the drive, try a different SATA/NVMe slot, and check SMART health once the system boots.

Quick recap

Start with Startup Repair, undo recent updates, then rebuild boot files, and when fixboot is denied, switch to bcdboot after assigning the EFI partition a letter. Run CHKDSK, and if you recently changed the BIOS storage mode, switch it back first. That single change resolves a large share of these blue screens.