Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15)

Fernando · July 15, 2016, 4:26pm

Meanwhile I have done with my Z97 system some benchmark comparison tests trying to find out, if the Intel ME driver version has any noticeable impact on the performance of my currently running system (256 GB Samsung 950 Pro SSD as system drive, OS: Win10 x64 Insider Preview Build 14388).
These were the 2 Intel Management Engine drivers I have tested:
1. Intel MEI driver v11.0.0.1057 (automaticly installed by Windows Update)
2. Intel MEI driver v11.5.0.1011 (manually installed by me)

Here are the results (left picture: Intel MEI driver v11.0.0.1157, right picture: Intel MEI driver v11.5.0.1011):

My conclusion: Although the scores of both drivers are very close together, the older Intel MEI driver v11.0.0.1157 gave my system a slightly better performance than the currently latest Intel MEI driver.

gpvecchi · July 15, 2016, 5:28pm

Experts probably know this, anyway I found this: FIT is Firmware Interface Table, a data structure embedded in BIOS so that Intel microcode and ACM can locate BIOS components.
So, probably we just need to understand wich BIOSes has this feature, to understand if we have to flash FIT or FWU version.

plutomaniac · July 15, 2016, 5:54pm

@ Feyd1364 & SK371:

Thank you for your report Feyd1364 and SK371. FW Status Register2 is different because PhaseStatus was changed temporarily. MEInfo automatically shows the decoded values of Register1 and Register2 at the beginning of the report (CurrentState - PhaseStatus). Unfortunately it does not do the same for Register3 or later and the documentation only mentions what Register1 and Register2 mean. So I don’t know the difference between 0420 (???) and 0200 (NOPDM) or 0220 (PDM) etc at Register3.

@ rootuser123:

Thank you for letting me know rootuser123. Based on build number, date (April) and unofficial/leaked Intel roadmaps for KBL release, these are Alpha to Pre-Beta drivers. Although it’s great that we have found them, I don’t believe anyone but advanced users should install these at this point. For the purposes of this thread, the latest driver is 11.0-based currently.

@ k-pax:

If you want to brick your system, it’s perfect. You obviously haven’t read the instructions of the threads you look into. So make sure you do that first.

@ khanmein:

Check the first post to see the latest driver and firmware for 9-series. Stick to 11.0 drivers for now and the latest 9.1 firmware for your 5MB system.

@ crystalorb:

Your BIOS has Consumer firmware so flash Consumer firmware, that simple. Use ME Analyzer to check the SKU of whatever firmware you want. There are many ways to tell 1.5MB and 5MB apart but size is not always one of them.

@ Fernando:

Regarding “GbE platform”, this has nothing to do with ME or it’s SKUs. GbE stands for Gigabit Ethernet and it’s an optional firmware for systems that use Intel’s controller and not a 3rd party one.

@ gpvecchi:

FIT stands for Flash Image Tool, it has nothing to do with BIOS FIT table for microcodes. FWU stands for FWUpdate. For ME 11.x EXTR images, FWUpdate is either accidentally or (more likely) intentionally broken and works only with RGN. So I create two versions, one which works with FWUpdate (FWU) and another which should be used at Flash Image Tool and Flash Programming Tool (FIT).

khanmein · July 15, 2016, 6:05pm

@plutomaniac unfortunately, 1.5MB not working & shown invalid file so i ended up flashed 5MB which working on my ASRock H97 Pro4. thanks for sharing.

plutomaniac · July 15, 2016, 6:11pm

@ khanmein:

Yes obviously. Your motherboard uses 5MB firmware so you flash 5MB firmware, not 1.5MB. I didn’t check what mobo you had at my previous reply so I assumed 1.5MB. Use ME Analyzer to check what firmware your latest mobo BIOS has inside and thus, what you need to flash.

Fernando · July 15, 2016, 6:53pm

Thanks for your remark. I just have corrected my mistake within the related posts.

100PIER · July 15, 2016, 7:12pm

@Fernando ,
I see a MEI v11.5.0.1015 WHQL driver available on station-drivers at:
MEI driver v11.5.0.1015 WHQL
Is it a new branch ?

Fernando · July 15, 2016, 7:22pm

That is the version of the Intel MEI Software, but the included Intel MEI drivers are v11.5.0.1011 WHQL.

Obviously yes.

sucka · July 15, 2016, 8:44pm

On Maximus VIII Extreme, flashed 11.0.15.1003_CON_H_D0_UKPDM_PRD_EXTR_FWU.bin and worked as charm.

Before flash i had 11.0.11.1005_CON_H_D0_NOPDM_PRD_RGN with register3 of course with value 0x00000200.

Thanks!

