2017 Hardware Thread [2]

fdegrove · 11 Nov 2017

Hi,

This is a firmware update as I understand it :

Intel has identified security vulnerabilities that could potentially place impacted platforms at risk.
Intel has validated and released a ME and software updates that address the identified security vulnerabilities.
Thus, we strongly suggest you to update your ME to the latest Version via using MEUpdateTool as attached.
*We suggest you update ME Driver to the latest Version 11.7.0.1040 simultaneously.

Release note:

Fix) Mitigated security vulnerability.
•(Fix) Failure to confirm remote configuration is enabled when running Intel(R) Common Services FW compliance test CS_040
•(Fix) Failure of Intel(R) ICC FW compliance test ICC_TST_02 at test step 4 with an error message "HECI CMD Status = 0x00000034 (NO_SUCH_TARGET_ID)".
•(Fix) FWUpdate will fail in case image includes Pre-update module
•(Fix) Playready DRM returns wrong value.
•(Fix) Failed to Get Record via CCT tool with INVALID_PARAMS
•(Fix) ICCWDT is not universal driver
•(Fix) Remove win7 support.

Updating ME drivers alone won't fix this vulnerability.

Asus also released a bios update for Z370 MBs that will incorporate a firmware updat for Intel ME.

Cheers,

OldMike65 · 11 Nov 2017

Cliff S said:

No need for 3rd party software, so does device manager:
Attachment 163388

Just easier to see in HWiNFO Cliff, explains it better too. BUT .....Looks like you got the Old Version

2017 Hardware Thread [2]-screenshot_56.png

Cliff S · 11 Nov 2017

OldMike65 said:

Just easier to see in HWiNFO Cliff, explains it better too. BUT .....Looks like you got the Old Version

Nope Mine was updated by MSI quite a while ago.
The ME is also by manufacturer and not just an intel generic.

OldMike65 · 11 Nov 2017

Cliff S said:

Nope Mine was updated by MSI quite a while ago.
The ME is also by manufacturer and not just an intel generic.

So was mine .....updated quite a while ago ....until this morning.
I might be teasing you....

Cliff S · 11 Nov 2017

But.....!
Of course I can never be sure...
it was THAT update(the fix I mean)

Notice this update number compared to my earlier screeny.
I bet it was Microsoft that fixed it.

OldMike65 · 11 Nov 2017

Cliff S said:

But.....!
Of course I can never be sure...
it was THAT update(the fix I mean)

Notice this update numbe.
I bet it was Microsoft that fixed it.

What MS has done to me sometimes Cliff is remove a newer driver, and replace it with a much older driver ....not all the time, but I've had to re-update some drivers after MS did.

:)

Cliff S · 11 Nov 2017

OldMike65 said:

What MS has done to me sometimes Cliff is remove a newer driver, and replace it with a much older driver ....not all the time, but I've had to re-update some drivers after MS did.

:)

The only time I get a driver update is when I actively go through all the drivers in Device Manager and manually search(I do that when I get bored, yes, I have no REAL life, I know

).