I have an HP Prodesk 600 G1 desktop mini, which is showing this HECI error on startup.
Upon pressing F1 the computer will boot into Windows, but there is no Intel ME functionality.
If I try to configure Intel ME by pressing Ctrl-P at boot up, it does not enter the menu, instead just continues to boot into Windows.
In BIOS the system information shows Intel ME as N/A

I performed the BIOS update again using the latest BIOS version from the HP site (sp96020.exe) which completes successfully but the HECI error is still there.

I downloaded the Intel ME System Tools v9.1 r7 and tried to run FWUpdlcl.exe after booting into DOS using the ME9.1_5M_Production.bin file which is in the ME folder of the firmware update from HP site for that model (SP90243.exe) but that would not run.

I located the Flash Descriptor Override pins on the keyboard, placed a jumper on them, and again booted into DOS to allow the MEInfo.exe to generate an output (run in verbose mode) - see attached MEINFOVE.TXT - this shows the ME File System Corrrupted value as Yes

Whilst in this same mode I ran FPT.exe with the FSTS switch I think to generate the attached FPTDUMPL.TXT file.
I also ran fpt.exe -desc -d FPTDESC.BIN to generate a dump file that is also attached (file renamed to FPTDESC.TXT)


I am not sure where to go from here, any help would be most appreciated. Thanks

I fixed this exact issue today. What I had to do was open up HP's official BIOS (they do provide the full SPI), and I opened it in FIT, since I could not open the exported full SPI from my computer in FIT for some reason. The jumper next to the power supply by itself is the jumper that allows full read write to the BIOS SPI chip with fptw64 utility. Anyways, once you open up HP's official BIOS (the 16mb file in HP's bios package), just build it without changing anything. Go into the build -> int folder I used the ME Region.bin it makes, and just flashed that over mine fptw64.exe -ME -F whatyounameit.bin. It totally worked. I don't know if this is necessary, but I flashed my BIOS in windows (I do this all from in windows, windows 11 actually) afterwards before I rebooted just to be safe. After I rebooted ME and AMT were back, I even upgraded the ME firmware again to see if that still works and it does.

HOWEVER I don't know why the frick it got corrupted in the first place. I haven't touched the BIOS or ME on this system since I got it.