Intel(R) MEInfo Version: 11.0.11.1002
Copyright(C) 2005 - 2016, Intel Corporation. All rights reserved.

FW Status Register1: 0x90000245
FW Status Register2: 0x06F60506
FW Status Register3: 0x00000420
FW Status Register4: 0x00084000
FW Status Register5: 0x00000000
FW Status Register6: 0x40000000

CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: CM0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
SPI Flash Log: Not Present
Phase: ROM/Preboot
ICC: Valid OEM data, ICC programmed
ME File System Corrupted: No
PhaseStatus: AFTER_SRAM_INIT

FPF and ME Config Status: Match
FW Capabilities value is 0x31111D40
Feature enablement is 0x11111940
Platform type is 0x71220322
No Intel vPro Wireless device was found
Intel(R) ME code versions:

Windows OS Version : 6.2.9200 “”
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
BIOS Version 1701

Windows OS Version : 6.2.9200 “”
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 22 (0x 16 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 10 ( 0x 0A ) found, size of 6 (0x 06 ) bytes
Table Type 11 ( 0x 0B ) found, size of 5 (0x 05 ) bytes
Table Type 12 ( 0x 0C ) found, size of 5 (0x 05 ) bytes
Table Type 32 ( 0x 20 ) found, size of 20 (0x 14 ) bytes
Table Type 34 ( 0x 22 ) found, size of 11 (0x 0B ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 36 ( 0x 24 ) found, size of 16 (0x 10 ) bytes
Table Type 35 ( 0x 23 ) found, size of 11 (0x 0B ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 39 ( 0x 27 ) found, size of 22 (0x 16 ) bytes
Table Type 40 ( 0x 28 ) found, size of 32 (0x 20 ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 4 ( 0x 04 ) found, size of 48 (0x 30 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 17 ( 0x 11 ) found, size of 40 (0x 28 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 221 ( 0x DD ) found, size of 12 (0x 0C ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 20 ( 0x 14 ) found, size of 35 (0x 23 ) bytes
Table Type 130 ( 0x 82 ) found, size of 20 (0x 14 ) bytes
Table Type 131 ( 0x 83 ) found, size of 64 (0x 40 ) bytes
MEBx Version found is 0.0.0.0000
MEBx Version 0.0.0.0000
GbE Version 0.7
Vendor ID 8086
PCH Version 31
FW Version 11.0.15.1003 H
LMS Version Not Available
MEI Driver Version 11.5.0.1011
Wireless Hardware Version Not Available
Wireless Driver Version Not Available

FW Capabilities 0x31111D40

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Protect Audio Video Path - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED
Service Advertisement & Discovery - NOT PRESENT
Intel(R) NFC Capabilities - NOT PRESENT
Intel(R) Platform Trust Technology - PRESENT/DISABLED

TLS Disabled
Last ME reset reason Firmware reset
Local FWUpdate Enabled
BIOS Config Lock Disabled
GbE Config Lock Disabled
Get flash master region access status…done
Host Read Access to ME Disabled
Host Write Access to ME Disabled
Get EC region access status…done
Host Read Access to EC Disabled
Host Write Access to EC Disabled
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0x0
Protected Range Register Limit #1 0x0
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
SPI Flash ID 1 EF4018
SPI Flash ID 2 Unknown
BIOS boot State Post Boot
OEM ID 00000000-0000-0000-0000-000000000000
Capability Licensing Service Enabled
OEM Tag 0x00000000
Slot 1 Board Manufacturer 0x00000000
Slot 2 System Assembler 0x00000000
Slot 3 Reserved 0x00000000
M3 Autotest Disabled
C-link Status Disabled
Independent Firmware Recovery Disabled
EPID Group ID 0xF83
OEM Public Key Hash FPF 0000000000000000000000000000000000000000000000000000000000000000

Retrieving Variable "OEM Public Key Hash"
OEM Public Key Hash ME 66687AADF862BD776C8FC18B8E9F8E20089714856EE233B3902A591D0D5F2925
ACM SVN FPF 0x0
KM SVN FPF 0x0
BSMM SVN FPF 0x0
GuC Encryption Key FPF 0000000000000000000000000000000000000000000000000000000000000000

Retrieving Variable "GuC Encryption Key"
GuC Encryption Key ME 6DB65FD59FD356F6729140571B5BCD6BB3B83492A16E1BF0A3884442FC3C8A0E

FPF ME
— –
Force Boot Guard ACM Disabled
Retrieving Variable “Force Boot Guard ACM Enabled”
Disabled
Protect BIOS Environment Disabled
Retrieving Variable “Protect BIOS Environment Enabled”
Disabled
CPU Debugging Enabled
Retrieving Variable “CPU Debugging”
Enabled
BSP Initialization Enabled
Retrieving Variable “BSP Initialization”
Enabled
Measured Boot Disabled
Retrieving Variable “Measured Boot Enabled”
Disabled
Verified Boot Disabled
Retrieving Variable “Verified Boot Enabled”
Disabled
Key Manifest ID 0x0
Retrieving Variable “Key Manifest ID”
0x0
Enforcement Policy 0x0
Retrieving Variable “Error Enforcement Policy”
0x0
PTT Enabled
Retrieving Variable “Intel(R) PTT Supported”
Enabled
PTT Lockout Override Counter 0x0
EK Revoke State Not Revoked
PTT RTC Clear Detection FPF 0x0

k-pax · July 16, 2016, 3:26pm

hi,plutomaniac please I need me region 8.0.4.1441 for me mac,i don’t see in the repository
MAC_PRD_EXTR thanks,good job this web

edit:i see “Removed ME 8.0.4.1441_1.5MB_PRD_EXTR”? I can used other?

plutomaniac · July 16, 2016, 5:00pm

There is no ME8 MAC firmware, use the latest regural 1.5MB as seen at the ME thread

k-pax · July 16, 2016, 8:15pm

hi,i use the latest regural 1.5MB,and mac running slow
hi,the latest regural 1.5MB,work fine in me machine mac?

stefan063 · July 18, 2016, 8:34pm

Hello,

I am new to this forum… Can you please tell me which Version of FWUpdlcl and which FW I need for my Alienware M18x R1… Also what is whit those FW regions? I have unlocked BIOS and Enable RE-FLASH FW ME… REgards

plutomaniac · July 20, 2016, 9:47pm

@ stefan063:

If I understand properly you want to reflash your ME region. After ME Reflash is enabled, use Flash Programming Tool with command fptw -f me_fix.bin -me followed by command fptw -greset. After the reset you can disable ME Reflash and check ME health via MEInfo and MEManuf as mentioned at the ME thread.

me_fix.rar (520 KB)

k-pax · July 21, 2016, 1:25am

hi plutomaniac,i need change me region this bios please.i find the me region(2.0.0.2060),i don’t see
thanks,i need you help

ipmbw-br rev 1.4 w25q64fw acer.zip (3.36 MB)

greg.chalk · July 24, 2016, 6:04am

Greetings,

just a feedback:

I have a Dell xps 13, 9350 Skylake. I flashed latest emei v11.0.12.1008 "NOPDM".
Before flash I had the last three numbers of "FW Status Register3" field: A value of "200".
After flash, last three numbers changed to "020".
Laptop seems to work normally.

kostar20071 · July 24, 2016, 4:43pm

I have yoga 500-15ISK , also Skylake , my register was 030 , flashed PDM version, seems fine.
Flashed also NOPDM and also fine.
Finally flashed the latest firmware from Lenovo website …

rvail623 · July 24, 2016, 8:00pm

In researching latest ME firmware for the GIGABYTE - Motherboard - Socket 1151 - GA-Z170MX-Gaming 5 (rev. 1.0)
the first post of this thread mentions the need to distinguish between PDM & NOPDM versions of Intel ME firmware.
The GA-Z170MX-Gaming 5 board was diagnosed (by me, using Intel’s command line utility “MEInfoWin64.exe -verbose”, version 11.0.11.1002) to be: NOPDM, and thus the latest ME firmware would seem to be:
11.0.11.1005_CON_H_D0_NOPDM_PRD_RGN.bin (one of several firmware versions found within the uncompressed file “Intel ME 11.0 Consumer PCH-H Firmware v11.0.15.1003.rar”.
That same page also states: “Skylake-S has LGA1151 & Skylake-H has BGA1440”, yet the firmware file shows the letter H instead of S.
Running MEInfoWin64.exe shows the letter H after the existing installed firmware version.
So: I’m thinking that “Skylake-S has LGA1151, Skylake-H has BGA1440” may be inaccurate
So: I’m fairly confident that “11.0.11.1005_CON_H_D0_NOPDM_PRD_RGN.bin” is the correct & latest ME firmware for the GA-Z170MX-Gaming 5 board.
UBU 155.3 says the ME firmware included in the latest beta bios F5e (direct from Gigabyte) is v. 11.0.0.1168 and is NOT the latest available ME firmware version.
Comments?

Scoty · July 25, 2016, 10:55am

Ths is the latest i have found Intel_ ME_11.5.0.1015. Can i use with my Asus Z170 Gaming Pro or which ist the best one for my Board?

Fernando · July 25, 2016, 12:14pm

You can install this package (has to be for 1.5M systems), but the latest drivers are not always the best (especially when they come from an early development stage).
I recommend to use the latest Intel MEI drivers (resp. the related MEI Drivers & Software Set), which are offered within the start post of this thread.