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-22T00:36:46+00:00

No I didn’t walk through all those settings and all the notes that you had in your one post.

I haven’t checked the thread since Friday and just was fed up so I decided to do a clean install. I appreciate the help though!

Yes that’s the update that I installed. So far so good
Was this answer helpful?

0 comments No comments

Anonymous

I just decided to do a clean install. Ran out of options with all the tinkering and suggestions. Microsoft 1 Me 0

I got the update installed that borked the machine to begin with and then got the patch that they released for the AMD chip issue. Everything is back to normal just took a couple days to get things configured and installed again.

Let’s not go through this again, shall we?

OH Dear, but I am not sure surprised. Did you use the tools I list above?

Did you got to the Catalog for this Update:

http://www.catalog.update.microsoft.com/Search.aspx?q=Windows+Update++2018-01

Update Details

http://www.catalog.update.microsoft.com/Search.aspx?q=KB4073290

OS Build 16299.194 (I am told, haven't done it yet)

2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4073290)

Last Modified: 1/17/2018

Size: 602.9 MB

Overview

Description: Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer. Architecture: AMD64 , X86 Classification: Updates Supported products: Windows 10 Supported languages: all

MSRC Number: n/a MSRC severity: Unspecified KB article numbers: 4073290 More information: http://support.microsoft.com/ Support Url: http://support.microsoft.com/

Package Details

This update has been replaced by the following updates:

n/a

This update replaces the following updates:

2017-11 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4051963) <<<<<<<<<<<<<<<<<

Best Regards,

Crysta

0 comments

Anonymous

2018-01-21T23:26:28+00:00

I just decided to do a clean install. Ran out of options with all the tinkering and suggestions. Microsoft 1 Me 0

I got the update installed that borked the machine to begin with and then got the patch that they released for the AMD chip issue. Everything is back to normal just took a couple days to get things configured and installed again.

Let’s not go through this again, shall we?
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-21T19:02:09+00:00

Thank you for your fix.......... but let me tell you how that worked with my notebook from Lenovo with Intel Chip!

Had the "inaccessible bootdrive" problem after the patch : KB4056892

Did try a lot of things that did not work, found your fix, tried it, but got allways this error: DISM 0x800f082f

I did try again a lot of things but could not remove the package.

After a long time searching I found this webside:

http://www.varidan.com.au/how-to-fix-the-dreaded-windows-error-0x800f082f/

with the hint to change this key in the registry

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending]

So, after changing the registry key : "Exclusive" from 4 to 0, the uninstall worked and the system is up and running again.

I did not try any updates yet but will wait some days.

So, if anybody is having the same error 0x800f082f while trying to revert maybay this helps

ade_Nob

needless to say, that I am very angry that things like this happen out of the blue because of Microsoft!

Hi Abe,

Thank You very much, I will add this to my NOTESl!!!!

There is no DOUBT Microsoft has allot to answer for, there are allot of angry people around these parts including me!

Best Regard,

Crysta
Was this answer helpful?

0 comments No comments