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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-03-16T20:00:36+00:00

    This is over a year later than these last posts.  This just happened to me on a Dell laptop I was updating - March 15, 2019.  The laptop took the first two updates from February but this last one on March 15th got me the Blue Screen and all of the roundabouts everyone has previously been talking about.  I was able to delete the last two updates using the above method, but the 1st one of the 3 states "Uninstall Pending" and the tool says that the update is "Not installed" "Operation completed successfully." I haven't been able to delete it. There were 3 KB448.... packages also  installed on March 15 before the 3 Rollup pages.  Should I try deleting the as well?  The computer seemed to run fine until the last Rollup update failed.  Need help - I thought this problem had been resolved in the last year!

    Thank you!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-03-17T18:19:38+00:00

    This is over a year later than these last posts.  This just happened to me on a Dell laptop I was updating - March 15, 2019.  The laptop took the first two updates from February but this last one on March 15th got me the Blue Screen and all of the roundabouts everyone has previously been talking about.  I was able to delete the last two updates using the above method, but the 1st one of the 3 states "Uninstall Pending" and the tool says that the update is "Not installed" "Operation completed successfully." I haven't been able to delete it. There were 3 KB448.... packages also  installed on March 15 before the 3 Rollup pages.  Should I try deleting the as well?  The computer seemed to run fine until the last Rollup update failed.  Need help - I thought this problem had been resolved in the last year!

    Thank you!!

    This problem WAS resolved a year ago.  Your problem is not the same.  Hence the solutions don't work.  Your best bet is to get into recovery mode.   Open up a command prompt, make sure  you perform a chkdsk and a SFC/Scannow.

    Then perform a system restore back to before the last update.

    If you get the system to boot.   Google "download Windows 10 ISO" and get the media creation tool from Microsoft.

    Run it.  I would download the ISO image rather than selecting the UPGRADE THIS PC option.  Then double click the iso to mount it and run the setup.  It will do an in-place upgrade to version1809.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-03-17T19:59:41+00:00

    Thank you for responding! 

    I am at a command prompt at x:\Windows\System 32 and performed  a chkdsk resulting in:  

    The type of file system is NTFS

    The volumn is in use by another process, Chkdsk

    might report errors when no corruption is present.

    Volume label is Boot

    WARNING!  /F parameter not specified.

    running CHKDSK in read-only mode.

    Read-only CHKDSK found bad on-disk uppercase table - using system table.

    Stage 1:  ….basic... 29 file records processed. File verification completed. No Files processed - Stage 2 ...file name linkage...43 index entries processed.  Index Verification complete, 0 unindexed files scanned or recovered and 0 reparse records processed.  Stage 3...security descriptors... Verification complete...Errors detected in the uppercase file.

    CHKDSK /F  will not run! says;

    Cannot lock current drive.  Windows cannot run disk checking on this volume because it is write protected.

    Ran SFC/Scannow

    Verification 100% complete.

    Windows Resource Protection could not perform the requested operation.

    I also have access to C: drive and D: drive from the command prompt.

    Windows still not booting.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-03-17T20:11:25+00:00

    Forgot to mention:

    I have 3 restore points available.  I have tried all 3.  They will each run for about 20 minutes purporting to be "Restoring files," but in the end the restore fails.

    Was this answer helpful?

    0 comments