Skip to content
Thea

How to fix INACCESSIBLE_BOOT_DEVICE after Windows update

Affects
  • Windows 10
  • Windows 11, version 24H2
Daniel Okafor6 min read

Quick answer

The INACCESSIBLE_BOOT_DEVICE error (Stop error 7B) occurs when Windows loses access to its system partition during startup after installing an update. You can resolve this issue by booting into the Windows Recovery Environment (WinRE) using installation media to revert pending update actions with DISM, rebuild the boot configuration database, or repair damaged boot files.

The INACCESSIBLE_BOOT_DEVICE error—also known as Stop error 7B—is a blue screen error that occurs when Windows fails to read the system partition during the startup process. This issue usually surfaces right after installing a new Windows update, deploying a patch, or when the TrustedInstaller service fails to properly commit newly installed update packages due to component store corruption. When this happens, Windows cannot locate the critical boot files or storage drivers it needs to launch, resulting in an immediate startup crash loop.

This issue affects both Windows 10 and Windows 11 systems. It happens when update files remain partially installed, pending registry actions fail to execute, or storage stack filter drivers misbehave during reboot. Follow the step-by-step methods below to revert pending updates, repair damaged boot configuration files, and verify boot-critical drivers using the Windows Recovery Environment (WinRE).

Method 1: Revert pending update actions with DISM

When an update fails to commit completely, pending update operations can lock your boot volume. Reverting these pending actions cleans up stuck update queues and restores normal startup behavior. Use this method first if the error appeared immediately following a recent system update.

  1. Start your computer using installation media for your installed version of Windows.
  2. On the Install Windows screen, select Next, and then click Repair your computer.
  3. On the System Recovery Options screen, select Next and click Command Prompt.
  4. Type diskpart and press Enter, then type list vol and press Enter to locate your main OS partition drive letter (such as C: or D:). Type exit to close diskpart.
  5. Type dism /Image:C:\ /Cleanup-Image /RevertPendingActions (replace C: with your system drive letter) and press Enter to revert uncommitted updates.
  6. Change directories to your Windows installation by typing cd C:\Windows\WinSxS and check if pending.xml exists. If it does, type ren pending.xml pending.xml.old and press Enter.
  7. Warning: The following sub-steps modify offline registry hives. Type regedit in the command prompt to open the Registry Editor.
  8. Highlight HKEY_LOCAL_MACHINE, select File > Load Hive, browse to C:\Windows\System32\config, select the COMPONENT file (with no extension), and name the hive OfflineComponentHive when prompted.
  9. Expand HKEY_LOCAL_MACHINE\OfflineComponentHive, locate the PendingXmlIdentifier key if present, right-click it, and select Delete. Highlight OfflineComponentHive and click File > Unload Hive.
  10. Highlight HKEY_LOCAL_MACHINE, select File > Load Hive, browse to C:\Windows\System32\config, select the SYSTEM file (with no extension), and name it OfflineSystemHive when prompted.
  11. Expand HKEY_LOCAL_MACHINE\OfflineSystemHive\Select and check the Default value data. If it displays 1, expand ControlSet001; if 2, expand ControlSet002.
  12. Navigate to Control\Session Manager, check if PendingFileRenameOperations exists, right-click it, select Delete, and then highlight OfflineSystemHive and select File > Unload Hive.

Close the Registry Editor and Command Prompt, then restart your computer to see if Windows boots properly.

Method 2: Rebuild the Boot Configuration Database and boot files

If file system or boot partition corruption broke your boot path, repairing the Boot Configuration Database (BCD) and re-creating the system boot files will restore startup functionality. Use this method if your drive layout is intact but Windows cannot locate the boot loader.

  1. Open Command Prompt from your WinRE installation media as shown in Method 1.
  2. Type bcdedit and press Enter to view your current boot configuration settings.
  3. Examine the {bootmgr} entry to ensure device and path point to the correct device (such as partition=\Device\HarddiskVolume2 and \EFI\Microsoft\Boot\bootmgfw.efi for UEFI systems, or partition=C: for BIOS systems).
  4. Check the {default} entry to ensure device, path, osdevice, and systemroot point to your correct operating system partition and Windows folder.
  5. Create a safety backup of your current BCD store by typing bcdedit /export C:\temp\bcdbackup and pressing Enter. (If you ever need to restore this backup later, run bcdedit /import C:\temp\bcdbackup).
  6. If you receive an error stating that the store could not be opened, type bootrec /rebuildbcd and press Enter to search for Windows installations and rebuild the BCD store.
  7. If boot files are missing, use diskpart (list vol) to identify your OS drive letter and System drive letter.
  8. Re-create all boot files by typing bcdboot D:\windows /s R: /f ALL (where D: is your OS drive letter and R: is your assigned system partition letter) and press Enter.

Restart your system after the command finishes recreating the boot files.

Method 3: Repair system files and hard drive corruption

Corrupted system files or bad sectors on your storage drive after an interrupted update can prevent the boot controller from accessing the OS volume. Running disk and system file diagnostics repairs these corruption issues.

  1. Access Command Prompt from your Windows Recovery Environment media.
  2. Type chkdsk /f /r C: (replace C: with your OS drive letter) and press Enter to scan the disk for system volume corruption and bad sectors.
  3. Allow the chkdsk utility to complete its scan and repair process entirely.
  4. Type sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (replace C: with your OS drive letter) and press Enter.
  5. The System File Checker will scan offline Windows system files and automatically replace damaged or missing files.

