Blue Screen after Windows Updates in Windows 11/10

If you see a Stop Error –0x7B INACCESSIBLE_BOOT_DEVICE after applying Windows Updates on your Windows 11/10/8/7 system, know that information technology is the leave of the rush state that the organisation gets. Microsoft has laid down some steps that will help you address this way out. Let us take a look away at them.

0x7B INACCESSIBLE_BOOT_DEVICE Blue Projection screen after Windows Updates

When you get the 0x7B INACCESSIBLE_BOOT_DEVICE error, you mightiness equal at a red. Perhaps you can't even understand the problem, but father't worry, that is only average. What's more, this apparently complicated job has many working solutions.

This turn back error stems from a blemish in the charge state attributable device drivers and data corruption. Sometimes it could also equal a result of hardware failure surgery 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 found from an unexpected closing" and this job can materialize on any version of Windows. If this is your problem as well, here are some solutions.

Just restart the device to see if the problem solves itself. Sometimes it does and never reappears once more. Eles, read on.

1] Spend a penny changes to the Hard Drive Comptroller

If you recently piddle changes to your hard drive controller, this could be the cause, so reverse the situation away undoing these changes. You carry out any of the succeeding procedures :

Use System Mend.
Reconfigure the new hard ram controller.
Remove the unweathered disk drive comptroller if reconfiguring doesn't work and you father't essentially require it.
Run Startup Repair
Extend to back to the edition of the problematic drive controller and twist drivers you had before the device driver update.

Altogether these Crataegus laevigata operating theater may not wor the job depending on what caused it. If this resolution doesn't work, at the least you'll know your hard campaign controller isn't the problem.

2] Verify SCSI chain termination

If you are using SCSI demanding drives, imperfect termination is likely the cause of the error. And so you need to cater to this problem in guild to solve it. However, abode computers usually use PATA and SATA and not SCSI, so this might not be your job, in the first place.

3] Verify initiation

Take in sure the hard drive is installed correctly. If you haven't installed any untested ram down recently, the problem could be something other.

4] Aver BIOS configuration

You need to make sure that your tall drive is correctly configured in the BIOS. Change settings pro re nata to ensure proper configuration.

5] Rake for virus

As mentioned earlier, the stop error can be a result of a virus. So you involve to scan for virus and in the main check iron boot sector and MBR for malware attacks. If this is the problem, follow the wonted routine of antivirus software aid and re-start 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 computer error. Change the SATA (AHCI) mode to IDE mode (ATA or Compatibility Mode) to undo the error and avoid it in the rising. In some older versions, the solution might be just the other way just about. Clearing the CMOS tooshie also help.

8] Endure chkdsk

If the boot volume is corrupted, working chkdsk on the hard force will solve the problem. You might have to hightail it chkdsk from the Recovery soothe.

9] Disk drive errors

If a disc drive has bypast malfunctioning, you will need to replace it. There is no way out from a damaged disc drive.

In order to avoid the error from occurring again, configure the patching infrastructure so that Atomic number 29 and delta updates are non simultaneously installed during a single bring up.

Advanced Troubleshooting: Wrongdoing 7B Inaccessible_Boot_Device after Windows 10 Update facility

When you receive Error 7B Inaccessible_Boot_Device afterward Windows Update induction, then it's altogether different from the scenarios we sustain covered above. We leave have to checkout if there is a unfinished Windows 11/10 installation and unload the registry beehive to fix IT. Boot out 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 Incit, and run the following command to verify the Windows update induction and dates. Assuming C is your arrangement drive:

Dism /Image:C: /Get-packages

The result of this instruction should reveal theInstall pending and Uninstall Pending packages.

Function the command dism /Image:C:\ /Cleanup-Image /RevertPendingActions.
Sail toC:\Windows\WinSxS, and then gibe whether theunfinished.xml file exists. If it does, rename it topending.xml.old.

Revert Registry Changes

Load Hive

Character regedit in the run prompt to nonunion the Registry Editor in chief.
SelectHKEY_LOCAL_MACHINE, then attend File >Encumbrance Hive.
Navigate to C:\Windows\System32\config, choose the file away that is named COMPONENT. Undisguised it.
Salvage the name equally "OfflineComponentHive." It is our new Hive.
Expand HKEY_LOCAL_MACHINE\OfflineComponentHive, and check whether thePendingXmlIdentifier distinguish exists.
Create a backup of the OfflineComponentHivekey, and then delete the PendingXmlIdentifier key.

Unload Beehive:

Take OfflineComponentHive, and so select File> Unload Hive. Pick out HKEY_LOCAL_MACHINE, attend File > Load Hive. Navigate to C:\Windows\System32\config, select the file that is named SYSTEM. Open it. When prompted, enrol the name OfflineSystemHive for the new beehive.

Expand HKEY_LOCAL_MACHINE\OfflineSystemHive, and then select theBlue-ribbon key out. Check the data for the Nonremittal value.

If the data in HKEY_LOCAL_MACHINE\OfflineSystemHive\Select\Default is 1, flesh out HKEY_LOCAL_MACHINE\OfflineHive\ControlSet001.
If it is 2, expatiate HKEY_LOCAL_MACHINE\OfflineHive\ControlSet002, etcetera.

Expand Control\Sitting Managing director. Check whether thePendingFileRenameOperations key exists. If it does, support up the SessionManagerkey, and then delete the PendingFileRenameOperationskey.

Reboot the computer, and you should not get any error related to 7B Inaccessible_Boot_Device.

For few more suggestions, visit Technet.

See this post if you receive INACCESSIBLE_BOOT_DEVICE misplay subsequently you used Readjust in Windows.