KB4497165 Intel microcode updates for Windows 10 1903 and 1909 Sept. 1 Win Update

Josey Wales · 20 May 2020

erpster4 said:

WU metadata 5/19/2020 change only for KB4497165, Brink.
while KB4497165 V4 from MUC has new dates, it still is the same msu v4 package that I downloaded back in end of Jan 2020.

use wushowhide.diagcab to hide KB4497165 if you really don't need it, Josey.

again, WU metadata detection change for KB4497165

It does not seem to be hurting anything so I will leave it be.

Josey Wales · 20 May 2020

pietcorus2 said:

" it still is the same msu v4 package "...............so, this microcode-update wont install , coz its already installed on January 2020 !

I did not have this PC in January so that is probably why it installed.

MUser · 20 May 2020

Ground Sloth said:

I don't know why Windows Update doesn't bother to check if the update is needed or even applicable.

But if the update is not applicable, then Windows won't load the microcode update on startup. And Windows won't load a microcode update on startup if it's older than what the BIOS/UEFI already loaded.

The update only installs the new Intel microcode file, the file is only used at boot time if you have an Intel CPU and your BIOS has an out of date microcode revision.

blueskyler · 20 May 2020

hi, how can i check the microcode revision installed on bios/uefi ?

MUser · 20 May 2020

blueskyler said:

hi, how can i check the microcode revision installed on bios/uefi ?

Restart and enter the BIOS/UEFI screen, it should be on the initial page somewhere?

Or use this with PowerShell View CPU microcode revision from powershell | xf.is blog

ddelo · 20 May 2020

blueskyler said:

hi, how can i check the microcode revision installed on bios/uefi ?

PowerShell script for CPU information, incl. CPUID

EdKiefer · 20 May 2020

blueskyler said:

hi, how can i check the microcode revision installed on bios/uefi ?

you can check your bios but that is mcode the bios comes with, this update adds on top if needed, so like for me the newest bios is back in 2014 way before all the hacks were found. One way to check is HWinfo64 it lists it..

Ddelo lists a better way, no app needed.

- - - Updated - - -

Josey Wales said:

I did not have this PC in January so that is probably why it installed.

As I posted above I think MS is just forcing this update, I had mcode from like 6-9 months ago updated to 21 and after this update its still 21 so nothing changed.

ddelo · 20 May 2020

Just to clarify a few things:

The list in the 1st post includes the microcode revisions implemented by Microsoft. They are not necessarily the most updated ones, as specified by intel.

The Microsoft microcode is stored in the files Mcupdate_genuineintel.dll and
mcupdate_AuthenticAMD.dll for Intel and AMD CPUs respectively.

If your UEFI has the same or higher microcode revision, with one Microsoft provides in this update (as seen in the 1st post), the update will either not offered or if it's offered and installed will not be implemented at PC startup, since the one in UEFI will prevail.

When the PC boots, it first checks and loads the UEFI microcode. When the OS (Windows 10, in our case) takes over, it checks to see if the Microsoft implemented microcode is newer than the UEFI one and if it is it loads the newer version. If not, it skips it and continues the boot process.

Ground Sloth · 20 May 2020

MUser said:

The update only installs the new Intel microcode file, the file is only used at boot time if you have an Intel CPU and your BIOS has an out of date microcode revision.

I know.

Tonyb · 20 May 2020

i just got this on my new amd ryzen machine a laptop what gives ?