You are already using the software microcode, there will be no lag loading it from the file instead of the bios.
Don't worry, Linux always uses software microcode, and most likely you are using the Microsoft microcode, and it was not loading from the bios.
Again, there is no lag, and you are already using it, it is just an update for a file you are already using, for the sake of the security you should update.
Ok thanks. I think now the concept has absorbed into my thick skull haha. Understanding better. I get to reading some sites like win-raid which are a wealth of extremely detailed knowledge, and think that Im missing out on doing things "the right way" but in the end I just confuse myself. I was reading their posts about microcode flashing and got lost....
No worries, the microcode update has fixes for a lot of CVE if you read the Intel and Microsoft release notesCommon Vulnerabilities and Exposures - Wikipedia
you are welcome,
so I manually applied the update and seemed to take just fine. However when I run that powershell script to see my microcode version, its still saying
Running microcode revision : 0x0F (loaded by UEFI)
UEFI CPU microcode revision : 0x0F
But the Update release notes indicate:
Coffee Lake S (6+2) 8th Generation Intel® Core™ Processor Family Intel® Core™ Processor i7-8670, i7-8670T, i7-8700, i7-8700K, i7-8700T Intel® Core™ Processor i5-8400, i5-8400T, i5-8420, i5-8420T, i5-8500 , i5-8500T, i5-8550, i5-8600, i5-8600K, i5-8600T, i5-8650, i5-8650K 906EA 0x96
Am I missing something?
Wow thanks for the input. I havent opened xtu for a while but what do you know, there is the microcode update. I wonder why that powershell did not indicate. I was just using the one provided on another thread. Thanks for your help.
The XTU utility outputs the currently running microcode (the one you got from the KB4465065, which is 0x96).
One would assume that, at least Intel’s utility will report the currently installed microcode in the firmware. Instead you get the most updated one (from the KB4465065), which supersedes the one in the firmware. So the script "correctly" reports that the "UEFI CPU microcode revision” (a.k.a the one the firmware has), as 0x0F, since you didn’t update the firmware.
The question is why the script, reports that the Running microcode revision is still 0x0F.
It is highly unlike that the KB4465065 doesn’t update the value “Update Revision” in the Registry key HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0, which is where the script gets the microcode revision from.
My guess would be that, this has something to do with KB4465065, since other users have also reported strange results after applying this update.
It won't offer it. You have to download it from Microsoft Update Catalog and install it manually.
To get it look at the first post of this thread in the section "How to obtain and install the update"
New update V3 9/4 Microsoft Update Catalog Not sure if it has something to do with Intel Microprocessor Memory Mapping Vulnerability Advisory - April 9 - Windows 10 Forums
O wait, it says 9/4 but downloading the same old file ??? is that normal?
Quote
