Does using Asus Ezflash from the UEFI bios updates ME ? because that's I always update my bios. Are there specific way ME is getting updated ? from Asus or other company Windows Bios Updater ? or Asus FlashBack and etc other companies ?

Hi,
I reinstalled windows and can't understand which intel Chipset Driver and intel Management Engine Interface I should install?

System: xps 13 (chipset: intel 7 series [QS77 Express]/C216)

Thanks

Zitat von gihan im Beitrag #2584

---

Zitat von gihan im Beitrag #1606

---

bro i have dell inspiron 7537(intel i7(4500U) HM87 ,laptop and i have updated my me firmware using this guide and i'm currently on v9.5.45.1922 and now i have bios update on dell site which is A13 (currently i'm on A12 which is old) and when i try to update bios it says me firmware is newer than gonging to flash ,,,and it exits !!!!!
please help me to fix this

---

merry christmas to you all guys :)
last time you helped with this problem when updating bios A12 to A13 !!!!(thanks ),
but unfortunately this happens again when updating A13 to A14 in my Dell system ,please help
new bios link:-http://www.dell.com/support/home/us/en/1...n&categoryId=BI

---

Hi guys.

This thread is 182 pages long so I didnt read all of it. but I did read main posts and warnings etc.
Im new at this, have some idea what Im doing but never done this bit before. So some guidance or help please?

Yesterday for no apparent reason (there were no drivers of this nature installed or upgraded), I get this error/notification just after POST

(A7) Me FW Downgrade - Request Me Spilock Failed

The system boots fine, Ive not yet taken steps to try remedy this... So please some advice.

Now, if I go the root of firmware upgrade, can I just grab the Intel ME 11.6 Consumer PCH-H Firmware v11.6.20.1221 and flash that as is?
Ive no idea how to modify firmwares or flashing this type of firmwares, but certainly would like to get rid of that notification.


Ive analysed by system (Asus TUF Mark 1 + kaby lake i7-7700K (socket 1151) with the MEInfoWin64 r6 the result is as below.



If there is any other information you guys need let me know.

Really appreciate this guys, thanks in advance

atomota

Zitat von plutomaniac im Beitrag #2730

---

@ atomota:

This is a brand new desktop motherboard so this is what you should do:

1) (Re-)Apply the latest BIOS from ASUS as provided at their site via the in-BIOS menu
2) If the error persists, try running Flash Programming Tool with parameter fptw -greset
3) If the error persists, contact ASUS support

---

Anyone have any advice at all other than whats been said?

Sorry to seem impatient but, Im out of ideas and web results dont yield anything that seems to work or has nothing to do with Asus anything. The explanations to what that message means are also no clew to the possible causes hence no solution gleamed thus far.

EDIT

Reading http://forums.aria.co.uk/showthread.php/...-SPilock-failed seems to indicate a reflash is needed for ME, so again I go back to my first post, as Ive simply no idea how to mod the ME FW for this mobo or if I just flash the one thats on the 1st post without modifications...

Also not being familiar with tools doesnt help...

:(

Thx for repIy,

I managed to speak to someone at Aus live Chat Germany (useless), but they will offer RMA, tbh Im not interested in RMA or downtime longer than 2 hours as this is a critical system, therefore its cheaper to buy a new board replace it and burn the old.

I havent tried to flash anything ME related, Or even touched anything ME related until you asked me to do the -greset, the only thing Ive updated was the the board bios from 0701 to 0801, which neither have the issue, then suddenly out of the blue this msg appears.

so what youre saying is Im stuffed without a hw programmer ;)

Ive reported the issue after the live chat, to Asus, as a form of complaint, because theres no other way to get to level 2 support, level one's reason for existing is (it seems) to make you lose the will to live.

Ill have a read of those posts you suggest, thank you so much for pointing, if for no other reason but to further my education in this matter.
I dont get that 2nd message though Error sending End Of Post message to ME, so its not a OS boot stopper.

In meanwhile I would like to either reflash the ME only or if thats not possible get another board, replace it and hope Asus release a bios with a fix, Im not holding my breath.

What a waste of time though in 2017 youd think resolving something like this would be simple, yet its like the dark ages, which is probably why your avatar is, Don Quixote de'la Mancha and his trusted Rocinate.

Zitat von plutomaniac im Beitrag #2735

---

Yeap, as I said, BIOS related. That's what I've observed as well from past experience.

---

Zitat von plutomaniac im Beitrag #2735

---

Well you can try to see if you have read/write access to the ME region but don't get your hopes up as it's common practice and an Intel recommendation to do the opposite for security purposes. Just run "fptw -d spi.bin" command and if you see CPU Access Error then you cannot do anything via software. I can already see from the MEInfo report you posted that it is locked so that's a bust too. Another way to enable read/write access is by doing the "pinmod" which requires shorting two pins of the audio chip while the system boots but in your case it's not possible because the board has a) a shroud and b) the audio chip has an EMI shield which does not allow pin shorting. Now that I think about it, the SPI chip is probably also under the board shroud so you wouldn't be able to get to it without first going through the trouble of removing that, let alone buying and using a programmer.

---

Zitat von plutomaniac im Beitrag #2735

---

That error should not cause any actual issues to the system, meaning that you can use it. It must be that ASUS has messed something up and the BIOS is trying to restore an older ME firmware version which is not possible as long as there is no read/write access there (locked SPI Flash Descriptor, FD) and thus the "Request Me Spilock Failed" message.

---

Zitat von plutomaniac im Beitrag #2735

---

The KBL boards are new so such bugs can happen. ASUS should fix it soon enough, hopefully. You can try updating the ME via FWUpdate as well just in case this will help the BIOS get over it. Who knows. I assume you have tried doing a clear CMOS, right?

---

Zitat von plutomaniac im Beitrag #2735

---

I don't honestly remember how I ended up using that avatar years ago but that's news to me. Ha-ha, thanks for letting me know.

---