sodcalculator

10 Tech How-To

Fix Inaccessible Boot Device Error in Windows 10

Guide 10-44230 · Updated · Step by step

The Inaccessible Boot Device error (stop code 0x0000007B) appears when Windows 10 cannot read the system drive during startup, often after a hardware change, a failed driver update, or a corrupted disk controller driver. The fix usually involves booting into the Windows Recovery Environment and using Startup Repair, checking the BIOS/UEFI storage mode, or rebuilding the Boot Configuration Data (BCD). Below are the most reliable methods, ordered from least to most invasive, with exact steps for each.

What Causes the Inaccessible Boot Device Error?

This stop code means the Windows kernel lost access to the boot volume. Common triggers include:

  • Changing SATA mode in BIOS/UEFI (e.g., switching from IDE to AHCI or vice versa) after Windows was installed with the other setting.
  • Moving the system drive to a different port or controller (e.g., from an Intel SATA port to an ASMedia or Marvell port).
  • Corrupted or outdated storage drivers (especially after a Windows update or a motherboard driver install).
  • Damaged boot files (BCD, bootmgr, or the Windows partition itself) from a power outage, disk error, or malware.
  • Physical drive failure – a failing SSD or HDD can produce this error intermittently before dying.

Before You Start: Prepare a Recovery Environment

Most fixes require booting into the Windows Recovery Environment (WinRE). If Windows fails to start three times, it should automatically enter WinRE. If not, you can create a Windows 10 installation USB on another PC using Microsoft’s Media Creation Tool. Insert the USB, boot from it, and choose Repair your computer instead of Install now. From there you’ll reach the blue screen with Troubleshoot and Advanced options.

Method 1: Run Startup Repair

  1. In WinRE, go to Troubleshoot → Advanced options → Startup Repair.
  2. Select your Windows 10 installation (usually the only one listed).
  3. Wait for the repair to finish. It may take 10–15 minutes.
  4. If it says it couldn’t repair, try again once – sometimes a second pass works.

Startup Repair scans for common problems like missing boot files or a corrupted registry. It won’t fix driver issues, but it’s the fastest thing to try and costs nothing. If it fails, move to the next method.

Method 2: Check the BIOS/UEFI SATA Mode

This is the single most common cause after a hardware change. Windows 10 installs with the storage controller in a specific mode – usually AHCI (modern) or IDE (legacy, rare on new systems). If you or a BIOS update changed it, Windows can’t find its boot drive.

  1. Restart and press the key to enter BIOS/UEFI (often Del, F2, F10, or Esc – check your motherboard manual).
  2. Look for a setting called SATA Mode, Storage Mode, or Controller Mode under a section like Advanced or Integrated Peripherals.
  3. Set it to AHCI if it’s on IDE, or to IDE if it’s on AHCI but you’re sure the drive worked before with IDE.
  4. Save and exit (usually F10). Try booting Windows.

If you changed from IDE to AHCI and Windows still fails, you may need to enable AHCI in Windows first before switching. That requires a registry edit – see Method 5.

Method 3: Rebuild the Boot Configuration Data (BCD)

If the BCD is corrupted, Windows can’t locate the boot files. Rebuilding it from the command prompt is a reliable fix.

  1. In WinRE, go to Troubleshoot → Advanced options → Command Prompt.
  2. Type bootrec /scanos and press Enter. It should find your Windows installation.
  3. Type bootrec /rebuildbcd. When asked to add the installation to the boot list, type Y and press Enter.
  4. Type bootrec /fixmbr and bootrec /fixboot (if these fail with “access denied”, skip them – the rebuild may be enough).
  5. Exit and restart.

If bootrec /rebuildbcd says the installation is not found, you may need to assign a drive letter to the boot partition first. That gets complicated; try the next method or use a third-party BCD editor from another PC.

Method 4: Re-enable the Storage Controller Driver

If the error appears after a Windows update or a driver update, the storage driver may have been disabled or replaced with one that doesn’t work. You can re-enable it from the registry.

  1. Boot into WinRE Command Prompt as above.
  2. Type regedit and press Enter.
  3. In the Registry Editor, click on the HKEY_LOCAL_MACHINE hive, then go to File → Load Hive.
  4. Navigate to the Windows\System32\config folder on your system drive (it may be D: or E: in the recovery environment). Select the file named SYSTEM.
  5. Give the hive a name like OfflineSystem.
  6. Go to OfflineSystem\ControlSet001\Services and find the driver for your storage controller – often storahci, iaStorV, or nvme. Right-click it and set Start to 0 (boot start) or 1 (system start).
  7. Close the registry, unload the hive (File → Unload Hive), and restart.

This is advanced. If you’re not comfortable with the registry, skip to Method 6.

Method 5: Use System Restore or Automatic Repair

If the error started after a recent change, a system restore point can roll back the problematic driver or update.

  1. In WinRE, go to Troubleshoot → Advanced options → System Restore.
  2. Choose a restore point from before the error started.
  3. Follow the prompts. This does not affect personal files.

If System Restore isn’t available, try Startup Repair again but this time choose Advanced options → Startup Settings → Restart, then press 4 or F4 to boot into Safe Mode. Safe Mode loads a minimal set of drivers; if Windows boots there, you can uninstall the problematic driver or run sfc /scannow from an elevated Command Prompt.

Method 6: Reset This PC (Last Resort)

If nothing else works, you can reinstall Windows while keeping your files. This is a nuclear option but often fixes even the most stubborn driver corruption.

  1. In WinRE, go to Troubleshoot → Reset this PC.
  2. Choose Keep my files (this removes apps and settings but keeps personal files in the Users folder).
  3. Follow the prompts. You’ll need to reinstall your programs afterward.

If the drive itself is failing, even this may fail. Back up what you can from the recovery environment – you can copy files to an external USB drive using Command Prompt or File Explorer if you can access it.

Frequently Asked Questions

Can I fix this error without reinstalling Windows?

Yes, in most cases. The methods above – especially Startup Repair and checking the SATA mode – resolve the issue without a reinstall. Only if the drive is physically damaged or the boot files are beyond repair would you need to reinstall.

What does “Inaccessible Boot Device” mean exactly?

It means Windows loaded its kernel but couldn’t read the boot volume – usually the C: drive. The stop code is 0x0000007B. It’s not a hardware failure by itself; it’s a communication problem between Windows and the storage controller.

How do I know if my drive is failing?

If you hear clicking sounds (HDD), see SMART warnings in BIOS, or the error appears randomly even without hardware changes, the drive may be failing. You can test it from another PC with tools like CrystalDiskInfo (for HDD/SSD health) or the manufacturer’s diagnostic tool.

Will changing SATA mode delete my files?

No. Changing the SATA mode in BIOS does not touch data on the drive. It only changes how the controller communicates with the drive. However, if Windows can’t boot after the change, you may need to revert it.

Can this error happen on a new SSD?

Yes. If you cloned Windows to a new SSD and didn’t enable AHCI mode (or the new SSD uses NVMe while the old one used SATA), the error can appear. Make sure the new drive is properly connected and the BIOS is set to the correct mode.

Is there a way to prevent this error?

Keep your storage drivers updated, avoid changing SATA modes after installation, and always shut down properly. If you plan to switch from IDE to AHCI, enable it in Windows first using the registry method (set storahci Start to 0) before changing BIOS.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →