Just wanted to report:
Computer:
Acer Veriton M2610G
Intel i5-2320
BIOS Version P01-B1 from 06/18/2012
Updated every available module with newest UBU and patched MMTool 5.2.0.24
System runs stable without any problems. Only a visual bug in Win10 taskmanager: It shows all cores at 100% all the time. CPUID HWMonitor shows real load without that bug.
@Sonix,
@Fernando
Please, can you explain in detail how to use to use the option ‘Modules\IRST\User’ ?
I have tried to guess what to do exactly with the 2 files recommended by Fernando (links), but my imagination is limited.
It will be preferable to have a detailed working example.
Maybe killkernel did something wrong, on my side i did not succeed to use this option.
@100PIER
Hello 100PIER! I’ve downloaded Intel RST(e) RAID ROM v16.0.2.3402 from AHCI & RAID ROM Modules and Intel RST(e) EFI “RaidDriver” v16.0.2.3402 (without header) from Intel EFI "RaidDriver" and "GopDriver" BIOS Modules and copied them into the ‘Modules\IRST\User’ path in UBU’s folder.
When UBU processed the BIOS for my motherboard, to update the EFI/RAID OROMs i’ve chosen the option “U” because in the menu has appeared with the OROM versions as this:
Intel RST OROM and EFI SataDriver
1 - Update to v11.2.0.1527 only OROM
2 - Update to v11.6.0.1702
3 - Update to v12.9.0.2006
4 - Update to v13.1.0.2126
5 - Update to v13.2.2.2224/13.2.0.2134
6 - Update to v13.5.0.2164
7 - Update to v14.8.2.2397
8 - Update to v15.1.0.2545
9 - Update to v16.0.1.3339
U - Update to EFI v16.0.2.3402OROM v16.0.2.3402
0 - Exit to Main Menu
All went fine without errors, flashed the BIOS but when i choose RAID option from storage section on next machine boot the relative RAID setup menu didn’t appear… 
Regards,
KK
@Fernando , @killkernel
Thanks for your comments.
Finally I do succeed BIOS update for OROM/EFI.
I had missed to rename the OROM original filenames. After renamed it, the UBU process is OK:
BEFORE:
PENDING:
AFTER:
I have not flashed yet the modded BIOS because this new (Z370) PC configuration is on going.
I had previously written asrock x99 apito 5 microcoding replacement after not seeing the version.
It is not visible because I use an ES processor and UBU has cleared ES microcodes.
After update microcod
Cleaned → Haswell-EP v3 ES/ES2 = cpuid 306F1
Cleaned → Broadwell-EP v4 ES0/ES2 = cpuid 406F0
Haswell-EP v3 preQS/QS/OEM/retail = cpuid 306F2
Broadwell-EP v4 preQS/QS/OEM/retail = cpuid 406F1
I would suggest to please keep ES codes.
@Sonix
I used the UEFI BIOS Updater Update v1.70 a16 Dev with MMTool v4.50.0.23 to try and update the venerable but older ASUS ROG G74Sx laptop bios v204 for microcode ONLY.
The CPU is the i7-2630QM, affectionately known as Sandy Bridge with CPUID of 206A7, platform 12, as per the March 6th, 2018 Intel guidance the final production microcode is 0x2D.
https://newsroom.intel.com/wp-content/up…te-guidance.pdf
Loading bios
ID microcode
Post mod Offset
Mod Final
Before and after bios uploaded for your review. The only marked difference so far is the size of the cpu microcode changes from 0x2000 to 0x3000 but the offset is showing as correct and the GUID before and after is identical.
Is this bios ready to flash and “good to go”…? 
G74SxAS.204.zip (1.04 MB)
mod_G74SxAS.204.zip (1.04 MB)
I do not recommend using UBU to update any modules.
[Discussion] UBU Tool related Questions, Reports and Suggestions (257)
@hancor
If I understand correctly, you have a notebook. You just need to update only 1 desired microcode using the "M" option.
You do not need the other microcodes.
SoniX said:
If I understand correctly, you have a notebook. You just need to update only 1 desired microcode using the “M” option.
You do not need the other microcodes.
@Sonix
Okay went through it again using the “M” option and yielded identical results by using a single microcode to manually update.
I did notice that the microcode files themselves are different sizes; the old 8 KB and the new 12 KB so that may account for the
size increasing from 0x2000 to 0x3000. We’ll see if there is indeed a performance hit on this old Sandy Bridge laptop.
It would appear the tool functioned correctly in “AUTO mode” as the GUID and offsets before and after are still the same using the manual method.
Cheers
Hey i am new here and thats my Setup:
Processor: Intel Core i5-4570, CPU ID: 000306C3
Mainboard: GIGABYTE H87-HD3, Chipset: Intel H87 (Lynx Point)
BIOS version: F10 dated 08/18/2015
I am using UBU Stable (UBU v1.69.16):
My Questions are:
1. Its save to Update to the latest RST?
2. How to Update to the latest Microcode?
Is the 06-3c-03 file from the Linux* Processor Microcode Data File the right for me?
1
HSW Cx/Dx 6-3c-3:32 22->24
UBU shows "only" a Microcode Patch from 2018-01-21 and i dont know if its the same?
EDIT by Fernando: Post reformatted (to save space)
@Nerd :
Welcome to the Win-RAID Forum!
It will be “safe”( you will not brick your mainboard), but the latest Intel RST platform, which natively supports Intel 8-Series Chipsets, is v14.
If your Intel SATA Controller is running in AHCI mode, you should not update the Intel RAID ROM/EFI modules at all (these modules will not be used).
If you don’t want to let the UBU tool do the job, I recommend to follow >this< guide.
Good luck!
Dieter (alias Fernando)
Every time I come here to check on updates, I feel utterly stupid… I can’t even find the patched MMTool 5.2… I figured it would be posted on the front page somewhere, in big bold letters…
A hint how to find the different MMTool versions and variants (in extra bold and red letters) can be found within the start post of >this< thread.
@Sonix:
Okay updated the Asus G74Sx laptop bios as per above modded bios v204 with the new 2D Sandybridge Intel microcode:
RESULT: SUCCESS!
Woot!
Thx again
EDIT by Fernando: Unneeded quoted posts (written by yourself) removed to save space
Hello
I Just tried the stable version with MMTOOL 5.0.0.7, to update the microcode for spectre.
Success on a Asus p8p67 pro REV3.0 (v3602 with sandybridge cpu)
Asus p8p67 PRO REV3.1 (V3602 with sandybridge cpu))
with the Embedded ezflash utility.
Success also on an Asus p8z77-v pro (v2104 with ivybridge CPU)
with asus USB flashback function.
Just a note about the asus usb flashback, the flashback function is desactivated if you have the ErP bios function on (to let the system consume less than 1W of power in S5 (shutdown) state), you will see no light at all when pushing the flashback button, I have tried many pendrives thinking the problem came from them before thinking about this function.
In general it’s better to desactivated this option, before flashing bios (even official one with ez flash, to have a recovery option in case of) and reactivating it after.
The latest UBU a16 build will not update the 2066 microcode cpu50654_platB7_ver02000043_2018-01-26_PRD_4840163E.bin into the MSI bios - http://download.msi.com/bos_exe/mb/7A93v18.zip
A new microcode module is built successfully, but I get “error in saving” from mmtool when it’s trying to save the new bios with the updated module. I’ve tried removing other microcode so it doesn’t seem to be a size issue, and also tried manually replacing/updating with mmtool 5.0.0.2.24, etc. Any other suggestions, or is this a known issue with MSI bioses?
Thanks!
@lettermand99
Maybe a silly question but, your system is new, MSI provided latest MCU necessary for your motherboard. We generally here using UBU if our mainboard vendor is not providing latest bios or MCU. Are you aiming for experimenting? UBU makers are not awfully working on very new (latest) systems so much (my belief but later more of course), because their bios is currently maintaining by it’s own manufacturer. Have you tried with UBU v1.70.a16-DEV with the patched MMTool_v5.02.0024? It is really good trusting UBU by the way…
Note: If you change your bios with UBU, flashing your mainboard vendor’s future bios or bios(es) may cause problem when updating, because they are checking the earlier versions, if they check it with new or newer algorithims, you may not change your bios again. This hapenned to my MSI Big Bang Marshal, I have installed the earlier bios by force and one of my bios is corrupted. I can only use it with by pressing bios button on the mainboard, which toggles second backup bios. (At being on Asus, MSI can not program bios 1 to 2 or 2 to 1, that feature is present on Rampage series.)
Be careful, MSI and Gigabyte bioses are not like Asus’s ones. I have several times locked even superb Asus bioses as well, and used an external programmer named CH341A to fix it. But you can not use it, because your bios chip is not removable!
It is safe to use patched MMTool v5.02.0024 with UBU v1.69.16 (GIGABYTE Modified Bios thred, post #4743 on TweakTown)?
SHA-1: 8e54ac68de355e1031527b89c0560ae1c9c8c508
@JanCerny
Patched MMTool v5.02.0024 is for Aptio V bioses, it is unnecessary to use it with Aptio IV group.
EDIT by Fernando:
This is not correct. The un-patched MMTool v5.2.0.24 has been designed just for AMI Aptio V BIOSes.
If you want to open an AMI Aptio IV BIOS by using the MMTool v5.2.0.24, you have to use the patched variant.
Wrong? OK, then… So, MMTool v5.2.0.24 is patched for using with older Aptio IV bioses! Right this time?
(I was thinking, understant as, it was patched for compatibility issues with new Aptio V ones. Sorry, JanCerny my fault. )