ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Intel Management Engine Issue INTEL-SA-00086 Fix
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Intel Management Engine Issue INTEL-SA-00086 Fix
 Post Reply Post Reply Page  <1 10111213>
Author
Message Reverse Sort Order
  Topic Search Topic Search  Topic Options Topic Options
alokep View Drop Down
Newbie
Newbie


Joined: 19 Jul 2015
Status: Offline
Points: 15 		Post Options Post Options   Thanks (0) Thanks(0)   Quote alokep Quote  Post ReplyReply Direct Link To This Post Posted: 29 Nov 2017 at 5:51pm
I have a Z97 Anniversary with the latest ASRock firmware (ver 2.0 dated 7/20/2016)
http://www.asrock.com/mb/Intel/Z97%20Anniversary/index.us.asp

Any idea why my system is not vulnerable?  I'm happy.. but puzzled.

Running the Intel detection tool says:

Based on the analysis performed by this tool: This system is not vulnerable."

INTEL-SA-00086 Detection Tool

Application Version: 1.0.0.135
Scan date: 11/29/2017 4:44:13 AM

Host Computer Information

Name: PC
Manufacturer: To Be Filled By O.E.M.
Model: To Be Filled By O.E.M.
Processor Name: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
OS Version: Microsoft Windows 10 Pro

Intel(R) ME Information

Engine: Intel(R) Management Engine
Version: 9.1.25.1005
SVN: 1
Back to Top
Atma View Drop Down
Newbie
Newbie


Joined: 26 Nov 2017
Status: Offline
Points: 5 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Atma Quote  Post ReplyReply Direct Link To This Post Posted: 27 Nov 2017 at 10:20pm
Originally posted by parsec parsec wrote:

All I can do is report this to ASRock.
That would be great, please do that as soon as possible :)
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996 		Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 27 Nov 2017 at 12:47pm
Originally posted by hoisdom hoisdom wrote:

When i run the me1 program, i get the error message:

"Error 8719: Firmware update cannot be initiated because Local Firmware update is disabled"

My motherboard is the z170 extreme4.

What should i do now? Please help me



Did you try running the update program a few times? I've seen examples of this error being posted in other forums (Intel's for example) for other mother boards, and I've seen this update program fail on other Z170 boards. When we ran it again it worked. We also have examples of that happening in this thread.

Do you have the update program on your C: OS drive?
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996 		Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 27 Nov 2017 at 12:42pm
Originally posted by Atma Atma wrote:

Originally posted by parsec parsec wrote:

Originally posted by Atma Atma wrote:

The ME1 Package doesn't work on the ASRock X299 Taichi. I get an SKU mismatch error.

Error 8704: Firmware update operation not initiated due to a SKU mismatch

What processor are you using?
I'm using an Core i7-7820X. According to the Intel Tool I'm affected:




That's strange, the update program, FWUpdLcl64, is supplied by Intel, and is the same program used by other mother board manufactures. I don't know why you would get an SKU mismatch.

It seems you have the INF/Chipset files installed, since the Risk Assessment tool is able to identify your processor. Unless each program uses a different method of processor identification.

All I can do is report this to ASRock.
Back to Top
hoisdom View Drop Down
Newbie
Newbie


Joined: 27 Nov 2017
Status: Offline
Points: 6 		Post Options Post Options   Thanks (0) Thanks(0)   Quote hoisdom Quote  Post ReplyReply Direct Link To This Post Posted: 27 Nov 2017 at 1:33am
When i run the me1 program, i get the error message:

"Error 8719: Firmware update cannot be initiated because Local Firmware update is disabled"

My motherboard is the z170 extreme4.

What should i do now? Please help me



Edited by hoisdom - 27 Nov 2017 at 2:28am
Back to Top
Atma View Drop Down
Newbie
Newbie


Joined: 26 Nov 2017
Status: Offline
Points: 5 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Atma Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2017 at 9:24pm
Originally posted by parsec parsec wrote:

Originally posted by Atma Atma wrote:

The ME1 Package doesn't work on the ASRock X299 Taichi. I get an SKU mismatch error.

Error 8704: Firmware update operation not initiated due to a SKU mismatch

What processor are you using?
I'm using an Core i7-7820X. According to the Intel Tool I'm affected:




Edited by Atma - 26 Nov 2017 at 9:30pm
Back to Top
Kloba12345 View Drop Down
Newbie
Newbie


Joined: 26 Nov 2017
Status: Offline
Points: 1 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Kloba12345 Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2017 at 8:22pm
It does not work on Z170 Gaming K4 with i7 7700K

Error 8746: Firmware update not initiated due to invalid image length

EDIT: Now it worked.


Edited by Kloba12345 - 27 Nov 2017 at 12:24am
Back to Top
OrpheusXx View Drop Down
Newbie
Newbie


Joined: 26 Nov 2017
Status: Offline
Points: 2 		Post Options Post Options   Thanks (0) Thanks(0)   Quote OrpheusXx Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2017 at 6:15pm
Downloaded the ME1 update from Asrock, followed the instructions, but it returned an error:
" Error 8771: Invalid File. " in the error.txt.



Edited by OrpheusXx - 26 Nov 2017 at 6:16pm
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996 		Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2017 at 11:14am
Originally posted by Atma Atma wrote:

The ME1 Package doesn't work on the ASRock X299 Taichi. I get an SKU mismatch error.

Error 8704: Firmware update operation not initiated due to a SKU mismatch


The SKU mismatch message is caused by your processor apparently not matching an affected processor. The SKU code of your processor was apparently not found.

What processor are you using?

The newest Intel High End Desktop (HEDT) processors, also called the X-Series, may not be included in this firmware update. I can't tell from Intel's information page if all of them are. Some definitely are.

Also while the list of affected chipsets includes the Intel 200 series, the X-series chipsets are many times excluded from the mainstream/performance chipsets. Usually Intel would specifically identify the X-series chipsets like the X299 as separate from the other 200 series chipsets. Intel's information is ambiguous about this.
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996 		Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 26 Nov 2017 at 10:44am
Originally posted by beard55 beard55 wrote:

I followed the instructions to run ME1 (ran as administrator).  The cmd window went so fast I couldn't see the result, but after rebooting the Intel diagnostic still reported the vulnerability and the bios is still reported as P7.10.  The MB is a ASRock Fatal1ty Z170 Gaming-ITX ac.

So.... Still waiting for a new bios to resolve the issue.


The CMD window disappeared because the program never ran, because you ran it in Admin mode.

It is reasonable to assume using Admin mode would be correct, but in this case it won't work.

I did not use Admin mode when I ran it on my ASRock Z170 board, and it ran fine. It takes a minute or so to complete, so just double click the file to run it.
Back to Top
 Post Reply Post Reply Page  <1 10111213>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.111 seconds.