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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-16T11:36:45+00:00

    Not sure my issue has anything to do with Veritas, but in any case, how can this registry key be added if Windows can't be logged into?  You did this through command prompt?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-16T11:31:01+00:00

    Meanwhile, I was able to not only find the root cause (Veritas System

    Recovery causing a GSOD/"inaccessible bloot device"), but also a

    solution:

    Starting with 17063, Microsoft obviously changed the default behaviour

    i.r.t. "Legacy File Systems", causing Veritas' (or any other vendor's)

    file system filter driver (for Veritas: "vtrack") to NOT be started,

    raising system event 1205 ("Windows is configured to block legacy file

    system filters").

    As a consequence of ignoring this file system filter driver to be used,

    the GSOD/"inaccessible boot device" will be thrown.

    This can be solved (bypassed) by explicitely allowing "Legacy File

    System Filters" with below registry setting to be added :

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\I/O System]

    "IoBlockLegacyFsFilters"=dword:00000000

    Hope this helps.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-16T09:37:22+00:00

    I have seen a similar behaviour with Lenovo Yoga's that originally had Windows 8.1 but have since been updated to Windows 10.

    The solution in this instance was to download the latest BIOS from Lenovo and install it.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-16T08:27:02+00:00

    I have exactly the same issue.

    I'm quite certain this is due to a Windows 10 update on 14th Jan.

    I'm have a 5-6 year old Lsnovo ThinkPad, running Intel i5.

    I've tried all theh fixes mentioned, but none work.

    Not sute what to do now..

    I'm based in the UK

    Was this answer helpful?

    0 comments