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-03T08:21:10+00:00

    what I can do if I did restart after first successful boot without in-place upgrade ? I get same "inaccessible-boot-device-error" and now unable to boot even following this instructions again

    I got now a laptop with the same issue. The repair is overwritten with next reboot, so beware everyone!

    allloohaaa, what is the shape of the image? In my case the install image is broken.

    try to run this command to find out:

    dism.exe /image:YOUR_REAL_WINDOWS_DRIVE:\ /cleanup-image /scanhealth to find out while booted from an USB stick.

    I analyzed package list in my instance and found that some packages changed state from installed to superseeded so uninstalling them in the same order as before (batch script) wouldnt work.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-03T11:05:10+00:00

    I have been unable to find a fix that will undo the final steps of the bad update that caused the initial blue screen.  There are literally hundreds of pending deleted and renames that happen.  I've spent considerable time trying to figure it out.  Thats why I imaged the drive before operating on it in the first place.

    My best advice at this point is to do the system reset, keep your data and reload the programs.  If I discover a way to resolve it at this point, I will post it, but don't hold your breath.  I spent way too much time working on recovering the crashed systems of mine and my clients.  They are all recovered now, and I am now way too busy trying to catch up.  So I won't be spending much additional time on it.

    Let this be a learning experience.  If the windows build is valuable, image it to a backup drive

    The cost of the data usually is higher than the cost of the hardware.

    You can get a 2 Tb external drive for under $70 from a variety of vendors.  Seagate, Western Digital have a version of Acronis that is free (but only works on their hardware).

    Schedule it to backup at the end of the day.  That way when you see a blue screen in the morning (after a bad update,) you can easily recover from it.

    Also, if you have a UEFI BIOS, unless you really are concerned about someone coming in your house, booting from a flash drive and stealing your data, Turn off Secure Boot in BIOS.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-03T11:06:37+00:00

     Now they suggest the only option is to reset/ rebuild my PC, but I don't want to lose various software that I no longer have install media and/or keys for.

    Hoping the collective wisdom of the internet may have some more suggestions?

    The command

    dism /online /cleanup-image /restorehealth won't work from preinstallaton environment.

    You need to check on which drive are your Windows files while running from the USB stick. Usually it is D: if you have the system partition.

    Then run dism.exe /image:D:\ /cleanup-image /restorehealth I am writtng this from off the top of my head.

    It is usually possible to see what is broken in the package by examining the dism logs. This is a very tedious work, not worth it if you have another recovery options.

    This didn't work either unfortunately. 

    Am I right in thinking that now my only option is to rebuild and lose all my software?

    If so, my OS and some software are on my SSD, whereas most of my software and files are on my HDD. Can I remove my HDD and then rebuild to protect most of my software or will this not work as all the "my documents" folders etc are on the HDD?

    Happy to try any other suggestions people have, including the registry change (although suggestion above is that it doesnt work)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-03T13:24:24+00:00

    TheWizardOfAhhs1 , I have restored already twice the image today on a pc where there the problem reappeared after reboot. I found that in the case of "second reboot halt" there are no items pending for installation. But  what genereates them is the command:

    dism.exe /image:e:\ /cleanup-image /revertpendingactions

    I go much further without running this command. Hope this helps.

    Was this answer helpful?

    0 comments