After the first “Choice:2”:
Stepping back, then selecting “Video OnBoard” again, is fine.
Another one: on the one hand, the text is garbled, and on the other hand, surely the OROM option must be there if you only have EFI in the BIOS?
@SoniX can UBU be made to insert NEW option rom, or maybe can you do a guide how to do it manually? I want to add VIA VT6421A option rom into the bios. The PCI Card is connected with a PCIE to 2XPCI to z690 UD DDR4. The “option rom” tab in MMTOOL I think is for EFI rom not legacy, and it makes the new saved bios invalid for BIOS UPDATE.
I simply added V041312.rom data to the end of my OROM body, forced bios flash(using recovery mode) and it did not work, the sata drive is not in the Bios boot menu,
You talked about “Size OROM”, do I need now to find hex value representing this in my OROM and increase it by the amount of V041312.rom size?, this is what I don’t understand, size as ‘bytes’, how is the hex representing this, example number 85 in hex normally as 38 35, or switched 35 38?
(it is the same GUID for me 365C62BA-05EF-4B2E-A7F7-92C1781AF4F9, in my OROM I see text ‘RAID’, ‘USB’, NVME, SATA, PCI, CD-ROM, FLOPPY, this:
.AMIBIOS(C)2010 American Megatrends, Inc. …BIOS Date: 12/24/18 09:42:34 Ver: 08.00.10 )
I tried with rambios(to load the rom and init it) I can access the ROM menu and see the sata drive connected, but FDISK or XFDISK hangs when attempting to access the new visible drive, and grub4dos does not see it(for it to then to boot from it)
z690_UD_DDR4_F25_OROM_BODY.zip (46.9 KB)
VIA VT6421 Option ROM V041312.zip (38.8 KB)
Another way I tried, I replaced lan pxe(from MMTOOL “Option ROM” tab) with the via option rom, the lan pxe boot(non uefi) option disappeared from boot menu but the disk connected to the via pci card did not appear.
(replaced the lan pxe with MMTOOL and UEFITOOL, same result)
Just got a new Intel LGA 1200 11th gen CPU microcode from extracting ASUS BIOS that UBU shows the message the mCode does not exist in the database and suggests me to share it. May I attach the microcode here ?
cpuA0671_plat02_ver0000005E_2023-09-14_PRD_45D810F0.bin
as shown by the file name : patch version 5E, dated as 2023-09-14
I have successfully transferred the new mCode to another Gigabyte Z590 mobo BIOS.
Possibly old MCE database in UBU since it’s known since DB281
Otherwise this thread would be the perfect place:
Latest is Intel cpuA0671_plat02_ver00000062_2024-03-07_PRD_2B7D62D5
But thanks a lot for sharing the µcode anyway!
Use this updated database (r276).
Only some AMD microcode is not included, which requires a newer version of MCE (1.94.2+).
MCE.rar (80.9 KB)
2 Likes
Got this error today:
- OS: Windows 7 Professional x64
- installed python-3.8.8rc1, also x64 (latest for Windows 7)
- updated pip and installed “colorama” and “pltable”
Does anyone have idea how to fix it?
If it worked before, something must have changed, right? Anyway, I think 3.8.19 is the latest version that still works with Windows 7. I’ve done the BIOS, if you’re interested.
Medion.rar (2.4 MB)
1 Like
No, this was on a fresh install.
But fixed it. 
I uninstalled python and this time i used v3.8.9 (i have no idea how to update it without a compiled installer, sorry) and checked the box for “PATH” while beginning of installation. Maybe this was the solution.
OS Windows 7 x64 Python 3.8.10 x64
Install to “C:\Python”
Install Launcer
Add to Enviroment “Path=…”
Assiciated Python Files
Wirks good!
2 Likes
Thank you very much for informing me this Github respositories. 
Thank you too for sharing me with the updated mCode and DB from Github reponsitories. 
i stucked at the Python stuff for a long time too. Sorry i am not good at the Environment path thing. Shoud i point the path to the Python installing directory by editing(adding) the environment system variable ?
By the way, adding the internal testing VMD-RST EFI driver from ASUS BIOS.
Intel-VMD-RST_EFI-RaidDrive v20.1.0.5817.rar (142.6 KB)
The BIOS version is 3.08 and the date is 22 July 2024(?). True, it is a Strix Point BIOS, but it works fine with another one.
1 Like
Hi all. This a carryover from this thread post.
UBU (UEFIReplace, I’m guessing) is slightly modifying the bios structure due to the size of 2 of 4 replaced/upgraded microcodes. To “buy some space”/minimize the issue, I’ve re-run UBU to maintain 1 of the MC’s so that I’m only dealing with 1 needed MC that is oversized.
UBU is getting rid of a non-empty Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1. The thinking is to add it back in, and then reduce the size of the Padding file under Microcode and/or reduce the size of the Volume free space.
I can hex editor add a Padding file under File GUID: B52282EE-9B66-44B9-B1CF-7E5040F787C1. But the original Padding file is not data free. I could also remove FF’s in the other 2 places. Looking for a little help to finish this off.
I ran fptw64 -a 0x1D50000 -l 0xF0000 -d ucode.bin, so I could flash the corrected ucode.bin, or just FPT the new full bios.
ucodebins.zip (974.1 KB)
The attached are the original/unmodified and UBU modified ucode bins + the UBU run result.
The wrong date (12/12/2012) will be a general error. It is also present in this BIOS.
I don’t fully understand the “BIOS release” and “BIOS version” parts either. I have looked at some BIOSes, but the BIOS version part is only visible for Strix Point. On older BIOSes, the version is listed before the date. Wouldn’t it be logical to have the date at “BIOS release” and the version at “BIOS version”? In fact, perhaps “date” instead of “release” would be a better choice.
Also, I deliberately use the latest version of MCE, and if I select option 5 in UBU, the microcode is automatically saved to that directory, as if the X command had been used. How intentional is this? I find it quite confusing.
I posted f15. MMTool is now used instead of UEFIReplace.
I do not give any guarantee that this solution will work as it should. Unfortunately, the tools are old, but there are no new ones.
1 Like
The version and model data are taken from two files. But it seems that the ACS decided to put their own rules in order.
1 Like
Thanks @SoniX. I’m seeing that now. I’ll make a run at it. I’ve been at this for a few months, now. I’ve learned patience, finally. Ok. I’ll follow up.