Inaccessible Boot Device error in Windows 10

Anonymous
2018-01-09T16:46:16+00:00

I manage multiple computers running Windows 10 Pro 64-bit with the latest Current Branch and recently had multiple computers randomly startup with this BSOD: Inaccessible Boot Device.

I have tried everything:

https://www.windowscentral.com/how-fix-update-causing-inaccessible-boot-device-error-windows-10

Which recommends deleting registry keys and install packages, though no pending installs could be found

SFC /SCANNOW - No corruption found

CHKDSK /R - Some minor issues corrected

BOOTREC - Scan OS shows 0 windows installations

FIXBOOT - Successful, but this tool finally made the entire process fail without being able to get to the recovery environment, just boots to the legacy screen and shows options for safe mode, but those fail too.

I am at my wits end, because I find thousands of websites and desperate users and admins, but the only fix that works is to clean install. I can't clean install the whole company. This is insane, there has to be a better known cause / fix out there...

*Modified title for accuracy*

*Original title: Inaccessible Boot Device error - cause? fix?*

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-01-17T17:16:49+00:00

WIN 10 BSOD FIX - Inaccessible Boot Device - THIS WORKS!  I Just Repaired 2 computers that went down at the same time last night on 1/16/18

Good Afternoon Bobby,

Here is the fix I came across from another kind IT tech, please see below.  Credits go to them, I'm just forwarding so everyone can finally get their computers back up and running.

Boot Windows 10

Go to Repair

Go to Tools/Options to get a command prompt.

Confirm the drive letter for the Windows image. Usually D: –> dir d:

Run the following to view the installed packages which will also show a date of install.

Dism /Image:D:\ /Get-Packages

Find the package(s) that were just installed by date. Run the following command on the last installed package:

example: dism.exe /image:d:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0

Reboot.

The patch that caused my issue was from 1/6/18 or 1/10/18     Remove the latest windows update entry with Rollup Fix in it's name.  Once complete, close command prompt, turn off computer.  Power back up.  You should be back into WIN10.

If you still receive BSOD, rinse and repeat with the next latest update, try it again.  You'll eventually boot right back into WIN10.

I hope this helps.

Have a great day.

Showster

Was this answer helpful?

30+ people found this answer helpful.
0 comments

506 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-02-06T20:26:37+00:00

    Again is there a procedure to ID the bad patch, delete it before it tries to load on a reboot?

    For reboot pending check up the registry in these places:PendingFileRenameOperationsat "HKLM:\SYSTEM\CRebootRequired  at "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update"RebootPending "HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\" System Center Configuration Manager wants to reboot by looking at Invoke-WmiMethod -Namespace root\ccm\clientsdk -Class CCM_ClientUtilities -Name DetermineIfRebootPending | Select-Object RebootPending

    There is a script from Microsoft checking in these places. The script did not work on a workstation for me though (it is meant for Microsoft Servers). https://gallery.technet.microsoft.com/scriptcenter/How-to-check-if-any-4b1e53f2/

    EDIT the registry keys break up after I paste them here, 

    PendingFileRena

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-02-07T04:46:06+00:00

    If windows is up and running, you need only do a repair install.  got to 

    https://www.microsoft.com/en-us/software-download/windows10

    and download the iso image.   once its done, click on it to mount it and then run the setup.

    It will reinstall windows 10 keeping all your programs and data.

    After that is done, your machine will reboot and startup normally.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-02-07T04:50:49+00:00

    there are half a dozen places with pending updates, pending deletions and pending xml and other stuff.

    When I looked there were over 500 items in the pending renames and pending deletes.

    It's a very complicated process.  Much easier to do a repair install after the first boot.

    The repair install will kill all the pending stuff and replace all the bad files and/or registry updates with ones that work.  Since the update that caused the problem is no longer an issue, you should be fine.

    Wiz

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-07T19:33:09+00:00

    I tried installing a MSU package offline unfortunately it was on an AMD PC this morning that WENT DOWN due to MICROSOFTS UPDATE. AGAIN.....  Very Frustrating.  I used DSIM to take out the packages, however, then when it rebooted, still got the BSOD and had to eventually take out the hard drive, back up the data and do yet another restore that kept this user down 2-3 hours until It reinstalled everything again.  This is BAD.  This is the first AMD system that was affected and its NOT OLD.  Its less than a year old, Core I5, 8GB, etc.  I seen where on OLDER AMD there may have been a problem, but this just happened today.  Should I install the patch that is available on the other AMD systems to prevent this from happening?  They are brand new Lenovo Core I5, 8gb, SSD, etc.  Or just turn off updates and leave them.  I still have about 50 PCs on Windows10 Pro that have not rebooted and they are pending reboots.  Which package is bad?  What ID??  So i can go in and uninstall this update?  We cannot afford for PCs to keep dropping.

    Some of them come back up after using DSIM from command prompt when you go into Troubleshooting and remove it, but I have now 3 pcs that have been affected by this that I could not just remove the package.  The BSOD still came up and had to do a restore with keeping user files, just had to reinstall office, etc again to get them going.  Just a lot of downtime.

    Appreciate any feedback.

    Thanks

    IT Admin

    Was this answer helpful?

    0 comments