Inaccessible Boot Device error in Windows 10

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

I am receiving the error: DISM Failed with error code: 0x8000ffff

Any ideas?

Thanks for the assistance.

Hi,

I was in a similar situation (just with the exception that the 2

"UpperFilter" entries for {533c5b84-ec70-11d2-9505-00c04f79deaf} and

{71a27cdd-812a-11d0-bec7-08002be2092f} contained references to "VTrack"

for "Veritas System Recovery", and everything was running fine for

Windows 10 current branch (build 16299.299 aka 1709) and previews (up

to/including build 17046).

Beginning with Windows 10 preview build 17063 I was hurt then by the

GSOD/"inaccessible boot device".

In my case, I was able to solve that problem by injecting (via Windows

Recovery Envrionment) the (now obviously required ?) setting

"IoBlockLegacyFsFilters=0".

Unfortunately, that setting seems to be removed again when installing a

next Windows 10 preview build (leading to some GSOD again afterwards),

so at the moment I'm forced to remove the 2 "UpperFilter" references to

Veritas before any Windows 10 preview build update, and adding them

again (together with "IoBlockLegacyFsFilters"=0) afterwards ... not very

nice !

But even if this works for Veritas, it might not work for other

products, so I'd recommend to remove any "non-default" "UpperFilter"

references and test, if this solves the "inaccessible boot device"

situations for current/future Windows 10 preview builds.

And again ... this was the solution for my particular situation

("inaccessible boot device" after updating from Windows 10 preview build

17046 to build 17063 or 17074 when using "Veritas System Recovery"), but

we know of course there are many other things triggering that problem ...

On an older, up-to-date working Windows 10 Pro x32 system with Intel RST RAID 1 that never experienced this BSOD:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E967-E325-11CE-BFC1-08002BE10318}\UpperFilters

contains both partmgr and EPMVolFlt

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{533c5b84-ec70-11d2-9505-00c04f79deaf}\UpperFilters

There is no entry for this key, so it is empty by definition.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{71a27cdd-812a-11d0-bec7-08002be2092f}\UpperFilters

contains both volsnap and EPMVolFlt

EPMVolFlt is a filter installed with EaseUS Partition Manager and provided by Microsoft.

Booting again with RE, starting "regedit" and doing a "load hive" of

your PC's system registry (C:\Windows\System32\config\system), check

(in the loaded hive, of course) for any 'suspicious' entries in ...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E967-E325-11CE-BFC1-08002BE10318}\UpperFilters

... this (MULTI_SZ) entry (for class "DiskDrive") should contain (on some "fresh" installation) only "partmgr"

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{533c5b84-ec70-11d2-9505-00c04f79deaf}\UpperFilters

... this (MULTI_SZ) entry (for class "VolumeSnapshot") should (on some "fresh" installation) be empty

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{71a27cdd-812a-11d0-bec7-08002be2092f}\UpperFilters

... this (MULTI_SZ) entry (for class "Volume") should (on some "fresh" installation) contain only "volsnap"

In case your current settings don't contain the above mentioned

"default/fresh" values, write them down, and change them accordingly.

Good luck !