如果您 在Windows 11/10/8/7系统上应用Windows 更新后看到停止错误 – (Windows Updates)0x7B INACCESSIBLE_BOOT_DEVICE，请知道这是系统获得的引导状态的结果。Microsoft已经制定了一些步骤来帮助您解决此问题。让我们来看看它们。
0x7B Windows 更新(Windows Updates)后INACCESSIBLE_BOOT_DEVICE 蓝屏(INACCESSIBLE_BOOT_DEVICE Blue Screen)
此停止错误源于设备驱动程序和数据损坏导致的启动状态缺陷。有时它也可能是硬件故障或病毒的结果。无一例外，您将在蓝屏死机或停止错误上收到此停止 0x0000007B 错误(Blue Screen of Death or Stop Error)。
即使 Windows 从问题中恢复，您仍然会收到提示“ Windows 已从意外关机中恢复(Windows has recovered from an unexpected shutdown)”，并且此问题可能发生在任何版本的Windows上。如果这也是您的问题，这里有一些解决方案。
只需重新启动设备以查看问题是否自行解决。有时它确实会再次出现并且永远不会再次出现。埃利斯，继续读下去。
1]对硬盘控制器进行(Hard Drive Controller)更改(Make)
如果您最近对硬盘控制器进行了更改，这可能是原因，因此请撤消这些更改来扭转这种情况。您执行以下任何程序：
- 使用系统还原。
- 重新配置新的硬盘控制器。
- 如果重新配置不起作用并且您基本上不需要它，请移除新的硬盘驱动器控制器。
- 运行启动修复
- 回到驱动程序更新之前的硬盘控制器和设备驱动程序版本。
所有这些可能会或可能不会解决问题，具体取决于导致问题的原因。如果这个解决方案不起作用，至少你会知道你的硬盘控制器不是问题所在。
2]验证SCSI链终止
如果您使用的是SCSI硬盘驱动器，则错误的终止可能是错误的原因。所以你需要迎合这个问题才能解决它。但是，家用计算机通常使用PATA和SATA而不是SCSI，所以这可能不是您的问题，首先。
3]验证安装
确保(Make)硬盘驱动器安装正确。如果您最近没有安装任何新驱动器，则问题可能是其他问题。
4]验证BIOS配置
您需要确保您的硬盘已在BIOS中正确配置。根据需要更改(Change)设置以确保正确配置。
5]扫描病毒
如前所述，停止错误可能是由病毒引起的。所以你需要扫描病毒，主要检查引导扇区和MBR是否有恶意软件攻击。如果这是问题所在，请按照防病毒软件帮助的常规程序重新启动您的设备。始终(Always)保持您的防病毒软件更新，以防止此问题发生。
6]更新驱动程序
过时的硬盘控制器驱动程序可能会导致此错误，因此请更新设备驱动程序。
7]在BIOS中更改模式
某些高级SATA功能可能会导致此错误。将SATA(SATA) ( AHCI ) 模式更改为IDE模式（ATA或兼容模式(Compatibility Mode)）以撤消错误并在以后避免它。在某些旧版本中，解决方案可能正好相反。清除CMOS也有帮助。
8]运行chkdsk
如果启动卷损坏，在硬盘驱动器上运行 chkdsk 将解决问题。您可能必须从故障恢复控制台运行 chkdsk 。
9]硬盘驱动器错误
如果硬盘驱动器坏了，您将需要更换它。损坏的硬盘驱动器没有出路。
为了避免错误再次发生，请配置修补基础结构，以便在单次重新启动期间不会同时安装 CU 和增量更新。
高级故障排除：安装Windows 10更新(Update)后出现错误 7B Inaccessible_Boot_Device
当您在安装Windows 更新(Windows Update)后收到错误 7B Inaccessible_Boot_Device时，这与我们上面介绍的情况完全不同。我们将不得不检查是否有挂起的Windows 11/10安装并卸载注册表配置单元以修复它。使用任何媒体安装将Windows 引导至安全模式，或者如果您可以访问高级恢复(Advanced Recovery)模式。
Windows 更新安装状态
打开命令提示符(Command Prompt)，然后运行以下命令来验证Windows更新安装和日期。假设 C 是您的系统驱动器：
Dism /Image:C: /Get-packages
此命令的结果应该显示 安装挂起(Install pending) 和卸载挂起(Uninstall Pending)包。
- 运行命令 dism /Image:C:\ /Cleanup-Image /RevertPendingActions.
- 导航到 C:\Windows\WinSxS，然后检查 pending.xml 文件是否存在。如果是，请将其重命名为 pending.xml.old。
还原注册表更改
加载配置单元
- 在运行提示中键入(Type)regedit 以打开 注册表编辑器(Registry Editor)。
- 选择 HKEY_LOCAL_MACHINE，然后转到 File > Load Hive。
- 导航(Navigate)到 C:WindowsSystem32config，选择名为 COMPONENT的文件。打开它。
- 将名称另存为“ OfflineComponentHive ”。这是我们的新蜂巢。
- 展开 HKEY_LOCAL_MACHINEOfflineComponentHive，查看 PendingXmlIdentifier 键(PendingXmlIdentifier key)是否存在。
- 创建 OfflineComponentHivekey的备份，然后删除 PendingXmlIdentifier 键(delete the PendingXmlIdentifier key)。
卸载蜂巢：
选择OfflineComponentHive，然后选择 File> Unload Hive。选择 HKEY_LOCAL_MACHINE，转到文件 > 加载 Hive。导航(Navigate)到C :WindowsSystem32config，选择名为 SYSTEM的文件。打开它。出现提示时，为新配置单元输入名称 OfflineSystemHive 。
展开 HKEY_LOCAL_MACHINE\OfflineSystemHive，然后选择 Select 键(Select key)。检查 默认(Default) 值的数据。
- 如果HKEY_LOCAL_MACHINE\OfflineSystemHive\Select\Default中的数据为 1，则展开HKEY_LOCAL_MACHINE\OfflineHive\ControlSet001。
- 如果是 2，则展开 HKEY_LOCAL_MACHINE\OfflineHive\ControlSet002，以此类推。
展开 ControlSession 管理器。检查(Check)PendingFileRenameOperations 键(PendingFileRenameOperations key exists)是否 存在。如果是，请备份 SessionManagerkey(back up the SessionManagerkey)，然后删除 PendingFileRenameOperations key 。
重新启动(Reboot)计算机，您应该不会收到任何与 7B Inaccessible_Boot_Device相关的错误。
如需更多建议，请访问Technet。
如果您在 Windows 中使用 Reset 后收到INACCESSIBLE_BOOT_DEVICE 错误，请参阅此帖子。(See this post if you receive INACCESSIBLE_BOOT_DEVICE error after you used Reset in Windows.)
Blue Screen after Windows Updates in Windows 11/10
If you see a Stоp Error – 0x7B INACCESSIBLE_BOOT_DEVICE after applying Windows Updates on your Windows 11/10/8/7 system, know that it is the result of the boot state that the system gets. Microsoft has laid down some steps that will help you address this issue. Let us take a look at them.
0x7B INACCESSIBLE_BOOT_DEVICE Blue Screen after Windows Updates
This stop error stems from a flaw in the boot state due to device drivers and data corruption. Sometimes it could also be a result of hardware failure or a virus. Without exception, you will get this stop 0x0000007B error on the Blue Screen of Death or Stop Error.
Even when Windows recovers from the problem, you still get a prompt that says “Windows has recovered from an unexpected shutdown” and this problem can happen on any version of Windows. If this is your problem too, here are some solutions.
Just restart the device to see if the problem solves itself. Sometimes it does and never reappears again. Eles, read on.
1] Make changes to the Hard Drive Controller
If you recently make changes to your hard drive controller, this could be the reason, so reverse the situation by undoing these changes. You carry out any of the following procedures :
- Use System Restore.
- Reconfigure the new hard drive controller.
- Remove the new hard drive controller if reconfiguring doesn’t work and you don’t essentially require it.
- Run Startup Repair
- Go back to the version of the hard drive controller and device drivers you had before the driver update.
All these may or may not solve the problem depending on what caused it. If this solution doesn’t work, at least you’ll know your hard drive controller isn’t the problem.
2] Verify SCSI chain termination
If you are using SCSI hard drives, faulty termination is likely the cause of the error. So you need to cater to this problem in order to solve it. However, home computers usually use PATA and SATA and not SCSI, so this might not be your problem, to begin with.
3] Verify installation
Make sure the hard drive is installed correctly. If you haven’t installed any new drive recently, the problem could be something else.
4] Verify BIOS configuration
You need to make sure that your hard drive is correctly configured in the BIOS. Change settings as needed to ensure proper configuration.
5] Scan for virus
As mentioned earlier, the stop error can be a result of a virus. So you need to scan for virus and mainly check the boot sector and MBR for malware attacks. If this is the problem, follow the usual routine of antivirus software assistance and restart your device. Always keep your antivirus updated in order to prevent this problem from happening at all.
6] Update drivers
Outdated hard drive controller drivers can cause this error, so update the device drivers.
7] Change mode in BIOS
Some advanced SATA features can cause this error. Change the SATA (AHCI) mode to IDE mode (ATA or Compatibility Mode) to undo the error and avoid it in the future. In some older versions, the solution might be just the other way around. Clearing the CMOS can also help.
8] Run chkdsk
If the boot volume is corrupted, running chkdsk on the hard drive will solve the problem. You might have to run chkdsk from the Recovery console.
9] Hard drive errors
If a hard drive has gone bad, you will need to replace it. There is no way out from a damaged hard drive.
In order to avoid the error from occurring again, configure the patching infrastructure so that CU and delta updates are not simultaneously installed during a single reboot.
Advanced Troubleshooting: Error 7B Inaccessible_Boot_Device after Windows 10 Update installation
When you receive Error 7B Inaccessible_Boot_Device after Windows Update installation, then it’s completely different from the scenarios we have covered above. We will have to check if there is a pending Windows 11/10 installation and unload the registry hive to fix it. Boot Windows into Safe Mode using any media installation or if you can get access to Advanced Recovery mode.
Windows Update Installation Status
Open the Command Prompt, and run the following command to verify the Windows update installation and dates. Assuming C is your system drive:
Dism /Image:C: /Get-packages
The result of this command should reveal the Install pending and Uninstall Pending packages.
- Run the command dism /Image:C:\ /Cleanup-Image /RevertPendingActions.
- Navigate to C:\Windows\WinSxS, and then check whether the pending.xml file exists. If it does, rename it to pending.xml.old.
Revert Registry Changes
Load Hive
- Type regedit in the run prompt to open the Registry Editor.
- Select HKEY_LOCAL_MACHINE, and then go to File > Load Hive.
- Navigate to C:\Windows\System32\config, select the file that is named COMPONENT. Open it.
- Save the name as “OfflineComponentHive.” It is our new Hive.
- Expand HKEY_LOCAL_MACHINE\OfflineComponentHive, and check whether the PendingXmlIdentifier key exists.
- Create a backup of the OfflineComponentHivekey, and then delete the PendingXmlIdentifier key.
Unload Hive:
Select OfflineComponentHive, and then select File> Unload Hive. Select HKEY_LOCAL_MACHINE, go to File > Load Hive. Navigate to C:\Windows\System32\config, select the file that is named SYSTEM. Open it. When prompted, enter the name OfflineSystemHive for the new hive.
Expand HKEY_LOCAL_MACHINE\OfflineSystemHive, and then select the Select key. Check the data for the Default value.
- If the data in HKEY_LOCAL_MACHINE\OfflineSystemHive\Select\Default is 1, expand HKEY_LOCAL_MACHINE\OfflineHive\ControlSet001.
- If it is 2, expand HKEY_LOCAL_MACHINE\OfflineHive\ControlSet002, and so on.
Expand Control\Session Manager. Check whether the PendingFileRenameOperations key exists. If it does, back up the SessionManagerkey, and then delete the PendingFileRenameOperations key.
Reboot the computer, and you should not get any error related to 7B Inaccessible_Boot_Device.
For a few more suggestions, visit Technet.
See this post if you receive INACCESSIBLE_BOOT_DEVICE error after you used Reset in Windows.
