Intel Management Engine:
Drivers, Firmware & System Tools

Last Updated: 2020-01-08
Intel Management Engine Introduction: Built into many Intel-based platforms is a small, low power computer subsystem called the Intel Management Engine (Intel ME). This can perform various tasks while the system is booting, running or sleeping. It operates independently from the main CPU, BIOS & OS but can interact with them if needed. The ME is responsible for many parts of an Intel-based system. Such functionality extends, but it's not limited, to Platform Clocks Control (ICC), Thermal Monitoring, Fan Control, Power Management, Overclocking, Silicon Workaround (resolves silicon bugs which would have otherwise required a new cpu stepping), Identity Protection Technology, Boot Guard, Rapid Start Technology, Smart Connect Technology, Sensor Hub Controller (ISHC), Active Management Technology (AMT), Small Business Advantage (SBA), Wireless Display, PlayReady, Protected Video/Audio Path etc. For certain advanced/corporate features (AMT, SBA etc) the ME uses an out-of-band (OOB) network interface to perform functions even when the system is powered down, the OS and/or hard drivers are non-functional etc. Thus it is essential for it to be operational in order for the platform to be working properly, no matter if the advanced/corporate features are available or not.

Intel Converged Security Engine Introduction: The evolution of Intel Management Engine into a unified security co-processor, running x86 code under a Minix-based Operating System. It was first introduced in 2015 with the release of Skylake CPUs working alongside 100-series Sunrise Point Platform Controller Hub (PCH). The CSE hardware can run Management Engine (ME) 11+, Trusted Execution Engine (TXE) 3+ or Server Platform Services (SPS) 4+ firmware. So there are a total of three families of CSE-based firmware: CSME (CSE ME), CSTXE (CSE TXE) and CSSPS (CSE SPS). The CSE hardware is also capable of running other types of firmware such as Power Management Controller (PMC), Integrated Sensor Hub (ISH), Imaging Unit (iUnit), Clear Audio Voice Speech (cAVS), Wireless Microcode (WCOD) etc.

Intel Power Management Controller Introduction: Handles all Platform Controller Hub (PCH) power management related activities, running ARC code on top of the CSE hardware. PMC administers power management functions of the PCH including interfacing with other logic and controllers on the platform to perform power state transitions, configure, manage and respond to wake events, aggregate and report latency tolerance information for devices and peripherals connected to and integrated into the PCH etc. It was first introduced in 2018 with the release of Coffee/Cannon Lake CPUs working alongside 300-series Cannon Point PCH.

This is a collection of everything Intel (CS)ME related. To extract most of the files below you need to use programs which support RAR5 compression!

Disclaimer: All the software & firmware below comes only from official updates which were provided and made public by various manufacturers! The System Tools are gathered and provided with the sole purpose of helping people who are out of other viable solutions. Thus, they can be extremely helpful to those who have major problems with their systems for which their manufacturer refuses to assist due to indifference and/or system age.

A. About Intel MEI Drivers

The latest v14.0 drivers are usable with 8-series Broadwell mobile & 100-series or newer desktop/mobile systems, meaning (CS)ME 10-14. Users of 9 & 8-series Haswell desktop/mobile systems, meaning ME 9, must use the latest v11.7 drivers instead. Users of 7 & 6-series Ivy/Sandy Bridge desktop/mobile systems, meaning ME 7 - 8, must use the latest v11.0 drivers instead. Users of 5-series or older desktop/mobile systems, meaning ME <= 6, must check Section D to find the driver they need. In order to check your current installed version, use Intel MEInfo tool as instructed below.

Note: To extract some of the files below you need to use programs which support RAR5 compression!

A1. Intel MEI Drivers & Software

These packages contain the Intel MEI drivers with their respective software & system services. It is advised to install these to enable all the Engine-related functionality. It is important to install the correct package depending on your Consumer/1.5MB or Corporate/5MB system. If your Windows 10 operating system requires Universal/DCH drivers, install these instead.

• Intel MEI Drivers & Software Consumer v1941.14.0.1366
• Intel MEI Drivers & Software Consumer v1939.13.0.1206
• Intel MEI Drivers & Software Consumer v1946.12.0.1328
• Intel MEI Drivers & Software Corporate v1937.12.0.1312
• Intel MEI Drivers & Software Consumer v11.7.0.1069
• Intel MEI Drivers & Software Corporate v11.7.0.1069
• Intel MEI Drivers & Software Consumer v11.0.6.1194
• Intel MEI Drivers & Software Corporate v11.0.6.1194

Note: MEI Drivers & Software v1941.14.0.1366 includes MEI v1931.14.0.1323. MEI Drivers & Software v1939.13.0.1206 includes MEI v1910.13.0.1060. MEI Drivers & Software v1946.12.0.1328 includes MEI v1914.12.0.1256. MEI Drivers & Software v11.7.0.1069 includes MEI v11.7.0.1057. MEI Drivers & Software v11.0.6.1194 includes MEI v11.0.5.1189.

A2. Intel MEI Driver Only

These packages contain only the Intel MEI Drivers without any additional software or system services. Installing these allow only very basic Engine-related functionality. They are compatible with both Consumer/1.5MB and Corporate/5MB systems. The MEI Installer is the setup file from Intel which includes the MEI Driver but also allows easy installation and adds a Control Panel entry for quick driver removal.

