@gpvecchi

Let me add a few things. The author of FTK is CodeRush and the site is this. It was mostly designed for ASUS boards, which use the module FD44820B- to store these informations. Any .bat that uses FD44Cpr.exe on other boards will probably fail, because of not finding ASUS signature and storage.

Edited: only biosrefl.bat and reflash.bat should fail on non-ASUS boards, because they rely on FD44820B- providing some data. GbErefl.bat will work because it reads the MAC from the backup it takes. But this requires that all regions are unlocked. So I still say that the next command should be tested first.

This is my question: why not use "fpt -rewrite -savemac -savesxid -gbe -f gbe.bin" instead, which should work on all boards?

And for Fernando's question: the GbE region seems to store info like MAC address, ID, name/presentation of Lan controller. So it is best to have the latest/cleanest version corresponding to your board.

Zitat von lordkag im Beitrag #213

---

@kevindd992002

I have tried the new 10.x package on my PM45 and the SMBus driver is not working, preventing sensors to read the temperature on my RAMs. Luckily I have the Synaptics touchpad drivers, which installs its own real driver. So it is best to stay with 9.x on older hardware.

---

Zitat von Fernando im Beitrag #218

---

Zitat von kevindd992002 im Beitrag #217

---

So will installing the latest 9.x package with the -overall switch fix the issue if you already went ahead and tried installing v10.x?
And any computer using 2nd gen Intel core is considered a newer platform that v10.x supports, correct?

---

Are you speaking about the Intel Managment Engine Drivers & Software Sets or the Intel Chipset Device Software Sets ("INF Update Utilities") v9 and v10?
Both contain completely different things. The topic of this thread is the Intel Management Engine Interface.

---

Zitat von lordkag im Beitrag #213

---

@tObber166
The new 9.1.x ME firmware has a new chipset / SKU version. The updater detects this new version and prevents any downgrade. Why it worked in the first place, it is a different question. Try to flash an original BIOS or use FPT.

---

@lordkag Thanks for updated infos!
I tried your updated manual remove of Intel drivers... No success... In particular I noticed that I have a very few of that entries, just some reg value.

@tObber166
@KuDeSnik33ra

Try the package corresponding to your board, at your own risk. I assume you know how to flash them, so please avoid "how to..." questions. They are compiled to that specific SKU, rather than an empty one.

tObber166 might also be in luck with other methods, since he has provided details about his board. First try flashing a BIOS file with UBF. It will most likely be pointless, because I don't think it will touch the ME region. Then try with "fpt -rewrite -me -f me.bin". Your board seems to have all regions unlocked, but I could be wrong and the BIOSLock is set. You can also try flashing a BIOS file using afuwin/afudos with the /ME command, which will flash the ME region - one warning though, better remove the capsule header. The last attempt would be to erase the ME region and then flash a new one, but this is dangerous without a programmer to recover (and pointless when you have a programmer to flash the full chip).

Please download the packages as soon as possible, because I plan to remove them to avoid cluttering the forum.

Edited: as promised, packages removed. The Q87 package was wrong from the start, since I had forgotten that it needs a 5MB firmware and not a 1.5MB one. It is also better to use FTK from here, since it packs some nice .bat files to avoid typing all commands. Some warnings: when flashing the ME using fpt, provide either a bios file or a full 1.5/5M ME file, not the small saved old.bin. Also, some ASUS users might watch for a new BIOS region protection.

@gpvecchi

At least we tried. Did you also cleaned the reg hives with CCleaner, to remove all remaining related keys? I even managed to remove a broken Office using the manual way, repairing .NET framework installation, correct some nasty bugs related to slui.exe, remove RST and MEI drivers, re-register broken dll etc...

I did also used procmon (Process Monitor) sometimes, but the important thing is to have a strong will and follow all connections. At this point, I think you are only left with a clean install.

Thanks for the files! I have successfully reverted to 9.0.* versions using FTK. Unpack archive to DOS bootable flash, place stock bios file as bios.bin - boot to this DOS - exec merefl.bat for ASUS, merefl_ga.bat for Gigabyte. For me everything works ok, BUT there can be problem with ASUS - write protection in BIOS, there is info in the internet how to remove protection with FTK. On my GA-Q87N there is no protection.

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.

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.

Zitat von lordkag im Beitrag #224

---

@gpvecchi

At least we tried. Did you also cleaned the reg hives with CCleaner, to remove all remaining related keys? I even managed to remove a broken Office using the manual way, repairing .NET framework installation, correct some nasty bugs related to slui.exe, remove RST and MEI drivers, re-register broken dll etc...

I did also used procmon (Process Monitor) sometimes, but the important thing is to have a strong will and follow all connections. At this point, I think you are only left with a clean install.

---