Page 1 of 263
#1 Intel Management Engine: Drivers, Firmware & System Tools by plutomaniac 12.11.2014 14:09

avatar

Intel Management Engine:
Drivers, Firmware & System Tools


Last Updated: 2018-05-17

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).

Intel Power Management Controller Introduction: Handles all Platform Controller Hub (PCH) power management related activities, running ARC code. 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 v12.0 drivers are usable with 8-series Broadwell mobile & 100-series or newer desktop/mobile systems (CS(ME) >= 10). Users of 9 & 8-series Haswell desktop/mobile systems (ME 9), must use the latest v11.7 drivers instead. Users of 7 & 6-series Ivy/Sandy Bridge desktop/mobile systems (ME 7 - 8), must use the latest v11.0 drivers instead. Users of 5-series or older desktop/mobile systems (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 Driver Only

These packages contain only the Intel MEI driver without any additional software or system services. They are compatible with both Consumer/1.5MB and Corporate/5MB systems. Since the software and system services are not really needed for Consumer/1.5MB systems, users of such systems should install the Drivers only (section A1). The MEI-Only Installer is the setup file from Intel which allows easy installation and adds a Control Panel entry for quick driver removal. For those who want to install the actual driver files manually via Device Manager, download the INF packages.


Note: The MEI drivers listed above are part of the complete Drivers & Software packages found at section A3. A newer Drivers & Software package has newer Software but the actual MEI driver may still be an older version. MEI-Only Installer v12.0.1097 includes MEI v12.0.1093. MEI-Only Installer v11.7.0.1069 includes MEI v11.7.0.1057. MEI-Only Installer v11.0.6.1194 includes MEI v11.0.5.1189.

Note: The MEI-Only Installer includes the "INF for manual installation" and allows easy installation of the latter. However, since we cannot always find the latest MEI-Only Installer, it is advised to use the "INF for manual installation" in case its version is newer.

A2. 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 A3).


Note: The SOL "driver" listed above is part of the complete Drivers & Software packages found at section A3. 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 SOL's equivalent of Intel Chipset INF utility.

A3. Intel MEI Drivers & Software

These packages contain the Intel MEI/SOL drivers with their respective software & system services. It's important to install the correct package depending on your Consumer/1.5MB or Corporate/5MB system.


Note: MEI Drivers & Software v12.0.1124 includes MEI v12.0.1115. 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.

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

Intel ME firmware is divided into two main categories: Consumer/Slim/1.5MB SKU for Consumer systems and Corporate/5MB SKU for Corporate systems. To understand your exact SKU, manual research on your hardware may be required first. Usually MEInfo, MEManuf (-verbose) and ME Analyzer (by loading your SPI/BIOS image) can help you sort most system specific details out.

General Notice: Be careful of what firmware your download relevant to your system. First, make sure that you know what series it is (examples: Z77 --> 7-series, B150 --> 100-series). Then run MEInfo Tool and check the "FW Version" line to determine your (CS)ME firmware version (examples: 8.1.52.1496 --> v8.x, 9.1.10.1005 --> v9.1). All the firmware below correspond to a specific series which comes with a specific (CS)ME firmware version (example: For 6/7/X79/C600/C210-series systems which come with ME 1.5MB v8).

Firmware Regions (RGN/EXTR/FWU): The SPI/BIOS chip firmware is divided into regions which control different aspects of an Intel-based system. Among others, the mandatory regions are the Flash Descriptor (FD, controls read/write access between the regions among other things), the Management Engine (CSME/ME, holds the (CS)ME firmware which has been configured for a specific system) and the BIOS. The (CS)ME firmware is neither static nor identical across different systems. Its CODE at the Engine region is always Configured by the manufacturer (OEM) as explained at Section A of the CleanUp Guide. The Type of each (CS)ME firmware Region can be either Stock (RGN, clean/stock/unconfigured images provided by Intel to OEMs), Extracted (EXTR, dirty/extracted/configured images from various SPI/BIOS) or FWUpdate (FWU, FWUpdate-targeted images generated by Intel Flash Image Tool which are usually clean/unconfigured)). The (CS)ME firmware at the system's SPI/BIOS chip is always EXTR, generated by the OEM after configuring the equivalent RGN. Never flash RGN or FWU firmware to the Engine region without first configuring them for your specific system (EXTR) via Intel Flash Image Tool. That means that the use of any general purpose firmware flasher software (Intel Flash Programming Tool, AMI AFU, Flashrom etc) or hardware (programmer), which directly reads/writes the Engine region of the SPI/BIOS chip, requires prior configuration of the (CS)ME firmware from RGN to EXTR. However, Intel FWUpdate tool does not require any prior configuration and can work with FWU images at CSME 12+ or both RGN & EXTR images at (CS)ME >= 8 platforms. FWUpdate tool uses the Converged Security/Management Engine co-processor itself to handle the update/downgrade. Contrary to general purpose firmware software (FPT etc) or hardware (programmer) flashers, FWUpdate tool works only when the system is working as intended and the Security Version Number (SVN), Version Control Number (VCN) and Production Version Status (PV) security measures are not violated.

