Sonix,

User Net7 asked me to mod his bios and I tried using Ubu 1.69.14 with patched MMTool and could not update both of his Lan modules using the tool.
His rom was for a buffalo NAS server that was running Aptio 4. Ubu's behavior would only update the first copy of the Intel Boot agent and sometimes
delete the second. I had to manually using UefiTool extract the raw section of CSMCore and make the corrections by hand. Not only that I recall that
once instead of viewing the microcodes it updated the Intel Raid rom on its own. Kind of wierd. Heres his rom for review:

http://www.smartredirect.de/redir/clickG...hp%3Fid%3D17163

Fwiw: MMTool 4.5 only updated one of the Lan modules as well. Not both.

Finished, please delete!

@ RoadrunnerDB
In v1.69.15 IRST 15_x removed. Update to 16_x.

@ davidm71
Link on original file?

Finished, please delete!

Is there a way to update the microcodes for both the engineering samples and retail chips? I'm trying to update the microcodes for my Supermicro X9SRi which gives me this:



But I cannot update both sets, only one or the other.

Tried to update a MSI H97 chipset Bios (H97M-G43- Aptio IV)- UBU_v1_69_15, mmtool 5.0.0.7.

If I update modules other than microcode everything seems fine. If I try to update the microcode, UBU shows both Broadwell and Haswell Microcodes for the original file. After updating the microcode I can see only the code that was updated at last.
In addition I checked what I assumed to be '_FIT_'. Looks the same when updating 'not microcode', gets 4 rows "FF" after updating microcode. That's like it's supposed to be?

Sorry if this is a stupid question! Thanks for all the work!

Older file:

After 'updating' Haswell from 22 to 22:

@SimpleTech
Use v1.70

@lfb6
You need to choose 2 microcodes, since the entire container with microcircuits is updated, and not separately as each file.

I think this is as expected, but I got "Error in Saving" from mmtool.exe (5.02.0024) when trying to update MSI bios X299 SLI PLUS bios 1.8 with the latest microcodes for 7820x:

1│50654│B7 (0,1,2,4,5,7)│2000043 │2018-01-26│PRD │0x7000│ 0x18 │Yes

Using the latest 1.7 UBU dev build. Please advise if this is normal, or there's something else I should try... Thanks!

Think there is something wrong with the script, if I update the microcodes , then go update any other rom afterwards, either before or after a save, Raid rom for example then save the bios, my FIT table ends up being completely blank.
I can reproduce this behavior every single time, using the same bios file/Motherboard, I posted a few pages back.
Basically if I update the microcodes, then update any other rom, FIT table ends up being completely blank.
If reopen the bios and redo the the micrcodes over again, the fit tables get corrected.

So in short, the microcodes have to be done last, unless you want to do them twice on this particular MSI bios.

MCE.exe is detected as Trojan:Win32/Tiggre!plock by Windows Defender after extracting both UBU_v1_69_15.7z and UBU_v1_70_a12_Dev.rar.

Virus Total picks up a couple from just the zip scans.
https://www.virustotal.com/#/file/fda7ba...1a785/detection
https://www.virustotal.com/#/file/c493dc...a2558/detection

@boktai1000
[Discussion] UBU Tool related Questions, Reports and Suggestions (242)

SoniX,

At Intel's latest microcode revision guidance February 24 2018, I have seen a new MCU for x99 chipset variant processors.
https://newsroom.intel.com/wp-content/up...te-guidance.pdf


For Intel® Core™ Extreme Processors: 5960x, 5930x, 5820x
CPUID: 40661
Platform ID: 32
There is a new Production MCU named: 0x19

When I try to update my Bios (currently 3601 with new microcodes of Intel for Spectre & melt) of my Asus H170 mobo I get the message that there is a lock on the capsule file.
It is a .CAP file that is modified by UBU from the official 3601 bios with new IRST Option ROM 16 (WHQL).
Anybody knows how to circumvent this lock ?