Fixing INACCESSIBLE_BOOT_DEVICE on Windows
Windows blue-screens with INACCESSIBLE_BOOT_DEVICE right at startup, before the desktop ever loads. Here's how to diagnose whether it's a driver, disk, or boot configuration problem from Recovery.
INACCESSIBLE_BOOT_DEVICE means Windows successfully started booting but then lost access to the disk holding the operating system itself — before the desktop, before most drivers even load — this walks through the most common causes.
Step 1: boot into Windows Recovery Environment
If the system fails to boot normally three times in a row, Windows Recovery Environment (WinRE) should launch automatically; otherwise, boot from installation media and select Repair your computer.
Step 2: check for a recent driver or storage controller change
This error commonly appears immediately after changing the SATA/storage controller mode in BIOS/UEFI (AHCI to RAID, or vice versa) without the corresponding storage driver already installed — check whether this precedes the problem, and if so, revert the BIOS setting first as the fastest fix.
Step 3: run Startup Repair
WinRE → Troubleshoot → Advanced options → Startup RepairStartup Repair specifically targets boot-configuration problems and can resolve a meaningful fraction of these cases automatically.
Step 4: check the boot configuration data manually if Startup Repair doesn’t resolve it
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcdRun from the Command Prompt available within WinRE — these rebuild the boot configuration store and re-scan for installable Windows installations if the BCD itself is the corrupted piece.
Step 5: check disk health directly
chkdsk C: /f /rA failing or corrupted disk can produce exactly this error if Windows loses access to critical system files partway through boot — running chkdsk from the recovery environment checks for and attempts to repair filesystem-level corruption.
Step 6: check for a missing or outdated storage driver, for unusual storage controllers
For NVMe drives or RAID configurations using a manufacturer-specific driver rather than the generic Windows one, boot with the correct driver injected via WinRE’s drvload command, then reinstall the correct driver once back in Windows:
drvload X:\drivers\storage_driver.infStep 7: check System Restore as a rollback option
WinRE → Troubleshoot → Advanced options → System RestoreIf the problem started right after a specific update or driver installation, rolling back to a restore point from before that change is often faster than diagnosing the specific root cause directly.
Step 8: as a last resort, repair-install Windows in place
Boot from installation media → Install now →
choose "Keep personal files and apps" when promptedThis reinstalls Windows system files while preserving user data and installed applications — appropriate when the above steps haven’t resolved a genuinely corrupted system installation.
Why checking for a recent BIOS storage-mode change first saves the most time
This specific error has a disproportionately common single cause — a storage controller mode change in firmware settings without a matching driver already present — which is fixable in under a minute by simply reverting the BIOS setting. Ruling this out before running chkdsk, rebuilding boot configuration data, or reinstalling Windows avoids much more time-consuming troubleshooting for what’s very often a one-setting fix.