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

After installing this update, some USB devices and onboard devices, such as a built-in laptop camera, keyboard or mouse, may stop working. This may occur when the windows update servicing stack incorrectly skips installing the newer version of some critical<br> drivers in the cumulative update and uninstalls the currently active drivers during maintenance.	Microsoft is working on a resolution and will provide an update<br> in an upcoming release.<br><br>Workaround steps are available in<br>KB4091240.
After installing this update, some devices may fail to boot with INACCESSIBLE_BOOT_DEVICE.<br><br><br>This issue occurs when the windows update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.	Microsoft is working on a resolution and will provide an update in an upcoming release.<br><br>Workaround steps are available in KB4075150.

0 comments

Anonymous

2018-02-24T01:12:31+00:00

Hello Wizard of Ahhs,

Per the MS Support Tech, 1703 and 1709 images contain the patch is not functioning. 1607 was the last image he had available without the problem patch.

Before this we had also been successfully running Win 10.

We were unable to rollback the latest updates, or do a clean install to a unpartitioned disk.

So the options presented to us by the MS Support Tech, move forward with 1607 into unknown territory, or stay with a working system in Windows 7.

Not having any major need on this particular machine to use Win 10, we decided to stay with the working system.

Thanks,

Jim
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-24T00:11:02+00:00

Jim.Anthony

Why would you want to install 1607 when there are two newer releases (1703 and 1709) and another one (1803) less than a month away?

I too own several HP machines that HP has "not tested" for compatibility. Some have Core Duo or Athlon x64 CPU's

All are running windows 10.

However I did run into a problem going from 1607 to anything newer on another machine.

I had a client with 8.1 and could not upgrade to 10 (1709).

He could do 1507 and 1511 and 1607 however. But that's as far as it went.

It turns out there are some bugs in the upgrade logic that will sometimes cause 1607 NOT to be able to upgrade any further, even though you can reinstall 1607 over it self without a problem. MS knows about the problem but has no fix only a workaround.

The Workaround:

In those cases a System reset fixes the problem. However all your programs will no longer run and you will need to re-install them.

I haven't seen a HP System that was shipped with 7, 8, 8.1 and was offered the Windows 10 upgrade that is not capable of running the latest version with a clean load.
Was this answer helpful?

0 comments No comments
Anonymous

2018-02-23T23:48:32+00:00

Another possible issue is that the image is corrupt. You may need to get into the repair tools on the hard drive to fix this. Let it try to boot from the hard drive and try to repair itself.

If the image is corrupt, most likely it will repair it as it tries to fix the startup problem.

then shutdown normally. Insert your boot media and try again.

wiz
Was this answer helpful?

0 comments No comments