When the Windows loading logo is on the screen, it hangs for about 5 minutes then it shows the Blue screen of death. The error is “inaccessible boot device”. What should I do to repair this Server inaccessible boot device error?”
The “Inaccessible Boot Device” is a common error or stop code that appears as a reference when you meet Blue Screen problem on Windows Server and Windows Server 2008/2012/2019. This error usually means that the Windows Server operating system has lost access to the system partition during startup. When it occurs, the system will shut itself down and show a Blue Screen or Stop Error to protect itself from potential data corruption or loss.
Possible causes of inaccessible boot device error in Server 2016
Most Server 2016 reported that this issue happens after Server 2016 updates pushed by Microsoft. Besides, the following factors can also lead to “Inaccessible Boot Device” error:
- Corrupted files in the boot partition;
- System file corruption;
- Bad sector on your main hard drive;
- The storage controller mode or settings in the BIOS are changed;
- A faulty motherboard or storage controller or faulty hardware;
- Newly installed hardware conflicting with other devices;
- Newly installed software incorrectly written or conflicting with other programs;
- Corrupted Master Boot Record or missing Boot Configuration Data.
5 Solutions to “inaccessible boot device” error in Server 2016
Here are a few inaccessible boot device repair methods you can try to resolve this error in Server 2016, 2019 or other Server OS. See what applies in your case.
- 1. Roll back recent Server update
- 2. Boot your Server into Last Know Good Configuration
- 3. Check the boot partition for errors via Command Prompt
- 4. Check the system files integrity
- 5. Repair damaged MBR/BCD
Solution 1. Roll back recent Server update
If you encounter the issue: an inaccessible boot device in Server 2016 after the update, you can try to roll it back. Complete steps are:
Step 1. Press the power button to boot your Server. When the White circles start displaying, press the power button to power off the Server.
Step 2. Interrupt the Server boot 3 consecutive times to initiate “Preparing Automatic Repair”.
Tips: if you fail to enter recovery mode via this method, you might need to use the Server 2016 installation DVD or CD.
1. Insert the installation media into your server and change your boot order to boot from the media.
2. Power up your Server and wait for the “press any key to boot from CD or DVD” screen to appear, and press any key to continue.
3. At the Windows Boot Manager, select “Windows Setup [EMS Enabled]” and hit the “Enter” key on your keyboard.
4. At the Windows Server 2016 installation screen, click “Next”.
5. Then click on “Repair your computer” to access the “Choose an option” window, and select “Troubleshoot”.
Step 3. Then you will get to the Recovery Mode, click “Troubleshoot” from the given recovery mode options.
Step 4. Choose “Command Prompt” in the advanced options, and then click the “Admin” account to load Command Prompt.
Step 5. Input the password for the administrator account and click “Continue” to open the Command Prompt window.
Step 6. In the elevated Command Prompt window, input the following commands in turn and press “Enter” after each one.
● reg load HKLM\temp c:\windows\system32\config\software: to load Windows registry to HKLM/temp.
● reg delete “HKLM\temp\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending” /v ● Exclusive: to delete the SessionsPending registry key. When you are prompted to confirm, type “Y” and press Enter.
● reg unload HKLM\temp: unload the Windows registry
● MKDIR c:\temp\BadUpdates: to create a temp folder to hold the unnecessary Windows Server updates.
● dism /image:C:\ /get-packages: list all installed updates.
Step 7. Now we need to execute other commands to delete the “Install Pending” Packages which might be real culprit behind the “Server 2016 inaccessible boot device”.
Note: before running the command below, check out the list of the result for packages with “Install Pending” status and note their Package Identity.
● dism /image:c:\ /remove-package /packagename:Package-Identity /scratchdir:c:\temp\BadUpdates: replace the Package-Identity with the package name in your situation.
Now you can check if the problem is solved. If not, proceed to the next method.
Solution 2. Boot your Server into Safe Mode
Last Known Good Configuration, known as LKGC, is a recovery option Microsoft built-into all versions of Windows. With that, you can recover Windows PC or Server to the last good status if you are having trouble starting it normally after a failed update, driver installation or software setup. It can be accessed from “Advanced Boot Options”.
Step 1. Refer to the fix 1 above to enter “Advanced Options”, and click “Startup Settings”.
Step 2. When the “Startup Settings” screen appears, click “Restart”.
Step 3. Then you will see the “Advanced Boot Options” screen. Use the keyboard to navigate to “Safe Mode (Advanced)” and press the “Enter” key.
Solution 3. Check the boot partition for errors via Command Prompt
If the “Server 2016 inaccessible boot device” persists, try to check the boot partition for possible bad sectors using Command Prompt. To do this, you just need to launch Command Prompt in Recovery mode like you do in Fix 1. And execute the command “chkdsk c: /f”. This command will check the C drive and fix the found errors. You can also check How to format Pen Drive using CMD
Solution 4. Check the system files integrity
Besides checking the system partition for errors, you can also make use of SFC (System File Checker) tool to scan for and restore corruptions in Windows system files. It will scan all protected system files, and replace corrupted files with a cached copy.
For this task, you just need to run “sfc/scannow” command in the Command Prompt window.
Solution 5. Repair damaged MBR/BCD
MBR and BCD are quite important for booting Server successfully. So when your Server 2016 cannot boot as usual, you can try to repair them. There are two methods available.
Repair MBR/BCD through Command Prompt
Step 1. Access the “Command Prompt” window in the recovery mode.
Step 2. Type the below commands and press “Enter” after each one.
● bootrec/fixmbr
● bootrec/rebuildbcd
После очередного апдейта Windows Server 2016 виртуальная машина перестала загружаться.
При загрузке вываливался синий экран BSOD с ошибкой INACCESSIBLE_BOOT_DEVICE — 0x0000007B.
Мне удалось победить этот глюк.
-
В гипервизоре (в моем случае — proxmox) устанавливаем тип диска, который будет доступен без дополнительных драйверов — IDE или SATA.
-
Загружаем систему в режиме автоматического восстановления (она сама это сделает после BSOD), либо загружаемся с инсталляционного диска и в окошке с кнопкой Install now слева снизу жмем Repair your computer.
-
Запускаем командную строку (Troubleshoot → Command Prompt).
-
В командной строке запускаем diskpart с помощью нижеприведенных команд определяем на месте ли разделы и какая сейчас буква у диска с Windows и у загрузочного раздела. Обычно достаточно list volume.
diskpart list volume select disk 0 detail disk list partition select partition 1 detail partition select partition 2 detail partition select disk 1 detail disk list partition exit
или
bcdedit |find "osdevice" osdevice partition=D:
-
Смотрим что файлы на месте и на всякий случай проверяем диск:
dir d:\ chkdsk /r d:
-
При необходимости — перезагружаемся опять в режим восстановления.
-
Проверяем целостность системных файлов:
sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
-
Чиним загрузочные компоненты:
bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
-
На этом этапе утилита может сказать, что Total identified Windows installations: 0. Тогда делаем так (предполагая, что буква C у нас назначена загрузочному разделу):
Готово. Перезагружаемся. Убеждаемся, что все в порядке, меняем в гипервизоре тип диска на необходимый и радуемся.
Encountering the Inaccessible Boot Device error, coded as 0x0000007b, is a common yet critical issue that manifests as a blue screen of death, often following a Windows update or system reset. This guide delineates five effective methods to rectify the Inaccessible Boot Device on Windows Server 2019.
Table of Contents
- Understand the Inaccessible Boot Device Error
- Root Causes of the Inaccessible Boot Device Error
- Solutions for the Inaccessible Boot Device Error
- Solution 1: Ensure Boot Disk Connectivity and Accessibility
- Solution 2: Revert Recent Updates
- Solution 3: Remove Recent Drivers and Software in Safe Mode
- Solution 4: Repair the Master Boot Record with BootRec Commands
- Solution 5: Activate Last Known Good Configuration for Recovery
- Solution 6 Conduct System and Disk Scans with SFC and Chkdsk
Understand the Inaccessible Boot Device Error
The Inaccessible Boot Device error is prevalent stop code that indicates Blue Screen problem on Windows Server platforms including versions 2019, 2022, 2016, and 2012. This error shows when the operating system unable to access system partition during startup, prompting protective shutdown to prevent potential data corruption.
Root Causes of the Inaccessible Boot Device Error
The error may stem from various sources, such as:
- Corrupted boot partition files
- File system corruption
- Bad sectors on the OS hard drive
- Changes in BIOS storage controller settings
- Faulty motherboard or storage hardware
- Hardware conflicts due to new installations
- Software conflicts from recent installations
- Damaged Master Boot Record or missing Boot Configuration Data
Solutions for the Inaccessible Boot Device Error
The appropriate fix hinges on the underlying cause. The following sections will explore the main causes, solutions, and a backup strategy for data protection and disaster recovery. The goal is to provide a clear path to resolving the error and safeguarding server integrity.
Solution 1: Ensure Boot Disk Connectivity and Accessibility
Verifying the connection and accessibility of the boot disk is a fundamental step when faced with the Inaccessible Boot Device error on Windows Server 2019. Here’s how to confirm that your server’s boot disk is properly detected:
- Power on the server and interrupt the boot sequence when the loading animation appears by shutting it down.
- Repeat the interruption twice more, and on the third attempt, the server will enter Recovery mode.
- Select ‘See advanced repair options’ and then ‘Troubleshoot’.
- Choose ‘Command Prompt’ and log in using the Admin account.
- Type the following command and press Enter:
diskpart - Enter the following command to display all connected disks and verify the system disk’s presence:
list disk - Type the following command to to list all volumes and ensure the boot device is recognized:
list vol
If the system disk does not appear, it’s advisable to seek support from the Original Equipment Manufacturer (OEM) or the provider of the virtualization platform for further technical assistance. This step is crucial to rule out hardware connectivity issues before delving into more intricate troubleshooting procedures.
Solution 2: Revert Recent Updates
To mitigate the Inaccessible Boot Device error, a rollback of recent updates may be necessary. Here’s a streamlined process:
- Initiate the server’s boot sequence and interrupt it once the loading indicators appear by powering off the server.
- Repeat the boot interruption process twice more. On the third attempt, the server will enter Recovery mode.
- In Recovery mode, navigate to ‘See advanced repair options’ followed by ‘Troubleshoot’.
- Select ‘Command Prompt’ and authenticate with the Admin account credentials.
- Within Command Prompt, execute the command the following command to load the registry hive:
reg load HKLM\temp c:\windows\system32\config\software - Proceed to remove the SessionsPending registry key by executing:
reg delete "HKLM\temp\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending" /v Exclusive - Confirm the deletion when prompted by typing ‘Y’ and pressing Enter.
- Unload the modified registry hive using:
reg unload HKLM\tem - Create a directory to isolate problematic updates with:
MKDIR c:\temp\BadUpdates - List all installed updates using the following command and identify those with an ‘Install Pending’ status:
dism /image:C:\ /get-packages - For each update marked ‘Install Pending’, execute the following command, substituting ‘Package-Identity’ with the actual name of the update.
dism /image:c:\ /remove-package /packagename:Package-Identity /scratchdir:c:\temp\BadUpdates
This procedure aims to eliminate updates that may be causing boot disruptions, thereby restoring server functionality.
Solution 3: Remove Recent Drivers and Software in Safe Mode
To rectify the Inaccessible Boot Device error, it’s essential to consider uninstalling newly installed drivers or software that might be causing the issue. Here’s how to proceed:
- Power on the server and interrupt the boot sequence when the loading indicators appear by shutting it down.
- Repeat the boot interruption twice more, and on the third attempt, the server will enter Recovery mode.
- Select ‘See advanced repair options’ and then ‘Troubleshoot’.
- Select ‘Startup Settings’ and opt for ‘Restart’.
- After the server restarts, it will present the Advanced boot options. Select Safe Mode using the arrow keys and confirm by pressing Enter.
- Once the server boots in Safe Mode, sign in as usual and proceed to uninstall any device drivers or software that were recently added.
The presence of “Safe mode” on the screen corners confirms that the server is in the correct mode for this operation. This step is crucial for eliminating any recent changes that may interfere with the server’s boot process.
Solution 4: Repair the Master Boot Record with BootRec Commands
To correct the Inaccessible Boot Device error, the BootRec command can be utilized to repair the Master Boot Record (MBR). Here is the procedure:
- Power on the server and interrupt the boot sequence when the loading animation appears by shutting it down.
- Repeat the interruption twice more, and on the third attempt, the server will enter Recovery mode.
- Select ‘See advanced repair options’ and then ‘Troubleshoot’.
- Choose ‘Command Prompt’ and log in using the Admin account.
- Once in Command Prompt, input the following command and press ENTER:
BOOTREC /FIXMBR - If the operation is successful, restart the server, which should now boot normally.
- Execute the following command to write a new boot sector if the current one is damaged:
Bootrec /fixboot- If an error such as “Boot Manager is Missing” appears, execute the following command to rebuild the MBR:
BOOTREC /RebuildBcd
This process aims to resolve issues with the boot record, which is a common cause of boot-related errors on Windows servers.
Solution 5: Activate Last Known Good Configuration for Recovery
The Last Known Good Configuration (LKGC) is a recovery feature in Windows system to revert to stable state before recent changes were made.
- Power on the server and interrupt the boot sequence when the loading indicators appear by shutting it down.
- Repeat the boot interruption twice more, and on the third attempt, the server will enter Recovery mode.
- Select ‘See advanced repair options’ and then ‘Troubleshoot’.
- Select ‘Startup Settings’ and opt for ‘Restart’.
- After the server restarts, it will present the Advanced boot options.
- Use the arrow keys to select ‘Last Known Good Configuration (Advanced)’ and press Enter.
This action can resolve issues caused by unsuccessful updates or new software and driver installations, restoring the server to its last operational configuration.
Solution 6 Conduct System and Disk Scans with SFC and Chkdsk
If the server continues to display the Inaccessible Boot Device error, it’s advisable to inspect the boot partition for errors. Utilize the Command Prompt to perform system and disk scans:
- Power on the server and interrupt the boot sequence when the loading animation appears by shutting it down.
- Repeat the interruption twice more, and on the third attempt, the server will enter Recovery mode.
- Select ‘See advanced repair options’ and then ‘Troubleshoot’.
- Choose ‘Command Prompt’ and log in using the Admin account.
- Once in Command Prompt, input the following command and press ENTER to initiate a scan and repair of the drive:
chkdsk /f /r X:Note: replace x with the actual drive letter. - Next, deploy the System File Checker (SFC) tool to identify and fix corrupted Windows system files by entering the following command:
sfc /scannow
These steps will help diagnose and potentially resolve issues with the file system and hard drive that could be causing the boot error.
How can the “inaccessible boot device” be fixed in VMWare Windows Server 2016? Read the article to learn more. At Bobcares, with our Windows Hosting Support, we can handle your issues.
Fixing the “Inaccessible Boot Device” in VMWare Windows Server 2016
A typical error or stop code that appears as a guide when we encounter a Blue Screen issue on Windows Server and Windows Server 2008/2012/2019 is “Inaccessible Boot Device.” This issue typically indicates that during startup, the Windows Server operating system lost access to the system partition. As a safeguard against possible data loss or corruption, the system will shut down and display a Blue Screen or Stop Error when it happens.
Some of the possible causes for the error are as follows:
1. Files in the boot partition that are corrupt.
2. Damage to system files.
3. A bad sector on the primary hard disk.
4. The BIOS’s storage controller mode or settings are modified.
5. A malfunctioning storage controller, motherboard, or other piece of hardware.
6. Conflict between recently installed hardware and other devices.
7. Recently installed software that is miswritten or incompatible with other apps.
8. Inaccurate Master Boot Record or no Boot Configuration Information.
Troubleshooting Tips
We can use any of the following steps in order to fix the error, “Inaccessible Boot Device.”
1. Revert the most recent server upgrade.
2. Launch the Last Known Good Configuration on the server.
3. Use Command Prompt to check the boot partition for problems.
4. Verify the integrity of the system files.
5. Fix broken MBRs and BCDs.
[Need to know more? Get in touch with us if you have any further inquiries.]
Conclusion
The article provides a brief explanation of the “inaccessible boot device” issue on VMWare, Windows Server 2016.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
Inaccessible Boot Device Server 2016 Fix Itechguides To run bootrecexe, you need to boot into Windows Recovery and then use Command Prompt to execute the bootrec commands The easiest method to fix your because the server or network failed
Inaccessible Boot Device Server 2016 Fix Itechguides
Inaccessible Boot Device Server 2016 Fix Itechguides
Inaccessible Boot Device Server 2016 Fix Itechguides