FWUpdate Regions (FWU): Starting from CSME 12+, Intel FWUpdate tool does not work with RGN or EXTR CSE firmware images as it additionally requires the presence of Power Management Controller (PMC) firmware, which is updated alongside the main CSE firmware. For that purpose, Intel Flash Image Tool (FIT) can generate "FWUpdate Region" (FWU) images which are CSE RGN/EXTR images with stitched PMC firmware. To check if a CSE firmware is FWU, input it at ME Analyzer tool and make sure that "Firmware Type" is reported as "Region, FWUpdate". To generate FWU regions via FIT with SPI/BIOS images as input, you need to load them, set "Flash Settings > Flash Components > Number of Flash Components" to "0" and build the image. To generate FWU regions via FIT with CSE RGN/EXTR images as input, you need to load them at "Flash Layout > Ifwi: Intel(R) Me and Pmc Region > Intel(R) ME Binary File", load the compatible (SKU & Stepping) Power Management Controller (PMC) firmware at "Flash Layout > Ifwi: Intel(R) Me and Pmc Region > PMC Binary File" (as found at Section B3 below), adjust the SKU selection at the top to the equivalent "H or LP Series Chipset", set "Flash Settings > Flash Components > Number of Flash Components" to "0" and build the image. In rare cases in which generating a FWU image via FIT is not possible, you can modify CSE RGN/EXTR images to manually stitch PMC firmware but that requires CSE firmware structure knowledge. Note that any such modified CSE RGN/EXTR images will still be reported as "Region, Stock/Extracted" at ME Analyzer tool, even though they can now work with FWUpdate tool. To check if a CSE RGN/EXTR firmware region is FWU-compatible, input it at ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes". The CSME v12+ archives below always include FWU or FWU-compatible RGN/EXTR CSE firmware images.

Firmware Updates (UPD): To allow quick and effortless on-field updating of the ME firmware, Intel provides a tool called FWUpdate. Update images (UPD) are partial Firmware Regions which contain only ME "CODE" without any "DATA" (read Section A of the CleanUp Guide). They are created and used only by Intel's FWUpdate tool. Thus, they can neither be opened nor configured by Intel's Flash Image Tool. Never flash UPD firmware to the Engine region via anything other than FWUpdate tool. UPD images are not needed for 7-series or newer systems as FWUpdate can update their (CS)ME firmware with all four possible Types (RGN/EXTR/FWU/UPD). However, all 6-series or older systems must use UPD images in combination with FWUpdate in order to initiate a ME firmware update. Thus, at sections B1 and B2 below, only RGN/EXTR images are provided for 7-series or newer systems and only UPD images are provided for 6-series or older systems. For the latter, you can find the equivalent RGN/EXTR for use with general purpose firmware flasher software (Intel Flash Programming Tool, AMI AFU, Flashrom etc) or hardware (programmer) at the Intel Engine Firmware Repositories thread.

Security Version Number (SVN): All (CS)ME 8 or newer 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. This upgrade/downgrade control method applies to Intel's FWUpdate tool only and not when using a general purpose firmware flasher software (Intel Flash Programming Tool, AMI AFU, Flashrom etc) or hardware (programmer). To view the SVN value of any (CS)ME firmware, you can use ME Analyzer tool.

Version Control Number (VCN): All (CS)ME 8 or newer 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. This upgrade/downgrade control method applies to Intel's FWUpdate tool only and not when using a general purpose firmware flasher software (Intel Flash Programming Tool, AMI AFU, Flashrom etc) or hardware (programmer). To view the VCN value of any (CS)ME firmware, you can use ME Analyzer tool.

Production Version Status (PV): All (CS)ME 8 or newer firmware are defined by a Production Version Status (PV) bit 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 bit is set to Yes when a firmware is validated 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. This upgrade/downgrade control method applies to Intel's FWUpdate tool only and not when using a general purpose firmware flasher software (Intel Flash Programming Tool, AMI AFU, Flashrom etc) or hardware (programmer). To view the PV status of any (CS)ME firmware, you can use ME Analyzer tool.

