@osk866 No problem with Intel ME System Tools v8 r3. If you'd have continued you'd have seen that there are two FIT versions included:

Use the newer one of the two.

I happen to know some Ivy Brigde bios that have a checksum error for the FPT partition table and they work just fine. This wont be of any concern. In addition: If you change settings and exchange ME region with a 'blank' ME from the repository the FPT partition table will be rebuild by FIT. And MEA is rather rigid and checks the ME regiosn very thoroughly but doesn't give any warnings for both versions .

You can change the checksum to the correct value (FD), UEFItool_NE will read without any error. Then make the changes in FIT, replace ME region.bin, build, check the new image- and there's your error again, checksum is again C0/wrong. It's an error in the tool...

Being able to load a dump in FIT doesn't mean too much. Don't rely on that!

And yes, my fault, it's as you state "MEInfoWin64.exe -fwsts"

EDIT For ME 9.1 you get the info regarding corruption either by "MEInfoWin64.exe -fwsts" or "MEInfoWin64.exe -verbose", but I think you'll have to try for different ME versions, syntax may change with ME versions.

Answering myself, not editing this time

@osk866 You see, it isn't strict rules always... Regarding the FPT partition table checksum error in UefitoolNE, I think the error might be in UEFItool itself, maybe. At least FIT and MEA are on the same side here:


@plutomaniac I assume UefitoolNE is wrong here?