![]()
Could somebody please kindly explain what is going on? I tried messing with FeatureSettingsOverride, setting it to 0 or 8 and rebooting the machine afterwards - nothing changes, InSpectre still reports the machine vulnerable to Meltdown. It is running Windows 10 1809, with manually installed KB4465065 microcode update. Before applying KB4465065, InSpectre was reporting the machine mitigated against Meltdown and vulnerable to Spectre. I want it protected against both.
-
Starlight5 Yes, I'm a cat. What else is there to say, really?
-
Starlight5 likes this.
-
Starlight5 Yes, I'm a cat. What else is there to say, really?
Code:KVAShadowRequired:False
I would really appreciate feedback from other users of similar machines - Atoms and Atom-derived Celerons and Pentiums, Surface 3 users in particular.Vasudev likes this. -
Starlight5 likes this.
-
Starlight5 Yes, I'm a cat. What else is there to say, really?
-
Starlight5 likes this.
-
Starlight5 Yes, I'm a cat. What else is there to say, really?
Vasudev likes this. -
Starlight5 likes this.
-
Starlight5 Yes, I'm a cat. What else is there to say, really?
-
Try a Linux LiveCD and check using SpecuCheck or meltdown spectre checker at github and if you find Linux is using KVAShadow thing then I suspect Windows did something.Starlight5 likes this. -
You have following setup in the registry which means Meltdown disabled & Spectre enabled without Retpoline patch:
"FeatureSettingsOverride"=dword:00000002
"FeatureSettingsOverrideMask"=dword:00000003
With Retpoline patch it becomes:
"FeatureSettingsOverride"=dword:00000 402
"FeatureSettingsOverrideMask"=dword:00000 403
So if you want to enable both with retpoline patch:
"FeatureSettingsOverride"=dword:00000400
"FeatureSettingsOverrideMask"=dword:00000403
If you want to enable both without retpoline patch:
"FeatureSettingsOverride"=dword:00000000
"FeatureSettingsOverrideMask"=dword:00000003
This is what i get with everything enabled:
"FeatureSettingsOverride"=dword:00000408
"FeatureSettingsOverrideMask"=dword:00000403
When i game, i disable everything to mitigate performance issues (I have a simple bat script to disable and enable).
(EDIT) PS. My CPU info is in my signature.Last edited: May 9, 2019Vasudev, Starlight5, Aroc and 1 other person like this. -
Starlight5 Yes, I'm a cat. What else is there to say, really?
Last edited: May 9, 2019 -
Source: https://support.microsoft.com/en-in...-of-get-speculationcontrolsettings-powershell
I think your version of "Get-SpeculationControlSettings" is outdated.Starlight5 and Vasudev like this. -
Starlight5 Yes, I'm a cat. What else is there to say, really?
I will rephrase my question then. Why is Celeron N3450 reporting KVAShadowRequired as False after applying updated Microcode? How can it become not vulnerable to Meltdown after mere firmware update, justifying disabling Meltdown OS protection? I couldn't find any article explaining the situation with these particular CPUs. Is it it really not vulnerable to Meltdown and thus safe to use, or did Intel/Microsoft disable protection because it would make these CPUs run prohibitively slow as a result, is the question that drives me mad. If there was some article explaining hows and whys, I wouldn't bother at all.
I like the machine, for what I typically use it for it performs quite well (otherwise it's a cheap pile of crap with fantastic display). But now I'd like to sometimes access my NAS with it, and herein lies the problem since it would greatly benefit from full access instead of couple read-only folders.Vasudev likes this. -
Starlight5 likes this.
Unable to enable Meltdown mitigation after installing updated Microcode
Discussion in 'Windows OS and Software' started by Starlight5, May 8, 2019.