New
#300
Ooops, I'm sorry about the last part. I didn't see that you had updated your post, regarding MDS enablement via registry!
With which, seems that we agree.....
Ooops, I'm sorry about the last part. I didn't see that you had updated your post, regarding MDS enablement via registry!
With which, seems that we agree.....
Not totally agree,
It is not clear if you enable mitigation for CVE-2018-3639, will keep MDS enabled,
Microsoft state:
To enable mitigations for Microarchitectural Data Sampling (CVE-2018-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130) along with Spectre (CVE-2017-5753 & CVE-2017-5715) and Meltdown (CVE-2017-5754) variants, including Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) as well as L1 Terminal Fault (L1TF) (CVE-2018-3615, CVE-2018-3620, and CVE-2018-3646) without disabling Hyper-Threading:
To be in the safe side, use the value 72, can't be sure unless the new Microcode released and tested,
OK... your opinion and I fully respect it.
To end this "misalignment" between us, please take a look at the first post of this thread:
Which is fully inline with the output of Speculation control:
Meaning that, adding the Registry entries "FeatureSettingsOverride" (0x048) and "FeatureSettingsOverrideMask" (0x003), is redundant as the CU KB4494441, has already enabled them, for MDS mitigation!
But as you said, it won't hurt if you also do it manually!
---End
Last edited by ddelo; 19 May 2019 at 05:32.
Check winver (win+r: winver). If you have the latest version of Windows (the update was installed and it's trying to install it again), hide the "duplicated" update with this: https://download.microsoft.com/downl...owhide.diagcab
Just an FYI that I got some guidance over at Wilders. I applied the KB4465065 standalone update. This upgraded me to the 0x2E microcode and with the already applied registry keys, I now have SSBD mitigated.
I'm not sure why my microcode was stuck at 0x2D prior to applying the update. The only fishy thing that occurred recently was a BSOD after an automatic Windows cumulative update (KB4494441, I believe). My PC also experienced a BSOD after I applied the KB4465065 standalone update. I ran both crashes through WhoCrashed. It identified the HAL as the culprit. Perhaps, the blue screens have something to do with the microcode updates not getting applied?
The only question that remains is whether to keep hyperthreading enabled or disabled! Google decided to disable it on all Chromebooks.