Ohh, your formatting due to microcodes? That's not going to help on Win10, as soon as it connects to the internet it's going to download updates which contain whatever microcode it wants to use.
It may also contain some implemented during it's install as-is, without having to connect to the internet, I'm not certain as I refuse to use Win10. You'd have to google how to disable that, if it's even possible (again, unsure)

If you want to confirm BIOS microcode drop BIOS I send you on MC Extractor, or look in BIOS main page, or during POST Screen if you hit TAB during logo, or disable full screen logo

I can try more on the 280 error, but sounds like the menu edits are still failing (The other file is same, minus the 280 attempt to bypass, so you wont get menus there either)
Back to the drawing board, let me look at the BIOS some more, please wait, no need to flash or continue messing with anything else here yet.

* Edit - the use of dual setups in this BIOS is what's messing me up, I need to figure out how to disable the AsusSetup and make it use Setup only. Since you have a programmer we can test simply removing AsusSetup, but you need to be sure you're ready to recover

I see @lordkag knows how to deal with all this, but I don't see him reply too often. I've found and edited the Boolean string to show all, if you see this lordkag, didn't make any difference, and all tabs at each seem to be enabled in hex/IDA

@Lost_N_BIOS
sadly @lordkag hasn't been online for Last online: 12.17.2018

Anyway I've reformatted my computer again without windows updates just to make sure that I won't get updates I disconnect my internet while formatting.

So here's my findings when I formatted my computer and installed Windows 10 the microcode update shows as "1C" tested with Windows 10 1507 LTSB which release is 2015, but when I formatted it with windows 8.1 it shows "1A" Both Windows 8.1 en_windows_embedded_8.1_industry_pro_with_update_x64_dvd_6052086 which was release in 2014 and Windows 8.1 Ultimate

So the microcode doesn't match could you please send me a bios with rev19 or with reinserted rev12. Dunno what was the issue and I'm sure that my PC is not patch with spectre.

@gjalleri - Windows 8/8.1 may also be inserting microcodes too now, from being connected to the internet or from installer source files, I'm not sure I only use Win7 and know it doesn't. 306C3 Rev 1A not in any BIOS I've sent you, or that you've sent me, so that has to be from windows.
Your stock BIOS contains rev 12 already, the last BIOS I sent you (BCPSString) contains only Rev 12 too, drop it in MC Extractor and you will see.
As mentioned though, I think you need rev. 19 - so here is BIOS with rev 19, this one should also allow FPT BIOS region reflash too once you've got it programmed in there (so no more error 280 as long as we build on this BIOS from now on)
https://www.sendspace.com/file/zwcmi2

@Lost_N_BIOS I've revisited this because I've installed Windows 10 LTSC 2019 which has microcode revision 24 which from the previous post that I had a rev1 on Windows 8.1. Anyway I don't know which microcode is flashed on my bios laptop and I would like to try this again.
Sonix said that from this processor that I had already unlock TSX bios which is rev12 ([ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions (315)).

Also I don't know if I installed the last bios that you've sent to me and I would like to ask you again if it's okay to you if you can send me a another bios with rev12 and rev19 so that I could try in again on my laptop.

Thank you very much and I really appreciate your help.

@Lost_N_BIOS

Good news I've finally found a way to disable the microcode that was installed though Windows Update. All you have to do is to delete or rename %WINDIR%\system32\mcupdate_GenuineIntel.dll.
Now is shows Rev19, before it shows 1C from the previous screenshot. Though Rev19 doesn't have TSX. I'll keep you update and I'll try to reflash rev12 see if it will re-enable TSX again.


Also note that I'm still getting 280 error when flash through FPTw.


Just another question though why UBUTool is now recommending me to use MMTool 5.0.7 instead of MMTool 4.

Tried the rev12 as well and it seems like we have to unlock the bios feature on the motherboard to enable the TSX. If you have time please try to unlock the bios feature thanks!