I’m getting the following error in MEInfo after updating the Managment Engine with FWupdate:
Error 86: Communication error between application and Intel(R) ME module (FWU client)
Error 81: Internal error (Could not determine FW features information)
Here’s what I did before the update:
I checked in UBU, MEAnalyzer and MEInfo what version of ME I have and if it was running normally (it was) and which Update file I needed to download for my SKU. I have a H170 Board and the tools said I needed PCH-H Corporate. Since 11.6.xx was running, I downloaded the latest 11.6.xx ME Firmware file for this SKU: 11.6.29.3287_COR_H_D0_PRD_RGN.bin
I used the FWUpdate tool in order to not lose the configuration of the Managment engine. FWUpdate completed the flashing process successfully.
I rebooted the system and checked MEInfo to see if it worked. I got the error above.
I then used the Flash Programming Tool to dump the currently flashed image to see what was going on. I could dump successfully and loaded the file into MEAnalyzer - please see the screenshot below I attached.
From what I can see, everything updated correctly and the latest Managment Engine is in there. Comparing with the unmodified rom from the Manufacturer, I selected the correct SKU and updated to the latest version.
Therefore I tried FPTW64 -greset. This has not fixed the problem. I have never used any other flashtool to modify the ME Region, only FWUpdate.
Does anyone have an idea what went wrong? The system appears to be running fine and the managment engine driver is loaded in device manager (I don’t have any errors or missing devices there).
How can I fix this? Can I theoretically revert back if I flash the unmodified Bios Rom in AFUWin if I check to completely overwrite the Managment Engine Area?
|addpics|h3l-1-45e9.jpg|/addpics|
I don’t see anything wrong with the steps you followed. Good job in your research before flashing. My best guess is that a -greset is needed. Try a manual greset. Shutdown the system and remove all power (AC + Battery, RTC is ok) for 1 minute. Does that solve the issue?
Unfortunately it did not solve the issue, MEInfo output is still:
Error 86: Communication error between application and Intel(R) ME module (FWU client)
Error 81: Internal error (Could not determine FW features information)
The Intel Managment Engine Interface shows up in device manager and appears to be running correctly and there are no yellow exclamation marks for borked devices.
I also updated to the latest ME Driver just now using the installer MEIsetup.exe. The installer didn’t show any errors and the driver is running.
I also checked the Windows Event Log for any errors or warnings pertaining Managment Engine. Nothing.
The CMOS was completely cleared after I powered on the system, so I think I did leave it without AC and Battery long enough (took a bathroom break and a quick prayer).
Is it dangerous to update to a higher ME version, i.e. from 11.6 to 11.7 using FWUpdate? I just downloaded the 11.7.0.3290 for the PCH-H Corporate SKU in addition to the 11.6.29.3287 I flashed using FWUpdate. Maybe this would fix things (I haven’t flashed anything yet)?
Thanks for your help.
Edit: I ran the Intel Managment and Security Status GUI Application and dumped the system information from there:
Systeminformationsbericht erstellt am: 08/27/17 14:48:11
Systemname: <removed>
[Intel(R) ME - System Report (C:\Users\xxx\AppData\Local\Temp\SystemInformation.nfo)]
Item Value
Intel manageability system information Generated by IMSS at 8/27/2017 2:45 PM
[Host Information]
Item Value
Operating System Name Microsoft Windows 10 Pro
Operating System Version 10.0.15063 Build 15063
System Manufacturer MSI
System Name <removed>
System Model MS-7978
Processor Intel(R) Core™ i7-6700 CPU @ 3.40GHz, 3,41 GHz, 4 Core(s), 8 Logical Processor(s)
BIOS Version American Megatrends Inc.2.C0
LAN DeviceID PCI\VEN_8086&DEV_15B8&SUBSYS_79781462&REV_31\3&11583659&0&FE
LAN Driver 12.15.25.6
WLAN DeviceID NA
WLAN Driver NA
[Intel(R) ME Information]
Item Value
ME Control Mode NA
Provisioning Mode Pre Provisioning
BIOS boot NA
Last ME reset reason Global System Reset
System UUID 00000000-0000-0000-0000-000000000000
Local FWUpdate NA
Power Policy Desktop: ON in S0, ME Wake in S3, S4-5
Cryptography Support NA
[FW Capabilities]
Item Value
Intel(R) Capability Licensing Service NA
Protect Audio Video Path NA
[Components Information]
Item Value
MEBx Version NA
FW Version 11.6.29.3287
LMS Version 11.6.0.1036
MEI Driver Version 11.7.0.1032
MEI DeviceID NA
SOL Driver Version NA
SOL DeviceID NA
[Network information]
Item Value
LAN MAC Address <removed>
LAN Configuration state DHCP
LAN Link Status Link Up
LAN IPv4 Address 0.0.0.0
LAN IPv6 Enablement NA
WLAN MAC Address NA
WLAN Configuration state NA
WLAN Link Status NA
WLAN IPv4 Address NA
WLAN IPv6 Enablement NA
[Components Information] reflects the updated FW Version correctly. The [Intel(R) ME Information] section looks like the configuration data is no longer there?
I am happy to report that the issue has resolved itself apparently - although I don’t know how. I had to leave my house for 3 hours and put the system in standby. After I returned, I woke it up and ran MEInfo again, hoping to find some command line switch in order to troubleshoot my problem.
I received the output in the screenshot attached to this post. I assume that ME is now running normally and fully operational?|addpics|h3l-2-88ec.jpg|/addpics|
Yes, everything is just fine, as expected. It was a matter of reset, those 3 hours did it or maybe IMSS kick-started it again. You’re good to go. Once again, good job researching what you need to do - it’s not common. 
Thank you for your help and kind words. The latter may have been misplaced as I just discovered an oversight of mine: I inadvertantly downloaded and used Intel ME System Tools v11.7 r1 instead of Intel ME System Tools v11.6 r16
So, in essence, I used FWupdate from the 11.7 System Tools to update a 11.6 Managment Engine rom. It doesn’t appear to have caused any damage because the system is running normally - probably because 11.7 ME is also running on some 100 Series Chipsets which I have (H170).
Just to be sure, I downloaded the correct System Tools v11.6 for my system and ME version and flashed the 11.6 ME Rom again with FWupdate -allowsv switch. The flash went fine, as did the last one.
That was nothing as far as mistakes are concerned, especially when you see people that use Flash Programming Tool instead of FWUpdate, try to update from ME 9.1 to 11.7, download the completely wrong System Tools etc. Theoretically, 11.7 is a direct upgrade to 11.0 so the same applies to the tools. Sometimes users may see some warnings due to certain differences when miss-matching ME 11.x firmware and tool versions (MEInfo & MEManuf especially) but they always work. In the end it doesn’t really mattered that you used 11.7 but if you stick to 11.6 FW, then yes it is better to use 11.6 tools. You didn’t need to reflash the ME with 11.6 FWUpdate but it doesn’t hurt either.
That is comforting to know, thanks for assuaging me. Just to clarify: it is still not advisable to upgrade within minor ME versions, i.e. flashing 11.7 ME when the OEM ships 11.6.xx in the BIOS image?
I am sort of tempted to go to the latest version, even though I don’t have any problems with the system.
It’s preferable for your OEM to have already released a newer BIOS/SPI update which includes 11.7 firmware. No problems have been reported from people that upgrade regardless but the general rule of thumb still applies.