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-31T23:01:57+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.

    Not necessarily.  This one sounds like the directory structure or the hard disk is at fault, not windows updates.

    you cant rebuild the BCD on X: and you do not need to.

    the rebuildbcd is reserved for when you are using recovery tools on the local windows volume hard drive, NOT booting from recovery media.

    You shouldn't need to do this anyway.  This topic is specific to windows patches causing inaccessible bot device.

    You may have other problems that are causing this message.

    if you can locate the windows volume, that is the drive letter that you need to use in the commands.

    The checkdsk error is normal.  when you run it from X: or a volume that you do not have rights to write the log.

    from the X: drive  type:

    dir c:\

    or dir d:\

    or dir e:\  and so on until you see your windows volume.

    Unless you can't see the windows volume, there is nothing to fix.

    If the windows volume directory is corrupt, you can fix it with a chkdsk but you must know which volume it is.

    when doing the dir command above, the windows volume should be one more letter above the drive that you see your

    recovery media on (but not always). 

    Your recovery media has the following 4 folders:

    boot

    efi

    sources

    support

    and some files.

    so if these folders appear on D:,

    your windows volume is usually E:\  (but not always)

    It's possible that the volume is corrupted.

    in the case where e: is your windows volume   try chkdsk E: /f

    If e: is your windows volume this will fix the directory structure so you can see and operate on it.

    If your problem was caused by windows updates, follow the instructions posted earlier in this thread.

    If the problem was caused by failing hardware, you will need to fix the hardware first.

    Wiz

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-31T22:46:23+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.

    What you haven't told us is what environment you are in, WinRE or WinPE. Depending on what you are trying to , I personally prefer WinPE.

    Logs are usually not kept in these offline environments BUT in some cases there are Options and Arguments that can be accessed.

    This is where "Help" becomes your friend to find out how to do that("/?" may help). My examples don't have them, you will have to study up and add them. I ignore any messages about logs in Offline modes:

    My examples for offline in comparison to the Online ones:

    sfc /scannow

    sfc /scannow /OFFBOOTDIR=R: /OFFWINDIR=F:\Windows                                                                 #  (OffLine)

    sfc /scannow /OFFBOOTDIR=R: /OFFWINDIR=G:\Windows                                                                 #  (OffLine)

    DISM /Online /Cleanup-Image /RestoreHealth

    DISM /Image:"G:" /WinDir:Windows /SysDriveDir:R:\ /Cleanup-Image /RestoreHealth                       # (OffLine)

    DISM /Image:"F:" /WinDir:Windows /SysDriveDir:R:\ /Cleanup-Image /StartComponentCleanup       # (OffLine)

    You have to replace drive letters with an appropriate one. Make sure you maintain spaces between /   To many should not be a problem but not between /Scan.

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-31T22:38:06+00:00

    Ok... good to know! Thanks Susan.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-31T22:31:53+00:00

    Given that my contacts at Microsoft say they don't have a root cause, I'm guessing it doesn't.

    Was this answer helpful?

    0 comments