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

ddelo said:

No way....0xc6 supersedes 0xb4.
It's what I mentioned before. The list in post 1 is the Microsoft implemented microcode versions and not necessarily the most recent ones according to intel's bulletin!

And if you want me to make it more complicated.
My Whiskey Lake U - 8th Generation Intel® Core™ Processors i7 8565U (806EC), according to Microsoft's list should be 0xB4, according to intel SA0277 should be 0xC6, but since February I have 0xCA, which was obtained by a BIOS/UEFI update provided by hp (my laptop's manufacturer)!!!!!!!

Does it make any sense...? Of course not!

Now to answer your question, where do you get 0xc6...? Only via a BIOS update from your manufacturer, unless you're the adventurous type and you can download the actual generic file from intel's Github and apply it yourself..... NOT Recommended.

So to make a long story short....don't get crazy with these vulnerabilities and the microcode updates mitigating them. Us, the "Average Joes", we're not the targets of these vulnerabilities. Major Corporations, Financial Institutions, Government Agencies and the Armed Forces, are most likely to worry!!! Not us.
That's just my humble opinion.

Good advice haha. Compiling ones own management engine firmware flash can be difficult enough to understand. I dont even want to consider updating my own microcode via flash haha. Plus Im happy with my BIOS so unless there is absolute reason to do so, I upgrade ME Firmware manually, and then rely on the microsoft updates to provide "latest" intel microcode.

meebers said:

I must be lost. I have a AMD 8 core FX-8350 AM3 and KB4497165 just installed on mine via WU

This installed today on my Ryzen 2700X system...

- - - Updated - - -

Josey Wales said:

Should not MS know what is in our UEFI???Why would MS update a Rysen CPU?

I'm wondering this too...

It is installed globally but it will used only by the affected cpus.

Sprenon said:

This installed today on my Ryzen 2700X system...

- - - Updated - - -



I'm wondering this too...

It does know. there are two ways of loading microcode. One is present and persistent across reboots via the BIOS. When you flash the BIOS it may contain newer microcode and that is basically what you have going forward. The other method is via Windows update. At startup Windows sees what version is present in the bios and also sees what version it has saved in the actual windows dll (I believe). if the windows version is newer than the BIOS it loads that one at startup. That's all it is

Guitarmageddon said:

. At startup Windows sees what version is present in the bios and also sees what version it has saved in the actual windows dll (I believe). if the windows version is newer than the BIOS it loads that one at startup. That's all it is

The only thing that I still don't understand is that if windows is capable of finding out that your bios is already patched or have a newer version, why would it simply not propose and install the patch in the first place instead of installing it and then choose at startup to use the one in bios!!

Polo6RGTI said:

Mitigations for Jump Conditional Code Erratum.pdf

Benchmarks Of JCC Erratum: A New Intel CPU Bug With Performance Implications On Skylake Through Cascade Lake - Phoronix

I had to do a system restore last night, just on the desktop the mouse was really laggy and even more so when opening a folder. The restore fixed it and I noticed all my drivers had been changed (and the restore rolled them back). Now I see a KB4497165 ready to install in windows update. Is this what totally screwed my PC? I was ready to reinstall!

I'm using a AMD 3900x though.