Warning for 8-series systems: The 8-series desktop systems initially come with v9.0 firmware. The latter is upgradeable to v9.1 firmware (initially comes with 9-series desktop systems) 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 1 for all CSME v11 - v12 systems: Make sure you choose the correct CSME v11/v12 firmware for your system based on its Platform/Chipset (PCH) and Firmware Features (SKU). There are three CSME v11/v12 firmware SKUs: Slim, Consumer and Corporate for the bare-bones, 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: SKL/KBL/CFL-S, SKL/KBL/CFL-H, SKL/KBL(R)/CFL/CNL-U and SKL/KBL/CFL/CNL-Y. The PCH-H chipset works with SKL/KBL/CFL-S & SKL/KBL/CFL-H processors and requires PCH-H (H) CSME firmware. The PCH-LP chipset works with SKL/KBL(R)/CFL/CNL-U & SKL/KBL/CFL/CNL-Y processors and requires PCH-LP (LP) CSME firmware. So in total there are six CSME v11/v12 firmware SKUs: Consumer PCH-H, Consumer PCH-LP, Corporate PCH-H, Corporate PCH-LP, Slim PCH-H and Slim PCH-LP.

Warning 2 for all CSME v11 systems: It is generally advised to wait for your Original Equipment Manufacturer (OEM) to release a new BIOS which supports a newer CSME v11 firmware minor release. All systems which initially come with CSME v11.0, v11.5, v11.6 or v11.7 are upgradable to v11.8 firmware. In a similar way, all systems which initially come with CSME v11.10 or v11.20 are upgradable to v11.11 or v11.21 firmware respectively. In most cases, upgrading the CSME v11 to a higher compatible minor release works fine, even without a prior OEM BIOS update. However, there is always the risk that you will face compatibility issues between the older BIOS and newer CSME firmware, after which going back to your previous configuration is often very difficult. For example, if your OEM BIOS is up to date but the accompanying CSME firmware is still at v11.6, then it is generally advised to not update to v11.8 but only to latter v11.6 releases, unless you can recover your firmware in case of issues or can contact the OEM and ask for a new BIOS. Since all CSME v11.0, v11.5, v11.6, v11.7, v11.10 & v11.20 firmware are vulnerable to INTEL-SA-00086, only v11.8, v11.11 & v11.21 updates are provided below. Anyone looking for older (but vulnerable) CSME firmware should visit the Intel Engine Firmware Repositories thread instead.

Warning for PCH-LP 100-series systems: Make sure to mind the firmware PDM status which is distinguished between YPDM (Yes) and NPDM (No). PDM stands for "Power Down Mitigation" and is some sort of erratum, which is only relevant to 100-series PCH-LP systems. Thus, it is an attribute of every CSME v11.x firmware which supports 100-series PCH-LP systems. The PDM status of a firmware can be detected by ME Analyzer. It is suggested to update from YPDM to YPDM and from NPDM to NPDM. From what has been observed, flashing from NPDM to YPDM or vice versa completes successfully in most cases. However, sometimes it can cause FWUpdate errors mid-way which can usually be solved by reflashing after a reboot. The CSME v11.x PCH-LP archives below include only the latest firmware regardless of their PDM status. In cases where we have YPDM and NPDM variants of that latest version, both are included.

Warning for all CSME v12 systems: Power Management Controller (PMC) firmware always targets a specific PCH SKU (H/LP) and PCH Stepping (A, B, C, D etc). For example, a hypothetical 300-series PCH-LP Stepping B1 system must use PMC 300.1.11.xxxx firmware, a hypothetical 300-series PCH-H Stepping A0 system must use PMC 300.2.00.xxxx firmware, a hypothetical 300-series PCH-LP Stepping D2 system must use PMC 300.1.32.xxxx firmware etc.

Notice for CSE INTEL-SA-00086 vulnerabilities: After the 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 A3) and execute command "SetupME.exe -tcs -nodrv -s" via a command line prompt.

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

B1. (Converged Security) Management Engine Consumer


B2. (Converged Security) Management Engine Corporate


B3. Power Management Controller (PMC)


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).

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 FWU or FWU-compatible CSE Region 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!


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 Driver Only

These packages contain only the Intel MEI driver without any additional software or system services. They are compatible with both Consumer/1.5MB and Corporate/5MB systems. Since the software and system services are not really needed for Consumer/1.5MB systems, users of such systems should install the Drivers only (section D1). The MEI-Only Installer is the setup file from Intel which allows easy installation and adds a Control Panel entry for quick driver removal. For those who want to install the actual driver files manually via Device Manager, download the INF packages.


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

Note: The MEI-Only Installer includes the "INF for manual installation" and allows easy installation of the latter. However, since we cannot always find the latest MEI-Only Installer, it is advised to use the "INF for manual installation" in case its version is newer.

D2. Old Intel SOL "Driver" Only


Note: The SOL "drivers" listed above are part of the complete Drivers & Software packages found at section D5. 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 SOL's equivalent of Intel Chipset INF utility.

D3. Old Intel TPM Driver Only


D4. Old Intel MEI Drivers & Software

These packages contain the Intel MEI/SOL drivers with their respective software & system services. It's important to install the correct package depending on your Consumer/1.5MB or Corporate/5MB system.


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

D5. Old Intel SOL "Drivers" & Software


D6. Old Intel TPM Drivers & Software

#2 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 25.09.2013 21:31

avatar

Reserved

#3 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 27.09.2013 16:30

avatar

Update/customization of the start post:

Today (09/27/2013) I have completely rebuilt and customized the chapters B ("Intel ME Firmware Update Tools") and C ("Intel MEInfo Tools") of the thread opener.
If there should be something wrong or missing, please let me know it.

Regards
Fernando

#4 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 28.09.2013 13:30

avatar

Update of the start post:

Today (09/28/2013) I have updated the start post again.

Changelog:

  1. new: Intel ME 9.5 Gbe 1.5M Firmware Update to v9.5.13.1706 (for Intel 8-Series Chipset Mobile systems)
  2. new: Intel ME 7 Gbe 1.3M Firmware Update to v7.1.52.1176 (for older Intel Chipset Desktop systems)
  3. new: as first step of the FW update procedure the old (currently working) Intel ME Firmware image will be saved as "old.bin" (can be reflashed in an emergency case)
  4. customized: the flash procedure of the different ME Firmware Update Tools by setting unified standards regarding the flash.bat commands and by renaming the flash and image files.

Good luck!
Fernando

#5 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 08.10.2013 15:10

avatar

Update of the start post:

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

Changelog:

  1. new: Intel ME 7 Gbe 1.3M Firmware Update to v7.1.70.1198 (for older Intel Chipset systems)
  2. new: Intel MEInfo tool for ME7 systems (for older Intel Chipset Desktop systems)

Credits go to ricktendo for the source files.

Good luck!
Fernando

#6 RE: Intel Management Engine: Drivers, Firmware & System Tools by 100PIER 11.10.2013 19:40

Fernando,
I have Code Error 10 (controller can't start) in Control Panel MEI after installation of MEI driver V 9.5.15.1730.
What do you suggest ?
[[File:MEI_95151730_1.PNG|none|auto]]
[[File:MEI_95151730_2.PNG|none|auto]]
[[File:MEI_95151730_3.PNG|none|auto]]

I don't understand why because previously i got no problem..

#7 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 11.10.2013 20:07

avatar

Zitat von 100PIER im Beitrag #6
I have Code Error 10 (controller can't start) in Control Panel MEI after installation of MEI driver V 9.5.15.1730.
What do you suggest ?
I got the same error message with my HM76 notebook system running Win8.1 RTM.
This is the way I solved it:
1. Open the Device Manager, do a right click onto the "Intel(R) Management Engine Interface" and choose "Uninstall".
2. Let the device been uninstalled, bot don't check the option "Uninstall driver software".
3. Reboot.

#8 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 11.10.2013 21:48

avatar

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

#9 RE: Intel Management Engine: Drivers, Firmware & System Tools by 100PIER 11.10.2013 22:28

Fernando,
Thanks for your help.
All is working nice now after MEI Driver and Firmware updates.
Here the result:

#10 RE: Intel Management Engine: Drivers, Firmware & System Tools by cybersm 12.10.2013 04:19

avatar

Updated. Everything is Ok.

#11 RE: Intel Management Engine: Drivers, Firmware & System Tools by gpvecchi 12.10.2013 15:40

avatar

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

#12 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 12.10.2013 18:01

avatar

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).

#13 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 13.10.2013 00:04

avatar

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

#14 RE: Intel Management Engine: Drivers, Firmware & System Tools by udixadjus 14.10.2013 11:49

HELLO FERNANDO,PLEASE HELP ME....CAN YOU POST INTEL ME FOR INTEL H55 CHIPSET????I NEED IT...
THANKS BEFORE....

#15 RE: Intel Management Engine: Drivers, Firmware & System Tools by Fernando 14.10.2013 12:07

avatar

@ 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

Xobor Forum Software von Xobor