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-23T23:43:13+00:00

    Thank you Crysta,

    I actually devoted a couple hours yesterday just plowing through this entire thread from page 1 until here. It was strangely inspiring to see that people had the same problems as me, and everyone just working hard to fix it.

    The DISM method worked for me I think. I don't know what made this time special, but when I removed some Updates, Restored my System to a Point on January 10, it just worked.

    I have the Windows 10 Home and was worried I only have this one normal boot to enjoy (before the Updates install themselves again) and I thought "Heck it. I'll just try and reboot, have it install itself, and let it have it's own way." And if I get stuck on the same BSoD again, ah well. I would just reinstall and start freshly clean. New PC and all.

    Well, the I rebooted the PC and it did install the Updates.... Loading screens, a few restarts later, and I'm back inside my OS again. Normal.

    I restarted my machine just to make sure. It still loaded normal. I don't know how long this might last, maybe a few days, a couple hours, or maybe the next restart would do it, but it seems I can use it normally again... for now.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-23T16:47:59+00:00

    Did you try making a WinPE on USB Drive from the 1709 ADK?

    Between Typhoon792 and myself there are instruction that will help, up Thread. Then you have more options with DiskPart/List Vol, DISM /RestoreHealth , SFC, CHKDSK etc. There is a load of help from about Page 10 on in this thread on, all you have to do is read it, learn and implement. Success does tend to be low though. If your PC is that new and you don't have something critical on it, one might want to just do a clean install. Newness really has no baring, all it takes it one (1) flipped bit in a critical flag on return instruction and these problems occur with these patches. 

    Reason, they are digging down so deep into the Kernel to change CPU processing architecture that have been accepted and implemented since 1995. That is what Meltdown and Spectre are all about....

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-23T16:29:48+00:00

    If DISM will run, just keep running SFC and DISM /RestoreHealth (Scanhealth is passive and all one gets on W 7 in the System Ready tool or Powershell.) over and over again in different order, until your errors are gone. I would also say interspersed by warm and cold starts but not in WinPE, only online. I have spent 3 hours doing that because it is like pealing an onion, layer by layer. I have been successful 99% of the time.

    At least the tools come out clean, is there potentially still corrupt there, yes but it might get you back online then one has more options like take a backup in case one makes matters worse in their efforts. 

    As well doing an In Place Update, etc......

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-23T16:17:34+00:00

    Does anyone have a link for Pausing Windows 10 updates via AD Group Policy?

    Thanks

    Dan

    https://docs.microsoft.com/en-us/windows/deployment/update/waas-wufb-group-policy

    Was this answer helpful?

    0 comments