@e.v.o :
Although it obviously was your intention to help
a) the Forum visitors, who are always waiting for an updated UBU version, and
b) SoniX, who has written, that he doesn’t have the required time to create a new UBU tool version,
I am not sure, whether it was a good idea to offer a v1.67 of SoniX’s UBU tool.
Did you get his ok, before you published the new version?
If not, you should remove your links.
I want to avoid everything, what may end with SoniX’s “good-bye” to our Forum.
Hoping for your understanding
Dieter
Generally, such modded versions cannot be posted at the non-discussion thread because SoniX may have different plans for his own 1.67 or at the very least such an action can confuse everyone when the official 1.67 is out. Maybe add a clear indication and don’t change the minor version, if SoniX is ok with that. Meaning v1.66.1_evo or similar. For future reference, the mmtool.txt hash file is indeed a good idea.
I am sorry! I would not harm anyone! Just read he didn’t had the time so i thought i could do it and help him. It is his tool and will always be. But i am removing it since i didn’t get his ok.
- LAN OROM PXE and EFI UNDI Intel, Realtek, BCM, QCA
----------------------------------------------------------------
3 - For 2 Intel NIC 82579/217/218+210/211/350
Possible Update ?
EFI Intel PRo/1000 UNDI 6.9.07 is in RAMPAGE-V-EDITION-10-ASUS-1503 (i218V & i211AT)
from 6.6.04 in UBU
http://dlcdnet.asus.com/pub/ASUS/mb/LGA2…0-ASUS-1503.zip
Can someone extract it properly for all of us to use in UBU or UefiTool ?
Thanks,
biozzz
@biozzz
Thank you.
This is an error in UBU. There should be an upgrade to version 7.x.xx, not to 6.6.04.
I will correct.
Added.
Find
1
2
2
if %s2011v3%==1 if %bacl%==1 if %bage%==1 set fefi=%sdl%\efi\E6604X3.efi
:x99
and repace
1
2
2
if %s2011v3%==1 if %bacl%==1 if %bage%==1 set fefi=%sdl%\efi\IntlGbEUndiX3.efi
:x99
@SoniX
Well… i have to thank you for UBU and your work! If i can help you in any way then please let me know 
All Thanks to SoniX & e.v.o,
works great now !
biozzz
Attach new files GenFFS, GenSec and LZMACompress for testing.
Debian has updated their intel-microcode package, and its changelog has some relevant details:
* New upstream microcode datafile 20170511
+ Updated Microcodes:
sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
sig 0x000306d4, pf_mask 0xc0, 2017-01-27, rev 0x0025, size 17408
sig 0x000306f2, pf_mask 0x6f, 2017-01-30, rev 0x003a, size 32768
sig 0x000306f4, pf_mask 0x80, 2017-01-30, rev 0x000f, size 16384
sig 0x00040651, pf_mask 0x72, 2017-01-27, rev 0x0020, size 20480
sig 0x00040661, pf_mask 0x32, 2017-01-27, rev 0x0017, size 24576
sig 0x00040671, pf_mask 0x22, 2017-01-27, rev 0x0017, size 11264
sig 0x000406e3, pf_mask 0xc0, 2017-04-09, rev 0x00ba, size 98304
sig 0x000406f1, pf_mask 0xef, 2017-03-01, rev 0xb000021, size 26624
sig 0x000506e3, pf_mask 0x36, 2017-04-09, rev 0x00ba, size 98304
+ This release fixes undisclosed errata on the desktop, mobile and server processor models from the Haswell, Broadwell, and Skylake families, including even the high-end multi-socket server Xeons
+ Likely fix the TSC-Deadline LAPIC errata (BDF89, SKL142 and similar) on several processor families
+ Fix erratum BDF90 on Xeon E7v4, E5v4(?) (closes: #862606)
+ Likely fix serious or critical Skylake errata: SKL138/144, SKL137/145, SLK149
* Likely fix nightmare-level Skylake erratum SKL150. Fortunately, either this erratum is very-low-hitting, or gcc/clang/icc/msvc won’t usually issue the affected opcode pattern and it ends up being rare.
SKL150 - Short loops using both the AH/BH/CH/DH registers and the corresponding wide register may result in unpredictable system behavior. Requires both logical processors of the same core (i.e. sibling hyperthreads) to be active to trigger, as well as a “complex set of micro-architectural conditions”
+ Updated Microcodes:
sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
sig 0x000306d4, pf_mask 0xc0, 2017-01-27, rev 0x0025, size 17408
sig 0x000306f2, pf_mask 0x6f, 2017-01-30, rev 0x003a, size 32768
sig 0x000306f4, pf_mask 0x80, 2017-01-30, rev 0x000f, size 16384
sig 0x00040651, pf_mask 0x72, 2017-01-27, rev 0x0020, size 20480
sig 0x00040661, pf_mask 0x32, 2017-01-27, rev 0x0017, size 24576
sig 0x00040671, pf_mask 0x22, 2017-01-27, rev 0x0017, size 11264
sig 0x000406e3, pf_mask 0xc0, 2017-04-09, rev 0x00ba, size 98304
sig 0x000406f1, pf_mask 0xef, 2017-03-01, rev 0xb000021, size 26624
sig 0x000506e3, pf_mask 0x36, 2017-04-09, rev 0x00ba, size 98304
+ This release fixes undisclosed errata on the desktop, mobile and server processor models from the Haswell, Broadwell, and Skylake families, including even the high-end multi-socket server Xeons
+ Likely fix the TSC-Deadline LAPIC errata (BDF89, SKL142 and similar) on several processor families
+ Fix erratum BDF90 on Xeon E7v4, E5v4(?) (closes: #862606)
+ Likely fix serious or critical Skylake errata: SKL138/144, SKL137/145, SLK149
* Likely fix nightmare-level Skylake erratum SKL150. Fortunately, either this erratum is very-low-hitting, or gcc/clang/icc/msvc won’t usually issue the affected opcode pattern and it ends up being rare.
SKL150 - Short loops using both the AH/BH/CH/DH registers and the corresponding wide register may result in unpredictable system behavior. Requires both logical processors of the same core (i.e. sibling hyperthreads) to be active to trigger, as well as a “complex set of micro-architectural conditions”
Basically: everyone should update their microcode for stability, this recent batch of updates is fixing some nasty issues… including the ones not part of the Intel public release (such as Kaby Lake).
EDIT by Fernando: Put the changelog into a spoiler (to save space within this voluminous thread)
strange, it was my working-backup since years.
With new "fresh" download from producer site UBU is working fine 
SoniX is right. That dump is completely broken. There are sections partially or fully missing, zero padding all over the place etc. Don’t ever flash that image. Download the one from MSI instead.
firstone, thx to all for the help, i have a question :), its there no poblem change the extension .ffs to .efi in the file Intel Skylake-Kabylake GOP 9.0.1064.ffs uploaded by Pacman? (thx for all your help), i do it, and i changed file on UBU, and i think wii be upadated with out problem, but i dont flashed on my mobo
before mod
after mod
|addpics|fpw-1-408b.png-invaddpicsinvv,fpw-2-4b38.png-invaddpicsinvv|/addpics|
BIOS EFI files with the extension *.ffs are complete ones (with GUID header), whereas *.efi files are the "pure" ones without GUID header. So it is not a good idea to simply rename an *.ffs file to an *.efi one.
Anyone know how to get the UEFI BIOS Updater tool to rename my Asus z270 Apex bios MAXIMUS-IX-APEX-ASUS-0906.CAP to rename the modded bios to .cap.I can only get it to save as mod_bios.bin or bios.bin .
Right on,thanks.So just type everything like your screenshot after rename:1 Restore Capsule Header bios bin ===> M9A.CAP
There is a problem with UEFIFind.exe in v1.68
It cannot find Intel Skylake GOP on Z170 Gigabyte BIOS.
The version from v1.66.0 works ok.
Also, mCodeInfo needs to get updated to support MCE.dat r28 or later. The date follows the ISO8601 YYYY-MM-DD format now.