• Intel MEI Driver v1931.14.0.1323 (Windows 8 & Windows 10)
• Intel MEI Driver v1931.14.0.1323 (Windows 7)
• Intel MEI Driver v1910.13.0.1060 (Windows 8 & Windows 10)
• Intel MEI Driver v1910.13.0.1060 (Windows 7)
• Intel MEI Driver v1914.12.0.1256 (Windows 8 & Windows 10)
• Intel MEI Driver v1914.12.0.1256 (Windows 7)
• Intel MEI Installer v11.7.0.1069
• Intel MEI Driver v11.7.0.1057 (Windows 8 & Windows 10)
• Intel MEI Driver v11.7.0.1057 (Windows XP & Windows 7)
• Intel MEI Installer v11.0.6.1194
• Intel MEI Driver v11.0.5.1189

Note: The MEI Drivers listed above are part of the complete Drivers & Software packages found at section A1. A newer Drivers & Software package has newer Software but the actual MEI Driver may still be an older version. MEI Installer v11.7.0.1069 includes MEI Driver v11.7.0.1057. MEI Installer v11.0.6.1194 includes MEI Driver v11.0.5.1189.

Note: The MEI Installer includes the MEI Driver but allows easy installation of it. However, since we cannot always find the latest MEI Installer, it is advised to manually install the MEI Driver in case its version is newer.

A3. Intel SOL "Driver" Only

This package contains only the Intel SOL "Driver" without any additional software or system services. It is compatible only with Corporate/5MB systems. If the software and system services are required in case of remote management etc, users of such systems should install the equivalent complete Drivers & Software package (section A1).

• Intel SOL "Driver" v1843.12.0.1169
• Intel SOL "Driver" v11.6.0.1009
• Intel SOL "Driver" v11.0.0.1136

Note: The SOL "Driver" listed above is part of the complete Drivers & Software packages found at section A1. A newer Drivers & Software package has newer Software but the actual SOL "Driver" may still be an older version.

Note: The SOL "Driver" is not really a driver but rather a placeholder INF file which assigns a correct device name at Device Manager and prevents the latter from showing the yellow exclamation mark of "No driver was found for this device". It's the SOLs' equivalent of Intel Chipset Device "Drivers" (= INF files).

B. About Intel (CS)ME & PMC Firmware Updates

