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-03-27T08:06:32+00:00

    when I try to log on into my computer blue screen appear and said '':(Your pc ran into a problem and needs to restart.we're just collecting some error info, and then we will restart for you" after that it just said "preparing automatic repair"

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-03-23T12:50:24+00:00

    It was $300-$40just for diagnostics and the hope that they could fix the problem, no guarantee they would be able to save my old data. But there's a support package you can buy for $199 that covers the computer in question, all other computers in the house (current or purchased) for the next year-in store, on phone, and 24/7 chat. It's not a bad deal, but I'm holding it has my last resort. One of the IT guys at my job has offered to take a look at it and I'm also getting a Linux operating system boot disc. Once I recover just a couple files, I don't particularly care if it gets wiped! I just need to get in one more time...

    Thanks for the suggestion PatCHall! There were other people in front of me with the same issue, so I'm sure they could take care of it, I just would really rather spend that money on some other things!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-03-22T23:26:16+00:00

    Thanks to Susan B for setting up a support call with Msft.   I spent almost 7 hours over two days trying to resolve.   No dice and I have no choice but to reset.  I asked asked out the restore procedure front rbailin.  Please see attached response 

    I am very unhappy. ....sigh

    Greetings from Microsoft!

    I have just checked with my TL regarding the same. We have tried to reproduce the issue to recover the machine from the windows.old folder as prescribed in the article which you have provided, however, it did not work for us. As per our discussion on call that day, I have explained you that, every system has different configurations and different purpose of use. There may be various possibilities that the solution provided might worked for some people but it is not sure that the resolution will work for every scenario. I hope you understand the reason why Microsoft did not recommend these such solution. If you have any other query please feel free to ask.

    Regards, <br><br> <br><br>  <br><br> <br><br>  <br><br> <br><br>Rahul Ghemud
    Support Engineer <br><br>Windows Performance  Broad Commercial Team <br><br>Customer Service & Support <br>Microsoft Services (  425.704.3638<br>X 2265499 <br><br>*<br>******@mssupport.microsoft.com<br> <br><br>¹ <br>Tue - Sat  6:00 AM – 3:30 PM<br>EST

    **Technical Leads :**Pavan Dhanani <v-2pavdh@microsoft.com>, Shirish Charde <v-2shcha@microsoft.com>, Hrishikesh Pandya <v-2hrpan@microsoft.com  >

    Team Manager : Vikrant Pandey <******@mssupport.microsoft.com>

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-03-22T22:47:37+00:00

    What was the cost?

    Was this answer helpful?

    0 comments