where version Test_3 is available ?

@SoniX:
UBU v1.71 DEVTest3
_List_Extri.TXT
Inrel VROC irste 560052004F00430020003.002E00
Intel typo ?

My MB bios 1704 has EFI IRSTe v5.4.0.1039 with VROC
https://dlcdnets.asus.com/pub/ASUS/mb/LG...E-ASUS-1704.zip
Intel_RST(e)_r4 has v6.0.0.1024. with all contents copied to UBU intel RSTe folder
UBU does not update to v6. Should it ?

Thanks for UBU

@Fernando
Thank you so much for the tests. :))

@biozzz
UBU test versions are made to solve some problems in the replacement of microcodes. I think that at the moment we managed to solve many of these problems.

Now you can do other modules, including IRSTe/VROC.
Immediately I will answer you - no typos. Since there are no common patterns for the files of IRSTe and VROC, therefore they will have to be considered separately.

Think the difference is clear?Thereby I was puzzled and wrote about it here.
Intel EFI "RaidDriver" and "GopDriver" BIOS Modules (45)

Therefore, UBU does not know how to work with new versions of IRSTe/VROC.
Now, for work, I have your BIOS image with the necessary files to implement support.

Added:
By the way, in the 5th version of IRSTe, I did not find any mention of VROC.

@Fernando, @Sonix
Do you have observed like me that after Exit UBU Dev Test3 you got a EXPLORER.exe crash like this one ?

Yes, all tests were done with MMTool v 5.0.0.7 added and renamed as indicate into UBU folder.

@Fernando
That's right, it should be.
In your case, Z170 has one container with microcodes and it is not in the PEI volume. This allows you to not use MMTool.
Z97 of these containers are larger and they are in the PEI-volume. Therefore, it is desirable to use MMTool.

@100PIER
I can only assume that this is somehow a problem in the OS. I have no other ideas.

Added:
100PIER Try the following:

Find the line "EXIT 0" and delete "0".
If the problem persists, then I don’t know the reason.

@Sonix, @Lost_N_BIOS, @Fernando,

1) Where in UBU Folder is located the "EXIT 0" to be replaced with "EXIT" for a test ?

2) I have tried to mod via UBU tool (with MMTool) the BIOS REGION of the ASUS Prime Z390M-Plus BIOS v2013. The BIOS REGION File size is 13 Mo only.
The BIOS REGION File was obtained via FPT Tool (under DOS interface) as Recommended by Lost_N_BIOS
Option Network to modd i719 component stuff is OK
Option µCode CPU update does seem OK, however I am worried about a message.
Here are the screenshots:






I am worried by the error message "Incompatible file size" at step10.
Does the µCodes update were properly done ?
Do you think this modded BIOS REGION can be flashed with FTP tool without bricking the motherboard ?

Thanks Fernando, I have modded UBU.BAT, via Notepad++, at line 1601, and will do test.

@100PIER - that looks like it's failed to me, on the microcode update/FIT table replacement.
If you do not have a flash controller, you shouldn't beta test BIOS mod programs (beta UBU I mean), that's risking a bricked system with no way to recover.

mCodeFIT error message "Incompatible file size"

At the moment, the adjustment of _FIT_ is possible only for complete BIOS images (8192KB or 16MB). Other sizes are not allowed.
This is done for 100% accuracy, since the offset of the microcodes is read from the real position in the BIOS image.

I can fix this for the BIOS Region, but I do not have absolute confidence that the resulting shifts will be correct for the entire BIOS image.