Storage · critical

How to fix INACCESSIBLE_BOOT_DEVICE (0x7B)

Storage troubleshooting guide

What this error means

Windows lost access to the drive it starts from while it was booting, so it cannot continue. Microsoft lists the typical triggers: a changed storage controller mode in the BIOS (for example AHCI or RAID), a new disk controller or moved drive, damaged boot or file system data, a storage driver that is missing or blocked, and an interrupted Windows update. A failing drive or controller can cause it too. Because Windows does not start, most fixes are done from the recovery environment.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Intermediate
Before changes
Medium; recovery commands change boot files, and a reset removes apps

Reviewed by Matyáš Rada · Documentation checked: 2026-10-30 · Checked against Microsoft's bug check and stop error 0x7B troubleshooting documentation; not tested on every configuration.

Before you begin

Do not reinstall Windows first: your files are usually still on the drive. If the drive is encrypted with BitLocker or device encryption, the recovery tools will ask for the recovery key, which you can find at aka.ms/myrecoverykey on another device. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Undo recent BIOS and hardware changes

Microsoft names a changed controller mode, a new disk controller and a moved drive as common triggers.

  1. Enter the BIOS/UEFI and check the storage or SATA mode. If you changed it (for example from RAID or Intel RST/VMD to AHCI, or the other way), set it back to the previous value.
  2. If you reset the BIOS or updated it recently, check the storage mode and boot order again; resets can change them.
  3. Check that the drive Windows is on appears in the BIOS. On a desktop, reseat the drive and its cables.
  4. Disconnect drives and controllers you added recently.

Changing the storage mode on a working installation can itself cause this error. Only change it back to what it was before.

What to expect

Windows starts once the original storage settings are restored.

If it does not help

If the drive does not appear in the BIOS at all, the problem is the drive or its connection, not Windows; go to step 4.

Browse related errors
02Run Startup Repair

Startup Repair fixes many boot configuration problems automatically.

  1. After two or three failed starts, Windows opens Automatic Repair. Choose Advanced options. If it does not appear, start from a Windows installation USB and choose Repair your computer.
  2. Choose Troubleshoot > Advanced options > Startup Repair and select your Windows installation.
What to expect

Windows starts normally after the repair.

If it does not help

If Startup Repair cannot fix the PC, go back to Advanced options for the next steps.

Browse related errors
03Remove the latest update

Microsoft documents this stop code after Windows updates that did not finish installing.

  1. In Troubleshoot > Advanced options, choose Uninstall Updates and remove the latest quality update first, then the latest feature update if needed.
  2. Alternatively, choose System Restore and pick a restore point from before the error.
  3. If that is not available, open Command Prompt from Advanced options and run dism /Image:C:\ /Cleanup-Image /RevertPendingActions (check first with dir C:\ that C: is the Windows drive in recovery).

The Windows drive may have a different letter in the recovery environment; use the letter where dir shows the Windows folder.

What to expect

Windows starts after the unfinished update is removed.

If it does not help

Pause updates for a week after you get back into Windows, then install them again.

Browse related errors
04Check that the drive is visible

If Windows recovery cannot see the drive, no software repair will work.

  1. In Advanced options, open Command Prompt.
  2. Run diskpart, then list disk and list vol. Look for your Windows drive and its letter, then type exit.
  3. Note the letter of the volume that contains the Windows folder.
What to expect

The disk and the Windows volume are listed.

If it does not help

If the disk is missing, test it in another PC or with the maker's tool. If it is listed but shows as RAW, go to step 5.

Browse related errors
05Check and repair the file system

Damaged file system data on the system drive prevents Windows from reading its boot files.

  1. In the recovery Command Prompt, run chkdsk C: /f /r (replace C: with the Windows volume letter).
  2. Then run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows with the same letter.
  3. Close the Command Prompt and choose Continue to start Windows.

Chkdsk /r can take hours on large drives. Do not interrupt it.

What to expect

Chkdsk and SFC finish and Windows starts.

If it does not help

If chkdsk reports many bad sectors, copy your files to another drive as soon as possible and replace the drive.

Browse related errors
06Rebuild the boot files

If the boot configuration points to the wrong partition, Windows cannot find its system drive.

  1. In the recovery Command Prompt, run bcdboot C:\Windows (with your Windows volume letter) to recreate the boot files.
  2. If Windows still does not start, run bootrec /rebuildbcd and add the Windows installation it finds.
What to expect

Windows starts with the new boot configuration.

If it does not help

If the error remains, the cause is more likely a driver or hardware problem; continue with step 7.

Browse related errors
07Reset or reinstall Windows

When storage drivers or system files cannot be repaired, a fresh installation restores a working boot.

  1. Copy your files off the drive first, for example by connecting it to another PC.
  2. Choose Troubleshoot > Reset this PC > Keep my files, or install Windows from a USB created with Microsoft's media creation tool.
  3. On newer Intel laptops, if the installer cannot see the drive, load the Intel RST/VMD driver from the laptop maker during setup.

Reset this PC removes installed apps even when you keep your files. A clean install erases the drive.

What to expect

A working Windows installation that starts normally.

If it does not help

If the error also appears on a fresh installation, the drive, controller or motherboard is faulty; contact the PC maker.

Browse related errors

Possible causes

  • Storage controller mode changed in the BIOS (AHCI, RAID, Intel RST/VMD)
  • A Windows update that did not finish installing
  • Damaged boot configuration or file system
  • Missing or blocked storage drivers, or third-party disk filter drivers
  • Failing drive, cable or storage controller

Sources & further reading