@Rez - I’ve only “heard” of that success in Windows with Ai Suite, not any EZ Flash windows (never heard of that program). But yes, I see we mean same now, I’ve never had luck with that method, even the old version. But, I have seen reports of success.
You’re supposed to see in the BIOS whatever version you wanted to flash, otherwise flash was a failure.
To see current microcodes you can sometimes see on BIOS main page, or CPU info pages in BIOS. Or you can check with HWINFO64, it’s shown in the middle of the little CPU-z like window (uC), or in the large window on the CPU area you will find too.
Thanks for the info, you can easily get around the 368 error, I made a guide for that, which I’d give you the variables to use but still waiting on your FPT dump (So for now you’ll have to use steps 1-5 to get, or wait and get me your FPT dump)
[GUIDE] Grub Fix Intel FPT Error 280 or 368 - BIOS Lock Asus/Other Mod BIOS Flash
* Edit - @Rez - Rename your .efi file to >> Shell.efi
You need to use these variables with setup_var >> 0x90C
So at grub prompt you type the following >> setup_var 0x90C 0x0
Do not flash stock BIOS with FPT, at all, in any way, this includes some other mod BIOS by someone built on stock BIOS or some stock BIOS you edited etc!
Always dump your BIOS region via FPT, edit that, then reflash via FPT. So, again to clarify, for you to use FPT you need to dump your BIOS region, then redo your bios mods/edits to that file, then reflash it with FPT
Also, on microcodes, if you have a BIOS dump, you can drop that dumped BIOS on MC Extractor and it will show you all the current microcodes in your BIOS.
But, to confirm one being used in windows, check how I mentioned above, because sometimes Window replaces what’s in BIOS, so checking BIOS may not give you proper answer of "currently used microcode"
https://github.com/platomav/MCExtractor