I'm sorry to hear about the disease, I understand why it would be difficult to do this constantly. Forget about that then, if the software solutions do not work, you should contact HP.

The link that lordkag mentioned is this one:

http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5056910&swLangOid=8&swEnvOid=4060
 

Check BIOS-Tools which has one download and Diagnostic which has two downloads.

So what BIOS version did you have before flashing F.61? We could try going back to that version in case it's an HP screw-up with some systems and newer bios releases.

Ok, you now have installed the HP recovery partition etc. I think lordkag implied that it's needed for the HP Flash Utility to work properly. Maybe that's why you were having trouble updating to F61 in the past.

Since you had F60 and it worked, can you try downgrading to it via the official HP package? Hopefully such a small downgrade is allowed.

Yes, HP UEFI Support Environment & HP BIOS Update UEFI which are both responsible for BIOS updating as well.

I don't know how the HP update system from the hard drive works. After downloading sp70943 (F60), why not simply run HPQFlash?

You can check what BIOS you have now from inside the BIOS if you are not certain. Otherwise I guess you can dump the bios using fptw -bios -d bios.bin and check manually by searching for $SIG with a hex editor.

If you have indeed rolled back to F60 and the problem persists, it's some kind of BIOS corruption. Other systems are having this issue so it must be HP's fault one way or the other.

The Flash Descriptor is locked so we cannot reflash the ME Region just to test if that's the issue (don't think so, the problem occurred with a BIOS update at which the ME was not touched at all).

The only thing I can think of would be to reflash the clean HP BIOS region as I said here which I don't think will cause issues other than loosing some serial numbers etc but I cannot guarantee that.

If these do not bring results, only HP may be able to help.

@ megatron:

You are right, you can use ME Analyzer to view your current firmware & driver versions. There is a separate tool provided called MEA_Info which does exactly that. You can run this via the MEA_Run executable or manually via a command prompt with administrator privileges.

It is possible that these monitoring utilities were sending commands to the MEI interface and thus you could not do both at the same time. Before flashing, it's always best to disable everything running in the background either way. Anything that could interfere and cause issues.

Intel ME 11.0 Consumer PCH-H Firmware v11.0.0.1178
Intel ME 11.0 Corporate PCH-H Firmware v11.0.0.1178

Zitat von NIK1 im Beitrag #1690

---

I am giving my nephews Acer Aspire laptop a tune-up today and wonder if there is firmware to update. It has me firmware 8.1.0.1248 and me driver 11.0.0.1166 .

---

@ bicalov:

Maybe if these "brand" info are missing the BIOS forces the system into a "recovery state" of sorts. Or at least the ME. Why, I don't know. It shouldn't be important to any actual functionality. Indeed, maybe that's the reason behind that program you were given by the supplier.

Today I read by chance an HP document which mentions that the ME can be disabled by (and I quote) "RightArrow + LetArrow and hit PowerButton in S5". ACPI state S5 means that the system is shut down mechanically or via Hibernation. HP probably means the system to be Shut Down completely. So let's see if that can give us access to the ME Region by unlocking the Flash Descriptor. First try with the system shut down and test via FPT as I said in the past (no error 26, full 8MB dump). If that fails, try while in Hibernation as well but I'm fairly certain HP means "mechanical" shut down by "S5".