SPI/BIOS Regions (FD/ME/BIOS): The SPI/BIOS chip firmware is divided into regions which control different aspects of an Intel-based system. The mandatory regions are the Flash Descriptor (FD, controls read/write access between the regions among other things), the (Converged Security) Management Engine (CSME/ME or Engine, holds the system's Engine firmware) and the BIOS. For security reasons, the Flash Descriptor and Engine regions of the SPI/BIOS chip are usually locked so that no read/write access is allowed via software means. Since the FD controls that read/write access, it must be locked/protected so that it is not manually overwritten to allow unauthorized access to the firmware regions of the system's SPI/BIOS chip. The Engine region at the system's SPI/BIOS chip is also locked/protected due to the nature of the (Converged Security) Management Engine co-processor, as explained at the Introductions above.

Engine Attributes (Platform/SKU/Version): Intel (CS)ME or Engine firmware is mainly categorized based on its target Platform (7,9,100,300-series etc), Chipset (H = Halo/Performance, LP = Low Power), SKU (Consumer/Corporate/Slim/1.5MB/5MB etc) and Version (8.1.40.1416, 12.0.6.1120 etc). Be careful of what firmware your download relevant to your system. To understand your exact Platform, SKU & Chipset, you can usually run MEInfo or MEManuf (-verbose) tools. Otherwise, ME Analyzer can show you all the relevant information, after loading your SPI/BIOS image, when the latter is available. All the firmware below correspond to a specific Platform which runs a specific (CS)ME firmware version (example: For 100/200-series systems which run CSME Corporate LP v11.0 - v11.8).

Engine Regions (RGN/EXTR): The Type of each Engine/(CS)ME firmware Region can be either Stock (RGN) or Extracted (EXTR). Stock are clean/stock/unconfigured images provided by Intel to OEMs. Extracted are dirty/extracted/configured images from various SPI/BIOS. The Engine firmware at the system's SPI/BIOS chip is always EXTR, generated by the OEM after configuring the equivalent RGN with the appropriate system settings.

Engine Configuration (CODE/DATA): The Engine Firmware Regions (RGN/EXTR) consist of two sections: CODE and DATA. CODE is the actual Engine firmware whereas DATA is where all the system-specific settings are stored, as configured by the OEM at the factory via Intel Flash Image Tool. The Engine firmware is not static as it holds system-specific configuration and can additionally be configured by the Engine co-processor itself while the system is running in order to provide the proper support and functionality. Any such changes are written into the DATA section of the Engine Region and the firmware is considered Initialized. That means that the DATA section can be in one of three states: Unconfigured, Configured or Initialized. Unconfigured means that the Engine firmware image is the stock one Intel provides and not configured by the OEM at all (RGN). Configured means that the OEM has applied model specific settings and the Engine region is ready for deployment (EXTR). Initialized means that the Engine region comes from a system which was already running and thus the Engine co-processor has further configured the DATA section to suit that particular system better (system specific or dirty EXTR).

FWUpdate Updates (UPD): FWUpdate images (UPD) are partial RGN/EXTR firmware regions which contain only ME CODE without any DATA. They are created and used only by Intel's FWUpdate tool. Thus, they can neither be opened nor configured by Intel Flash Image Tool (FIT). Never flash UPD images via anything other than Intel FWUpdate tool. UPD images are not needed for 7-series (ME 8) or newer systems. However, all 6-series (ME 7) or older systems must use UPD images in order to initiate a ME firmware update. Thus, at section B1 below, only RGN/EXTR images are provided for 7-series (ME 8) or newer systems and only UPD images are provided for 6-series (ME 7) or older systems.

Engine Security Version Number (SVN): All (CS)ME 8 or newer Engine firmware, as well as all PMC CNP or newer Power Management Controller firmware, are defined by a Security Version Number (SVN) like 1,2,3 etc which is used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The SVN gets incremented if there is a high or critical security fix that requires a Trusted Computing Base (TCB) recovery operation, a significant event in the life cycle of the firmware which requires renewal of the security signing keys in use. A downgrade to a lower SVN value via FWUpdate tool is prohibited whereas an upgrade to the same or higher SVN is allowed. For example if your current firmware has a SVN of 2, you can update to another firmware with SVN >= 2 (for example 3) but you cannot downgrade to another firmware with SVN < 2 (for example 1). Trying to flash a firmware with lower SVN will result in the error "The image provided is not supported by the platform" or similar. To view the SVN value of any (CS)ME or PMC firmware, you can use ME Analyzer tool.

Engine Version Control Number (VCN): All (CS)ME 8 or newer Engine firmware are defined by a Version Control Number (VCN) like 1,2,45,193 etc which is used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The VCN gets incremented if there is a security fix, a significant firmware change or a new feature addition. A downgrade to a lower VCN value via FWUpdate tool is prohibited whereas an upgrade to the same or higher VCN is allowed. For example if your current firmware has a VCN of 176, you can update to another firmware with VCN >= 176 (for example 193) but you cannot downgrade to another firmware with VCN < 176 (for example 174). Trying to flash a firmware with lower VCN will result in the error "The image provided is not supported by the platform" or similar. To view the VCN value of any (CS)ME firmware, you can use ME Analyzer tool.

Engine Production Ready Status (PV): All (CS)ME 8 or newer Engine firmware are defined by a Production Version/Ready Status (PV) which can be either Yes or No and is used to control the possible upgrade/downgrade paths provided by Intel's FWUpdate tool. The PV status is set to Yes when a firmware is validated/ready for use at Production platforms, thus when its status is Stable and not Beta, Alpha etc. An upgrade/downgrade from PV to non-PV firmware via FWUpdate tool is prohibited whereas upgrades/downgrades to the same PV or from non-PV to PV are allowed. For example if your current firmware has PV set to Yes, you can upgrade/downgrade to another firmware with PV set to Yes but you cannot upgrade/downgrade to another firmware with PV set to No. Trying to flash a firmware with incompatible PV will result in the error "The image provided is not supported by the platform" or similar. To view the PV status of any (CS)ME firmware, you can use ME Analyzer tool.

Engine Firmware Updating: There are two ways to upgrade or downgrade the Engine firmware, either via Intel FWUpdate tool or manually.

• The Intel FWUpdate tool is an official command line utility provided by Intel which uses the Engine co-processor itself to upgrade/downgrade the (CS)ME firmware quickly and easily. FWUpdate tool requires that the Engine co-processor is operational and that its current Engine firmware region is healthy at the system's SPI/BIOS chip. To check if the Engine itself as well as its current firmware are healthy, you can use Intel MEInfo and MEManuf tools, as instructed below. FWUpdate tool also requires that the SVN, VCN and PV are not violated. Since FWUpdate tool relies solely on the Engine co-processor itself for the upgrade/downgrade, it does not require the user to have read/write access to the Engine firmware region of the system's SPI/BIOS chip, as dictated by the Flash Descriptor region permissions. Moreover, FWUpdate tool does not require any prior Engine Configuration (DATA) and can thus work with merged RGN/EXTR + PMC images at CSME 12+ or both RGN & EXTR images at 8 <= (CS)ME <= 11 platforms. The basic usage is FWUpdLcl -f update_file_name.bin for (CS)ME >= 7 or FWUpdLcl update_file_name.bin -generic for ME <= 6. You can see the entire supported parameters by displaying the utility's help screen via FWUpdLcl -?. You can also see a few basic usage examples via FWUpdLcl -exp.

• In the event in which the usage of Intel FWUpdate tool is not possible, you can try to upgrade/downgrade the (CS)ME firmware manually. Such cases include downgrading to Engine firmware which violate SVN, VCN or PV, repairing a corruption/problem etc. To upgrade/downgrade/repair manually, you need first & foremost to have read/write access to the Engine firmware region of the system's SPI/BIOS chip. To check if your FD is locked or to attempt to unlock it, follow the [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing. Once you have read/write access to the Engine firmware region of your system's SPI/BIOS chip, you can use any general purpose firmware flasher software such as Intel Flash Programming Tool, AMI AFU, Flashrom etc, which directly reads/writes the system's SPI/BIOS chip firmware. Before flashing, you must make sure that the Engine firmware region to be flashed back is Configured (EXTR) for your specific system via Intel Flash Image Tool (FIT). In order to do that, follow the [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization. Never flash RGN or 3rd-party EXTR firmware to the Engine firmware region of the system's SPI/BIOS chip without first configuring them for your specific system (EXTR) via FIT. Since general purpose firmware software do not upgrade/downgrade/repair the Engine firmware region of the system's SPI/BIOS chip via the Engine co-processor itself, they are not restricted by the SVN, VCN and PV security measures. As long as you have read/write access to the Engine firmware region of the system's SPI/BIOS chip and a DATA Configured (EXTR) Engine firmware image, they should accomplish the desired action.

Warning for 8-series systems: The 8-series desktop systems initially come with v9.0 firmware. The latter is upgradeable to v9.1 firmware only if the OEM has updated the BIOS to be compatible as well. If your BIOS is up to date and the firmware is still v9.0 then avoid updating to v9.1 but only to latter v9.0 releases. The system will not brick but, if the BIOS is not ready, you may face BCLK, fan control and other issues after which going back to v9.0 firmware is often difficult. However, if your current 8-series system has firmware v9.1 (after a BIOS update) then you can update to the latest v9.1 firmware as provided below.

Warning for all CSME v11 - v14 systems: Make sure you choose the correct firmware for your system based on its Platform/Chipset (PCH) and Firmware Features (SKU). There are three firmware SKUs: Slim, Consumer and Corporate for the minimal, basic and full Feature Set respectively. When it comes to Platform, there are two chipsets: PCH-H (Halo, performance) and PCH-LP (Low Power). There are four CPU families: S, H, U and Y. The PCH-H chipset works with S & H processors and requires PCH-H (H) CSME firmware. The PCH-LP chipset works with U & Y processors and requires PCH-LP (LP) CSME firmware. So in total there are six firmware SKUs: Consumer PCH-H, Consumer PCH-LP, Corporate PCH-H, Corporate PCH-LP, Slim PCH-H and Slim PCH-LP.

Warning for all CSME v11 systems: All systems which initially come with CSME v11.0, v11.5, v11.6 or v11.7 are upgradable to v11.8 firmware. All systems which initially come with CSME v11.10 or v11.11 are upgradable to v11.12 firmware. All systems which initially come with CSME v11.20 or v11.21 are upgradable to v11.22 firmware. Only v11.8, v11.12 & v11.22 updates are provided below.

Warning for PCH-LP 100-series systems: Make sure to mind the firmware Power Down Mitigation (PDM) status which is distinguished between YPDM (Yes) and NPDM (No). PDM is some sort of erratum, which is only relevant to 100-series PCH-LP systems. Thus, it is an attribute of every CSME v11.0 - v11.8 firmware which supports 100-series PCH-LP systems. It is suggested to update from YPDM to YPDM and from NPDM to NPDM. The PDM status of a firmware can be detected by ME Analyzer by loading either your SPI/BIOS image or an Engine Firmware Recovery image which can be generated via FWUpdate tool parameter "-save recovery.bin". The CSME v11.8 PCH-LP archives below include only the latest firmware regardless of their PDM status. If the latest found firmware is not PDM-suitable for your system, you can find the last equivalent compatible version at Intel Engine: Firmware Repositories. In cases where we have YPDM and NPDM variants of that latest version, both are included.

Notice for CSME v11 INTEL-SA-00086 vulnerabilities: After the CSME v11.8, v11.11/v11.12 or v11.21/v11.22 firmware update, run MEInfo tool and verify that "Re-key needed" is False. Re-Keying is the process of renewing the Intel Enhanced Privacy ID (EPID) and Intel PTT’s TPM 2.0 Endorsement Key, CSME’s remote attestation keys. It requires software running on the host OS to communicate with Intel servers. If "Re-key needed" is True, download the latest Drivers & Software (section A1) and execute command "SetupME.exe -tcs -nodrv -s" via a command line prompt.

Warning for all CSME v12 - v14 systems: Power Management Controller (PMC) firmware always targets a specific PCH SKU (H/LP) and PCH Stepping (A, B, C, D etc). The versioning scheme is Platform Series (CNP = 300, ICP = 130, CMP = 140 etc) + PCH SKU (1 = LP, 2 = H) + PCH Stepping (0 = A, 1 = B, 2 = C etc). For example, a hypothetical 300-series PCH-H Stepping B1 system must use PMC 300.2.1x.xxxx firmware, a hypothetical 300-series PCH-LP Stepping A0 system must use PMC 300.1.0x.xxxx firmware, a hypothetical 300-series PCH-LP Stepping D2 system must use PMC 300.1.3x.xxxx firmware etc. The PMC firmware can only be updated after being merged with a CSME 12-14 firmware via Flash Image Tool.

Notice about CSME 12-14 FWUpdate Tool: Starting from CSME 12, Intel FWUpdate tool does not work with bare RGN or EXTR CSE firmware as it requires that they are first combined/stitched with the equivalent Power Management Controller (PMC) firmware, which is updated alongside the main CSE firmware. The CSME v12 - v14 archives below always include bare RGN or EXTR CSE firmware images so you must always stitch the equivalent PMC firmware first, via Flash Image Tool (FIT), before using Intel FWUpdate tool. To check if a CSE RGN/EXTR firmware region is already FWUpdate compatible, input it at ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes". To generate the correct FWUpdate compatible CSME + PMC firmware combination for your system via FIT, you must first know your system's Chipset Platform (H, LP), Chipset Type (Consumer, Corporate, Slim) and Chipset Stepping/Revision (A, B, C etc).

• Download the latest Intel CSME System Tools (Section C) as well as ME Analyzer tool.
• From Intel CSME System Tools, run MEInfo command line tool and under "Intel(R) ME code versions" > "FW Version" you will find your system's Chipset Platform as well as Type (i.e. H Consumer etc). Under "PCH Information" > "PCH Step Data" you will find your system's Chipset Stepping which starts with a letter (Ax, Bx, Cx etc).
• Alternatively, only if you cannot use MEInfo, drag & drop your system's SPI/BIOS image at ME Analyzer tool and find "SKU" field which shows your system's Chipset Type and Platform (i.e. Consumer H). Next, find "Chipset Stepping" field which lists one or more supported Chipset Steppings in the form of letters (A, B, C etc).
• Based on your system's Chipset Platform, Type and Stepping, choose the correct CSME and PMC firmware (Section B).
• Input the chosen CSME firmware into ME Analyzer tool and make sure that "FWUpdate Support" is not reported as "Impossible".
• From Intel CSME System Tools, run Flash Image Tool (FIT) and adjust the PCH Platform drop-down menu at the top to either "H Series Chipset" or "LP Series Chipset" based on your system's PCH Platform. For the purposes of FWUpdate, there is no need to further adjust the PCH SKU.
• Load/drop the chosen CSME firmware image and then input the chosen PMC firmware at "Flash Layout" > "Ifwi: Intel(R) Me and Pmc Region" > "PMC Binary File".
• Adjust "Flash Settings" > "Flash Components" > "Number of Flash Components" to "0".
• Adjust "Integrated Sensor Hub" > "Integrated Sensor Hub" > "Integrated Sensor Hub Supported" to "No".
• Build the image and use "cse_image_FWU_Full.bin" at Intel FWUpdate tool.

Note: To extract some of the files below you need to use programs which support RAR5 compression!

B1. (Converged Security) Management Engine - (CS)ME

• Intel CSME 14.0 Consumer PCH-LP A Firmware v14.0.11.1205
  For Comet Lake mobile systems which run CSME Consumer LP A v14.0
• Intel CSME 13.0 Consumer PCH-LP X Firmware v13.0.0.0000 (Placeholder)
  For Ice Lake mobile systems which run CSME Consumer LP X v13.0
• Intel CSME 12.0 Consumer PCH-H B,A Firmware v12.0.49.1534
  For 300/C240-series systems which run CSME Consumer H B,A v12.0
• Intel CSME 12.0 Corporate PCH-H B,A Firmware v12.0.49.1534
  For 300/C240-series systems which run CSME Corporate H B,A v12.0
• Intel CSME 12.0 Consumer PCH-LP C Firmware v12.0.49.1534
  For 300/C240-series systems which run CSME Consumer LP C v12.0
• Intel CSME 12.0 Consumer PCH-LP B Firmware v12.0.0.1062
  For 300/C240-series systems which run CSME Consumer LP B v12.0
• Intel CSME 12.0 Corporate PCH-LP C Firmware v12.0.49.1534
  For 300/C240-series systems which run CSME Corporate LP C v12.0
• Intel CSME 12.0 Slim PCH-H B,A Firmware v12.0.45.1509
  For 300/C240-series systems which run CSME Slim H B,A v12.0
• Intel CSME 12.0 Slim PCH-LP C Firmware v12.0.45.1509
  For 300/C240-series systems which run CSME Slim LP C v12.0
• Intel CSME 11.22 Corporate PCH-H B,A Firmware v11.22.70.1622
  For C620-series systems which run CSME Corporate H B,A v11.20 - v11.22
• Intel CSME 11.22 Slim PCH-H B,A Firmware v11.22.72.1628
  For C620-series systems which run CSME Slim H B,A v11.20 - v11.22
• Intel CSME 11.12 Consumer PCH-H A Firmware v11.12.0.1622
  For X299 systems which run CSME Consumer H A v11.10 - v11.12
• Intel CSME 11.12 Corporate PCH-H A Firmware v11.12.0.1622
  For C400-series systems which run CSME Corporate H A v11.10 - v11.12
• Intel CSME 11.11 Slim PCH-H A Firmware v11.11.70.1622
  For X299/C400-series systems which run CSME Slim H A v11.10 - v11.11
• Intel CSME 11.8 Consumer PCH-H D,A Firmware v11.8.71.3630
  For 100/200/H310C/B365/Z370-series systems which run CSME Consumer H D,A v11.0 - v11.8
• Intel CSME 11.8 Corporate PCH-H D,A Firmware v11.8.71.3630
  For 100/200-series systems which run CSME Corporate H D,A v11.0 - v11.8
• Intel CSME 11.8 Consumer PCH-LP C Firmware v11.8.71.3630
  For 100/200-series systems which run CSME Consumer LP C v11.0 - v11.8
• Intel CSME 11.8 Corporate PCH-LP C Firmware v11.8.71.3630
  For 100/200-series systems which run CSME Corporate LP C v11.0 - v11.8
• Intel CSME 11.8 Slim PCH-H D,A Firmware v11.8.70.3626
  For 100/200-series systems which run CSME Slim H D,A v11.0 - v11.8
• Intel CSME 11.8 Slim PCH-LP C Firmware v11.8.70.3626
  For 100/200-series systems which run CSME Slim LP C v11.0 - v11.8
• Intel ME 10.0 1.5MB Firmware v10.0.55.3000
  For 8-series systems which run ME 1.5MB v10.0
• Intel ME 10.0 5MB Firmware v10.0.60.3000
  For 8-series systems which run ME 5MB v10.0
• Intel ME 10.0 Slim Firmware v10.0.35.1012
  For 8-series systems which run ME Slim v10.0
• Intel ME 9.5 1.5MB Firmware v9.5.60.1952
  For 8-series systems which run ME 1.5MB v9.5
• Intel ME 9.5 5MB Firmware v9.5.65.3000
  For 8-series systems which run ME 5MB v9.5
• Intel ME 9.5 Slim Firmware v9.5.4.1856
  For 8-series systems which run ME Slim v9.5
• Intel ME 9.1 1.5MB Firmware v9.1.37.1002
  For 8/9/X99/C220/C610-series systems which run ME 1.5MB v9.0 - v9.1
• Intel ME 9.1 5MB Firmware v9.1.45.3000
  For 8/9/C220/C610-series systems which run ME 5MB v9.0 - v9.1
• Intel ME 9.0 1.5MB Firmware v9.0.31.1487
  For 8/C220-series systems which run ME 1.5MB v9.0
• Intel ME 9.0 5MB Firmware v9.0.31.3488
  For 8/C220-series systems which run ME 5MB v9.0
• Intel ME 8 1.5MB Firmware v8.1.70.1590
  For 6/7/X79/C600/C210-series systems which run ME 1.5MB v8
• Intel ME 8 5MB Firmware v8.1.72.3002
  For 6/7/X79/C600/C210-series systems which run ME 5MB v8
• Intel ME 7 1.5MB Firmware v7.1.80.1214
  For 6/X79/C600-series systems which run ME 1.5MB v7
• Intel ME 7 5MB Firmware v7.1.92.3273
  For 6/X79/C600-series systems which run ME 5MB v7
• Intel ME 7 Slim Firmware v7.0.1.1205
  For 6/X79/C600-series systems which run ME Slim v7
• Intel ME 6 1.5MB Firmware v6.2.50.1062
  For 5/34xx-series systems which run ME 1.5MB v6
• Intel ME 6 Desktop 5MB Firmware v6.2.61.3535
  For 5/34xx-series desktop systems which run ME 5MB DT v6
• Intel ME 6 Mobile 5MB Firmware v6.2.61.3535
  For 5/34xx-series mobile systems which run ME 5MB MB v6
• Intel ME 6 Ignition IBX Firmware v6.0.30.1199
  For 5/34xx-series systems which run ME Ignition IBX v6
• Intel ME 6 Ignition CCK Firmware v6.0.50.1252
  For 89xx-series systems which run ME Ignition CCK v6.0.50
• Intel ME 5 Base Consumer Firmware v5.2.0.1002
  For ICH10 systems which run ME Base Consumer v5
• Intel ME 5 Digital Office Firmware v5.2.71.1048
  For ICH10 systems which run ME Digital Office v5
• Intel ME 4 TPM Firmware v4.2.30.1040
  For ICH9M systems which run ME TPM v4
• Intel ME 4 AMT Firmware v4.2.60.1060
  For ICH9M systems which run ME AMT v4
• Intel ME 4 AMT + TPM Firmware v4.2.60.1060
  For ICH9M systems which run ME AMT + TPM v4
• Intel ME 3 QST Firmware v3.2.3.1037
  For ICH9 systems which run ME QST v3
• Intel ME 3 ASF Firmware v3.2.10.1041
  For ICH9 systems which run ME ASF v3
• Intel ME 3 AMT Firmware v3.2.60.1060
  For ICH9 systems which run ME AMT v3
• Intel ME 2 QST Firmware v2.0.6.1125
  For ICH8 systems which run ME QST v2
• Intel ME 2 Mobile AMT Firmware v2.6.50.1056
  For ICH8M systems which run ME AMT MB v2.5 - v2.6
• Intel ME 2 Desktop AMT Firmware v2.2.30.1046
  For ICH8 systems which run ME AMT DT v2.0 - v2.2

B2. Power Management Controller - PMC

• Intel PMC CMP PCH-LP A Firmware v140.1.01.1005
  For Comet Lake mobile systems which run PMC CMP LP A v140.1.0x
• Intel PMC ICP PCH-H X Firmware v130.1.00.0000 (Placeholder)
  For Ice Lake mobile systems which run PMC ICP LP X v130.1.xx
• Intel PMC CNP PCH-H B Firmware v300.2.11.1022
  For 300/C240-series systems which run PMC CNP H B v300.2.1x
• Intel PMC CNP PCH-LP C Firmware v300.1.20.1026
  For 300/C240-series systems which run PMC CNP LP C v300.1.2x
• Intel PMC CNP PCH-LP B Firmware v300.1.11.1014
  For 300/C240-series systems which run PMC CNP LP B v300.1.1x

C. About Intel (CS)ME System Tools

The Intel (CS)ME System Tools are used for creating, modifying, and writing binary image files, manufacturing testing, Intel (CS)ME setting information gathering and Intel (CS)ME firmware configuration and updating. These tools are not released to end-users but only to OEMs. The software below comes only from official updates which were provided and made public by various OEMs.

Flash Image Tool: Creates and configures a complete SPI image file which includes regions Flash Descriptor Region, BIOS, Intel integrated LAN (GbE), Intel (CS)ME & Platform Descriptor Region. The user can manipulate the completed SPI image via a GUI and change the various chipset parameters to match the target hardware.

Flash Programming Tool: Used to program a complete SPI image into the SPI flash device(s). FPT can program each region individually or it can program all of the regions with a single command. The user can also use FPT to perform various functions such as view the contents of the flash on the screen, write the contents of the flash to a log file, perform a binary file to flash comparison, write to a specific address block, program fixed offset variables etc.

Manifest Extension Utility: Used to generate a 3rd party Independent Update Partitions (IUP) which are compressed and signed by an external signing tool, such as OpenSSL. The signed contents may then be stitched into a SPI/BIOS image using the Intel Flash Image Tool (FIT).

Notice: Avoid using the Windows builds of very old (CS)ME System Tools which either retrieve info (MEInfo, MEManuf, Flash Programming Tool) or modify the platform (FWUpdate, Flash Programming Tool, Integrated Clock Controller) as they may not work properly on newer operating system versions. When available, it is advised to use either the DOS or EFI builds of said very old tools.

C1. Identifying, Updating & Diagnosing Intel (CS)ME Firmware

Those who are looking to update/downgrade their firmware should use MEInfo, FWUpdate & MEManuf tools for status information, updating and functionality checking accordingly. The information & instructions below apply to these three tools only and can be found inside the full Intel ME System Tools Packages.

MEInfo: Checks that the (CS)ME is operating normally on the software/firmware level by querying the (CS)ME device on its status. Make sure it doesn't report any red errors. The yellow "GBE Region does not exist" warning is normal for systems that don't have an Intel GbE Controller, you can safely ignore it.

MEManuf: A diagnostic tool which can be used to run certain manufacturing-line tests to ensure that the (CS)ME is working properly on the hardware level. It should report a green message such as "MEManuf Operation Passed".

FWUpdate: Used to upgrade or downgrade the (CS)ME firmware and/or Independent Update Partitions (IUP) such as Intel Sensor Hub (ISH), Power Management Controller (PMC) etc. Up until ME v7, it works only with special Update (UPD) images. From ME v8 to CSME 11, FWUpdate works with the Engine Region images (RGN/EXTR). From CSME 12+, FWUpdate works with RGN/EXTR + PMC merged images, as explained at Section B. FWUpdate does not change any (CS)ME configuration settings (DATA section) which are model or system specific.

C2. Intel (CS)ME System Tools

Note: To extract some of the files below you need to use programs which support RAR5 compression!

• Intel CSME System Tools v14 r1 - (2020-01-08)
  For 400-series systems which run CSME v14
• Intel CSME System Tools v13 r0 - (Placeholder)
  For 400-series systems which run CSME v14
• Intel CSME System Tools v12 r20 - (2020-01-07)
  For 300/C240-series systems which run CSME v12
• Intel CSME System Tools v11 r29 - (2020-01-07)
  For 100/200/Z370/H310C/B365/X299/C400/C620-series systems which run CSME v11
• Intel ME System Tools v10.0 r7 - (2018-08-08)
  For 8-series systems which run ME v10.0
• Intel ME System Tools v9.5 r6 - (2018-07-31)
  For 8-series systems which run ME v9.5
• Intel ME System Tools v9.1 r7 - (2018-09-01)
  For 8/9/X99/C220/C610-series systems which run ME v9.0 - v9.1
• Intel ME System Tools v8 r3 - (2017-11-19)
  For 6/7/X79/C600/C210-series systems which run ME v8
• Intel ME System Tools v7 r2 - (2018-09-08)
  For 6/X79/C600-series systems which run ME v7
• Intel ME System Tools v6 IBX r2 - (2018-02-09)
  For 5/34xx-series systems which run ME 1.5MB, 5MB DT, 5MB MB, Ignition IBX v6
• Intel ME System Tools v6 CCK r1 - (2018-01-25)
  For 89xx-series systems which run ME Ignition CCK v6.0.50
• Intel ME System Tools v5 r1 - (2016-10-13)
  For ICH10 systems which run ME v5
• Intel ME System Tools v4 r1 - (2016-10-13)
  For ICH9M systems which run ME v4
• Intel ME System Tools v3 r1 - (2016-10-13)
  For ICH9 systems which run ME v3
• Intel ME System Tools v2 r1 - (2016-10-13)
  For ICH8(M) systems which run ME v2

D. About Old Intel MEI Drivers

You should always install the latest drivers for all 6-series & up systems, which can be found at section A. The driver versions linked below are the latest of each older Engine major branch.

Note: To extract some of the files below you need to use programs which support RAR5 compression!

D1. Old Intel MEI Drivers & Software

These packages contain the Intel MEI/SOL drivers with their respective software & system services. It is advised to install these to enable all the Engine-related functionality. It is important to install the correct package depending on your Consumer/1.5MB or Corporate/5MB system.

• Intel MEI Drivers & Software v6.2.50.1062 (ME 6)
• Intel MEI Drivers & Software v5.2.20.1030 (ME 5)
• Intel MEI Drivers & Software v4.2.0.1008 (ME 4)
• Intel MEI Drivers & Software v3.2.50.1059 (ME 3)
• Intel MEI Drivers & Software v2.6.30.1051 (ME 2 MB)
• Intel MEI Drivers & Software v2.1.22.1033 (ME 2 DT)

Note: MEI Drivers & Software v6.2.50.1062 package includes MEI Driver v6.2.50.1050. MEI Drivers & Software v3.2.50.1059 package includes MEI Driver v3.2.20.1046. MEI Drivers & Software v2.6.30.1051 package includes MEI Driver v2.6.30.1046.

D2. Old Intel SOL "Drivers" & Software

• Intel SOL Drivers & Software v5.5.1.1012 (ME 5)
• Intel SOL Drivers & Software v5.4.1.1016 (ME 4)
• Intel SOL Drivers & Software v5.4.1.1051 (ME 3)
• Intel SOL Drivers & Software v5.3.1.1046 (ME 2 MB)
• Intel SOL Drivers & Software v5.2.0.1019 (ME 2 DT)

D3. Old Intel TPM Drivers & Software

• Intel TPM Drivers & Software v5.2.20.1030 (ME 4 & 5)

D4. Old Intel MEI Driver Only

These packages contain only the Intel MEI Driver without any additional software or system services. Installing these allow only very basic Engine-related functionality. They are compatible with both Consumer/1.5MB and Corporate/5MB systems. The MEI Installer is the setup file from Intel which includes the MEI Driver but also allows easy installation and adds a Control Panel entry for quick driver removal.

• Intel MEI Driver v6.2.50.1050 (ME 6)
• Intel MEI Driver v5.2.0.1008 (ME 5)
• Intel MEI Driver v4.2.0.1008 (ME 4)
• Intel MEI Driver v3.2.20.1046 (ME 3)
• Intel MEI Driver v2.6.30.1046 (ME 2 MB)
• Intel MEI Driver v2.1.22.1033 (ME 2 DT)
• Intel AMT Driver v1.1.30.2 (AMT 1 GbE)

Note: The MEI Drivers listed above are part of the complete Drivers & Software packages found at section D1. A newer Drivers & Software package has newer Software but the actual MEI Driver may still be an older version.

Note: The MEI Installer includes the MEI Driver but allows easy installation of it. However, since we cannot always find the latest MEI Installer, it is advised to manually install the MEI Driver in case its version is newer.

D5. Old Intel SOL "Driver" Only

• Intel SOL "Driver" v6.2.50.1060 (ME 6)
• Intel SOL "Driver" v5.5.1.1012 (ME 5)
• Intel SOL "Driver" v5.4.1.1016 (ME 4)
• Intel SOL "Driver" v5.4.1.1051 (ME 3)
• Intel SOL "Driver" v5.3.1.1046 (ME 2 MB)
• Intel SOL "Driver" v5.2.0.1019 (ME 2 DT)

Note: The SOL "Drivers" listed above are part of the complete Drivers & Software packages found at section D2. A newer Drivers & Software package has newer Software but the actual SOL "Driver" may still be an older version.

Note: The SOL "Driver" is not really a driver but rather a placeholder INF file which assigns a correct device name at Device Manager and prevents the latter from showing the yellow exclamation mark of "No driver was found for this device". It's the SOLs' equivalent of Intel Chipset Device "Drivers" (= INF files).

D6. Old Intel TPM Driver Only

• Intel TPM Driver v5.0.1.1085 (ME 4 & 5)

Update of the start post:

Today (10/11/2013) I have updated the start post again.

Changelog:

1. new: Intel ME 8 Gbe 1.3M/1.5M Firmware Update to v8.1.51.1471
   Note: The Firmware Update is only for Intel ME 8 with Gbe 1.3M or 1.5M (will support many Intel 6/7 Series Chipset systems).

Credits go to Station-Drivers and especially to VirtualFred for the source files.

Here is the result after having successfully updated the ME Firmware of my Intel HM76 Chipset Mobile system:



Good luck!
Fernando

Zitat von gpvecchi im Beitrag #11

---

May someone clarify what difference are between GBe 1.3 and 1.5? Is it an "upgrade"? Does it worth to mod?

---

AFAIK the Gbe v1.5 is not an update of Gbe v1.3, both Gbe versions are designed for different systems.

EDIT: The rest of the original post has been deleted by me, because the content obviously was wrong (thanks to Florin9doi for his private comment).

Update of the start post:

Today (10/12/2013) I have updated the start post again.

Changelog:

1. new: Intel ME 7 1.5MB Firmware Update to v7.1.60.1193
   Note: The Firmware Update is only for Intel ME 7 consumer systems (will support many Intel 6/7 Series Chipset systems). Credits go to Florin9doi for the file.
2. corrected: the Gbe version informations regarding the ME Firmware packages

Credits go to Florin9doi for his informations and advices.

Good luck!
Fernando

@ udixadjus:
Welcome at Win-RAID Forum!

Zitat von udixadjus im Beitrag #14

---

CAN YOU POST INTEL ME FOR INTEL H55 CHIPSET????I NEED IT...

---

Please check the current ME version by running the appropriate MEInfo tool.

Regards
Fernando

Zitat von gpvecchi im Beitrag #19

---

is ME firmware overwritten when flashing a new motherboard bios?

---

AFAIK it depends on the flashing procedure. Look >here<.