Re:Meltdown and Spectre Linux kernel status
by newman314 on Saturday January 06, 2018 @02:50PM
(#16087068)
This appears to be my experience too. I'm checking a few VMs and they are showing as missing hw support.
Do note that Microsoft appears to have updated their doc in the last day or so. They are now saying that three registry settings need to be set (instead of 2 previously).
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization" /v MinVmVersionForCpuBasedMitigations /t REG_SZ /d "1.0" /f
Some quick Googling seems to indicate that Windows has the ability to update microcode.http://forum.notebookreview.com/threads/how-to-update-microc...
Maybe this will happen with a later update from Microsoft as I'm doubtful that BIOS updates will happen with at least one of my systems.
Re:Meltdown and Spectre Linux kernel status
by cyann on Monday January 08, 2018 @02:31PM
(#16099456)
MinVmVersionForCpuBasedMitigations is for VM/Hyper-V: https://docs.microsoft.com/en-us/virtualization/hyper-v-on-w...
Of all of my computers only one has been issued a BIOS update so far. I ran the PowerShell script before and after installing the BIOS. Installing the BIOS flipped the status of the fix for CVE-2017-5715 to on.
I also ran the free HwInfo utility that will show the microcode revision before and after installing the Windows update and before and after installing the BIOS. It only ever changed with the BIOS update.
I hope this changes and Windows does start updating CPU microcode. I also have a few older motherboard's that aren't likely to ever see a BIOS update again.