Inaccessible Boot Device error in Windows 10

Anonymous

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?*

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

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

0 comments

506 additional answers

Anonymous

2018-01-15T20:18:44+00:00

Another one just bit the dust and it is stuck on Preparing Automatic Repair. I am hoping I can get into Reset or Restore.

Microsoft I am outraged. You have people on this forum talking about failure rates of 17% - 50%! That is I have experienced a failure rate of over 20%. This is a huge issue and you are far to quiet. What is the problem and then what is the fix?
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-15T17:18:22+00:00

We've had 3 out of 26 PC's go down in the last week - 1 was repairable using the "repair start-up" function, one is currently going through the repair function so fingers crossed and the 3rd cannot be repaired at all as it appears the the C: drive has now become the D: drive (I can access all files on the PC in D: drive through command prompt). These PC's are 5 years old and we've never had one go down so for 3 to fail within a week is more than a coincidence and has to be related to a Windows update.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-15T16:55:32+00:00

My office is 5 out of 25 so far. Unfortunately, because we are using OneDrive Files on Demand, we are unable to perform a System Restore. It errors out when trying to rollback the OneDrive files. So we have had to Reset each PC with this issue. Many hours lost...

I forgot to add, we are running Windows 10 Pro 64-bit with PC-Matic Pro for Antivirus
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-15T16:31:59+00:00

We've had 5 work computers out of 80 so far stuck in the repair loop in the past week after recent windows updates.

(My colleague mentioned that some folks in Dell/Microsoft/Symantec forums have reported 50% of their computers with problems)

They are Dells with Intel (not AMD) processors.

The 5 all had "Inaccessible Boot Device."

There was nothing out-of-the-ordinary with these computers.

No new external devices or software besides windows and AV updates.

(They all have Symantec Endpoint Protection.)

We've tried many of the fixes found by doing a web search of the last week for "windows 10 inaccessible boot device after update".

None of them have worked.

If there was a restore point, we were able to restore from it.

If there was not, we were able to save the user files but had to reinstall all other software, a very time consuming process.

We wanted to create a restore point for every computer here.

(Search/magnifying glass enter "Create a restore point")

However, some computers do not have the System Protection tab.

There is no group policy in place to disable setting a restore point.

It would require going to each computer and logging in as admin.

There are many discussions online about this secondary issue.

There are restore points being created by critical updates on some computers.

System Protection tab, System Restore, click on show more restore points.

If anyone else has had this problem, please post numbers of computers affected/not affected/Intel or AMD and what AV is running.

There may be a common thread.
Was this answer helpful?

0 comments No comments