New
#650
Hi,
Up to 1709 that would do it but not yet for the latest April 2018 version (1803).Yes that's what I thought. I just mention it because I think some got good to go readings with it or I think I read that somewhere...
I find it quite strange how MS has released various KB's for older versions of W10 to resolve this issue to then release a new version that does not have a KB ready to corner this...
Cheers,
Hi,
I doubt any OEM will go back as far as Haswell CPUs but soon enough MS will issue a KB for the April version of W10.for the make and model of my PC HP Envy 700-329 CPUID: 306C3
Should you stick to 1709 then you should be fine if you installed KB4090007.
Cheers,
According to this KB4090007, my CPUID is in production. Doesn't that mean that I should be getting a BIOS/UEFI firmware update in the foreseeable future. My PC is not that old, you know. I bought it, as far as I remember, In June or July 2015.
"Should you stick to 1709 then you should be fine if you installed KB4090007." That's what I did in order to have the green light from InSpectre, but after the April 2018 feature Update, I got back to square One. I even tried to re-install the update from the Microsoft Update Catalog after this latest feature Update, and I got the error message saying that this update is not for your PC or something of that ilk.
Hi,
My point exactly. MS will release a KB for the 1803 April 2018 version of W10 soon."Should you stick to 1709 then you should be fine if you installed KB4090007." That's what I did in order to have the green light from InSpectre, but after the April 2018 feature Update, I got back to square One. I even tried to re-install the update from the Microsoft Update Catalog after this latest feature Update, and I got the error message saying that this update is not for your PC or something of that ilk.
MCU for Haswell is ready, it was included in KB409007, right? So all it takes is for MS to include it into a new KB that's compatible with the newest OS.According to this KB4090007, my CPUID is in production. Doesn't that mean that I should be getting a BIOS/UEFI firmware update in the foreseeable future. My PC is not that old, you know. I bought it, as far as I remember, In June or July 2015.
I have one PC with a Haswell CPU as well. It's still on Fujitsu's support list but I really doubt they care to issue another bios/uefi update. I used to work for this company when it was Siemens-Nixdorf, most other "Intel/MS companies" follow the same policy.
Cheers,
A great many thanks for the insight and all the clarification. It really helps me better understand. Patience is the name of the game. I have read somewhere in an article that when they won't issue a firmware update (BIOS/UEFI) for the CPU on one's mobo which is too old, it is because it is a "closed system" and therefore less likely to be vulnerable to Spectre & Meltdown.
Hi,
You're most welcome.I have read somewhere in an article that when they won't issue a firmware update (BIOS/UEFI) for the CPU on one's mobo which is too old, it is because it is a "closed system" and therefore less likely to be vulnerable to Spectre & Meltdown.
Well, what they're saying is that those systems were meant to be stand alones. Sure enough, when you're not connected to a network you're not going to be vulnerable to these kinds of attacks....
Guess they have to draw the line somewhere.
Cheers,
Why was the CPU microcode update patch for 1709 designed to work only in 1709? They'll probably release the patch next Tuesday. I'm glad I bought a new computer last week and now have the BIOS loading the microcode update.
Last edited by Ground Sloth; 13 May 2018 at 11:29.