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-31T22:23:39+00:00

    Now this is out today: https://support.microsoft.com/mk-mk/help/4058258  I have no idea if this will fix any of the things we have been discussing.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-31T22:22:56+00:00

    Trying this solution again I got "error: 1639"

    "The DISM log file can be found at X:\windows\Logs\DISM\dism.log

    I get the same messages anyway I try it. Under "chkdsk" I get "Failed to transfer logged messages to the event log with status 50"

    In "DiskPart" I can call up all volumes but X:

    Using D:>sfc /scannow I get "Windows Resource Protection could not perform the requested operation"

    Using D:>bootrec /RebuildBcd it runs and returns saying no windows installations were found.

    I have tried these and 50 other commands on all drives c:-h: (mounted & unmounted) and get the same results?

    I believe this is irreparable at this point.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-31T22:19:30+00:00

    This whole situation is a total mess. I had to rebuild my work PC because none of these fixes worked, and I'm getting inundated with calls from work colleagues and friends with similar problems. One colleague is going on a business trip abroad tomorrow morning and her laptop's just bricked following a Windows update! Unbelievable.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-31T21:10:39+00:00

    I got this problem on Jan 9-11, but had to go out of town to work for 12 days. I thought that they would have a fix by that time. I have tried all of the fixes on this thread several times... It will not allow that comp to boot anything. In "Startup Settings" there are no f4, f5, f6, etc.. options, just bullet points in front of these options. I have used every DOS scan, repair, etc.. & still come up with errors inside of drive c: that says it can not do anything because of lines of Caps are inside (which is the x: drive). It does find a backup on an external drive, but won't let it run.

    I have been on the phone with several other IT pros that just scratch their heads at this mess. I had to correct the IT person from MS on how to make a USB bootable copy of 1709, that gave me confidence... not (after 4 hours they had no answers either).

    Thanks for your advice, but all I've found is 100s of different problems caused by the same bad updates (Oct/17 & Jan/18) on every brand of comp & cpu's.

    MS put out bad updates for what I thought was a decent OS. I am going back to Linix for my home network once the file recovery process is done. Or I will code a batch file that will stop all Win 10 updates from installing on startup or shutdown.

    I'm still amazed that MS has not came out with a fix for the problems that we are all here discussing. Have a Great week.

    Was this answer helpful?

    0 comments