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-01-29T03:50:37+00:00

    Did Microsoft release the patch yet?  The main fix?  Please post it!

    Showster

    I am not sure there is going to be a "Main Fix" Showster. Microsoft has been dribbling Patches out in total silence over the last couple of days. Look at my feed backwards and you will see what I mean. I was having 'cookie' problems with Microsoft.com so I am slow with the one I posted here. Only Reason, allot of BSoD going on here.

    Several of us are trying to keep up with each other and Microsoft's proceedings???? It is not easy.....

    In the Catalog: "2018-01 Windows Update" you will see some but not all which I am tracking. WU/MU may or may not present even when it is suppose to.

    My best suggest is one I made earlier:

    Watch:

    Patchmangement.org That is where you will witness Susan Bradley and others.....

    On Twitter:

    https://twitter.com/PhantomofMobile

    https://twitter.com/woodyleonhard

    https://twitter.com/rodtrent

    Susan rarely Tweets. These folks, including myself are on Twitter mostly for Technical Reasons. Some are Professional Reporters. If you watch close enough, one can get to know some of the critical MS people in various disciplines BUT none of them are saying very much at all about Meltdown or Spectre.

    It really only stands to reason. None of them whats their words to haunt them in a/several Court Cases

    Take Care Showster. This is the beginning of a several year....something.....

    Best Regards,

    Crysta

    @Phantomofmobile (A take on "Phantom of the Opera")

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-29T03:16:34+00:00

    Did Microsoft release the patch yet?  The main fix?  Please post it!

    Showster

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-29T03:16:05+00:00

    My USB sticks where not accessible when I put them in , had tried to update driver, no luck, so I did a troubleshooting on Control Panel Devices and Printers which said it changed things and needed to reboot. When it did I got the Inaccessible Boot Device screen. I couldn't  get to boot to Windows 10 Repair so I ran on power up to go to command prompt but when I entered the above fix D:\ Dism /Image:D:\ /Get-Packages it said command line is missing a required servicing command. Any suggestion? Thanks.

    Not being sure what Environment your in, this should work in all environments:

    DISM /Image:F:\ /Get-Packages /norestart /Scratchdir:R:\Temp\Scratch\

    Make the appropriate adjustment for your Disk setup. if these Directories are not setup "R:\Temp\Scratch", DISM will default to it's own Directory of Scratch on the same Disk. This is most necessary in a WinPE/RE Environments, though I have never run out of space without it.

    Also check your BIOS/UFEI Menu for accurate setup for USB Drives. If your in WinPE/RE check your disk layout in DISKPART with List Vol. To exit, type EXIT.

    Best Regards,

    Crysta

    @Phantomofmobile

    PS. I am not here much anymore. If you want me contact me on Twitter.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-29T03:01:40+00:00

    I don't know how many of you are still watching this thread?

    Here is something y'all should be aware of:  Stop Errors = BSoD

    Crysta T. Lacey‏ @PhantomofMobile

    Crysta T. Lacey Retweeted Rod Trent

    Stop errors caused by spurious interrupt on systems PIC and APIC interrupt controllers

    Thank You: @SBSDiva @rodtrent

    ICYMI: @AdminKirsty @maryjofoley @woodyleonhard @mehedih_ @ruthm @WithinRafael @thurrott @MPECSInc @SGgrc @MalwareJake @sans_isc

    Crysta T. Lacey added,

    ![](https://pbs.twimg.com/profile_images/918845621867503616/E0zBVm85_bigger.jpg)Rod Trent‏ @rodtrent

    Stop errors caused by spurious interrupt on systems PIC and APIC interrupt controllers

    https://support.microsoft.com/en-us/help/4077561/stop-errors-caused-by-spurious-interrupt-on-systems-pic-and-apic-inter …

    2:24 PM - 26 Jan 2018

    7:35 PM - 28 Jan 2018

    Crysta T. Lacey‏ @PhantomofMobile

    KB4077561 Applies to: Windows 8.1Windows Server 2012 R2 Standard

    January 3, 2018 - KB4056898 (Security-Only Update)

    January 8, 2018 - KB4056895 (Monthly Update)

    January 10, 2018 - KB4073576

    January 17, 2018 - KB4057401 (Preview of Monthly Rollup)

    http://www.catalog.update.microsoft.com/Search.aspx?q=KB4077561 …

    7:35 PM - 28 Jan 2018

    Was this answer helpful?

    0 comments