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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-01T00:50:26+00:00

    Thanks Crysta,

    I have recovery images on an external HD that is unplugged after each backup. When plugged in it will show them but stops when trying to load them & returns to

    I have new bootable ISO 1709 USB thumb drives made directly from the MS site yesterday. I also have a unused new copy of Windows 10 Pro. These all show up on my other comps fine & try to load. But will not even attempt to load on the bricked up comp with blue screen.

    Also inside of this drive X: I have several system backups that it won't identify now. I back the system up 2-3 times a week. There are no bad sectors on the internal HD & all files show no problems in scans.

    As soon as you turn on that comp it goes in to automatic repair mode then to blue "Choose an option" screen. None of the options or advanced options work except command prompt. The comp will not go past this point so I can't get a screen copy. In DiskPart I get a list of drives C - H, with 1 being the DVDRW & the rest being on 1 HD. I do not have multi drives hooked to that comp. The update formed my HD into 5 drives = 1 OS, 1 system, 1 HP recovery & 2 unknown small drives (4 unchangeable partitions now). Partition Magic or my repair disk couldn't even break them up.

    I know it sounds like it would be simple to load something, but it will only run my repair disk & Partition Magic which can make no changes to that system now. The HD is good, the backups are good, the USB ISO drive is good, the Win 10 updates caused a "Meltdown" of that comp.

    Thanks again.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-01T00:15:14+00:00

    I can't seem to get away from drive X: where my boot files are being held hostage. It will list up file locations in drive X: but will not allow any access. Online & offline it still  results in errors stating file locations, missing commands, etc.. It will not allow anything to fix any drive(s) or show log files.

    It will not even find a windows installation record in DOS, but still lists the version in errors.

    After roaming Google on this laptop for days seeing ??? # of people with every problem you can think of from these updates, it has me dreaming about DOS commands in my sleep. The problem desktop here will not allow anything to be loaded in it, it just goes to auto repair mode when started (even after changing the boot order 20 times trying to load ISO & full versions from disks & USB drives)

    I just want to remove Version: 10.0.16299.15 & get back to 1709 minus Jan update.

    Thanks for any ideas (waiting on Quantum)

    Quantum???? As in Quantum Computing??? You think we have problems now......?????? lol

    2 directions possible but I need more specific detailed Information.

    • I need a detailed description of exactly what you are using and how you are getting to where you get to?

    Is it a WINRE(Recovery Environment from USB or Hard Disk) or something else?

    Is it a WinPE (Preliminary/Preinstallation Environment, a USB Disk You made yourself from the 1709 ADK) or from some other source.

    Most 3rd Party Recovery/Restore USB/DVD use WinPE, may be able to give you your disk layout as well as a CMDLine.

    • Can you make or do you have an W 10.0 1709 Installation USB/DVD. In other words can you tolerate a Clean Install? How much would you loose. It sounds like, what somebody said to you, here, your drives are rather tangled up. Not being there I can't see what your seeing. Could you do a C&P of the DISKPART >> List Vol.

    You certainly seem like you have a conundrum. Have you heard of "The School of Hard Knocks", your attending it whether you want to or not.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-31T23:55:12+00:00

    Thanks for the input Wiz, I have ran it from every drive available (except x:) and it all checks out good until I try to change anything & then it refers you right back to x:\Windows\system32 or another folder/file on x: which can not be accessed.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-31T23:37:04+00:00

    I can't seem to get away from drive X: where my boot files are being held hostage. It will list up file locations in drive X: but will not allow any access. Online & offline it still  results in errors stating file locations, missing commands, etc.. It will not allow anything to fix any drive(s) or show log files.

    It will not even find a windows installation record in DOS, but still lists the version in errors.

    After roaming Google on this laptop for days seeing ??? # of people with every problem you can think of from these updates, it has me dreaming about DOS commands in my sleep. The problem desktop here will not allow anything to be loaded in it, it just goes to auto repair mode when started (even after changing the boot order 20 times trying to load ISO & full versions from disks & USB drives)

    I just want to remove Version: 10.0.16299.15 & get back to 1709 minus Jan update.

    Thanks for any ideas (waiting on Quantum)

    Was this answer helpful?

    0 comments