@ davidm71
UBU reassembles the FFS file with microcodes. That is, the replacement is not made of individual microcodes, but of the whole file with microcodes.
@Sonix,
But then why is the Kaby Lake MC removed? On subsequent UBU scan it no longer comes up such that if one was too upgrade their cpu to a KabyLake they would be without the appropriate Microcode? I suppose if you want to keep the original code you should reselect it right?
Thanks Sonix.
Sorry for confusing the issue…
@ davidm71
UBU checks what microcodes are present.
If there is a KBL microcode, then the KBL MC selection menu is available.
If the KBL MC is not available, then the KBL MC selection menu is not available.
This is done specially because there are BIOSes in which there is no microcode KBL And the user, for the fun, might think that he will have a KBL processor after adding the microcode. ;))
Similar to the previous HSW and BDW.
The boards on the 8th chipset do not support BDW, which means that BDW MC is not needed.
Therefore, you should always choose both microcodes, if available.
If only one microcode was selected, in this case SKL, then you need to download the BIOS from the manufacturer’s website and repeat the update procedure.
@SoniX
That’s very interesting but the danger here is let’s say you have a dual Kaby and Skylake board with both MCs in the original bios and you choose skip for Kaby update and only update Skylake … Ubu will delete the Kaby MC such that a rerunning Ubu only shows the Skylake MC being present. Now let’s say I upgrade my CPU next year to a Kaby Lake would I not have a problem?
Thanks
Ps: On an Asus board does Ubu set the Trampoline issues caused by Uefitool resetting FIT table data automatically and possibility of multiple ffs MC entries?
Thanks
Edit: sonix I get what your saying now… one file… guess you got be careful when u mod. Lol.
Any one familiar on how to use menu option M under "User Select Microcode File"? I have selected a CPU.bin code since the the tool seems to strip all codes originally included w/in the bios and only updates what is in the Socket 2011 database within the unzipped file. The Socket 2011 folder does not match the format of the other CPU code folders, other folder have a list on .BIN files - not the 2011 folder.
@dpast76 :
Welcome at Win-RAID Forum!
I have moved your post into the correct UBU Discussion thread. The other thread has been designed just for the announcements of new UBU versions by the developer SoniX.
Regards
Dieter (alias Fernando)
@ dpast76
Oprion 7 -> m Is intended for selecting only one microcode file.
In the folder s2011 are FFS files with different microcodes.
This is done for the reason that if you select all the microcodes for S2011, then the size of the FFS file will be large, and when you update there will be an error that there is not enough free space.
Sonix,
I am inquiring about the Socket 2011 CPU microcodes folder since I have both the Gigabyte GA-X79-UD5 & the Asus X79 Deluxe. Currently when trying to update the CPU codes included in the Bios it is stripping away the original microcodes and only applies the updated codes which may be within the .ffs files. Note it removes all old cup codes and only applied 2 or cpu codes which limits cpu compatibility If I drop in current updated .Bin microcodes to apply to the bios the program/ process just hangs - no out put. I am unable to attach the compiled .bin file with all the CPU codes - attached is the screen shot of the codes. Let me know if the >ffs file extensions is needed or can be a work around?
Once option 7 is selected on UEFI I only have 3 cpu microcodes available.
@ dpast76
Are both motherboards hanging?
Processors are engineering samples?
What specific microcodes do you need?
Addwd:Take screenshots of the results
1
mmtool < Original BIOS Image> /p
Attached are the original bios details from the command provided: Both units are using i7-4930K , my concern is the process strips off the added cpu codes which were embedded within the original bios. As you can see on "Gigabyte MOD" when any of the fields are processed for updates it strips off the original included microcodes that of which none match the originals included or updated. Both screen shots for Asus X79 P & Gigabyte X79 P are from the original bios from the manufacturer.
@ dpast76
By screenshots. In ASUS there are no engineering samples, in GB there is. But if you do not have processors ES (Engineering Sample), then you do not need some microcodes.
What CPUID do your processors have?
It uses i7-4930K Latest CPUID: cpu000306E4_platED_ver00000428_date2014-05-29.bin
Processor core ? Ivy Bridge-E
Core stepping ? S1 (QF81, SR1AT)
CPUID 306E4 (QF81)
I have a Sony Vaio notebook named VPC-F21Z1E. It can not support 22nm CPU’s because of no bios support.
I have modified it’s bios with UBU 1.9.5 updated to Ivy Bridge 1C and Sandy Bridge 29 microcodes. After them, I have updated LAN option rom too. Saved and tried to program with Aptio 4 windows utility with AFUWINGUI at Windows screen and get:
"4 - Error. ROMID is not compatible with existing BIOS ROMID."
I have decided to program the bios update at DOS screen this time by booting by USB stick. Run classic BIOS update procedure command but get the same ROMID error.
This time I used /X parameter after the command, and done! 
Notebook flawlessly opened! BUT I want to ask?
—> Did I do right? Is there any other way? Is there and other program(s) without seeing this error? <—
waiting response…
What is the difference between the 2 types of LAN modes - Automatic and Forced? Which is the one I need/should use? Currently I am on:
OROM Intel Boot Agent CL - 0.1.06
EFI Intel Gigabit UNDI - 0.0.09
Intel RSTe 5.2.0.1029 - extracted via UEFITool.exe (Raw Section -> Extract as is) from MSI 7A93 v1.41 beta bios
rste520_1029.zip (105 KB)
@SoniX @Fernando
Hello
Intel RST RAID 15.8.0.3109 OROM & EFI
Intel Skylake-Kabylake GOP 9.0.1068
Intel Skylake-Kabylake VBIOS 9.0.1054
Stuff.zip (232 KB)
Thanks, any compatible BSF for new VBIOS?
[Guide] Transfer of specific Intel VBIOS settings by using Intels BMP tool (11)
@Pacman
Many thanx. 
For GOP what version VBT?