You are here
Home > Latest Posts > How To & Tutorials > How to fix Inaccessible Boot Device Error in Windows 10 (WSUS/SCCM Managed)

How to fix Inaccessible Boot Device Error in Windows 10 (WSUS/SCCM Managed)

Inaccessible Boot Device

If you are running a Windows 10 PC with the Anniversary or the Creators Update installed, you may have recently updated your machine to the latest build released on October 10 i.e. KB4041691 (OS Build 14393.1770) or KB4041676 (OS Build 15063.674).

Customers who have downloaded the bits directly from Windows Update (Home and consumer devices) or Windows Update for Business are not impacted. However, the October 10th, 2017 monthly security update for Windows 10 v1703 (KB4041676) and v1607 (KB4041691), and Windows Server 2016 (KB4041691) for WSUS/SCCM managed devices seems to have impacted and broke the boot up on these devices with the following stop code: INACCESSIBLE BOOT DEVICE.

If you are still struggling to get the device to work, Microsoft has come up with a pretty long but working workaround. Let’s deep dive and fix INACCESSIBLE BOOT DEVICE error.

1. Plug into AC power and turn on the device.

2. Windows will enter the Windows 10 Recovery Environment. Select “Advanced options” on the Automatic Repair screen. Then click on ‘Troubleshooting’.

3. Select Command Prompt
. You may be asked to enter a BitLocker Recovery Key or username/password. If prompted for a username/password, you must enter a local account.

4. Microsoft Support advises getting rid of the SessionsPending reg key. Let’s load the software registry hive:
reg load hklm\temp c:\windows\system32\config\software

5. Delete the SessionsPending registry key (if exists):

reg delete “HKLM\temp\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending”/v Exclusive

6. Unload the software registry hive:

reg unload HKLM\temp

7. Pullout with DISM.exe the list of installed packages

dism /image:C:\ /get-packages

8.Checkout the ones which are state “Install Pending” as one of those was causing the issues (highly like the last entries in your list)

before we can remove them we need to create a temporary directory first to where we can move the updates to

MKDIR C:\temp\packages

9. Now let’s (re)move the “pending” package(s) with the DISM command

dism /image:c:\ /remove-package /packagename:PACKAGEIDENTITYNAME /scratchdir:c:\temp\packages

be focused on the output of the command and if it completes successfully

Sourcep-image-1216″ alt=”” src=”https://msdnshared.blob.core.windows.net/media/2017/10/dism_remove_package.jpg” />

10. Reboot your VM and it will reboot again and you can run Windows update afterwards as the faulty update was already corrected.

Official Microsoft KB:
https://support.microsoft.com/en-us/help/4049094/windows-devices-may-fail-to-boot-after-installing-october-10-version-o

Source

Shafat

Shafat has more than 5 years of Tech journalism experience. He likes to write about latest Tech and Gadgets. He is a proud Lumia 950 owner and Windows fan. He has been covering Tech and Gadget news on other well-known Tech sites GadgetOx and Nokiapoweruser since long. He loves to code and is a proficient developer.
Write to him at Email: [email protected]

Top