Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,099 (0.45/day)
https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver#instructions
Even if the mb manufactures doesn't bother to update the microcode and microsoft doesn't bother to update the microcode loaded by windows you can still use a newer microcode in windows following the stuff in the link above, but we still need Intel to release a microcode update (the latest https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File is from 11/17/2017).
Keep in mind that if you decide to use the method described in the link above you do it on your own risk.
(I saw no problems on my Haswell cpu while using the method described in the link above to update the microcode, but well this is just my case.)
Note 1 : On boot the bios will load the old microcode, the stuff from the above link is basicaly a driver that will load a newer microcode (as long as it's available) in Windows (it has to be loaded every time Windows starts because it doesn't changes the microcode in your bios).
Note 2: From what I tested with this stuff I know it also works with AMD k10 cpus but it doesn't work with AMD k8 cpu (similar with linux, didn't bothered to read the amd k8 family cpu errata, maybe the k8 microcode update procedure is bugged or well there is no such procedure to begin with).
In Linux you can update the cpu microcode from Drivers Manager (or whatever the name for this things is in your distro). It's actually easier in Linux.
Don't even try it. VMware CPU Microcode Updater can fry your hardware.