INACCESSIBLE_BOOT_DEVICE (Stop Code 0x7B) After an Update? The Fix That Isn't a Reinstall

Your PC blue-screens on startup with INACCESSIBLE_BOOT_DEVICE (stop code 0x7B) — often right after a Windows update, a BIOS storage-mode change (AHCI/RAID/IDE), or moving the drive to another machine.

What it means: Windows reached the point where it needs to mount the system drive and couldn’t — either the boot driver it expects isn’t loading, or an update is stuck half-applied. The disk is usually fine. That’s why the nuclear options you see everywhere are the wrong first move.

Why the usual advice misfires: most articles jump straight to bootrec /fixmbr /rebuildbcd or a clean reinstall. Those don’t address the two most common real causes — a pending update that didn’t finish, or a storage-controller driver that’s disabled — and a reinstall wipes your data to fix something that’s a 2-minute change.

Get to recovery first: force-power-off during boot three times to trigger Automatic Repair → Advanced options → Troubleshoot → Advanced options → Command Prompt. (Or boot from Windows install media → Repair your computer.)

Fix 1: Roll back a stuck update (most common after Windows Update)

From the WinRE Command Prompt, revert the half-applied update offline:

DISM /Image:C:\ /Cleanup-Image /RevertPendingActions

(Adjust C: if your Windows volume has a different letter in WinRE — check with diskpart → list volume.) Then neutralize a stuck pending operation:

ren C:\Windows\WinSxS\pending.xml pending.old

Reboot. This is Microsoft’s documented offline recovery for a pending-update 0x7B.

Fix 2: If it started after changing SATA mode (AHCI/RAID/IDE)

If 0x7B began right after a BIOS/UEFI change or a new motherboard, the storage driver Windows needs is disabled. Easiest fix: reboot into BIOS and set the SATA/NVMe mode back to what it was (usually AHCI). If you must keep the new mode, the driver’s Start value has to be enabled before the switch — so revert the BIOS setting, boot Windows, then change it the supported way.

Fix 3: Run Startup Repair, then SFC/DISM against the offline image

1. Troubleshoot → Advanced options → Startup Repair — let it run fully.
2. If it can’t fix it, from the Command Prompt repair system files offline:

   sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
   DISM /Image:C:\ /Cleanup-Image /RestoreHealth

Fix 4: Bad filter drivers (last resort, advanced)

A leftover UpperFilters/LowerFilters entry from uninstalled disk software (some AV, encryption, or backup tools) can block the boot device. In regedit (load the offline SYSTEM hive), removing the offending filter entries on the storage controller’s class key resolves it — but back up the hive first; wrong edits re-trigger 0x7B.

FAQ

Is my drive dead? Rarely. 0x7B is about Windows loading the boot driver, not the disk failing. If Fixes 1–3 work, your data was never at risk.

It happened right after a feature update — coincidence? No — a pending/half-applied update is the #1 cause. Start with Fix 1 (RevertPendingActions).

Can I avoid the offline registry surgery? Usually yes — Fixes 1–3 resolve the vast majority. Save Fix 4 for cases tied to known disk-filter software.

Sources: Microsoft Learn — Advanced troubleshooting for Stop error 7B or INACCESSIBLE_BOOT_DEVICE