Blue Screen after Windows Updates in Windows 10

If y'all encounter a Stop Error – 0x7B INACCESSIBLE_BOOT_DEVICE afterward applying Windows Updates on your Windows 10/8/7 system, know that it is the resultant of the kicking nation that the organisation gets. Microsoft has set downwardly about steps that volition assist y'all address this issue. Let us have got a facial expression at them.

0x7B INACCESSIBLE_BOOT_DEVICE Blue Screen afterward Windows Updates

When y'all larn the 0x7B INACCESSIBLE_BOOT_DEVICE error, y'all mightiness live on at a loss. Maybe y'all can’t fifty-fifty empathise the problem, but don’t worry, that is exclusively normal. What’s more, this patently complicated occupation has about working solutions.

This halt fault stems from a flaw inward the kicking nation due to device drivers in addition to information corruption. Sometimes it could also live on a resultant of hardware failure or a virus. Without exception, y'all volition larn this halt 0x0000007B fault on the Blue Screen of Death or Stop Error.

Even when Windows recovers from the problem, y'all even therefore larn a prompt that says “Windows has recovered from an unexpected shutdown” in addition to this occupation tin sack hand on whatever version of Windows. If this is your occupation too, hither are about solutions.

Just restart the device to encounter if the occupation solves itself. Sometimes it does in addition to never reappears again. Eles, read on.

1] Make changes to the Hard Drive Controller

If y'all late brand changes to your difficult drive controller, this could live on the reason, therefore opposite the province of affairs past times undoing these changes. You acquit out whatever of the next procedures :

1. Use System Restore.
2. Reconfigure the novel difficult drive controller.
3. Remove the novel difficult drive controller if reconfiguring doesn’t operate in addition to y'all don’t essentially require it.
4. Start upwards amongst the Last Known Good Configuration inward monastic tell to undo registry in addition to avoid the touching on of driver changes.
5. Go dorsum to the version of difficult drive controller in addition to device drivers y'all had before the driver update.

All these may or may non solve the occupation depending on what caused it. If this solution doesn’t work, at to the lowest degree you’ll know your difficult drive controller isn’t the problem.

2] Verify SCSI chain termination

If y'all are using SCSI difficult drives, faulty termination is probable the drive of the error. So y'all postulate to cater to this occupation inward monastic tell to solve it. However, habitation computers unremarkably role PATA in addition to SATA in addition to non SCSI, therefore this mightiness non live on your problem, to get with.

3] Verify installation

Make certain the difficult drive is installed correctly. If y'all haven’t installed whatever novel drive recently, the occupation could live on something else.

4] Verify BIOS configuration

You postulate to brand certain that your difficult drive is correctly configured inward the BIOS. Change settings every bit needed to ensure proper configuration.

5] Scan for virus

As mentioned earlier, the halt fault tin sack live on a resultant of a virus. So y'all postulate to scan for virus in addition to mainly cheque the kicking sector in addition to MBR for malware attacks. If this is the problem, follow the commons routine of antivirus software assistance in addition to restart your device. Always continue your antivirus updated inward monastic tell to preclude this occupation from happening at all.

6] Update drivers

Outdated difficult drive controller drivers tin sack drive this error, therefore update the device drivers.

7] Change agency inward BIOS

Some advanced SATA features tin sack drive this error. Change the SATA (AHCI) agency to IDE agency (ATA or Compatibility Mode) to undo the fault in addition to avoid it inward the future. In about older versions, the solution mightiness live on simply the other agency around. Clearing the CMOS tin sack also help.

8] Run chkdsk

If the kicking book is corrupted, running chkdsk on the difficult drive volition solve the problem. You mightiness have got to run chkdsk from the Recovery console.

9] Hard drive errors

If a difficult drive has gone bad, y'all volition postulate to supervene upon it. There is no agency out from a damaged difficult drive.

In monastic tell to avoid the fault from occurring again, configure the patching infrastructure therefore that CU in addition to delta updates are non simultaneously installed during a unmarried reboot.

Advanced Troubleshooting: Error 7B Inaccessible_Boot_Device afterward Windows 10 Update installation

When y'all receive Error 7B Inaccessible_Boot_Device afterward Windows 10 Update installation, in addition to then its completely dissimilar from the scenarios nosotros have got covered above. We volition have got to cheque if in that place a pending Windows 10 installation in addition to unload the registry hive to arrive at it. Boot Windows 10 into Safe Mode using whatever media installation or if y'all tin sack larn access to Advanced Recovery mode.

Windows Update Installation Status

Open the Command Prompt, in addition to run the next command to verify the Windows update installation in addition to dates. Assuming C is your organisation drive:

Dism /Image:C: /Get-packages

The resultant of this command should expose the Install pending and Uninstall Pending packages.

1. Run the command dism /Image:C:\ /Cleanup-Image /RevertPendingActions. 
2. Navigate to C:\Windows\WinSxS, in addition to and then cheque whether the pending.xml file exists. If it does, rename it to pending.xml.old.

Revert Registry Changes

Load Hive

1. Type regedit inward the run prompt to opened upwards the Registry Editor.
2. Select HKEY_LOCAL_MACHINE, in addition to and then become to File > Load Hive.
3. Navigate to C:\Windows\System32\config, pick out the file that is named COMPONENT. Open it.
4. Save the scream every bit “OfflineComponentHive.” It is our novel Hive.
5. Expand HKEY_LOCAL_MACHINE\OfflineComponentHive, in addition to cheque whether the PendingXmlIdentifier key exists.
6. Create a backup of the OfflineComponentHivekey, in addition to and then delete the PendingXmlIdentifier key.

Unload Hive:

Select OfflineComponentHive, in addition to and then select File> Unload Hive. Select HKEY_LOCAL_MACHINE, become to File > Load Hive. Navigate to C:\Windows\System32\config, pick out the file that is named SYSTEM. Open it. When prompted, larn inward the name OfflineSystemHive for the novel hive.

Expand HKEY_LOCAL_MACHINE\OfflineSystemHive, in addition to and then pick out the Select key. Check the information for the Default value.

• If the information 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, in addition to therefore on.

Expand Control\Session Manager. Check whether the PendingFileRenameOperations key exists. If it does, back upwards the SessionManagerkey, in addition to and then delete the PendingFileRenameOperations key.

Reboot the computer, in addition to y'all should non larn whatever fault related to 7B Inaccessible_Boot_Device.

For a few to a greater extent than suggestions, see Technet.

See this post service if y'all have INACCESSIBLE_BOOT_DEVICE fault afterward y'all used Reset inward Windows 10.

Source: https://www.thewindowsclub.com/

Share This :