hi all I seem to have run into a problem after flashing the ME from v11.8.50.3460 to v11.8.50.3470 on my Maximus X Hero. When running MEInfoWin64 [from Intel.CSME.SYSTEM.Tools.v11.r11] I get the following output: "Error 82: Unknown or unsupported hardware platform". The command I ran to update the firmware in an elevated CMD prompt was:

FWUpdLcl64.exe -f 11.8.50.3470_CON_H_D0_PRD_RGN.bin

The flash went ahead successfully, the UEFI BIOS shows MEI v11.8.50.3470. What has happened? Can anyone please point me in the right direction to sort this out. I'm thinking of going back to v11.8.50.3460 but I shall hold off until someone here tells me otherwise.TIA for any help.

UPDATE: Never mind folks, I used the wrong version of MEInfoWin64!, which is strange because I would have thought that the same tool version that I used to flash the ME would also be the correct tool to check the MEI with MEInfoWin64? I used "Intel.CSME.SYSTEM.Tools.v11.r11" toolset to flash the ME but when I used the MEInfoWin64 tool from that toolset version, I got the error 82. However using MEInfoWin64 from the previous version "Intel.CSME.SYSTEM.Tools.v11.r10" I got a readoutput [made-up word] without any errors. Please see first spoiler for a partial output of MEInfo64 from "Intel.CSME.SYSTEM.Tools.v11.r10".

@plutomaniac

thank you [again] for your help. How do you run that command exactly? just on it's own or in conjunction with one of the tools e.g. with FWUpdLcl64.exe? TIA

PS why wasn't MEInfo from version Intel.CSME.System.Tools.v11.r11 not able to read the ME from my mobo [error 82]? although I updated the firmware with FWUpdLcl64.exe from that version? Why did I have to use MEInfo from a previous version [Intel.CSME.System.Tools.v11.r10] to read the updated ME? Is there a problem with MEInfo from version Intel.CSME.System.Tools.v11.r11? I find that strange ... it has never happened before with previous FW updates that I've done.

@ plutomaniac

Then there must be something wrong with how MEInfo from Intel.CSME.System.Tools.v11 r11 works on my system? Please see the screenshot. I first ran MEInfo successfully from "Intel.CSME.System.Tools.v11 r10" followed by MEInfo from "Intel.CSME.System.Tools.v11 r11". The latter keeps giving error 82 each and every time I run it???

In case you missed what I said in the OP I used FWUpdLcl64.exe from the version that the MEInfo give error 82 [Intel.CSME.System.Tools.v11 r11] to update the ME firmware from v11.8.50.3460 to v11.8.50.3470. However, I have to use "Intel.CSME.System.Tools.v11 r10" to read the me info without the error 82?

What could be the problem? Is there any command I could run to diag this error with any tool?



UPDATE:

I ran "FPTW64.exe -d spi.bin" from "Intel.CSME.System.Tools.v11 r11" which ran successfully with the following output:



However I thought I should report this as asked at the bottom of the CMD because the MEAnalyzer tool that I ran on the spi.bin file reported that the firmware is not found at the database [but I got the firmware from the first post of this thread?] :

@ Plutomaniac

I have been running it from c:\ and I have tried different names with and without spaces and from just 2 letters long to the full name of how the file un-rars. BTW talking about un-raring...interestingly enough I just discovered another bug/error. I get an error with 7zip v1805 when I try and extract only the WIN64 and WIN folders of MEInfo by either drag and drop or highlight either folder and choose "Extract"? See screenshots;


I get this error no matter where I store "Intel CSME System Tools v11 r11.rar" on my drive and no matter what I rename it to.

Next step is testing different versions of 7zip and also if there is another source/mirror for "Intel CSME System Tools v11 r11" to test it against the one I got from the 1st post of this thread. There MUST be a link between what 7zip is doing with the very folder/files that I am getting error 82 from where MEInfo is taken from. Maybe, just maybe I am getting close to solving this mystery [hopefully, soon to be mystery no more :]

Have I lost you or anyone else in this mess??

yes I certainly shall report this to Igor, it's the second bug that I have had to report, although the first one was actually a Windows 10 bug that got fixed in the April update [the cursor would jump out of the 7zip window when you click and drag with multiple files when either Horizontal and/or Vertical scroll bar was active and at its/their default position]. Thanks for your continual feedback and support :}

Hi all,

Need some help. I own a Dell Latitude E7440, which presents the error described in "https://apingxh.blogspot.com/2016/11/how-to-fix-asf2-force-off-on-dell-e7440.html" .

I've found that its current installed BIOS version is A09, and I can't upgrade to the most recent, A25. I'm able to run the executable file, the computer restarts but nothing changes. It doesn't even show a screen updating BIOS, it's a normal restart.

Looking at the first page of the topic, I've tried to run MEInfo, the result is shown below:

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


Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)

Error 9459: Internal error (Could not determine FW features information)
-----

There is no Intel Management driver installed in Device Manager. When I try to install such driver, I got a "this platform is not supported" error message.

Could you please help me?

Thanks in advance.

No, it's locked, i'm not able to dump SPI content. I've read the thread you mentioned, but I couldn't find a way to apply the info.

Great, I'm trying to use "E6. OEM/ODM Hidden BIOS-UEFI Options" method. I don't know how to find my this item:

"Download the same version SPI/BIOS image from your manufacturer or dump your own."

Thanks!