Inaccessible Boot Device error in Windows 10

It's minor widespread, not major widespread is the problem.

It's a wonder why we haven't had one official response to resolve the main issue.  Agreed Crysta, it will continue.  Eventually, they won't be able to hide forever.  Especially on an issue this wide spread.

Showster

hehehe I know it is NOT funny, BUT I never expect OFFICIAL RESPONSES! So if they come on occasion I might be presently surprised. Most of the time what they have to say no matter which Corp it is, is simply useless.....

We bought these balls of Bandaids and Plaster Casts one way or another, now we must make the best of it. For years now, I have advocated that each user must become their OWN IT/Network IT/Admin/InfoSec/DevOPS person for a PC/Workstation/Server farm(mine is more like a paddock under my TV) or it is going to cost you many more times than what one payed for the equipment in the first place. Some listen, Most do not. It has been that way since the early 70's for me on Main Frames. There is always some Reason/Some Obstetrical/Some Buffoonery OR mostly Some Blame Game so that they didn't have too. Then it was in an Engineering department, these people were professional, and it was no different then, then it has been these last couple of weeks on this thread.

I am not trying to point any figures, I just saying you and others are not unique and no different than people 45+ years ago and all the way through.....

Have a Great Evening, and Goodnight,

Best Regards,

Crysta

@Phantomofmobile

Can anyone try this update to see if it fixes the problem?

support.microsoft.com/en-us/help/4078130/update-to-disable-mitigation-

Based on what I read, Intel acknowledged a microcode issue and recommended everyone stop deploying the fix. I am assuming the fix they are referring to was contained in the kb4056892. So the linked kb update disables the problematic portion of the update. I don't have a machine to test it on currently. It looks like a temporary fix until they can fix the issue without crashing broadwell and haswell processors.

Download link:https://www.catalog.update.microsoft.com/Search.aspx?q=KB4078130

Can anyone try this update to see if it fixes the problem?

support.microsoft.com/en-us/help/4078130/update-to-disable-mitigation-

Based on what I read, Intel acknowledged a microcode issue and recommended everyone stop deploying the fix. I am assuming the fix they are referring to was contained in the kb4056892. So the linked kb update disables the problematic portion of the update. I don't have a machine to test it on currently. It looks like a temporary fix until they can fix the issue without crashing broadwell and haswell processors.

Download link:https://www.catalog.update.microsoft.com/Search.aspx?q=KB4078130

Bobby,

This is what I wrote for the LIST, it still hasn't been Posted yet, that I have seen.......

@Phantomofmobile on Twitter.

Hi Folks,

I am going to endeavor to make this as SIMPLISTIC as I can for those people whom don't know Boolean Algebra and Bit Maps or for those who need a refresher.

Those of you whom know this COLD, Please bare with those who don't. If you have a better way to explain this, please feel free.

Maybe we can fend off some confusion early on here. My partitions are fully patched with NO MICROCODEand no issues. I am going to describe behavior on W 8.1 but I would NOT expect any difference on any other W OS.

KB4078130in my experience, does very little. For those Folks who would just as soon not go into the Registry, it turns off  "Spectre Variant 2" or in official speak: "disable Variant 2: CVE 2017-5715"Branch Target Injection", by setting bit 1 in the Registry Key Name 'FeatureSettingsOverride' to the Value of "1" or in 'DWORD' speak "0x00000001". YourMileageMayVary if you have "Microcode" but I don't see that as a possibility. I DID NOT get any indication the the .exe Ran, was Running, or even Completed! I had to look in the Registry itself, Knowing how I had left it SET, to see the results. I also Ran it in CMDLine, same thing, nothing indicated except NO ERROR was Thrown!

In an earlier Email, that Susan kindly forwarded, Thank You, Susan, I demonstrated the very simple bit Map that we are talking about.

An excerpt from KB4073119:

​"​

Windows Client Guidance for IT Pros to protect against speculative execution side-channel vulnerabilities

Last Updated: Jan 26, 2018

To disable Variant 2: CVE 2017-5715"Branch Target Injection":

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 1 /f

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 1 /f

Note disabling and enabling the Variant 2 via registry setting changes will require a reboot and administrative rights.

​"​

One needs to Restart on every change for it to take affect. It is brutal if one is testing to see the different RESULTS!

(Yes I was in CRAZY Restart Hell for over 2 hours, So you don't have too, unless you like "CRAZY Restart Hell" or are a Beta Tester like me)

From the above we are seeing in the first "Reg Add" what KB4078130 is doing but in the second Reg Add what it is NOT. It leaves****'FeatureSettingsOverrid'at "3" or in DWORD speack "0x00000003". As we see though, 'FeatureSettingsOverrideMask' bit 2 in both 'FeatureSettingsOverride' and'FeatureSettingsOverrideMa', one can MASK OFF bit 2 so that it is not affected by adjustments and changes to the bit Map for Spectre Variant 2  by making it "0". Thus for 'FeatureSettingsOverrideMa' the 'DWORD' is "0x00000001".

As far as I understand this "Spectre Variant 1" is active in the Patches from earlier in January, it is strictly Kernel Software and is "ON" all of the time. It can not be turned off.

For 'FeatureSettingsOverride' "1" is OFF.

For****'FeatureSettingsOverrideMa' "1" is Active.

Decimal: 0 (0x00000000) |  Binary Bits: 00

Decimal: 1 (0x00000001) |  Binary Bits: 01

Decimal: 2 (0x00000002) |  Binary Bits: 10

Decimal: 3 (0x00000003) |  Binary Bits: 11

Spectre is in Bit Position '1', Meltdown is in Bit Position '2'  Bits are counted FROM THE RIGHT.

I hope this clarifies some of this confusing "Mumbo Jumbo" of the Boolean Binary World, for some of you and gives those whom know all of this, an example that you can show to those who don't.

It is my guess that most will leave 'FeatureSettingsOverride' on "3", "0x00000003" for the DWORD and just vary 'FeatureSettingsOverride'

I am not advocating either way. Just keep in mind though, we are in a period of immense FLUX, and it could be that way for years?????

Hope this helps some of you,

​Best Regards,

Crysta​

Bobby,

As specified in the KB's, they are for IT Admins/DevOPS, which if I am not mistaken you're one. Others here may not be.

I do not see any indication that it does anymore that what I specified above.

Best Regards,

Crysta