02-14-2019 04:59 AM
I have 3 machines with docks . All take about 1 min to get into windows.
Fastboot is enabled.
At least one of them states this during boot
"(A7) Me FW Downgrade - Request MeSpilLock Failed"
02-14-2019 11:17 AM
I had the same issue. I wasn't sure if it came from the BIOS update or from the IME. But seeing this post, I understand.
I had my motherboard replaced. This was for me the fix.
02-14-2019 06:27 PM - edited 02-14-2019 06:29 PM
Intel is still trying to find a way to fix this problem that doesn't involve replacing hardware. If you don't want to wait, getting this repaired under warranty (by replacing motherboard) is certainly an option. If you're willing to wait some more, Intel may be able to find some other way. I wish I had the solution already, but I just don't know anything more at this point. Sorry for this trouble.
02-15-2019 10:15 PM
I've got the same problem since I updated the IME 1310, that messed me up and I found no way to fix it. How your Lenovo staff released the package without systematic test. Hysteretic response speed and result is oppressive. I have to say, Lenovo is disappointed me. Think about your Trace Point and IME microcode.
That is a severe fault the Lenovo made, As long as you update the IME from Vantage, congratulations, you died. The repair station would suggest you changing your motherboard, why should we deserved disassembling a brand new laptop by your fault. Does your laptops between brand new and refreshed have the same value? I strongly require the IWS extend to 3 years as the compensation.
Meanwhile, I hope an official sulation as soon as possible, at least, you should tell us waiting for the update or changing the hardware.
02-15-2019 10:33 PM
I noticed that the faulty update is no longer proposed by Vantage. This is good; at least other people won't be "infected" any more.
02-15-2019 11:48 PM
Hello to all,
I got the same problem here. I tried some ways to solve the problem, but no chance. I hope lenovo will find a solution as soon as possible. Greetings Lutz
02-16-2019 02:52 AM
02-16-2019 06:28 AM
@someotherguy. If Intel broke this through a Firmware update, then they can fix it through a firmware update. Lenovo MUST apply pressure on Intel to resolve this issue ASAP.