Once both scans complete, close Command Prompt and restart your computer.

Method 4: Verify boot-critical drivers and non-standard filter drivers

Missing or disabled boot-critical drivers or incompatible non-Microsoft storage filter drivers can block storage controllers from loading during boot. Verifying driver registry entries resolves these underlying controller crashes.

  1. Open Command Prompt in WinRE, type regedit, and press Enter to launch Registry Editor.
  2. Warning: Modifying driver registry settings alters core startup behavior. Highlight HKEY_LOCAL_MACHINE, click File > Load Hive, browse to C:\Windows\System32\config\SYSTEM, and name the hive OfflineHive when prompted.
  3. Expand OfflineHive\ControlSet001\Services (or ControlSet002 based on your hive's Select\Default value).
  4. Check for the following essential driver keys under Services: ACPI, DISK, VOLMGR, PARTMGR, VOLSNAP, and VOLUME.
  5. Select each key and ensure the Start DWORD value is set to 0. If it is set to a different number, double-click Start and change the value data to 0.
  6. If any of these essential registry keys are missing, replace the system hive using the RegBack folder by running these commands at the WinRE command prompt: cd C:\Windows\System32\config, ren SYSTEM SYSTEM.old, and copy C:\Windows\System32\config\RegBack\SYSTEM C:\Windows\System32\config\.
  7. To check for corrupted filter drivers, expand OfflineHive\ControlSet001\Control\Class in Registry Editor.
  8. Search through the storage class entries (such as {4D36E96A-E325-11CE-BFC1-08002BE10318}) for UpperFilters or LowerFilters entries.
  9. If you spot a non-standard, non-Microsoft filter driver entry, double-click it in the right pane and delete only that specific filter driver name.
  10. Highlight OfflineHive, select File > Unload Hive, exit Registry Editor, and restart your computer.

If nothing worked

If none of these troubleshooting steps resolve the INACCESSIBLE_BOOT_DEVICE error, your PC may have encountered a physical hardware failure or a corrupted BIOS storage controller setting. Restart your computer and open your BIOS/UEFI firmware setup screen to verify whether your hard drive or SSD is listed under connected storage devices. Ensure that your storage controller mode settings (such as AHCI or RAID) have not been changed. If the drive does not appear in your BIOS or shows as missing when running list disk inside diskpart in WinRE, contact your computer manufacturer (OEM) or virtualization provider for hardware repair.

Sources

Frequently asked questions

What causes the INACCESSIBLE_BOOT_DEVICE stop error after a Windows update?

This error occurs when Windows loses access to the boot partition due to component-based store corruption during updates, bad storage controller settings, damaged system files, or corrupted boot configuration data.

Will reverting pending update actions delete my personal files?

No, running the DISM revert command only cancels uncommitted update installations and cleans pending update queues without deleting your personal files or documents.

What should I do if command prompt says the boot configuration data store cannot be found?

If Windows cannot locate the BCD store, run the bootrec /rebuildbcd command in the recovery command prompt to search for installed operating systems and rebuild the boot database from scratch.

Checked against Microsoft's release notes on ; re-checked when a new build ships.

Written by

Daniel Okafor

Writes Thea's error-code and app-breakage guides. Each fix is checked against Microsoft's documentation and community reports, and updated when a new Windows 11 build changes the steps.

More from Daniel Okafor

Related guides

  • Update ProblemsWindows 11, version 25H2 (OS Build 26200.9278)

    KB5120998 Not Installing or Stuck in Windows 11

    KB5120998 is an optional preview update for Windows 11 versions 24H2 and 25H2. If it becomes stuck during download or fails to install, you can resolve the issue by running the Windows Update troubleshooter, clearing the SoftwareDistribution cache folder, or running SFC and DISM scans. Because KB5120998 is a non-security preview release, you can also safely pause or skip the update until next month.

    Maya Reyes

  • Update ProblemsWindows 11 version 23H2

    KB5078883 Not Installing or Stuck in Windows 11

    If KB5078883 fails or gets stuck during installation on Windows 11, run the automated Windows Update troubleshooter from Settings. You can also use the Get Help app to reset update components or clear temporary system update files in Storage settings. Restart your PC afterwards and check for updates again to trigger a fresh download of OS Build 22631.6783.

    Daniel Okafor

  • How-To GuidesWindows 11, version 26H1

    How to run the Windows Update troubleshooter

    To run the Windows Update troubleshooter in Windows 11, navigate to Settings > System > Troubleshoot > Other troubleshooters and click the Run button next to Windows Update. The tool automatically scans background update components, resolves configuration errors, and clears cached files. After the process finishes, restart your computer and check for updates again.

    Priya Natarajan

  • Apps Not WorkingWindows 11 24H2

    Sound Not Working After Windows 11 Update

    If sound is not working after a Windows 11 update, your primary audio device may have been muted or swapped during the installation. You can resolve this issue by selecting your correct output device in Quick Settings, running the automated audio troubleshooter, or reconnecting your Bluetooth audio hardware. Follow these step-by-step methods to restore sound on your PC.

    Daniel Okafor