Rightek Rescue · Guides · Inaccessible Boot Device

INACCESSIBLE_BOOT_DEVICE (0x7B)? Here's how to fix it

This blue-screen stop code means Windows started to boot but couldn't reach the drive it lives on — usually because the storage controller mode changed or a driver isn't primed. The disk and your files are fine; Windows just can't talk to the controller.

Updated ยท written and tested by Rightek IT Services

What you're seeing

  • A blue screen: INACCESSIBLE_BOOT_DEVICE
  • Stop code 0x0000007B
  • It started after a BIOS/UEFI change (AHCI ↔ RAID ↔ VMD), a Windows update, or cloning to a new SSD/PC

Why it happens

  • The firmware's storage controller mode (AHCI / RAID / Intel VMD) was switched, so Windows loads the wrong disk driver
  • The boot-start storage driver is missing or was half-injected after a hardware move
  • A failed update left the storage stack in a bad state

Fix it yourself — the manual steps

  1. Easiest: reboot into BIOS/UEFI and set the SATA/VMD mode back to what it was (often AHCI). If you don't know, try toggling AHCI ↔ RAID/VMD.
  2. Or boot Windows install media → Repair → Troubleshoot → Command Prompt and prime the inbox controllers so Windows can start in any mode.
  3. If it followed a clone, make sure the new drive is first in the boot order.
  4. Reboot.

Which controller mode should it be on?

Toggling blindly between AHCI, RAID and Intel VMD works often enough that it is worth trying, but you can narrow it down first. In the BIOS/UEFI, look for a setting named SATA Mode, SATA Operation, Storage Configuration or VMD Controller.

  • Most desktops and self-built machines: AHCI.
  • Many Dell, HP and Lenovo laptops shipped in the last few years: RAID On or Intel VMD, even with a single drive, because the platform driver expects it.
  • If the machine worked yesterday and you changed nothing: a firmware update may have reset it to defaults. Setting it back to what it was is the whole fix.

Change one setting at a time and reboot between changes. Changing the mode does not touch your data — it only changes how Windows talks to the disk.

Making Windows work in either mode

If you do not know which mode it was on, you can tell Windows to load the drivers for all of them, which makes the machine boot whichever way the firmware is set. From the Recovery Environment's Command Prompt, boot Windows into Safe Mode once (bcdedit /set {current} safeboot minimal, reboot), change the BIOS mode, let Windows start in Safe Mode — which loads the driver it needs — then clear the flag with bcdedit /deletevalue {current} safeboot and reboot normally.

It is a well-known sequence and it works, but note what it involves: modifying the boot configuration twice and a BIOS change in the middle, with a non-booting machine in between. Get the order wrong and you have a machine that boots to Safe Mode and nothing else.

If it started after cloning to a new drive

Cloning is the other common route to 0x7B, and the cause is different. The clone copied Windows successfully, but:

  • The old drive may still be first in the boot order, so the firmware is booting the original. Check the boot order and remove or disconnect the source drive to be certain.
  • The new drive may be on a different controller — SATA to NVMe especially — and Windows has no boot-start driver primed for it.
  • If the source was a different machine entirely, the storage driver it needs may never have been installed at all.

When it is not the controller

0x7B means Windows could not reach the disk. Usually that is the driver, but not always. If the BIOS itself cannot see the drive reliably — it appears on some boots and not others — no driver change will help, and you are looking at a cable or a failing drive. Check the drive is listed in the firmware before spending time on Windows.

⚡ The one-click way: let Rightek Rescue do it

Rescue switches Windows’ own storage drivers back on so Windows can reach the disk again — automatically. On any working PC: download Rescue, put it on a USB (one click makes it bootable), boot the affected PC from it, and choose Fix My PC. It finds the cause and repairs Windows in place — your files, accounts and programs stay where they are. Not sure what's wrong? It tells you free before it fixes anything.

FAQ

Will changing the BIOS mode erase my drive?

No - switching AHCI/RAID/VMD mode doesn't touch your data. It only changes how Windows talks to the disk.

Will I lose my files?

Very unlikely. This is a boot/system problem, not a data problem - your files are almost always intact. Rescue repairs the system side and leaves your personal files where they are. Any repair on a damaged drive carries some risk, so copy irreplaceable files off first if you can.

Do I need a second computer?

Yes - any working PC to download Rescue and make the USB. Any USB stick 8GB+ works.

Which Windows versions are supported?

Windows 10 and 11. Rescue runs from the USB, outside your broken Windows, so it works even when Windows won't start.

Does switching between AHCI and RAID erase my data?

No. The controller mode changes how Windows communicates with the disk, not what is written on it. Your partitions and files are untouched. The only risk is a machine that will not boot until the mode matches the driver Windows has primed, which is reversible by changing it back.

Why did this happen after a BIOS update?

Firmware updates commonly reset settings to their defaults, and storage mode is one of them. If your machine was set to AHCI and the default is RAID or VMD, Windows suddenly has the wrong driver primed for the controller it now sees. Setting it back is the entire fix.

I cloned my drive and now get 0x7B. What went wrong?

Usually one of three things: the old drive is still first in the boot order so the firmware is booting the original, the new drive is on a different controller type with no boot-start driver primed, or the source came from a different machine. Check the boot order first, since it costs nothing.