Haddii aad aragto cilad Joojin -  0x7B INACCESSIBLE_BOOT_DEVICE ka dib markaad ku dhejiso Windows Updates kaaga Windows 11/10/8/7 nidaamka, ogow inay tahay natiijada gobolka boot in nidaamku helo. Microsoft waxay dejisay tillaabooyin kaa caawin doona inaad wax ka qabato arrintan. Aynu eegno iyaga.

0x7B INACCESSIBLE_BOOT_DEVICE Shaashadda buluuga ah^{(INACCESSIBLE_BOOT_DEVICE Blue Screen)} kadib Cusbooneysiinta Daaqadaha^{(Windows Updates)}

Ciladan joogsigu waxay ka timid cilad ka jirta xaalada bootka taasoo ay ugu wacan tahay wadayaasha aaladaha iyo musuqmaasuqa xogta. Mararka qaarkood waxay sidoo kale noqon kartaa natiijo ka dhalata cillad hardware ama fayras. Iyadoo aan laga reebin, waxaad heli doontaa qaladka joogsiga 0x0000007B ee shaashadda buluuga ah ee dhimashada ama Joojinta Khaladka^{(Blue Screen of Death or Stop Error)} .

Xitaa marka uu Windows ka soo kabsado dhibaatada, waxaad weli helaysaa degdeg ah oo leh " Daaqadaha ayaa ka soo kabsaday xiritaan lama filaan ah^{(Windows has recovered from an unexpected shutdown)} " oo dhibaatadani waxay ku dhici kartaa nooc kasta oo Windows ah . Haddii tani ay tahay dhibaatadaada sidoo kale, halkan waxaa ah qaar xalal ah.

Kaliya dib u billow qalabka si aad u aragto haddii dhibaatadu is xalliso. Mararka qaarkood way dhacdaa oo dib uma soo noqoto. Eles, sii akhri.

1] Isbeddel ku samee ^(Make)Kontoroolka Hard Drive -ka^{(Hard Drive Controller)}

Haddii aad dhawaan isbeddel ku samayso kontaroolahaaga darawalka adag, tani waxay noqon kartaa sababta, markaa dib u celi xaalada adoo dib u dhigaya isbeddeladan. Waxaad fulisaa mid ka mid ah hababka soo socda:

1. Isticmaal Nidaamka Soo Celinta .
2. Dib u habayn kontaroolaha cusub ee wadida adag
3. Ka saar kontaroolaha cusub ee wadida adag haddi dib u habayntu shaqayn waydo oo aanad u baahnayn.
4. Orod dayactirka bilowga
5. Ku laabo nooca kantaroolaha wadida adag iyo wadayaasha aaladaha aad lahayd kahor cusboonaysiinta darawalka.

Waxaas oo dhami waxay xallin karaan ama ma xallin karaan dhibaatada iyadoo ku xiran waxa sababay. Haddii xalkani shaqayn waayo, ugu yaraan waxaad ogaan doontaa kontaroolahaaga wadida adag in aanu dhibku ahayn.

2] Xaqiiji joojinta silsiladda SCSI

Haddii aad isticmaalayso SCSI hard drives, cilad joojinta waxay u badan tahay inay tahay sababta qaladka. Markaa waxaad u baahan tahay inaad wax ka qabato dhibaatadan si aad u xalliso. Si kastaba ha ahaatee, kombuyuutarrada gurigu waxay inta badan isticmaalaan PATA iyo SATA ee maaha SCSI , markaa tani ma noqon karto dhibkaaga, marka hore.

3] Xaqiiji rakibidda

Hubi^(Make) in dariiqa adag uu si sax ah u rakiban yahay. Haddii aadan dhawaan rakibin darawal cusub, dhibaatadu waxay noqon kartaa wax kale.

4] Xaqiiji qaabeynta BIOS

Waxaad u baahan tahay inaad hubiso in dariiqaaga adag si sax ah loogu habeeyey BIOS -ka . Beddel^(Change) habka loo baahan yahay si loo xaqiijiyo qaabaynta saxda ah.

5] Ka baadh fayraska

Sidii hore loo sheegay, cilada joogsiga waxay noqon kartaa natiijo ka timid fayras. Markaa waxaad u baahan tahay inaad iska baarto fayraska oo aad inta badan ka hubiso qaybta boot-ka iyo MBR weerarada malware. Haddii ay tani tahay dhibaatadu, raac habka caadiga ah ee kaalmada software ka-hortagga oo dib u billow qalabkaaga. Had^(Always) iyo jeer dib u cusboonaysii anti-virus-kaaga si aad uga hortagto inay dhibaatadani dhacdo gabi ahaanba.

