Fixing INACCESSIBLE_BOOT_DEVICE on Windows

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 Repair

Startup 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 /rebuildbcd

Run 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 /r

A 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.inf

Step 7: check System Restore as a rollback option

WinRE → Troubleshoot → Advanced options → System Restore

If 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 prompted

This 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.

Why this specific error means the boot driver, not the OS itself, failed

INACCESSIBLE_BOOT_DEVICE occurs at a very specific, early point in Windows’ own boot sequence — after the boot manager has successfully located and begun loading the kernel, but before the storage driver stack needed to actually read the rest of the operating system from disk has finished initializing correctly. This timing is exactly why it’s such a strong, specific signal pointing at the storage driver or controller configuration rather than a generic “something is broken” boot failure: Windows has already proven it can find and start loading itself, and the failure is specifically in the next step, gaining continued read access to the disk it just started reading from. Recognizing this narrows the entire investigation immediately toward storage-related causes rather than a broader, less-targeted boot troubleshooting sweep.

Checking disk connections physically, before assuming a software cause

For a desktop machine or a laptop with a user-accessible drive bay, a genuinely loose SATA or NVMe connection — from a recent case-opening for an upgrade, cleaning, or hardware change — can produce intermittent or total loss of disk access that presents identically to a driver or boot-configuration problem from Windows’ own perspective. Before working through the more involved recovery-environment steps above, physically reseating the drive’s data and power connections (for a desktop) or reseating an NVMe module (on laptops where this is feasible) rules out a purely physical, non-software cause that no amount of bootrec or chkdsk troubleshooting from within Windows would ever actually address.

Related:

Sources: