Intel Management Engine: Drivers, Firmware & System Tools

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Intel Management Engine: Drivers, Firmware & System Tools

Page 1 of 358 � Page 1 2 3 4 5 ... 358 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#1 | Intel Management Engine: Drivers, Firmware & System Tools datum

Wed Nov 12, 2014 3:09 pm (Last edited: Yesterday 2:32 pm)

Intel Management Engine:
Drivers, Firmware & System Tools

Last Updated: 2021-01-22
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 v15.0 DCH drivers are usable with (CS)ME 10, 11, 12, 13, 14 & 15 systems running under Windows 10 >= 1709. The latest v15.0 MSI drivers are usable with (CS)ME 10, 11 & 12 systems running under Windows 8, 10 <= 1703 or (CS)ME 10 & 11 systems running under Windows 7. Users of systems with ME <= 9, 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. Since the Intel MEI Drivers & Software are OS version dependent, search & run "winver.exe" to determine your own.

Note: MEI Drivers & Software v2101.15.0.2080 DCH includes MEI v2047.100.0.1039. MEI Drivers & Software v2044.15.0.1951 MSI includes MEI v2040.100.0.1029.

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. Since the Intel MEI Driver is OS version dependent, search & run "winver.exe" to determine your own.

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.

B. About Intel (CS)ME, PMC, PHY & PCHC 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, LP = Low Power, N = Nano, V = Value), SKU (Consumer/Corporate/Slim/Lite/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 tools with "-verbose" parameter. Otherwise, ME Analyzer can show you all the relevant information, after loading your SPI/BIOS image, when the latter is available. If a SPI/BIOS image is not available, run FWUpdate tool with parameter "-save fw.bin" and load the resulting "fw.bin" image into ME Analyzer instead. All the firmware below correspond to a specific Platform which runs a specific (CS)ME firmware version (example: For systems running CSME Corporate H 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, PMC, PHY & PCHC 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, PMC, PHY & PCHC 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, PMC, PHY & PCHC 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 + PHY + PCHC images at CSME 13.30, RGN/EXTR + PMC + PCHC images at CSME 13+, 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. Note however that some platforms have the current TCB SVN and/or ARB SVN value permanently set/fused/burned in the Chipset so you cannot downgrade their firmware with another which has lower TCB SVN and/or ARB SVN.

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 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. After the upgrade, 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 CSME v11 PCH-LP 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 are separated between YPDM and NPDM.

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

Warning for all CSME v13+ systems: Platform Controller Hub Configuration (PCHC) firmware always targets a specific Chipset Series (ICP = 13.0, LKF = 13.30, CMP = 14.0, TGP = 15.0 etc). For example, a hypothetical 130-series system must use PCHC ICP 13.0.x.xxxx firmware, a hypothetical 150-series system must use PCHC TGP 15.0.x.xxxx firmware etc. The PCHC firmware can only be updated after being merged with a compatible CSME firmware via Flash Image Tool.

Warning for all CSME v13.30+ systems: USB Type C Physical (PHY) firmware always targets a specific Chipset Series (LKF, CMP, TGP etc) which corresponds to specific PHY SKU (LKF = S, CMP = P, TGP = P etc) and PHY Major Version (LKF S = 10, CMP P = 12, TGP P = 12 etc). For example, a hypothetical CSME 13.30 LKF S v10 system must use LKF_S_10.xxx.xxx.xxxx firmware, a hypothetical CSME 15.0 TGP P v12 system must use TGP_P_12.xxx.xxx.xxxx firmware etc. The PHY firmware can only be updated after being merged with a compatible CSME firmware via Flash Image Tool.

How to use CSME v14.1 FWUpdate Tool: At CSME 14.1, 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), Platform Controller Hub Configuration (PCHC) and USB Type C Physical (PHY) firmware, which are updated alongside the main CSE firmware. The CSME v14.1 archives below always include bare RGN or EXTR CSE firmware images so you must always stitch the equivalent PMC, PCHC & PHY firmware first, via Flash Image Tool (FIT), before using Intel FWUpdate tool. However, due to a temporary bug in the current FIT, a pre-made CSME 14.1 FWUpdate image (CSME + PMC + PCHC + PHY) is provided here.

How to use CSME v13.0, v14.0 & v15.0 FWUpdate Tool: At CSME 13.0, 14.0 & v15.0, 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) and Platform Controller Hub Configuration (PCHC) firmware, which are updated alongside the main CSE firmware. The CSME v13.0, v14.0 & v15.0 archives below always include bare RGN or EXTR CSE firmware images so you must always stitch the equivalent PMC & PCHC 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 + PCHC firmware combination for your system via FIT, you must first know your system's Chipset Series (ICP, CMP, TGP), Chipset Platform (H, LP, N, V), 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 Series, Platform, Type and Stepping, choose the correct CSME, PMC & PCHC 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, go to Flash Image Tool folder and make sure that only two (2) files exist: fit.exe and vsccommn.bin. Otherwise, delete the rest.
Run Flash Image Tool (FIT) and adjust the Chipset Platform drop-down menu at the top to either "H series Chipset" or "LP series Chipset" or "N series Chipset" based on your system's Chipset Platform. For the purposes of FWUpdate, there is no need to further adjust the Chipset 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" as well as the chosen PCHC firmware at "Flash Layout" > "PCH Configuration Sub-Partition" > "PCH Configuration File".
Click the green "Build Image For FWUpdate" button and a "FWUpdate.bin" file will be generated.
Input "FWUpdate.bin" file into ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes".
Use FWUpdate tool to flash the "FWUpdate.bin" image.

How to use CSME v13.30 FWUpdate Tool: At CSME 13.30, 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), USB Type C Physical (PHY) and Platform Controller Hub Configuration (PCHC) firmware, which are updated alongside the main CSE firmware. The CSME v13.30 archives below always include bare RGN or EXTR CSE firmware images so you must always stitch the equivalent PMC, PHY & PCHC 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 + PHY + PCHC firmware combination for your system via FIT, you must first know your system's Chipset Series (LKF).

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. LP Lite 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. Lite LP). 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 Series, Platform, Type and Stepping, choose the correct CSME, PMC, PHY & PCHC 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, go to Flash Image Tool folder and make sure that only two (2) files exist: fit.exe and vsccommn.bin. Otherwise, delete the rest.
Run Flash Image Tool (FIT) and adjust the Chipset Platform drop-down menu at the top to either "Lakefield (? Step)" based on your system's Chipset Stepping. For the purposes of FWUpdate, there is no need to further adjust the Chipset SKU.
Load/drop the chosen CSME firmware image and then input the chosen PMC firmware at "FW Update Image Build" > "PMC Image" > "PMC Binary File", the chosen PHY firmware at "FW Update Image Build" > "South PHY Image" > "PHY Binary Configuration File" and the chosen PCHC firmware at "FW Update Image Build" > "PCHC Image" > "PCH Configuration File".
Click the green "Build Image For FWUpdate" button and a "FWUpdate.bin" file will be generated.
Input "FWUpdate.bin" file into ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes".
Use FWUpdate tool to flash the "FWUpdate.bin" image.

How to use CSME v12 FWUpdate Tool: At 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 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, go to Flash Image Tool folder and make sure that only two (2) files exist: fit.exe and vsccommn.bin. Otherwise, delete the rest.
Run Flash Image Tool (FIT) and adjust the Chipset Platform drop-down menu at the top to either "H Series Chipset" or "LP Series Chipset" based on your system's Chipset Platform. For the purposes of FWUpdate, there is no need to further adjust the Chipset 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 a "cse_image_FWU_Base.bin" file will be generated.
Input "cse_image_FWU_Base.bin" file into ME Analyzer tool and make sure that "FWUpdate Support" is reported as "Yes".
Use FWUpdate tool to flash the "cse_image_FWU_Base.bin" image.

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

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

CSME 15.40 Server LP X SPI v15.40.xx.xxxx (Placeholder)
For systems running CSME Server LP X SPI v15.40
CSME 15.0 Consumer H A v15.0.21.1549
For systems running CSME Consumer H A v15.0
CSME 15.0 Consumer LP B v15.0.10.1469
For systems running CSME Consumer LP B v15.0
CSME 15.0 Corporate LP B v15.0.10.1469
For systems running CSME Corporate LP B v15.0
CSME 14.5 Consumer V A v14.5.25.1229
For systems running CSME Consumer V A v14.5
CSME 14.1 Consumer H A v14.1.52.1560
For systems running CSME Consumer H A v14.0 - v14.1
CSME 14.0 Corporate H A v14.0.47.1558
For systems running CSME Corporate H A v14.0
CSME 14.0 Consumer LP B,A v14.0.47.1558
For systems running CSME Consumer LP B,A v14.0
CSME 14.0 Corporate LP B,A v14.0.47.1558
For systems running CSME Corporate LP B,A v14.0
CSME 14.0 Slim H A v14.0.33.1125
For systems running CSME Slim H A v14.0
CSME 13.50 Atom N X v13.50.xx.xxxx (Placeholder)
For systems running CSME Atom N X v13.50
CSME 13.30 Lite LP B SPI v13.30.10.1147
For systems running CSME Lite LP B SPI v13.30
CSME 13.0 Consumer LP D v13.0.40.1738
For systems running CSME Consumer LP D v13.0
CSME 13.0 Slim N B v13.0.40.1594
For systems running CSME Slim N B v13.0
CSME 12.0 Consumer H B,A v12.0.71.1681
For systems running CSME Consumer H B,A v12.0
CSME 12.0 Corporate H B,A v12.0.71.1681
For systems running CSME Corporate H B,A v12.0
CSME 12.0 Consumer LP C v12.0.71.1681
For systems running CSME Consumer LP C v12.0
CSME 12.0 Consumer LP B v12.0.0.1062
For systems running CSME Consumer LP B v12.0
CSME 12.0 Corporate LP C v12.0.71.1681
For systems running CSME Corporate LP C v12.0
CSME 12.0 Slim H B,A v12.0.70.1652
For systems running CSME Slim H B,A v12.0
CSME 12.0 Slim LP C v12.0.70.1652
For systems running CSME Slim LP C v12.0
CSME 11.22 Corporate H B,A v11.22.80.1734
For systems running CSME Corporate H B,A v11.20 - v11.22
CSME 11.22 Slim H B,A v11.22.80.1734
For systems running CSME Slim H B,A v11.20 - v11.22
CSME 11.12 Consumer H A v11.12.80.1734
For systems running CSME Consumer H A v11.10 - v11.12
CSME 11.12 Corporate H A v11.12.80.1734
For systems running CSME Corporate H A v11.10 - v11.12
CSME 11.12 Slim H A v11.12.80.1734
For systems running CSME Slim H A v11.10 - v11.12
CSME 11.8 Consumer H D,A v11.8.82.3838
For systems running CSME Consumer H D,A v11.0 - v11.8
CSME 11.8 Corporate H D,A v11.8.82.3838
For systems running CSME Corporate H D,A v11.0 - v11.8
CSME 11.8 Consumer LP C NPDM v11.8.82.3838
For systems running CSME Consumer LP C NPDM v11.0 - v11.8
CSME 11.8 Consumer LP C YPDM v11.8.79.3722
For systems running CSME Consumer LP C YPDM v11.0 - v11.8
CSME 11.8 Corporate LP C NPDM v11.8.82.3838
For systems running CSME Corporate LP C NPDM v11.0 - v11.8
CSME 11.8 Corporate LP C YPDM v11.8.82.3838
For systems running CSME Corporate LP C YPDM v11.0 - v11.8
CSME 11.8 Slim H D,A v11.8.80.3746
For systems running CSME Slim H D,A v11.0 - v11.8
CSME 11.8 Slim LP C NPDM v11.8.80.3746
For systems running CSME Slim LP C NPDM v11.0 - v11.8
ME 10.0 1.5MB v10.0.55.3000
For systems running ME 1.5MB v10.0
ME 10.0 5MB v10.0.60.3000
For systems running ME 5MB v10.0
ME 10.0 Slim v10.0.35.1012
For systems running ME Slim v10.0
ME 9.5 1.5MB v9.5.60.1952
For systems running ME 1.5MB v9.5
ME 9.5 5MB v9.5.65.3000
For systems running ME 5MB v9.5
ME 9.5 Slim v9.5.4.1856
For systems running ME Slim v9.5
ME 9.1 1.5MB v9.1.40.1000
For systems running ME 1.5MB v9.0 - v9.1
ME 9.1 5MB v9.1.45.3000
For systems running ME 5MB v9.0 - v9.1
ME 9.0 1.5MB v9.0.31.1487
For systems running ME 1.5MB v9.0
ME 9.0 5MB v9.0.31.3488
For systems running ME 5MB v9.0
ME 8 1.5MB v8.1.70.1590
For systems running ME 1.5MB v8
ME 8 5MB v8.1.72.3002
For systems running ME 5MB v8
ME 7 1.5MB v7.1.80.1214
For systems running ME 1.5MB v7
ME 7 5MB v7.1.92.3273
For systems running ME 5MB v7
ME 7 Slim v7.0.1.1205
For systems running ME Slim v7
ME 6 1.5MB v6.2.50.1062
For systems running ME 1.5MB v6
ME 6 Desktop 5MB v6.2.61.3535
For systems running ME 5MB DT v6
ME 6 Mobile 5MB v6.2.61.3535
For systems running ME 5MB MB v6
ME 6 Ignition IBX v6.0.30.1199
For systems running ME Ignition IBX v6
ME 6 Ignition CCK v6.0.50.1252
For systems running ME Ignition CCK v6.0.50
ME 5 Base Consumer v5.2.0.1002
For systems running ME Base Consumer v5
ME 5 Digital Office v5.2.71.1048
For systems running ME Digital Office v5
ME 4 TPM v4.2.30.1040
For systems running ME TPM v4
ME 4 AMT v4.2.60.1060
For systems running ME AMT v4
ME 4 AMT + TPM v4.2.60.1060
For systems running ME AMT + TPM v4
ME 3 QST v3.2.3.1037
For systems running ME QST v3
ME 3 ASF v3.2.10.1041
For systems running ME ASF v3
ME 3 AMT v3.2.60.1060
For systems running ME AMT v3
ME 2 QST v2.0.6.1125
For systems running ME QST v2
ME 2 Mobile AMT v2.6.50.1056
For systems running ME AMT MB v2.5 - v2.6
ME 2 Desktop AMT v2.2.30.1046
For systems running ME AMT DT v2.0 - v2.2

B2. Power Management Controller - PMC

PMC EHL LP X v154.1.xx.xxxx (Placeholder)
For systems running PMC EHL LP X v154.1.xx
PMC TGP H B v150.2.10.1010
For systems running PMC TGP H B v150.2.1x
PMC TGP LP C (B) v150.1.20.1030
For systems running PMC TGP LP C (B) v150.1.2x
PMC CMP V A v140.1.00.1005
For systems running PMC CMP V A v140.1.0x
PMC CMP H A v140.2.01.1015
For systems running PMC CMP H A v140.2.0x
PMC CMP LP A v140.1.01.1010
For systems running PMC CMP LP A v140.1.0x
PMC JSP N X v130.3.xx.xxxx (Placeholder)
For systems running PMC JSP N X v130.3.xx
PMC LKF LP B v133.0.10.1046
For systems running PMC LKF LP B v133.0.1x
PMC ICP LP D v130.1.30.1051
For systems running PMC ICP LP D v130.1.3x
PMC ICP N B v130.3.10.1032
For systems running PMC ICP N B v130.3.1x
PMC CNP H B v300.2.11.1025
For systems running PMC CNP H B v300.2.1x
PMC CNP LP C v300.1.20.1030
For systems running PMC CNP LP C v300.1.2x
PMC CNP LP B v300.1.11.1014
For systems running PMC CNP LP B v300.1.1x

B3. Platform Controller Hub Configuration - PCHC

PCHC EHL LP v15.0.x.xxxx (Placeholder)
For systems running PCHC EHL LP v15.0
PCHC TGP H/LP v15.0.0.1014
For systems running PCHC TGP H/LP v15.0
PCHC CMP V v14.5.0.1001
For systems running PCHC CMP V v14.5
PCHC CMP H/LP v14.0.0.7002
For systems running PCHC CMP H/LP v14.0
PCHC JSP N v13.5.x.xxxx (Placeholder)
For systems running PCHC JSP N v13.5
PCHC LKF LP v13.30.0.1005
For systems running PCHC LKF LP v13.30
PCHC ICP LP/N v13.0.0.1005
For systems running PCHC ICP LP/N v13.0

B4. USB Type C Physical - PHY

PHY P TGP v12.14.211.2011
For systems running PHY P TGP v12
PHY P CMP v12.14.211.2011
For systems running PHY P CMP v12
PHY S LKF v10.227.203.1144
For systems running PHY S LKF v10

reply

#2 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Oct 11, 2013 9:07 pm (Last edited: Tue Jan 05, 2021 7:51 pm)

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 such as Flash Descriptor (FD), BIOS/UEFI, Intel Integrated LAN (GbE), Intel (CS)ME etc. 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), Platform Controller Hub Configuration (PCHC) 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). At CSME 12, FWUpdate works with RGN/EXTR + PMC merged images, as explained at Section B. At CSME 13.0 & 14.0, FWUpdate works with RGN/EXTR + PMC + PCHC merged images, as explained at Section B. At CSME 13.30, FWUpdate works with RGN/EXTR + PMC + PHY + PCHC 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!

CSME System Tools v15.0 r3 - (2020-12-05)
For systems running CSME v15.0
CSME System Tools v14.5 r4 - (2020-10-31)
For systems running CSME v14.5
CSME System Tools v14.0.20+ r11 - (2020-12-05)
For systems running CSME v14.0.20 or newer
CSME System Tools v14.0.11- r1 - (2020-07-06)
For systems running CSME v14.0.11 or older
CSME System Tools v13.30 r1 - (2020-12-22)
For systems running CSME v13.30
CSME System Tools v13.0 r4 - (2020-09-28)
For systems running CSME v13.0
CSME System Tools v12 r30 - (2020-12-30)
For systems running CSME v12
CSME System Tools v11 r37 - (2020-12-05)
For systems running CSME v11
ME System Tools v10.0 r8 - (2020-10-17)
For systems running ME v10.0
ME System Tools v9.5 r6 - (2018-07-31)
For systems running ME v9.5
ME System Tools v9.1 r7 - (2018-09-01)
For systems running ME v9.0 - v9.1
ME System Tools v8 r3 - (2017-11-19)
For systems running ME v8
ME System Tools v7 r2 - (2018-09-08)
For systems running ME v7
ME System Tools v6 IBX r2 - (2018-02-09)
For systems running ME v6 1.5MB, 5MB DT, 5MB MB or Ignition IBX
ME System Tools v6 CCK r1 - (2018-01-25)
For systems running ME v6.0.50 Ignition CCK
ME System Tools v5 r2 - (2020-03-10)
For systems running ME v5
ME System Tools v4 r1 - (2016-10-13)
For systems running ME v4
ME System Tools v3 r2 - (2020-03-10)
For systems running ME v3
ME System Tools v2 r1 - (2016-10-13)
For systems running ME v2

D. About Old Intel MEI Drivers

You should always install the latest drivers for all 8-series Broadwell mobile & 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.

Note: 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. MEI Drivers & Software v6.2.50.1062 includes MEI Driver v6.2.50.1050. MEI Drivers & Software v3.2.50.1059 includes MEI Driver v3.2.20.1046. MEI Drivers & Software v2.6.30.1051 includes MEI Driver v2.6.30.1046.

D2. Old Intel SOL "Drivers" & Software

D3. Old Intel TPM Drivers & Software

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.

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

D5. Old Intel SOL "Driver" Only

These packages contain 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 D1).

Note: The SOL "Drivers" for ME 2-5 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

TPM Driver v5.0.1.1085 (ME 4 & 5)

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 1 TB Sabrent Rocket 4.0, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#3 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Oct 11, 2013 10:48 pm

Update of the start post:

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

Changelog:

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

reply

#4 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Oct 11, 2013 11:28 pm

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

ASUS Sabertooth X99/USB 3.1, W10 x64 v2004 on i750, BIOS v4101, CPU Intel i7 5930K, 32GB DDR4, Asus GTX 1660TI 6GB DDR6
Two ASUS PRIME Z390M-Plus W10 x64 v2004 PCs, BIOS v2808, 16GB DDR4, one Intel i3-8400 (4 cores) + GPU UHD 630, and other one i5-9400F (6 cores) + GTX 980 4GB DDR5.

reply

#5 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Oct 12, 2013 5:19 am

Updated. Everything is Ok.

Mobo: P8Z68-V/GEN3

reply

#6 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Oct 12, 2013 4:40 pm

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

reply

#7 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Oct 12, 2013 7:01 pm (Last edited: Sun Oct 13, 2013 12:55 am)

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

reply

#8 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sun Oct 13, 2013 1:04 am

Update of the start post:

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

Changelog:

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.
corrected: the Gbe version informations regarding the ME Firmware packages

Credits go to Florin9doi for his informations and advices.

Good luck!
Fernando

reply

#9 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Oct 14, 2013 12:49 pm

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

reply

#10 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Mon Oct 14, 2013 1:07 pm

@ 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

reply

#11 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sun Oct 20, 2013 12:26 pm

Motherboard Gigabyte GA-H55M-S2 Rev. 1.3
MEI version 6.0.0.1179
how to upgrade this firmware,maybe need update because Intel Management Engine Failed to install,on device manager interjection mark intel management engine.
and startup computer too long...about 15-30 seconds.
Can you help me sir....
thanks before....

reply

#12 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sun Oct 20, 2013 1:38 pm

@ udixadjus:

AFAIK the Intel MEI driver v6.0.0.1179 is the latest for Intel 5-Series Chipset mainboards.
Maybe it will help, if you run the installer of the related Intel MEI driverpack, which is offered by Gigabyte for your board.

reply

#13 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Thu Oct 24, 2013 2:19 pm

Update of the OP:

new: Intel ME9 Firmware v9.0.30.1482 for Intel 8-Series Chipset Consumer Desktop Systems (1.5MB)
Thanks to Pacman for the source files.

reply

#14 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Fri Oct 25, 2013 10:40 pm

Stupid question: is ME firmware overwritten when flashing a new motherboard bios? AKA: do I have to reflash ME firmware after motherboard bios update? I assume no...
Thanks

reply

#15 | RE: Intel Management Engine: Drivers, Firmware & System Tools datum

Sat Oct 26, 2013 12:26 am

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

reply

Asus X552V Win10x64 20H2 shuts down but you can hear the fan still running, did the same when it had windows 7 on it. � � Deactivate Intel ME/AMT pros/cons?, ME firmware update also via Windows Update?

Page 1 of 358 � Page 1 2 3 4 5 ... 358 Page �

Please enter a reason for warning.