Intel (Converged Security) Management Engine: Drivers, Firmware and Tools (2-15)

Sorry - but your files are incorrect for me - my mobo need 5MB versions. Can some one clarify - is 9.1.* version from *97 chipsets? Looks like it is bad idea to use them for *87 chipsets.

The v9.1 ME Firmware is obviously running fine with some 8-Series chipset systems. Look >here<.

Working now don’t means new versions will work later. But reverting from 9.1 to 9.0 is not guaranted… So I think, adding warning in thread header about problems with downgrade will be good.

It’s already done!
Thanks for the suggestion.


I really appreciate your help! I used both Ccleaner and Wise Registry Cleaner… I tried even a sfc /scannow, to check the integrity of OS. It’s a pain in the *** to fresh install, because of latest RAID OROM that doesn’t boot from CD…

Just a small report:
>Intel ME 8 Consumer Firmware Update v8.1.52.1496< working on Z68.
Also MEI drivers 10.0.0.1204 working on Z68.



But is it recommended when overclocking? I mean, sure it would work but we’re not sure yet if it’s ideal to do so?

There is always a risk, if you are going to flash a brandnew Firmware.
So if your system is running fine with your current Intel ME Firmware and driver versions, you shouldn’t touch them.



Also tested on my P67 system. Working here, too.

DELL LATITUDE E5530 NON VPRO can anyone suggest any ideas, this laptop came to me with bios chip missing,i replaced the chip and a good known bios dump with no service tag programmed via a programmer.The machine works perfect ,until i try to flash the bios from a09 to a13 it just reboots back into windows. intel management interface is not showing in the device manager.i feel there must be something in the bios i need to edit so it matchs the intel firmware inside the chipset.thats my idea can anyone shed some light.or is there anyway i can do bios crisis,seems the key combinations dont work on these machines tried end key doesnt work,

@ PROMAN28:

As first step you should check the Intel ME components (Firmware, driver etc.) your current system is using. You can do it very easily by running the ME Info Tool for ME8 series.

@fernando thankyou but intel management itself is disabled via bios,in windows it isnt even being detected. when i try to the tools communication errors,there something in the bios which it compares to enable it.

@ PROMAN28:

In this case I would be very careful regarding the update of anything, which belongs to the Intel ME Interface.
What does the "System Devices" section of the Device Manager show? Do you see a device named "Intel(R) Management Interface" at all (maybe with a yellow mark)?

@fernando i think i might be on the right patch, seems the the tools can not locate ME device driver in dos and in windows does this means it has to have right driver in the bios for it to work i will attach both bios dumps if anyone can insert the me driver in or can suggest anything

@fernando in device manager it isnt even being detected, and when i use the me tools it coming up error cannot find me driver, suggesting bios hasnt got right driver or no driver for it.

@PROMAN28 :

Since I am not an expert regarding the Intel ME components, someone else (maybe lordkag) may help you.

@fernando thankyou i open the bios dump and looked at the ME section, and compared with the dump of bios taken out of another machine. ME part of dump is empty on my orignal bios.i then proceeded to copy the whole ME from working dump and inserted into the the orignal dump and :slight_smile: it worked. ME is in device manager i can use ME tools ,but i cant flash it it keep saying oem id incorrect any ideas fernando or anyone.

That was a good idea - congratulations!

Maybe lordkag or someone else …

@PROMAN28

Both of the files you uploaded are broken/incomplete. It is a wonder that they actually work for your machine, maybe your programmer misread the original chip. I would expect it to be 8 or 16 MB, since the hdr is 13,8 MB.

Get a proper dump from a working Dell Latitude E5530 non-vPro and flash that with a programmer. Then check the service tag of the broken PC and add/change it with one of programs floating around, some of them at MDL forums. This way the A13 BIOS should install without problems on top of A09.

If you don’t reinstate the service tag or provide a pretty good explanation for not doing that, then I won’t help you any further. But if you do this and still have problems, post here a proper dump. And please use external storage (without ads!!!) for such large files, don’t clutter the forum with them.

@lordkag thank you for your advice,and this is my first forum i joined really didn’t know if i uploaded dump files here was causing clutter i wouldn’t have uploaded them,the bios dumps i uploaded is from 2 bios chips which i read,they both are working dumps, 1 dump fits into a 8mb chip other dump into 4mb chip,the hdr file is lot bigger then these dumps i understand what you mean,but these 2 dumps are working,last quote i gave to fernando i managed to fix the issue.where i copied another dump from working machine, and copied the ME part of the dump over into my orignal dump and it did the job.the only thing confusing me, is how can i change service tag when i use the ME tool. i download firmware from the machine and using hxd im trying to figure out the service tag is just totally confused me.by the way with the orignal dell e5530 dumps i couldnt flash the bios it would shutdown and reboot but skip flash part and just go into windows.but as above by changing ME part of my bios it fixed that problem to just posting this info, if anyone else has this issue it will point them to right direction.@lordkag serivice tag is already in the chipset and set but im trying to figure out how to amend it.