6] Cusbooneysii darawalada

Dareewalada kontaroolada adag ee wakhtigoodu dhamaaday waxay keeni karaan ciladan, markaa cusboonaysii darawalada qalabka .

7] Beddel habka BIOS

Qaar ka mid ah sifooyinka SATA ee horumarsan ayaa sababi kara khaladkan. U beddel qaabka SATA ( AHCI ) una beddel qaabka IDE ( ATA ama Habka Laqabsiga^{(Compatibility Mode)} ) si aad u tirtirto khaladka oo aad uga fogaato mustaqbalka. Qaar ka mid ah noocyada hore, xalku wuxuu noqon karaa si kale. Nadiifinta CMOS waxay kaloo ku caawin kartaa.

8] Orod chkdsk

Haddii mugga bootku uu xumaado, ku socodsiinta chkdsk ee dariiqa adag ayaa xallin doona dhibaatada. Waxa laga yaabaa in aad chkdsk ka maamusho console Recovery.

9] Khaladaadka Hard Drive-ka

Haddii darawal adagi xumaaday, waxaad u baahan doontaa inaad bedesho. Ma jirto waddo looga baxo darawalka adag ee xumaaday.

Si looga fogaado khaladku inuu mar kale dhaco, habbee kaabayaasha balastar-ka si aan CU iyo cusboonaysiinta delta isku mar loo rakibin inta lagu jiro hal dib-u-bilow.

Cilad horumarsan: Cilad 7B Aanaccessible_Boot_Device^{(Inaccessible_Boot_Device)} ka dib Windows 10 Cusbooneysii^(Update) rakibaadda

Markaad hesho Cilad 7B Inaccessible_Boot_Device ka dib rakibidda Cusbooneysiinta Windows^{(Windows Update)} , markaas gabi ahaanba way ka duwan tahay xaaladaha aan kor ku soo sheegnay. Waa inaan hubinaa haddii uu jiro rakibaad Windows 11/10 oo aan soo dejinno rugta diiwaanka si loo hagaajiyo. Ku dheji Windows qaab badbaado leh adigoo isticmaalaya qalab kasta oo warbaahin ah ama haddii aad heli karto habka Soo kabashada Sare^{(Advanced Recovery)} .

Xaaladda Rakibaadda Cusboonaysiinta Windows

Fur Command Prompt , oo socodsii amarka soo socda si aad u xaqiijiso rakibaadda iyo taariikhaha Windows cusboonaysiinta. U malayn in C uu yahay nidaamkaaga wadista:

Dism /Image:C: /Get-packages

Natiijada amarkan waa in ay muujiso  Ku rakibka la sugayo^{(Install pending)}  iyo Uninstall^{(Uninstall Pending)} xidhmooyinka la sugayo.

1. Ku socodsii amarka dism /Image:C:\ /Cleanup-Image /RevertPendingActions. 
2. U gudub  C:\Windows\WinSxS , ka dibna hubi in  faylka la sugayo.xml^{(pending.xml)}  uu jiro. Haddii ay dhacdo, ku beddel magaca la  sugayo.xml.old^{(pending.xml.old)} .

Dib u celi Isbeddelada Diiwaanka

Soo qaado rugta

1. Ku qor^(Type) regedit gudaha orodka degdega ah si aad u furto  Tifaftiraha Diiwaanka^{(Registry Editor)} .
2. Dooro  HKEY_LOCAL_MACHINE , ka dibna u tag File >  Load Hive .
3. U gudub C: WindowsSystem32config^(Navigate) , dooro faylka lagu magacaabo  COMPONENT . Furo.
4. U keydi magaca sida " OfflineComponentHive ." Waa rugteena cusub.
5. Balaadhi HKEY_LOCAL_MACHINEOfflineComponentHive, oo hubi in  furaha la sugayoXmlIdentifier^{(PendingXmlIdentifier key)} uu jiro.
6. Samee kaydinta  OfflineComponentHivekey , ka dibna tirtir furaha la sugayoXmlIdentifier^{(delete the PendingXmlIdentifier key)} .

Soo deji rugta:

Dooro OfflineComponentHive , ka dibna dooro File> Soodeji rugta. Dooro HKEY_LOCAL_MACHINE, u gudub Faylka> Xero-qaadista. U gudub C : WindowsSystem32config^(Navigate) , dooro faylka lagu magacaabo  SYSTEM . Furo. Marka laguu sheego, geli magaca  OfflineSystemHive  rugta cusub

