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

I just updated a Haswell PC having an i5-4670K CPU to v1909. This was reported as having microcode revision 0x25 (loaded by Microsoft Windows 10 Pro). The latest version according to this thread is 0x27. I can't find a similar update for v1909 so I just ran this update KB4497165 which installed fine in v1909 and gave me the latest microcode version 0x27.

Steve C said:

I just updated a Haswell PC having an i5-4670K CPU to v1909. This was reported as having microcode revision 0x25 (loaded by Microsoft Windows 10 Pro). The latest version according to this thread is 0x27. I can't find a similar update for v1909 so I just ran this update KB4497165 which installed fine in v1909 and gave me the latest microcode version 0x27.

The microcode file mcupdate_GenuineIntel.dll in Windows 1909 version is 10.0.18362.1 which is 1903

You can safely install the microcode for 1903 on 1909 and you will update mcupdate_GenuineIntel.dll to version 10.0.18362.291

JenyJ said:

The microcode file mcupdate_GenuineIntel.dll in Windows 1909 version is 10.0.18362.1 which is 1903

You can safely install the microcode for 1903 on 1909 and you will update mcupdate_GenuineIntel.dll to version 10.0.18362.291

I wonder why MS doesn't install the latest microcode when they already have the file required?

ddelo said:

Maybe because, this is a 4th Gen. CPU and since the most recent one is Gen. 10....they probably consider it as their last priority!

Why not simply supply v1909 with file mcupdate_GenuineIntel.dll version 10.0.18362.291 already tested by MS?

I did a BIOS/UEFI update yesterday, and the CPU microcode was updated (among other things). I think the microcode update addresses the TSX vulnerability that was disclosed a couple months ago.

BIOS updates still scare the heck out of me. I always think I'm going to brick my computer. I came close once.

Ground Sloth said:

I did a BIOS/UEFI update yesterday, and the CPU microcode was updated (among other things). I think the microcode update addresses the TSX vulnerability that was disclosed a couple months ago.

BIOS updates still scare the heck out of me. I always think I'm going to brick my computer. I came close once.

Nowadays, it is very difficult to brick one's PC when it runs on UEFI and not on legacy BIOS:

Modern PCs no longer use a BIOS, but instead start up using the Unified Extensible Firmware Interface (UEFI). On UEFI-based PCs, the portion of firmware that's hosted on the motherboard is relatively small and simple; its job is to find the EFI partition and load the UEFI code stored there, then find the boot loader.

Beginning with Windows 8 in 2012, Windows uses an update mechanism that delivers update packages to a known system location; the UEFI firmware then installs the update package on its own, after a restart. This architecture makes UEFI updates far more reliable than those old BIOS updates, with error-checking mechanisms that can roll back unsuccessful changes automatically.

5 popular Windows 10 settings tweaks you need to quit using | ZDNet

IronZorg89 said:

Nowadays, it is very difficult to brick one's PC when it runs on UEFI and not on legacy BIOS:


5 popular Windows 10 settings tweaks you need to quit using | ZDNet

The Unified Extensible Firmware Interface definitely makes it more difficult, but my experience a little over a year ago gives pause.

After a bad update, one of my computers (which uses UEFI) wouldn't POST and would just keep cycling on and off. I eventually somehow got it to POST.

Ground Sloth said:

The Unified Extensible Firmware Interface definitely makes it more difficult, but my experience a little over a year ago gives pause.

But at least, the UEFI has kind of a failsafe mechanism to prevent your machine from bricking as explained in my previous post #147.

BTW, what was the firmware you updated with regard to your CPUID (Mine is 306C3 for an HP Envy desktop). I have checked the Specs in your profile and there is barely enough info.