Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Receiving the “inaccessible boot device” error in Windows Server 2016 (or any Windows Server) can cause serious concern. Here are the steps to fix this error.

Cause of this Windows Server Error

When you install a new Software, or driver on your Windows server, it may corrupt some Windows OS files and this may lead to the “inaccessible boot device” error.

Another known action that could cause this error is Windows Update. Finally, bad sectors on the Operating System hard drive can also cause this error.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Essentially, anything that affects essential boot files of your Windows Server can trigger this disturbing error.

Here are the possible fixes for this error. The fix that works for you depends on the reason for the error.

Fixing this error message is a two-step process. First you need to boot your Windows Server to the Recovery Mode. After that, apply one of the methods discussed

Step 1: Boot Windows Server 2016 to Recovery Mode

Follow the steps below:

  1. Press the power button on your server to boot it up. Wait for the circles to show up. Then press the power button to shut the server down.
  1. Press the power button to boot the server again. When the circles show up, power the server off using the power button.
  2. When you boot the third time, Windows Server will start Recovery mode.
inaccessible boot device server 2016 fix - boot to repair mode
Forcing Windows server to boot to Recovery mode involves interrupting the boot 3 consecutive times. For each step described below, you will boot to Repair mode as described above. When you try the first method, reboot your Server to check whether “Inaccessible Boot Device” error in Server 2016 is fixed. If not proceed to the next method.

Step 2 (Option 1): Roll Back Recent Updates

If you received “inaccessible boot device” error after installing a Windows update, here are the steps to fix it:

  1. Interrupt Windows Server boot to force it to boot to Repair mode.
inaccessible boot device server 2016 fix - boot to repair mode
  1. Next, click See advanced repair options.
See advanced repair options.
  1. Then click Troubleshoot.
  1. Next, click Command Prompt. Then click the Admin account to load Command Prompt.
  1. Enter the password for the administrator account and click Continue. Windows Command Prompt will load as shown in the second image below.
  1. At the Command Prompt, type the following command and press Enter:
reg load HKLM\temp c:\windows\system32\config\software 
The above command will load Windows registry to HKLM\temp. In the next step, you will access Registry from HKLM\temp.
type and run "reg load HKLM\temp c:\windows\system32\config\software" in command prompt
  1. Next, you need to delete the SessionsPending registry key. Execute the command below:
reg delete "HKLM\temp\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending" /v Exclusive 
  1. When you press Enter to execute the command above, you will be prompted to confirm. Type Y. Then press Enter key.
  1. Before you proceed to the next step, unload the registry using the command:
reg unload HKLM\temp 
inaccessible boot device server 2016 fix - reg unload HKLM\temp

Delete “Install Pending” Packages

The next step to fix this error is to delete all “Install Pending” Packages. Follow the steps below:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Create a temp folder to move the “bad” updates to. Type the command below:
MKDIR c:\temp\BadUpdates 
MKDIR - cerate a temp directory to move  bad updates
  1. The next step is to list al installed updates. To list all installed packages, at the command prompt, type the command below. Then press Enter.
dism /image:C:\ /get-packages 
inaccessible boot device server 2016 fix - dism /image:C:\ /get-packages
The next step is to delete all updates with “Install Pending” status. These are the packages likely causing the “inaccessible boot device” error.
Before you run the next command, look through the list of the result for packages with status, “Install Pending”. Note their Package Identity.
  1. To remove a package with “Install Pending” status, run the command below:
dism /image:c:\ /remove-package /packagename:Package-Identity  /scratchdir:c:\temp\BadUpdates  
In the last command, replace Package-Identity with the name of the package. You have to run this command one by one for all packages you wish to remove.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Step 2 (Option 2): Uninstall Newly Installed Device Drivers or Software

If you received the error after installing a device driver or software, follow the steps below to fix the problem.

Also popular on Amazon
9th & Vine Compatible Driver Pack Dvd for Windows 10, 8.1, 8, 7, Vista, XP in 32/64 Bit for Most Computers and Laptops
  • Drivers Pack for Internet, Wireless, Lan Ethernet, Video Graphics, Audio Sound, USB 3.0, Motherboard, Webcams, Bluetooth, Chipset. It will scan your Windows and install the latest drivers. No Internet connection is required. Perfect to update drivers, installing new hard drive or installing a missing driver. Supports Windows 10, 7, 8, 8.1, Vista, & XP in 64 & 32 Bit. In 42 Languages
  1. Interrupt Windows Server boot to force it to boot to Repair mode.
  1. Then select See advanced repair options.
  1. Next, click Troubleshoot.
  1. Then click Startup Settings. Finally, click Restart.
  1. When your server restarts, it will load Advanced boot options. Use the up/down arrow key to select Safe Mode. Then press Enter to boot to safe mode.
inaccessible boot device server 2016 fix - Windows server 2016 advanced boot options
  1. When your server boots, login as normal. Then uninstall any recently installed device driver or software.
To confirm that you are on Safe mode, when you login “Safe mode” will show on the four corners of your screen.

Step 2 (Option 3 Fix): Fix the Boot Record with the BootRec Command

This is the last method that could fix the error message. Follow the steps outline in this guide Run BootRec /FIXMBR.

Conclusion

I hope you were able to get your Windows Server up and running using one of the methods in this guide.

If you have any questions or comments use the “Leave a Reply” form at the end of the page. Alternatively, use our one-click feedback by responding to the “Was this page helpful?” question below.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.