Balaadhi  HKEY_LOCAL_MACHINE\OfflineSystemHive , ka dibna dooro  furaha Xulo^{(Select key)} . Hubi xogta  qiimaha asalka^(Default)  ah.

• Haddii xogta ku jirta HKEY_LOCAL_MACHINE\OfflineSystemHive\Select\Default ay tahay 1, balaadhi HKEY_LOCAL_MACHINE\OfflineHive\ControlSet001 .
• Haddii ay tahay 2, balaadhi  HKEY_LOCAL_MACHINE\OfflineHive\ControlSet002 , iyo wixii la mid ah.

Kordhi Maamulaha Kulanka. Hubi^(Check) in uu  jiro furaha RenameOperations^{(PendingFileRenameOperations key exists)} ee sugaya iyo in kale . Haddii ay sameyso, ku celi SessionManagerkey^{(back up the SessionManagerkey)} , ka dibna tirtir furaha la  sugayoFileRenameOperations  ^{( PendingFileRenameOperations )}.

Dib u kici kombayutarka^(Reboot) , oo waa inaadan helin wax khalad ah oo la xidhiidha 7B Aanaccessible_Boot_Device^{(Inaccessible_Boot_Device)} .

Waxoogaa talo soo jeedin ah, booqo Technet .

Fiiri qoraalkan haddii aad hesho cilad INACCESSIBLE_BOOT_DEVICE ka dib markii aad dib u dejin ku isticmaashay Windows.^{(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 Stop 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 :

1. Use System Restore.
2. Reconfigure the new hard drive controller.
3. Remove the new hard drive controller if reconfiguring doesn’t work and you don’t essentially require it.
4. Run Startup Repair
5. 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.

1. Run the command dism /Image:C:\ /Cleanup-Image /RevertPendingActions. 
2. 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

1. Type regedit in the run prompt to open the Registry Editor.
2. Select HKEY_LOCAL_MACHINE, and then go to File > Load Hive.
3. Navigate to C:\Windows\System32\config, select the file that is named COMPONENT. Open it.
4. Save the name as “OfflineComponentHive.” It is our new Hive.
5. Expand HKEY_LOCAL_MACHINE\OfflineComponentHive, and check whether the PendingXmlIdentifier key exists.
6. 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.

Related posts

• Hagaaji khaladka Shaashada Buluugga ah ee Klif.sys Windows 11/10

• Sida loo hagaajiyo muraayadda Orange ee dhimashada gudaha Windows 11/10

• SESSION_HAS_VALID_POOL_ON_EXIT Shaashada buluuga ah ee Windows 11/10

• Hagaaji ADEEGGA NIDAAMKA SHASHADA buluuga ah ee ka reeban Windows 11/10

• Hubinta Amniga Kernel Cilad ku fashilantay gudaha Windows 11/10

• Hagaaji TIMER_OR_DPC_INVALID Shaashada buluuga ah ee Windows 11/10

• Cusboonaysiinta Windows waxay ku xayiran tahay hubinta wixii ku soo kordha Windows 11/10

• Ma geli karo Windows 11/10 Cusbooneysii ka dib

• Hagaaji C000021A Khaladka Nidaamka Fatal ee Windows 11/10

• Ururkaagu waxa uu damiyay cusboonaysiinta tooska ah Windows 11/10

• Hagaaji WDF_VIOLATION Cilada Shaashada Buluuga ee Windows 11/10

• Dib u deji wakiilka Cusboonaysiinta Windows si uu ugu noqdo Windows 11/10 haddii uu xumaaday

• Aaway faylka log ee BSOD gudaha Windows 11/10?

• Liisaska Dhamaystiran ee Koodadka Cilada Cusbooneysiinta Windows ee ku jira Windows 11/10

• Ma ku rakibi kartaa Cusboonaysiinta Windows qaab Badbaado leh gudaha Windows 11/10?

• Sida loo isticmaalo BlueScreenView on Windows 11/10

• Cusboonaysiinta Windows ayaa ku xayiran soo dejinta cusbooneysiinta gudaha Windows 11/10

• Hagaaji aksdf.sys Screen Blue of Death qaladka gudaha Windows 11/10

• Hagaaji Cillada galka Xogta KerNEL (Msis.SYS) gudaha Windows 11/10

• Waanu ku xidhi waynay adeega cusboonaysiinta gudaha Windows 11/10