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 No 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 No comments

506 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-01-23T05:02:11+00:00

    "The /SysDriveDir option specifies the path to the location of the BootMgr files."

    Wouldn't the path you want to reference there also be the C: partition (or whichever letter the OS is designated to) rather than WinPE?  

    Did I say it Ref WinPE, if so that would be a fau pau. However some 3rd party Recovery systems that have WinPE in them sometime embed themselves in the BCD and thus come up on the Boot Menu. I would NOT do that unless one has a separate System Recovery with centralized Boot Environment implementation on a partition(This the way I run). In my case it is called 'R' and is also where my WinRE files are, that way THEY ARE NOT on 'C'.

    That is why one has "/SysDriveDir". 

    On 'R' I have Backup Images extra BCD backups that I can copy over if the active one gets corrupted, etc....... It is quit custom. Some OEM Companies build a Recovery partition and hide it. Sometimes they put the Boot files on it as well. Then one need a facility to unhide...

    If this is not similar to your configuration and every thing is on 'C' than you don't need "/SysDriveDir".

    Best Regards,

    Crysta

    Ah, that's smart.  In my present case scenario, I have WinPE separately on a drive and only the native (upgraded) OS to the computer on hand.  That being the case, would the DISM commands look like the following?

    "DISM /Image:C:  /WinDir:Windows  /SysDriveDir:C:\  /Cleanup-Image"

    In other words, both directories pointing to "C:" (or in my case, having checked with Diskpart, "D:")?

    Thanks! :)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-23T04:49:02+00:00

    "The /SysDriveDir option specifies the path to the location of the BootMgr files."

    Wouldn't the path you want to reference there also be the C: partition (or whichever letter the OS is designated to) rather than WinPE?  

    Did I say it Ref WinPE, if so that would be a fau pau. However some 3rd party Recovery systems that operate in WinPE, sometimes embed themselves in the BCD and thus come up on the Boot Menu. I would NOT do that unless one has a separate System Recovery with centralized Boot Environment implementation on a partition(This the way I run). In my case it is called 'R' and is also where my WinRE files are, that way THEY ARE NOT on 'C'.

    That is why one has "/SysDriveDir". 

    On 'R' I have Backup Images extra BCD backups that I can copy over if the active one gets corrupted, etc....... It is quit custom. Some OEM Companies build a Recovery partition and hide it. Sometimes they put the Boot files on it as well. Then one need a facility to unhide...

    If this is not similar to your configuration and every thing is on 'C' than you don't need "/SysDriveDir".

    Best Regards,

    Crysta

    PS I just went back and looked at Page 12 and what I wrote there(is that where you were looking,Dave?). Were you also meaning doing this in WinPE? If so sometimes one needs to get a bit more specific than one usually has to, in WinPE to get results. In other words sometimes I have noticed that one needs to state the obvious.....

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-23T04:28:12+00:00

    "The /SysDriveDir option specifies the path to the location of the BootMgr files."

    Wouldn't the path you want to reference there also be the C: partion (or whichever letter the OS is designated to) rather than WinPE?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-22T21:01:13+00:00

    For 0x8000ffff, I tried:

    • Renaming ..\windows\winsxs\pending.xml
    • Renaming ..\windows\SoftwareDistribution
    • Renaming ..\windows\system32\Catroot2
    • Set both  "Exclusive" and "TotalSessionPhases" data to "0".
    • Mounted the Components registry file and removed some value(was mentioned in a Microsoft article, didn't archive the solution's steps).
    • Ran DISM's /scanhealth and /restorehealth commands(tried a second time choosing a 1709 version Windows 10 disk "install.esd" file as the source).
    • Ran chkdsk
    • Ran SFC

    Still getting 0x8000ffff when adding or removing packages using DISM. That computer is also getting the clean install treatment.

    OKAY,

    Here is what I found using Bing(because both are MS): "0x8000ffff".

    Microsoft "Fix It": Fix Windows Update Error 0x8000FFFF Fix it Live!  https://answers.microsoft.com/en-us/windows/forum/windows_other-update/microsoft-fix-it-fix-windows-update-error/2c5c9562-fa47-47f3-9748-a03f638cb96b

    Fix Windows Update Error 0x8000FFFF Fix it Live! https://blogs.technet.microsoft.com/fixit4me/2009/01/07/fix-windows-update-error-0x8000ffff-fix-it-live/

    This will get you started..... it is old....

    I will update with more, I revised Bing(because both are MS): "0x8000ffff Windows 10".

    UPDATE, ADD FROM A 2015 POST

    This may or not be applicable???? https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_store/windows-10-windows-store-error-code-0x8000ffff/4bdf96fb-73b6-4bba-8dac-0a00056a67cc

    Ankit Rajput replied on

    Microsoft

    Hello,

    Thank you for your response. I appreciate your time.

    If you are using third party security software, try disabling third party security software and check. Disable third-party Security Software.

    a. You should see an icon for your Antivirus program in the Task-bar notification area. It is usually at the bottom right corner of your desktop.

    b. Click on the third-party Security Software Icon, you will see a pop up.

    c. In that pop and select the option to disable, click on it.

    d. Now the third-party Security Software will be disabled.

    Important Note: Antivirus software can help protect your computer against viruses and other security threats. In most cases, you shouldn't disable your antivirus software. If you have to temporarily disable it to install other software, you should re-enable it as soon as you're done.  If you're connected to the Internet or a network while your antivirus software is disabled, your computer is vulnerable to attacks.

    Sincerely,

    Ankit Rajput

    Regards,

    UPDATE ADD ANOTHER POST

    The problem I am finding is the nobody seems to be resolving it within MS. So now one need to go to 3rd Party sites....

    Here is a short POST from 2015.....     https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-windows-update-fails-error-0x8000ffff/da837175-2632-4840-97cb-a957744f2879

    DAVIDSMELVILLE asked on

    Q:windows 10 ,windows update fails error 0x8000ffff 

    Using windows update it windows 10 , I found a cumulative update  for x64 based system which I have.  This it for kb3081445 . When download , it attempts to install and fails error 0x8000ffff . This has happened several times and I have no idea what can be causing it to fail. Can someone please assist me.

    I need to make a meal. I will look some more if you haven't found a resolution with the revised Search:   "0x8000ffff Windows 10", using a number of different Search Engines(I have about 6 avail).

    Let us know how you are doing.....

    Best Regards,

    Crysta

    Was this answer helpful?

    0 comments No comments