UEFI BIOS Updater (UBU)

UEFI BIOS Updater (UBU) is a free Windows script toolkit by SoniX of the Win-Raid Forum that updates the modules inside an AMI Aptio UEFI BIOS image: storage and network option ROMs, Intel and AMD graphics drivers, and CPU microcode. If you searched for “uefi bios updater”, this is the tool BIOS modders mean, not a vendor flashing utility.

For miners it is a niche but handy tool. Rig motherboards often stay on one BIOS for years after the vendor stops updating it, and UBU lets you refresh the network boot modules and microcode in that image yourself. It edits a file on disk; flashing the result is a separate step, and that is where the real risk lies.

UEFI BIOS Updater at a glance

What it does

• Scans a BIOS image and lists the versions of the option ROM and EFI modules it contains.
• Replaces Intel RAID/RST and AHCI modules, and some ASMedia SATA and AMD RAID modules, with newer versions from its own library.
• Updates Intel and Realtek LAN modules (UNDI and PXE boot ROMs).
• Updates Intel GOP drivers and AMD GOP drivers used by integrated graphics.
• Updates Intel and AMD CPU microcode using the bundled MC Extractor database.
• Shows motherboard and BIOS information before you change anything.
• Saves the modified image as a new file, leaving your original untouched.

How miners use it

Refresh the LAN boot module for diskless rigs

Some farms boot rigs over the network (PXE) instead of from a USB stick or SSD. That depends on the motherboard’s LAN boot ROM, and old boards often ship outdated versions.

1. Download the latest BIOS for your exact board from the vendor.
2. Copy it into the UBU folder and run UBU.bat.
3. Choose the network menu, compare the current and offered Intel or Realtek LAN versions, and update only the module your board actually uses.
4. Save the result and flash it using a method your board supports.

Update CPU microcode on an old rig board

1. Run UBU.bat with the BIOS file in place and open the microcode menu.
2. Check which microcode versions are present for your CPU family.
3. Apply the update; UBU may ask for AMI MMTool for some boards and will say so.

Newer microcode often brings security and stability fixes, but it can also lower performance on some CPUs. If you mine on the CPU too, compare hashrate before and after.

Typical folder layout

C:UBU
  UBU.bat
  YOUR_BIOS_FILE  (the BIOS image from your board's vendor)
  Files          (module library bundled with UBU)
  mmtool_a5.exe   (only if UBU asks for MMTool)

Install and first run

Get it from the Win-Raid Forum. UBU is announced and linked in its thread on the Win-Raid Forum, the official source for docs and updates. Copies on download portals are often old or repacked; check the version against the latest post in the thread.

Requirements. Windows, extraction to a short path in the root of drive C: (for example C:UBU), and Python 3.7 or later for microcode updates, as the Win-Raid guide states. AMI MMTool is not included at AMI’s request; UBU works without it for most tasks and tells you when it is needed.

Antivirus. UBU is a batch script that runs several command-line BIOS tools, and some security products flag such bundles. Check the file against the thread before trusting it rather than turning protection off.

Flashing the result. UBU never writes to the chip. Many vendor update tools and built-in UEFI flashers reject modified images because of signature or capsule checks. Depending on the board, the options include the vendor’s BIOS Flashback feature, AMI’s AFU tools or an external SPI programmer. Read the Win-Raid guide for your board before flashing, because a wrong method can leave the board unable to boot.

Back up first. Keep the original BIOS file and, where possible, a dump of the current chip. If the board has dual BIOS, test on one chip only.

Limitations

• Works only with AMI Aptio IV and V UEFI images. Award, Phoenix, Insyde and non-UEFI AMI BIOSes are not supported.
• Updates modules that already exist in the image; it cannot add a missing module or remove one.
• Designed for desktop boards; laptop BIOSes are for advanced users only, and the iGPU VBIOS needs extra preparation.
• Development has slowed: the last stable build is from 2021 and the 1.80 line is still beta. A community-maintained “UBU 1.79 alternative” with refreshed modules is also posted in the same Win-Raid thread.
• Modifying and flashing a BIOS can brick the board and will void the warranty.

UEFI BIOS Updater vs alternatives

UBU automates what you could do by hand with UEFITool or AMI MMTool: find each module and swap it for a newer one. Those tools are more flexible but need far more knowledge. If you only want the vendor’s latest BIOS, use the board maker’s own update method and skip UBU entirely. For graphics card firmware rather than motherboard firmware, see AMDVBFlash (ATIFlash); for memory tuning on ASRock boards, see ASRock Timing Configurator.

FAQ

Where can I get the UEFI BIOS Updater download?

From the UBU thread on the Win-Raid Forum, which links the developer’s releases. Download portals often host outdated builds.

What is UEFI BIOS Updater v1.80 B1?

The latest build posted by SoniX, on November 4, 2024. It is marked beta; the last stable build is 1.79.17 from 2021.

Does UBU flash my BIOS?

No. It only creates an updated image file. You flash it separately with a method your motherboard supports.

Is the UBU tool safe?

Editing the file is safe because the original stays untouched. The risk comes when flashing, so keep backups and know how to recover the board.

Does UBU work with ASUS, MSI, Gigabyte and ASRock BIOS files?

Yes, if the image is AMI Aptio IV or V, which covers most desktop boards from these brands. Some vendor files must be extracted from their update package first.

Will updating the BIOS improve my mining hashrate?

Usually not. Module and microcode updates fix bugs and security issues; hashrate depends on the GPUs, CPU and memory, and profitability on electricity and coin prices.

Last checked against official sources: 1 October 2026 (developer website: winraid.level1techs.com). Versions and licence terms change — confirm on the developer's site before deploying in production.