This info is applicable to Windows OS's running on Intel or AMD CPUs.
This Fling is a Windows driver that can be used to update the microcode on a computer system’s central processor(s) (“CPU”). This type of update is most commonly performed by a system’s firmware (“BIOS”). However, if a newer BIOS cannot be obtained from a system vendor then this driver can be a potential substitute.
VMware CPU Microcode Update Driver: https://labs.vmware....e-update-driver
Linux Processor Microcode Data File Version: 20180108 (Latest) Date: 1/8/2018: https://downloadcent...e-Data-File?v=t
EDIT: Version 20180108 has been removed from download page, and replaced with Version: 20171117 (Latest) Date: 11/17/2017.
I am on a i3 3225 Win7x64 PC, followed instruction on page https://labs.vmware....er#instructions and was able to confirm on "Event Viewer" "Successfully updated microcode on one or more CPUs".
Unfortunatelly after running SpecuCheck I got this:
NOTE: Wasn't able to run PowerShell script on my win7x64 so that's why I ran SpecuCheck. Of course KB4056897 was installed on my system before doing all this.
VMware program did work (as I confirmed), but in file "microcode-20180108.tgz" Intel Microcode Data File for my i3 3225 was not patched for this vulnerabilities. So this means Intel is launching this file "microcode-20180108.tgz" to public and not all Microcode Data have been updated to fix this vulnerabilities and no mention to this on download page.
INTEL HAS LOST ALL CREDIBILITY FOR ME.
Somebody with a newer Processor should check this in order to verify if Intel has really fixed this on recent Processors.