Intel halts microcode patch development for 230+ CPUs

[HEXUS]

Updates official guidance with these 'stopped' status security flawed processors.

Read more.

[Sunderas]

Intel at its best.

"Oh, these are old so we do not even care... Keep on buying the newer ones and you'll be completely protected... Maybe..."

As Brian Fantana put it: "They have done studies you know? 60% of the time it works every time".

[kingpotnoodle]

Those are some pretty old CPUs, there aren't going to be many still running in systems that are relevant to attack with Spectre/Meltdown. Given that they are already so old how many of the remaining users are going to want the slowdown effect of the fixes, even assuming the fix can be applied.

[Fury559]

I'm upgrading in a fortnight to a 1700x from 3570k, I was waiting for Icelake with 8c/16t but Intel not fixing old mistakes fast makes me want to say screw them with bad TIM and support, maybe I'll go back to Intel in the future.

[Kanoe]

As per usual though, it's nice that Intel has gone back over CPUs that are 9 years + old but the issue is the mobo manufactures. How many of these microcode patches are actually going to make it to bios updates for older platforms?

Intel has fixed the microcode for my CPUs but there is zero intention from ASUS to release a BIOS update with it in for my Z9 series motherboard. The series is not even marked as a TBD on their list.

[ETR316]

Wolfdale Xeon, Yorkfield? who here is still using these? and do not bother telling me lots of people or companies are in their servers, I am aware, I dont need education. all i am asking is for honesty, because i am curious, who here is still using 10 year old hardware? thanks

[Corky34]

You could always modify the BIOS file yourself, there's quiet a few guides out there if you're brave enough.

[ik9000]

As per usual though, it's nice that Intel has gone back over CPUs that are 9 years + old but the issue is the mobo manufactures. How many of these microcode patches are actually going to make it to bios updates for older platforms?

Intel has fixed the microcode for my CPUs but there is zero intention from ASUS to release a BIOS update with it in for my Z9 series motherboard. The series is not even marked as a TBD on their list.

I was raising this yesterday when it was fresh news and someone helpfully pointed out to me that the microcode can be applied by the OS during startup, and MS does appear to be doing this, so while not as good as a BIOS update from the MOBO manufacturer, it is not leaving you up the creek. Z9 series - what's that, Ivy Bridge? Hasn't that already had its patch released?

[ik9000]

Wolfdale Xeon, Yorkfield? who here is still using these? and do not bother telling me lots of people or companies are in their servers, I am aware, I dont need education. all i am asking is for honesty, because i am curious, who here is still using 10 year old hardware? thanks

I'm still using Lynnfield/Clarkdale on win7, an old core2duo Dell and even a P4 s478 - though the latter two XP machines rarely see the internet so not as fussed about those. Very relieved Lynnfield got a patch.

[Tabbykatze]

You could always modify the BIOS file yourself, there's quiet a few guides out there if you're brave enough.

I do hope you're kidding...

[Kanoe]

I was raising this yesterday when it was fresh news and someone helpfully pointed out to me that the microcode can be applied by the OS during startup, and MS does appear to be doing this, so while not as good as a BIOS update from the MOBO manufacturer, it is not leaving you up the creek. Z9 series - what's that, Ivy Bridge? Hasn't that already had its patch released?

That's good to know, now got to wait for M$ to release a patch and hope they do a version that supports pre Fall Update (1709) versions of Win 10 cause for whatever reason I just cannot get the Fall Update to work on my PC.

[Corky34]

I do hope you're kidding...

Why would i be kidding, this is a technology forum isn't it? Extracting a BIOS file, replacing one or more files, and re-packaging them isn't much different than working with any other compressed file format, the hardest part is checking compatibility. (Having said that it's not something I'd recommend to someone whose not familiar with the CLI, backing up and recovering BIOS'.

[Iota]

someone helpfully pointed out to me that the microcode can be applied by the OS during startup, and MS does appear to be doing this, so while not as good as a BIOS update from the MOBO manufacturer, it is not leaving you up the creek.

Sadly it hasn't occurred for Sandy Bridge or other systems yet, and it doesn't look like Gigabyte are going to produce a new BIOS for my old (but still quite good) motherboard. Guess we'll have to wait and see, but looking at the support occurring it's likely I'll go with ASUS as my next motherboard, regardless of Intel or AMD.

[Tabbykatze]

Why would i be kidding, this is a technology forum isn't it? Extracting a BIOS file, replacing one or more files, and re-packaging them isn't much different than working with any other compressed file format, the hardest part is checking compatibility. (Having said that it's not something I'd recommend to someone whose not familiar with the CLI, backing up and recovering BIOS'.

This is a technical forum but this is only a minor subset of the greater user base. But saying "why don't you just modify the BIOS yourself, there's loads of guides" on a technical forum is like someone on a motoring forum saying "it's fine, why don't you just upgrade the spark plugs yourself, there's loads of guides".

Plus, validating Intel just deciding to drop the development of these microcode fixes to spectre-2 on their older platforms where there is still a reasonably large user base still on them and 'they should do it themselves' is a bit naff. Sure they're out of support but it's Intels responsibility to fix their problem.

[ik9000]

This is a technical forum but this is only a minor subset of the greater user base. But saying "why don't you just modify the BIOS yourself, there's loads of guides" on a technical forum is like someone on a motoring forum saying "it's fine, why don't you just upgrade the spark plugs yourself, there's loads of guides".

Plus, validating Intel just deciding to drop the development of these microcode fixes to spectre-2 on their older platforms where there is still a reasonably large user base still on them and 'they should do it themselves' is a bit naff. Sure they're out of support but it's Intels responsibility to fix their problem.

Not sure if I've misunderstood but I read their post differently - ie saying that applying the microcode from intel into the BIOS is doable as a DIY (albeit complicated - and it does seem a bit complicated, though not totally impossible, SFAIK from when I've been looking into it) rather than develop your own microcode fix which would be crazy, and less like "upgrade the spark plugs", and more "reprogram your engine management unit with your own custom firmware".

[ik9000]

Sadly it hasn't occurred for Sandy Bridge or other systems yet, and it doesn't look like Gigabyte are going to produce a new BIOS for my old (but still quite good) motherboard. Guess we'll have to wait and see, but looking at the support occurring it's likely I'll go with ASUS as my next motherboard, regardless of Intel or AMD.

I have the same problem with ASUS, and their tech support is renowned as being worse than Gigabyte's. Plus they misadvertised the capability of my motherboard and duped me into buying something that doesn't meet the spec I bought it for. Cunning little blighters. So my next mobo will NOT be Asus if i can help it.