@RogueDragon - Please run >> MEINFOWin.exe -verbose
From the ME System tools package, and show me the end of this report (in image, not text)
We're checking to see Measured and Verified Boot, on the Left/FPF side, do you see either enabled on Left/FPF side?

Well, this BIOS is a bit oddly laid out, so may take a few different sets of BIOS test before we get a final unlock, but don't worry as you can see I don't give up easily, and can usually best a BIOS menu up and down so should be all good once we wrap it up

Please see my edit above

Hmm, this does not look like I expected, but I've not seen v14 report output so maybe this is normal for V14
Please try this one and show me >> MEINFOwin.exe -fwsts (This report, on V11-12, looks like above, so wonder what it looks like here on V14) I will have to send PM to plutomaniac and wait on this before we do anything, in case Boot Guard is enabled at FPF

Unless! See if you can dump ME FW, then I can check directly if you can dump it, from Flash Programming Tool folder >> Win32 >> FPTw.exe -me -d ME.bin
Send me this file, if created

Here is the screenshot of -fwsts and the ME.bin

Sweet, now I can check directly.... Of course, after I've already sent PM to plutomaniac too, I work too fast sometimes
See, fwsts looks same as verbose, how strange!! Must be some bug with that MEINFOWin version!

I don't mind

plutomaniac -Please check that ME FW at #34 when you have time, thanks! It has tons of errors in MEA, and it will not open in FITc, even if I cut off top, or add line of zeros to beginning, or cut off end/padding.
Not sure if that is broken ME FW, and maybe that's why verbose output looks wrong, but we only needed to check FPF Measure/Verified status, there was no reported ME related issues here
* Edit - Never mind on MEA errors, latest MEA OK But, FITc from r3 package still no go here I see r4 package, trying now, if/when I can download it.... = Same/same, can't open file
AND, I also see same, cannot open if I try to open 14.0.0.1061_CON_LP_BA_PRD_RGN.bin from the repo too, so must be some bug with FITc I guess?

so what do i need to do?

Wait, sorry, we have to know ME Side Boot Guard Status before we do anything here menu-wise. I have to leave in few minutes anyway, so nothing can be done right now no matter what. I'll be back in about 8 hours

No worries, take your time.

@Lost_N_BIOS, I will be leaving for a camping trip soon. I will be back earliest Monday night, maybe later if my family decides to stay longer. Thought I let you know so you wouldn't think I gave up.

plutomaniac so FPT dumped ME entire region no longer is able to be opened in V14? I have no issues with previous ME FW opening in FITc
$FPT is in the dump he sent at post #34, I get similar errors (but different) and cannot open file in FITc, if I try to open the extracted ME FW backup image body from BIOS's ME FW Backup area (DE90FFA8-B985-4575-AB8D-ADE52C362CA3)
Something else must be going on here with v14, I never have these issues with anything V12 or under, from user dumped ME FW region or if checking extracted ME from online BIOS upgrades etc.
I can't find dump online, so will have to build once he send me FD, but I expect the same outcome...

MEINFOWIN - thanks, I will have him test with/without params and use the newer version you linked

@RogueDragon - Please dump your FD and send to me >> FPTw.exe -desc -d fd.bin
No worries about having to leave for a few days, I will see you when you get back
Please also dump this, in case I need, and if present, if error or nothing created then it's not part of your BIOS >> FPTw.exe -gbe -d gbe.bin

Also, please try the above attached MEINFOwin64, and run the following commands and show me output (if long, like expected/desired, show me end of report on that one only - looking for Measured Boot/Verified Boot status and mention of FPF in same area)
Just zip all if you are not sure, if one is long and you still are not sure, scroll up/down as needed and take screenshot so I can see it all.
MEINFOWIN64.exe
MEINFOWIN64.exe -verbose
MEINFOWIN64.exe -fwsts

I am finally back!!!. Sorry for taking so long, there were complications during our trip so it was much longer than expected.

Here is the fd.bin.

gbe.bin gave error 177: reigon does not exist.

MEINFOWIN64 still gives the same short output.

@RogueDragon - I wondered where you'd been Hope trip was OK, despite being longer than expected!
Sorry, but for safety, for now, please wait some more, until I work this out with plutomaniac so we can know if it's safe to flash in mod BIOS here or not.

plutomaniac - Still at a loss here, I compiled his FD, dumped ME region + dumped BIOS region, still cannot open in FITc. I know opening this really doesn't help to check FPF side anyway, but it bugs me
And, the new MEINFOWin attached at #41 still does not give correct -verbose output
Is there any other way to check Measure/Verified boot status at FPF side?