I am stumped. I copied the folder Local-Win64 to C drive and it has the update renamed to ME.BIN in it.When I run the Command Prompt as Administrator and type in C:\Local-Win64 I get Local-Win64 is not recognized as an internal or external command, operable program or batch file.
@ NIK1:
You have to navigate into the folder C:\Local-Win64 by using the DOS commands (CD = change direction etc.), before you can execute the Firmware Update command.
I finally got it to update.I checked in the bios and it now shows 8.1.5.2.1496,before it was 8.1.0.1248.The Asus sabertooth downloads site has a firmware update for Intel Management Engine Firmware upgrade program
For better WindowsÂŽ 8 compatibility, this tool will update the IntelÂŽ Management Engine(ME) firmware to 8.1.
Before using the tool, make sure the Intel Management Engine Interface Driver is installed and follow the simple instruction.
1.Download and extract the file to a folder
2.Double click the MEtool execution file to run the updating tool
3.Follow the tool instruction to complete updating
*During updating, DO NOT shut down or restart system to prevent an incomplete update. Inside the unzipped folder is Data.BIN .I deleted this file and replaced it with the 1496 ME.Bin.I renamed the me.bin to Data.bin and ran the MEtool.exe.It ran fine updating the firmware to the 8.1.5.2.1496.I will attach the Asus Mei Firmware update tool for you to check out.
IntelME81_Updating_Tool_V10001.zip (1.73 MB)
The Command Prompt is the DOS Box. If you want to change the directory, you have to use the "cd" command.
By the way: If you would have typed "C:\Local-Win64\FWUpdLcl64.exe -f ME.BIN", everything would have been fine.
Coming in the near future:
â ME Analyzer tool written by me with full ME2-10 & TXE support
â New ME2,3,4,5,6 firmware based on all SKUs
â ME Firmware Repository (237 firmware to date)
â TXE Firmware Repository (15 firmware to date)
Updates:
Updated at ME System Tools v2.x: FWUpdate (DOS) from v2.1.0.1031 â v2.1.0.1036
Added at ME System Tools v3.x: MEBx Release Notes v3.0.2.0004
Added at ME System Tools v4.x: ASF 2.0 Tools
Fixed at ME System Tools v4.x: Flash Image Tool v4.1.0.1031 instead of 4.1.3.1031 (wrong PE description)
Added at ME System Tools v6.x: FITC + ConfigWizard v6.0.0.1184 (for ConfigWizard use only)
Added at ME System Tools v6.x: Intel ME Ignition Firmware Introduction (good read, user friendly)
Updated at ME System Tools v6.x: MEInfo (DOS) from v6.0.30.1202 â v6.2.0.1022
Added at ME System Tools v7.1: MEInfo (Windows64) v7.1.50.1166
Updated at ME System Tools v7.1: MEInfo (DOS) from v7.1.30.1139 â v7.1.50.1166
Added to ME System Tools v8.1: MEBx Release Notes v8.0.0.0066
Added at ME System Tools v8.1: Intel Management Engine 8.x Manufacturing (must-read)
Added at ME System Tools v8.1: Intel Management Engine 8.x Introduction (ME8 + MEBx guidelines)
Updated at ME System Tools v8.1: 5MB FW Bring Up Guide from v8.0.20.1513 â v8.1.0.1265
Updated at ME System Tools v8.1: 5MB FW Release Notes from v8.0.20.1513 â v8.1.0.1265
Updated at ME System Tools v9.0: FWUpdate (Local-DOS) from v9.0.21.1452 â v9.0.22.1467
Updated at ME System Tools v9.0: FWUpdate (Local-EFI) from v9.0.21.1452 â v9.0.22.1467
Updated at ME System Tools v9.0: MEInfo (DOS) from v9.0.21.1452 â v9.0.22.1467
Updated at ME System Tools v9.0: MEInfo (EFI) from v9.0.21.1452 â v9.0.22.1467
Updated at ME System Tools v9.0: MEInfo (Windows) from v9.0.21.1452 â v9.0.22.1467
Updated at ME System Tools v9.0: MEInfo (Windows64) from v9.0.21.1452 â v9.0.22.1467
I would like to ask a question about IME. I recently did an install of Windows 7 64bit to my nephewâs system and I went to see if I could
update the IME on his board and the IME is NOT listed in the device manager anywhere that I can see. I was under the impression that
99% of Intel chipsets had this as a part of them.
The MB is a GB GA33M DS2R and it has the latest BIOS, version 9a dated 2009. 1. Is this some kind of silent install? or 2. Is it that this
ICH9R chipset doesnât use IME? Any ideas would be very helpful. 
@Pendaws :
i think ich9r (g33 chipset?) Should have heci driver3.0 and me firmware 3.0, But I think the system has enough built-in version, even if it is a newer version, but because it is too long and hard to find.
Itâs funny that you asked this now, I added support for all ME3 SKUs the day before yesterday at my tool. As I said at my previous post, soon I will add all update images for ME2,3,4,5,6 that are currently not listed or have a wrong name.
ME3 (ICH9, Desktop) has 3 SKUs: AMT, ASF or QST. Apart from HECI (called MEI the last years) driver communication, updates could be done via direct PCI up until ME6 days. So itâs not necessary to have a HECI driver on your system, especially for an entry-level (and optional according to ICH9 datasheet) SKU such as QST.
Your Gigabyte boardâs latest BIOS (F9a) has QST firmware v3.0.1.1104:
The latest ME3 QST UPD image I have is v3.2.3.1037:
When I release the new ME3 SKUs and since itâs hard to find ME3 users nowadays, can you try it with FWUpdate and let me know how it goes?
Thanks for the quick reply. I had looked at the BIOS file but, not with the tool you used. I just checked out the BIOS file with CBROM.
I will wait until I see you have the new file and try the update, thanks again.
Makes sense, these tools (MMTool, CBROM etc) deal with (scan) only the BIOS region of the SPI flash. The SPI flash (chip) consists of 5 regions: Flash Descriptor, ME, Gbe, BIOS & PDR. We call it BIOS image to make our life easier but BIOS itâs actually one region of the SPI flash image, ME is another. Iâll let you know when the new firmware is up by tagging you (@username).
Also, ME System Tools v7.1 was reuploaded just now due to a text mistake at Tool_Version.txt file. Itâs MEInfo that now has a Windows x64 version (MEInfoWin64), not FWUpdate.
Well I followed plutomaniac advice and updated my FW Version to: 8.1.52.1496 (which is the latest for my X79 MSI Big Bang motherboard). It was easy to do and MEManuf passed the test.
Now I am wondering; what drivers should I download now?
FW Version: 8.1.52.149
MEI Driver Version: 9.0.0.1287 (current one installed)
If I look at the MSI website in the download section of my motherboard and Windows 8, the latest driver set is: 9.5.15.1730
On here I found an even newer set: 9.5.24.1790
//update
Well decided to install the latest driver version: 9.5.24.1790
Rebooted and ran MEInfo, which now reports:
FW Version: 8.1.52.1496
MEI Driver Version: 9.5.24.1790
Also ran MEManuf and it passed the test. Guess I am good.
Hello
Intel ME firmware 9.5.45.1922 1.5MB & 5MB
http://www.station-drivers.com/index.phpâŚx/Serie-9.5.x/
@HHawk : Install the latest driver v10.0.30.1054
@Pacman : Thank you for the new ME9.5 firmware (and thank you Lenovo as well I guess)
@Pendaws : Check the ME3 QST firmware update and let me know how it goes
Updates:
NEW! Intel ME6 Consumer Ignition Firmware v6.0.50.1252
NEW! Intel ME5 Consumer AMT Basic Firmware v5.2.0.1002
NEW! Intel ME4 Consumer TPM Firmware v4.2.30.1040
NEW! Intel ME3 Consumer QST Firmware v3.2.3.1037
NEW! Intel ME2 Consumer QST Firmware v2.0.6.1125
NEW! Intel ME5 Business AMT Pro Firmware v5.2.50.1039
NEW! Intel ME4 Business AMT + TPM Firmware v4.2.60.1060
NEW! Intel ME4 Business AMT Firmware v4.2.60.1060
NEW! Intel ME3 Business AMT Firmware v3.2.60.1060
NEW! Intel ME2 Business AMT Mobile Firmware v2.6.50.1056
NEW! Intel ME2 Business AMT Desktop Firmware v2.2.30.1046
[[File:ME_Analyzer_AMT+TPM.PNG|none|auto]]
Please read the sort description below every ME firmware in order to see if your system is compatible. After research this is it:
ME2 Desktop ICH8 SKUs: AMT, QST (2.0 & 2.1 & 2.2)
ME2 Mobile ICH8M SKUs: AMT (2.5 & 2.6)
ME3 Desktop ICH9x SKUs: QST (optional)
ME3 Desktop ICH9DO SKUs: ASF, AMT
ME4 Mobile ICH9M SKUs: TPM
ME4 Mobile ICH9M-E SKUs: AMT, AMT + TPM
ME5 Desktop ICH10D SKUs: AMT Basic
ME5 Desktop ICH10DO SKUs: AMT Professional
ME6 Desktop SKUs: Ignition, 1.5MB, 5MB Desktop
ME6 Mobile SKUs: Ignition, 1.5MB, 5MB Mobile
ME7-ME10 SKUs: 1.5MB, 5MB
Note: The direct tool links (MEInfo, FWUpdate) that were recently uploaded with the full packages, are not updated yet.
It is? I didnât know I could go beyond. v9.5. Anyways thank you will install it now remotely. 
Oops⌠completely missed:
I also see Intel MEI Drivers & Software v10.0.38.1036 for 1.5MB systems complete installer package
It seems that version is higher than Intel MEI Drivers v10.0.30.1054 for manual Have Disk installation?
Or does the installer include that version? I will check it myself in the meantime. TY
The complete Intel MEI Drivers & Software package v10.0.38.1036 contains the Intel MEI drivers v10.0.30.1054 and no newer ones.
We do not really recommend to install the Intel ME Software.
So, if I understand correctly; itâs better to install the drivers by hand (from A1-post) instead of using the complete installer (from A2-post), right?
Never installed it by hand before though.
I checked my home pcâs Device Manager; so I should only update "Intel (R) Management Engine Interface" with have disk?
Just that single device and nothing else?
In regards not using the installer; is that because the installer is meant for NUC systems?
Yes!
Yes!
You can run the installer, if you want, but this way you will get a lot of things installed, which are not very useful for the "normal" users, but may drop your system performance.
Thanks for the explanation Fernando
Updates:
NEW! ME9.5 Firmware 1.5MB from v9.5.41.1904 â> v9.5.45.1922
NEW! ME9.5 Firmware 5MB from v9.5.41.1904 â> v9.5.45.1922
Note: VCN was raised from 8 to 9, you cannot downgrade to anything below v9.5.45.1922 firmware once updated.
* The individual tool links (MEInfo, FWUpdate) are now updated according to the latest news.
A small addition: ME software is not really useful for 1.5MB SKUs, so in such systems install the driver only via the Have Disk Method. Users of 5MB SKUs must install the software package for full AMT, LMS, SOL, KVM etc functionality. In this case, indeed itâs not necessary for his 1.5MB system.
Updates:
Added at ME System Tools v7.1: Flash Image Tool v7.1.20.1119
Added at ME System Tools v7.1: Flash Image Tool v7.1.11.1069
Added at ME System Tools v9.5: UpdParam (DOS) v9.5.0.1225
Added at ME System Tools v9.5: Configuration Tools v9.5.0.1225
Added at ME System Tools v9.5: 5MB FW Bring Up Guide v9.5.0.1225 (11/2012)
Added at ME System Tools v9.5: 5MB FW MEBX User Guide v0.5.2 (11/2012)
Added at ME System Tools v9.5: AMT 9.5 OEM WebUI Guide v0.5 (10/2012)
** Before you use FITC v7, read the WARNING document first, attached below as well.
Problem: For some years now it was known that some versions of FITC v7 produced corrupted ME images. That is not exactly true. It seems that after some point (v7.1.20.x and above probably) Intel changed the way some FITC settings are written in the firmware binary image. So if you try to load an image with the ânew methodâ at a FITC version that does not support it, errors will occur and corruption if you flash such a built image.
Reproduction: The issue occurs only when loading FITC-dirty (modified, extracted-from-BIOS) images. It does not occur with stock Region images from Intel because these have FF padding at these settings initially. The first time a stock RGN image is imported in FITC this FF will be replaced with the appropriate settings and their binary/hex code in the image. This binary/hex code in the image changed after some point though making certain extracted/modified firmware incompatible with older FITC releases.
Solution: For those EXTR images, I have included two FITC versions at the latest v7.1 package. Read the WARNING document and be careful to avoid errors and thus corruption.
WARNING.pdf (79.5 KB)