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-02-05T19:34:47+00:00

    This fix does seem to work, SOMETIMES...  I have had 3 systems now that I have tried the fix described above and the PC rebooted and kept giving me the BSOD.  System restore also did NOT bring it back.  I had to finally on these systems REMOVE the hard drive and backup the users information for e-mail, etc. and then do a RESTORE (Keeping user files to make it easier).  Once restored I then had to reinstall Microsoft Office and other programs that the restore deleted.

    This downtime is definitely NOT REASONABLE!  I know this is a bad SECURITY ROLLUP FIX and once removed it usually allows your machine to boot again..  HOW TO PREVENT THESE FROM INSTALLING????  I have quit upgrading firmware on PCs per Intels suggestion right now and I have TURNED OFF WINDOWS UPDATES / PAUSED them for 35 days.  Is this going to happen again to the fixed ones after the 35 day pause, and what about the other 60 I have in our company?  They are all Windows 10 Pro 64 bit so far.  Windows 7 and our AMD systems seem to be UNAFFECTED!

    Someone if you would please let me know, or how about Microsoft roll out a fix that works.

    Thanks

    IT Admin

    To stop the windows update just stop the windows update service and put it into "Disabled" state. I will keep it this way until a working patch from MS arrives.

    If your patch is already installed and waiting for reboot, stopping the service won't prevent the update from damaging your PC next reboot! I learned it the hard way. Disable the service and reboot the PC right away. If it comes back on, it will be OK.

    I spent one and a half work days on fixing this clear Microsoft failure  - I have PCs where a restore is  too troublesome, so I am happy. I know the procedure works. If not, some standard steps are needed like bootcfg.exe /fixboot are needed.

    I analyzed the dism debug logs and it looks that if someone downloads the patches now, they will be alright. The first two RollupFixes will be superseded and won't install at all. The newest rollupFix can be uninstalled easily as the package is repaired.

    All in all, I am well versed now in Microsoft technology, I know these commands by heart and I can install the updates offline from command line with Microsoft update turned completely off... It may be a viable option for critical pc, as these MS updates are more and more unpredictable. Some updates back Windows update installed a partition (yes!) on some of our PCs, causing dual boot not possible, now this...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-05T18:47:00+00:00

    This fix does seem to work, SOMETIMES...  I have had 3 systems now that I have tried the fix described above and the PC rebooted and kept giving me the BSOD.  System restore also did NOT bring it back.  I had to finally on these systems REMOVE the hard drive and backup the users information for e-mail, etc. and then do a RESTORE (Keeping user files to make it easier).  Once restored I then had to reinstall Microsoft Office and other programs that the restore deleted.

    This downtime is definitely NOT REASONABLE!  I know this is a bad SECURITY ROLLUP FIX and once removed it usually allows your machine to boot again..  HOW TO PREVENT THESE FROM INSTALLING????  I have quit upgrading firmware on PCs per Intels suggestion right now and I have TURNED OFF WINDOWS UPDATES / PAUSED them for 35 days.  Is this going to happen again to the fixed ones after the 35 day pause, and what about the other 60 I have in our company?  They are all Windows 10 Pro 64 bit so far.  Windows 7 and our AMD systems seem to be UNAFFECTED!

    Someone if you would please let me know, or how about Microsoft roll out a fix that works.

    Thanks

    IT Admin

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-05T07:15:25+00:00

    There is a .wim file  on an official DVD from Microsoft.

    If you have a .esd image, dism should work with it as well, simply use install.esd instead of install.wim. I did not try it, something along these lines:

    DISM /image:\d:\ \scratchdir:d:\temp  /Cleanup-Image /RestoreHealth /Source:esd:e:$Windows.~BT\Sources\Install.esd:1 /LimitAccess

    The index there 1 or 2 depends on which version of windows is in use.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-05T07:10:59+00:00

    In case somebody has no backup, I was able to solve the "twice broken" system issue. See my post on the end of page 26.

    Was this answer helpful?

    0 comments