@ Sylar76
I sympathize. It turns out that the IRST 15 series is not supported on the X99 controllers. 
Or maybe there is something wrong inside the 15.0.0.2606 efi/orom modules.
I do not think. Most likely in the new files do not include support for the previous generation of chips.
I do not be surprised that the next 15th IRST version will not work on the 8th and 9th chipsets.
The text "FW MEI of scanned BIOS" would be better than "FW MEI on Your computer".
@Fernando
Fixed. The version number is not changed, there is no point. New file for download "UBU_v1_59_fix.rar"
- MEI = Management Engine Inteface so Driver, not Firmware
2) If a BIOS/SPI has TXE or SPS, it will still say "MEI" which is obviously wrong
Parameter "-extr" is used for Extractor/UEFIStrip and outputs 5 firmware attributes separated by spaces at a single line. We have:
The command is:
1
for /f "tokens=1-5" %%a in ('MEA\MEA.exe bios.bin -extr -adir -disuf') do (echo WHATEVER)
%%a = Type (ME,TXE,SPS)
%%b = Full File Name
%%c = SKU
%%d = Version
%%e = Date
UBU should only use a,c, d and optionally e. Not b, this is only useful for Extractor/UEFIStrip which needs to extract and rename the extracted file appropriately. So, instead of saying FW MEI, you can say FW %%a. Also, "FW" text is not needed: UBU obviously deals with firmware. I don't see RST being mentioned as FW anywhere because it's obvious.
Now, someone needs to answer me this question:
Why does MEA make people believe that it shows the FW of their system and not the (obvious, maybe to me only?) fw inside their just loaded BIOS/SPI image? Why don't they (in a similar fashion) believe that the RST or CPU Microcode or LAN modules shown above are the ones the system currently uses? Why is MEA any different? I really cannot understand that logic.
I have tried to explain this many,many,many times and even added a dedicated message at UBU, when people press 9 to see their BIOS/SPI image (not system's) Engine firmware version.
So, for the new UBU Menu text shown I see two possible solutions:
1) The above purple text is added at the UBU Pre-Menu screen when Engine firmware is detected
2) The echo text at the for /f command shown above needs to say that this is the Engine FW of the just loaded BIOS/SPI image
Regardless of that, I have decided that from next version of MEA, parameter “-info” will be removed entirely and MEA will only show the fw of the loaded image just like it always did and just like it’s intended.
@ plutomaniac
I thought that in the UBU, make the sub-menu for the MEA, by analogy in the GUI
Selecting "9" will be the next menu:
1
2
3
4
5
6
7
8
9
2
3
4
5
6
7
8
9
ME Analyzer:
1 - Info from BIOS Image
2 - Info DKER from BIOS Image
3 - Info from Your System
etc...
0 - Exit
Edit:
At the moment, I changed the display line in the main menu:
1
echo FW %%a of scanned BIOS Image %%c %%d
"Alice’s Adventures in Wonderland" - no logic, but it is a fantasy. 
Here me back again, just to tell you that using efi/orom sata 15.0.0.2371 everything perfectly works
in both uefi/legacy modes showing the "Intel Rapid Storage Technology" menu in the UEFI mode.
However, I do not know if 15.0.0.2606 changes something but the 15.0.0.2371 is working fine on X99
as well as previous efi/orom versions.
IRST 13 and 6 chipset…
Issue with UBU 1.59_fix: after manually replacing LAN OROM (8086;15b8) and (8086;1539) with IntlOromCL.LOM and IntelOromGE.LOM, UBU can’t update the EFI Intel Gigabit UNDI. I have it in option 3, but selecting it I get only the EFI LAN Intel PRO/1000 UNDI.
Hmm too. Redone later.
Edit:
In version 1.59.1, Framed "crutches". It would be easier if the motherboard manufacturers are correctly exposed DevID.
@ SoniX:
Parameter -dker is not needed for UBU (it will appear automatically if the SKU cannot be detected for post-SKL firmware). If you want to have it, just add it automatically and not mention DKER because noone knows what it is or what it does other than 3-4 people.
Parameter -info will be removed from MEA but I can create an additional exe at the Dev folder which will just print those 2 lines or an error if MEI/TXEI is not installed. However, it makes no sense to have this. Anyone can load an Intel image while working on an AMD system or a system without MEI or TXEI drivers installed, which will cause an error and thus -info will not show anything at that system. I wouldn’t be surprised at all if people complain because they cannot use -info at their AMD or VIA system.
@ plutomaniac
Then I do not change anything. If you have ideas, then I will gladly add them. 
With the same success can add MEInfo files from FPT package.
In general, I think that’ll leave as is. Then time will tell.
Ehm, sorry read it just now, 1.59.1 is "later"? 'cos issue is still present…
Specify exactly what is the problem?
If the first updated OROM, do not display one EFI module Gigabit UNDI, only PRO/1000.
I corrected, and now the module is displayed.
Not for me (Z170 Deluxe)
I used an already modded bios…
Using a clean bios messes things up more!
@gpvecchi
Look carefully title, my screenshot. What sort of model? 
Attach your mod file, that something was wrong with him.
Added:
Check Boot Agents:
- Boot Agent CL - DevID 15b8
- Boot Agent GE - DevID 1539
Otherwise, one of the modules will not work.
The issue is with iGE: motherboard has 8086;1559 (as in MMTool) but 1559 is in DevID_List_iCL.txt list. So, if I replace it with the iGE module, UBU can’t recognize it.
In attachment a bios build from scratch with all modules (VBIOS, 2x OROM, legacy IRST) replaced BUT the option 3 of UBU.
I’d say that solution is put 1559 in DevID_List_iGE.txt
Z170D.rar (7.15 MB)
That’s right. DevID 1559 is Boot Agent CL and is not supported by new Boot Agent GE.
There are 2 variants of solutions.
1) Use old Boot Agent GE version 1.5.62 (E1562X3.LOM) + DevID 1559. This is correct and the old module supports the DevID.
2) For new Boot Agent GE 1.5.70 and above use a compatible DevID, eg 1539. That is, to replace the incompatible DeviD 1559 to a compatible 1539 or any of the list “DevID_List_iGE.txt”. It will also be correct.
Edit:
You have a complete disaster!
Never use MMTool for replacement Tab “Option ROM” (GUID A032 …)
We have already talked about this many times, that MMTool spoils this storage.Now you’ll update the BIOS.
Added:
@gpvecchi
Mod for Asus Z170-Deluxe, updated:
- OROM/EFI IRST 15.0.0.2606
- OROM VBIOS SKL 1043
- EFI GOP Driver 9.0.0.1048
- OROM Boot Agent CL 0.1.10 as DevID 15b8 - i219 Lan Chip
- OROM Boor Agent GE 1.5.79 as DevID 1539 instead of 1559 - i210/211 Lan Chip
- EFI Gigabit UNDI 0.0.13
- EFI PRO/1000 UNDI 7.1.07
- CPU mCode SKL 9E
mod_ASUS_Z170D.rar (7.32 MB)
so this is the command
NETWORK OROM
Search patterm "5043495286805915" for DevID 1559 (1539 use this id)
504349528680B815" for DevID 15B8
romhdr.exe -v 0x8086 -d 0x1539 -i IntlOromGE.LOM -o Lan1539.lom
romhdr.exe -v 0x8086 -d 0x15b8 -i IntlOromCL.LOM -o Lan15b8.lom
Then replace Lan1539.lom and Lan15b8.lom it into UEFITool.exe
Is this right.