Windows Client Guidance against speculative execution vulnerabilities

what is that tool you all use is it from intel??

Hi,

IronZorg89 said:

Has anybody found or heard anything yet for Intel?. I have an HP Envy 700-329 with CPU: Intel Core i7 4770 @ 3.40GHz. So far, when I check the Intel's site for either a BIOS/UEFI firmware update or the Display Adapter driver update (NVIDIA GeForce GT 635) , there is nothing past December 2017. Last time I checked was yesterday afternoon.

HP is supposed to make an update available for you, not Intel.

Cheers,

Tonyb said:

what is that tool you all use is it from intel??

It's linked here:

Windows Client Guidance against speculative execution vulnerabilities - Page 18 - Windows 10 Forums

fdegrove said:

Hi,



HP is supposed to make an update available for you, not Intel.

Cheers,

Thanks for clarifying on the matter. Maybe I misspoke, but here is the site I usually check for any available update:

https://support.hp.com/ca-en/document/c00007682

Hi,

IronZorg89 said:

Thanks for clarifying on the matter. Maybe I misspoke, but here is the site I usually check for any available update:

https://support.hp.com/ca-en/document/c00007682

That's it. It may take them a while as a machine with a Haswell cpu is already out of their zone of direct interest commercially spoken. I happen to have a Fujitsu machine (amongst others) with the exact same cpu as you do and no more love from its maker either.

That said, I don't worry too much about it. If someone decides to hack it then so be it, nothing of interest there just the OS. Anything else is on external drives.
Just for info, I had it running on a 4790K at one point and it's still a very fast machine compared to machines running I7 6700 and even I7 7700K. It's a keeper.

Cheers,

IronZorg89 said:

Has anybody found or heard anything yet for Intel?. I have an HP Envy 700-329 with CPU: Intel Core i7 4770 @ 3.40GHz. So far, when I check the Intel's site for either a BIOS/UEFI firmware update or the Display Adapter driver update (NVIDIA GeForce GT 635) , there is nothing past December 2017. Last time I checked was yesterday afternoon.

I have a HP Envy 700-030 with the same processor and a NVIDIA GeForce GTX645 graphics chip. At the beginning of this thread is a list of manufacturer websites with info about BIOS updates for their systems. When I checked HP's site when this was first posted, it indicated that there would be a BIOS update for the 700-xxx series coming in late February, but the ID for the BIOS was not the same as I currently have. Now that entry is gone. So I don't know what is up. We may be SOL.

JohnD

Hey JohnD,
I"m not sure what's up with HP, myself. I've got an HP Envy 17 m7-k010 (i7 4710HQ) and it was listed on HP's site, but the link to the updated bios pointed to the wrong SPxxxx. Now it's been removed from the list and according to HP I'm not vulnerable, despite every tool I run saying I am.

johnpd said:

I have a HP Envy 700-030 with the same processor and a NVIDIA GeForce GTX645 graphics chip. At the beginning of this thread is a list of manufacturer websites with info about BIOS updates for their systems. When I checked HP's site when this was first posted, it indicated that there would be a BIOS update for the 700-xxx series coming in late February, but the ID for the BIOS was not the same as I currently have. Now that entry is gone. So I don't know what is up. We may be SOL.

JohnD

The info you provided is really welcome. To tell you the truth, I was not expecting an update anytime soon. I suppose this type of problem with Spectre & Meltdown being able to cause these Speculative Execution Side Channel attacks can take a while to figure out how to fix it. We are talking about a flaw in the architecture of all CPUs. My only concern is that they (manufacturers) don't come out with an update that can cause more harm than good. Let them take their time..:)

i my self am patiently waiting on MSI they assure me a fix is coming but now ETA

Eagle51 said:

Now it's been removed from the list and according to HP I'm not vulnerable, despite every tool I run saying I am.

:)