KB4100347 Intel microcode updates for Windows 10 v1803 - January 8 Win Update

Hi,

IronZorg89 said:

If I may say, this is becoming a real joke. The reason is while Intel is trying to mitigate old speculative side-channels attacks, new ones are being discovered all the time. The following is just an example:

https://www.zdnet.com/article/spectr...10237760721960

I think one would be better off waiting until there are new PCs with flawless microprocessors (say Intel i8..) and buy a new one.

Totally agree. Intel has been comprimising security for ages just to stay ahead of the competition.
I'd love to see secure cpus that deliver power at low energy cost for a change. Having been part of this industry I know it can be done.

Cheers,

fdegrove said:

Hi,



Totally agree. Intel has been comprimising security for ages just to stay ahead of the competition.
I'd love to see secure cpus that deliver power at low energy cost for a change. Having been part of this industry I know it can be done.

Cheers,

Good reasoning..!. I am glad I am not the only one in the boat to see it that way.

Ground Sloth said:

As far as I can tell, the only thing that was added were microcode updates for Xeon Phi processors. These are not the new microcode updates that were released by Intel this month.

bummer. I guess the updated microcode for Arrandale & Clarkdale (1st gen) Intel core CPUs have not been implemented in KB4100347 yet.

erpster4 said:

bummer. I guess the updated microcode for Arrandale & Clarkdale (1st gen) Intel core CPUs have not been implemented in KB4100347 yet.

Correct. They are glaring omissions by Microsoft and I can only assume that they feel the performance impact is so great that they don't want to be associated with the 'patch' that cripples a users CPU.

Only problem is the OEMs are well past caring about that customer base as the equipment is probably 7-8 years old.

I don't have the tools to modify equipment of that age as they're not BIOSes that have tools to modify them readily.

winactive said:

Correct. They are glaring omissions by Microsoft and I can only assume that they feel the performance impact is so great that they don't want to be associated with the 'patch' that cripples a users CPU.

Only problem is the OEMs are well past caring about that customer base as the equipment is probably 7-8 years old.

I don't have the tools to modify equipment of that age as they're not BIOSes that have tools to modify them readily.

Intel said that new microcode updates were released for some first-generation Core processors, but the updates don't actually seem to exist. The microcode data file from 4/25 didn't have new microcode updates for first-generation Core processors, and the data file from 7/3 doesn't seem to either.

Ground Sloth said:

Intel said that new microcode updates were released for some first-generation Core processors, but the updates don't actually seem to exist. The microcode data file from 4/25 didn't have new microcode updates for first-generation Core processors, and the data file from 7/3 doesn't seem to either.

Like I said, omission by Microsoft. The July 13th MCUs are not in the July 24th revised update, the Xeon Phi CPUs that are added aren't in the latest Intel release information, which is odd. Unless the public list is different from the partner list.

winactive said:

Like I said, omission by Microsoft. The July 13th MCUs are not in the July 24th revised update, the Xeon Phi CPUs that are added aren't in the latest Intel release information, which is odd. Unless the public list is different from the partner list.

It's not an omission by Microsoft. Intel puts all the most recent microcode updates into a single data file (which Microsoft then uses). Intel said it released new microcode updates for some first-generation Core processors (first in April and then again this month), but for whatever reason they appear not to be putting the new updates in the data file.

Ground Sloth said:

It's not an omission by Microsoft. Intel puts all the most recent microcode updates into a single data file (which Microsoft then uses). Intel said it released new microcode updates for some first-generation Core processors (first in April and then again this month), but for whatever reason they appear not to be putting the new updates in the data file.

The patch IS from Microsoft. Intel HAVE created the MCUs.

They are updated for Linux (July 3rd). Intel do not do the patch integration, that would be crazy. They have updated the patch and the Xeon Phi's are NOT in the Intel documentation, but they ARE in the MICROSOFT patch! The patch was issued on July 10th!

The Linux data file is not a document (OR for use on a Windows PC 'as is'), the Microcode Revision Guidance document is.