Windows 10: Intel-SA-00086 (v1.1.169.0)

How to fixed this particular issue? Thanks.

:)

 

Don't install windows 10 on a Asus et2701i all in one computer. or maybe all computer with install errors, roll backs

This is getting far above my "pay grade". Unknown (to me) whether (SA-00075) is the same as the "Meltdown" and "Spectre" vulnerabilities. Note the date is 9/12/2017, which is earlier that all the talk about "Meltdown" and "Spectre". I had previously found
a test for "SA-00086" dated 26-Dec-2017, which was also negative. Is that for "Meltdown" and "Spectre" ?

MT

 

Windows 10 - Problem waking up from sleep mode

I guess my laptop is not getting version 11.7.0.1045 since Driver Update tells me I'm already at newest. Intel has security vulnerability (Intel-SA-00086) which my particular processor version doesn't have or my hardware has a different branch of IMEI software.

Does the version 11.7.0.1045 driver have a Power Management tab under Properties? If so uncheck the box to allow Windows 10 to put the driver to sleep.

There are many Windows sleep problems. This one was particular in that the machine would lockup when trying to wake, requiring a hard reset. On a laptop you could force sleep within a few minutes of waking or booting and sleep would often work - laptop
would sleep then wake normally. However, the failure mode was when the user idle signal was sent after a period of inactivity, the IMEI driver did something erroneous with that signal, laptop would enter sleep but never wake again. Unchecking that enable
driver sleep was a reasonably good workaround but quite frankly Intel needs to test their code better!

A lot of us have lost a lot of sleep debugging various sleep issues

 

To put it simply, you have to find an updated version of the Intel Management firmware that addresses this vulnerability. Because I have two Asrock motherboards that I've repaired for this, I can point you at the Asrock page where the downloads may be found: ASRock---Intel Firmware vulnerability INTEL-SA-00086. They also provide instructions on which download to choose based on your chipset, and instructions on how to apply it.
Enjoy and HTH,
--Ed--

 

Hi,
I personally wouldn't worry about it
You have a decent antivirus Malwarebytes premium
If you uninstalled IME in programs the Intel evaluation would spin like a top and never complete *Smile

 

@EdTittel My motherboad is ASRock H97 Pro4, which is not listed on the page.

@ThrashZone Yeah, I hope so. By default, my IMEI v11.6.0.1026 & now I've updated to v11.7.0.1057

 

If the motherboard isn't listed -- and I just re-read the page and indeed it and/or its chipsets are not mentioned -- then they do not have a patch for your Intel ME firmware. Although the tool says you're vulnerable, Asrock apparently does not offer a patch. That leaves two choices:
1. Practice safe computing and eternal vigilance to avoid exposure to attack.
2. Look for a patch source from someplace other than Asrock. I'd suggest asking around at sites like Win-RAID or look to other BIOS hackers to see if something is available. I see that, for example, MSI released a patch for this for H97 mobos based on an Intel release of the base patch to OEMs. If you dig deeply enough you may be able to come up with a workaround. That said, it could also brick your PC if something goes kerflooey.
Your call, but I vote for option 1.
HTH,
--Ed--

PS: here's a link to the MSI Post, in case you're interested: Intel ME Firmware updates for H97/Z97 Mate Motherboard

 

A little bird tells me that the ME firmware versions are released and signed by Intel so the binaries are exactly the same between OEMs. Intel also releases its own firmware update tool.

That said, there may be secure boot, BitLocker, and/or measured boot implications if you update the ME without going through the OEM's tool.

For a home desktop system I would not bother. The ME9 vulnerabilities are both in AMT, which no home user ever provisions. To actually enable AMT an attacker would have to have local execution privileges on your system, in which case you have bigger problems.

 

Yes, you are correct PolarNettles. REAL MEN (or real nerds, anyway) will hack their own BIOSes/UEFIs, using tools to slipstream the OEM updates from Intel directly into their own runtime environments.
--Ed--

 

Hi,
Any one with direct access wouldn't bother hacking a computer in place they would just take it and hack it elsewhere *Smile
This is overblown BS
Just disabling remote access kills at least one of the vulnerabilities
Use a standard user account pretty much mitigates a host of others.
I'm doing nothing to either of my systems
I'd get hit by a train in my living room before either of these exploits hit me *Biggrin

 

Thanks for your kind and friendly input, ThrashZone. Your thoughts and reflections are always welcome.
--Ed--

 

I ran the FWUpdate with 9.1.42.3002_5MB_PRD_RGN.bin.

Thanks guys. *Party

 

Dear Khanmein: Good work. Those who persevere, eventually succeed. Glad you got it worked out. Please share your final, working solution in your next post to this thread. Other readers will want to know how your fixed this. Thanks in advance for helping others out.
Best wishes,
--Ed--

 

@EdTittel Previously, I'm using Intel ME 9.1 1.5MB Firmware v9.1.37.1002 (Consumers) which caused vulnerable & the problem is solved by updating the Intel ME 9.1 5MB Firmware v9.1.43.3004 (Corporate).

Procedure;
1) Download Intel ME System Tools v9.1 r5 & Intel ME 9.1 5MB Firmware v9.1.43.3004 (Corporate)
2) Extracted both into a directory folder
3) Put "v9.1.43.3004_5MB_PRD_RGN.bin" into FWupdate\Local-Win64
4) Run CMD as administrator & used the cd command to change from the current directory to the directory that contains the file
5) E.g. E:\xxx\Intel ME System Tools v9.1 r5\FWupdate\Local-Win64>FWUpdLcl64 -f v9.1.43.3004_5MB_PRD_RGN.bin
6) After the update is completed, then reboot your PC.

For more information, please kindly read the link below.
Forum - Intel Management Engine: Drivers, Firmware System Tools
Credited to @plutomaniac & Win-Raid.

 

Again: good work! Thanks for sharing your solution, too.
--Ed--