You see both now?? But you didn't before, correct? that is odd, should only one show up, but I guess maybe either method works OK

Yes,I see both of them.
For the previous version，maybe I need to change back to the previous version to confirm it again？

OK, thanks for confirming. You don't need to check back to other version, you posted images at #22 and neither was there, so it's OK, both ways will work of what I did this time so I can use either one.

* Edit - @June Da Pek - Here, please test, if Intel TXT still auto-disabled on reboot, then you will need to send me FPT BIOS region dump so I can edit entire NVRAM and send back to you for FPT BIOS region reflash.
https://ufile.io/bn1n44nf

I think... you should teach me how to send you the FPT BIOS region dump... It doesn't work,still auto-disable after reboot...
And I think we had a mistake on this plan,Intel controll the Instruction Set via microcode.I did a modify on my H87,and I set Enable on Intel TXT ,CPU-z will sow me TSX was supported in Instruction area after reboot ,
Some old news reported Intel update the microcode to fix some bugs about TSX,the update will imprison TSX. I mean maybe we should to confirm the version of microcode...

OK, thanks. Then yes, maybe we need to dump via FPT and reflash via FPT, so I can mod the entire NVRAM. If that does not work, then you CPU does not support this, or there is some hardware needed for that on this board that's missing.
Yes, you may need to be using a certain microcode, I assume latest would be fine, not some older one. Not sure what we did about microcodes, but if you wanted me to put in some older one, then that may be the issue with this.
Lets do that before doing the FPT stuff, in case it's not necessary. Please link me to the BIOS you used on the H87 board, and I will check what microcode is there.

I checked back, microcode in current BIOS for your CPU is latest for 40661 CPUID (rev 1B), shown on page one, post #7

The file what I used for modify :
microcode https://ufile.io/6872v5lo
full binary https://ufile.io/hcehiga3

I don't need microcodes. Please give me the BIOS only, that you used and tested TXT on H87 with, that worked. Or, just tell me what microcode you put in there, if you modified it (What revision of 40661 microcode)?
Never mind, i checked your all.bin file, it's rev 12 from 2014. Maybe there is a bug in latest revision I used, or Intel blocked something now, that wasn't blocked back in 2014?
Please wait, I will re-edit late BIOS I sent you with this microcode

It's 40661 ver12,I used to put it in Z87 mainboard ,but the TXT is also doesn't work

I think we should probably try other versions of the BIOS，cause I found ver15 can set different CPU ratio for each cores,then maybe old version BIOS can enable the TXT... MSI is so difficul...

Yes, I see that is revision. You said this revision works with H87 board, but not Z87 (This board, or some other)? Did you put it into last BIOS I sent you, or you wait on me to do that?

Yes,I put it into last BIOS you sent to me.

Did you also fix FIT after you inserted microcode? If not, then it would not be loaded.
BIOS coming shortly, please refresh for edited in BIOS to test

*Edit - please test - https://ufile.io/f7nuw5wb

If this fails, please send me the exact H87 BIOS you used, with this exact CPU, that worked for Intel TXT function. I will check, maybe something in ME FW is allowing it in that BIOS that isn't in this BIOS?

M-Flash show me this

That is unexpected! You didn't rename the file did you?
Please wait, let me check and see if I can see what's going on, why that happened!

I don't rename the binary file,and it can't open by amibcp

Here, please try this one, if still same, maybe I think I know what's going on, and will make you another. This is same exact file, rebuilt, but hex match and MD5 match too
https://ufile.io/ki9ofqv7

Also, the file I sent you before (And) this, opens fine for me in AMIBCP, I just checked since you mentioned.
Maybe was bad download, or bad upload? Try redownloading it MD5 for file at #41 (extracted file) = BF7E2345358FFB890BD425E2B14101A8

* Edit * Never mind, if you saw this, I was incorrect - However, see above for corrected MD5 * Edit *