Updating BIOS used to be terrifying. A power blip mid-flash bricked the board, and the fix involved mailing it back. Modern boards have BIOS Flashback, dual BIOS chips, and crash recovery that make the process safer than installing Windows. But the rules still matter – wrong file, interrupted flash, or skipping the verification step can still kill a motherboard. Here’s how to update BIOS safely on ASUS, MSI, Gigabyte, and ASRock boards in 2026.

What you’ll need

A USB drive between 4 GB and 32 GB, formatted FAT32. ASUS and MSI boards reject NTFS-formatted drives at the flashback stage. Most boards also reject drives over 32 GB, even if you format the partition smaller – the controller checks total size. Cheap Kingston DataTraveler or SanDisk Cruzer sticks work fine. Don’t use a USB 3.2 high-speed stick – some flashback controllers can’t negotiate the right protocol and time out.

A wired internet connection or a second device to download the BIOS file. The motherboard maker’s website is the only safe source. Don’t grab from random forums or “BIOS mod” sites – tampered files can lock the board permanently. Find your exact board model on the silkscreen (e.g. “PRIME B650-PLUS” or “MAG B550M MORTAR WIFI”) and match the version revision if applicable. Some boards have a “Rev 1.0” vs “Rev 1.1” with different BIOS files – they’re not cross-compatible.

A stable power source. If you’re on a desktop, that means a UPS if you live somewhere with flaky power. Laptops obviously need to be plugged in. Don’t update BIOS during a thunderstorm. Don’t update during a Windows Update either – the system can reboot mid-flash if you let WU finish its restart cycle.

Step 1: Identify your board and current BIOS

Open Run (Win+R) and type “msinfo32”. The System Summary lists BaseBoard Manufacturer, BaseBoard Product, and BIOS Version/Date. Note all three. If the current BIOS date is more than 18 months old and your CPU isn’t booting properly with a recent chip, you probably need an update. If everything works, ask yourself why you’re updating – “newer is better” isn’t a good reason. BIOS updates can introduce bugs, not just fix them.

Common reasons to update: installing a newer CPU than the board originally shipped to support (e.g. dropping a Ryzen 9000 into a board that shipped with Ryzen 7000 firmware), AGESA security patches, memory compatibility fixes for a new RAM kit, or a confirmed bug fix in the release notes that affects your hardware. Read the release notes before downloading. Each version’s changelog is on the maker’s download page.

Step 2: Download the right file

Go to the support page for your specific board model. ASUS: asus.com/supportonly, find your board, click Driver & Tools, then BIOS & Firmware. MSI: msi.com/Motherboard, search for the model, go to Support tab. Gigabyte: gigabyte.com/Motherboard, find the model, go to Support, then BIOS. ASRock: asrock.com/mb, find model, Support, BIOS.

Download the latest stable release – skip beta versions unless you’re chasing a specific fix. The file extension varies by maker. ASUS uses .CAP. MSI uses no extension or .B5 type strings. Gigabyte uses .F or numbered files like “Z790.F12”. ASRock uses .ROM or numbered. Some downloads come as a ZIP – extract it before copying to USB. Verify the file size matches what the download page lists – corruption during download is rare but it happens.

Step 3: Copy to USB and rename if needed

Format the USB as FAT32. In File Explorer, right-click the drive, Format, FAT32, Quick Format checked, Start. Copy the BIOS file to the root of the drive – don’t put it in a subfolder.

For BIOS Flashback feature (used when no CPU is installed or the board won’t POST), each brand requires a specific filename. ASUS: rename to a board-specific name listed in the manual, often the board model with no spaces. MSI: rename to “MSI.ROM” on most boards. Gigabyte: rename to “GIGABYTE.BIN” on Q-Flash Plus boards. ASRock: use the file as-downloaded for BIOS Flashback – don’t rename. Check the manual’s flashback section for the exact name your specific model needs. Wrong name means the controller won’t recognize the file and the flash light blinks indefinitely.

Step 4: Flash from inside BIOS (preferred method)

If your board POSTs and boots normally, do the update from inside BIOS – it’s safer than flashing from Windows. Reboot, press Del (or F2 on some Gigabyte boards) to enter BIOS. Find the flash utility: ASUS calls it EZ Flash 3, MSI calls it M-Flash, Gigabyte calls it Q-Flash, ASRock calls it Instant Flash.

Launch the utility, select USB drive, choose the BIOS file. The utility verifies the file’s checksum and CPU compatibility before flashing. If it warns “this BIOS may not be compatible,” stop and double-check the file. If verification passes, hit “Update” and walk away. The flash takes 60-180 seconds. The board reboots 1-3 times during the process – don’t touch it, don’t power off, don’t move it. When you see the POST screen again, enter BIOS, load optimized defaults (F5 on most boards), save and exit. Reconfigure XMP/EXPO and boot order from scratch – they don’t carry over.

Step 5: BIOS Flashback (when board won’t POST)

If the board won’t boot at all – new CPU not yet supported, failed previous flash, or no CPU installed – use the flashback button on the rear I/O. Power off, unplug. Insert the USB stick into the dedicated flashback port (it’s labeled on the I/O shield, usually with a green border or “BIOS” text). Plug in the 24-pin power and CPU 8-pin only – no other components needed. Plug the PSU back in but keep the system powered off.

Press and hold the flashback button on the rear for 3 seconds until the dedicated LED starts blinking. Release. The LED blinks for 3-8 minutes during the flash. When it goes solid or turns off, the flash is done. Unplug PSU for 30 seconds to fully reset, plug back in, and POST normally. If the LED blinks fast or strobes, the file wasn’t recognized – usually a naming issue. Reformat the USB, rename, try again.

Verify it worked

After the flash completes and the board boots, enter BIOS and check the version string. It should match what you flashed. Run msinfo32 in Windows to double-confirm. Boot a stability run with Cinebench R23 for 15 minutes to confirm no crashes or microcode bugs. Re-enable XMP/EXPO and any custom curves – they’re wiped clean. Save your working profile to a BIOS slot so you can restore it later.

Common mistakes

Don’t flash via a Windows utility unless it’s the only option (some Gigabyte boards still ship one). Windows can hang, crash, or update mid-flash and brick the board. Don’t skip the file verification screen because you’re impatient – the wrong file at the right moment kills boards. Don’t update BIOS to “fix” a problem you haven’t diagnosed – it’s rarely the cause of crashes or stutter, and you can introduce new bugs.

Common questions

What happens if power is lost during a BIOS flash?

On older boards with single BIOS, the board bricks. You’ll need a CH341A programmer to reflash the chip directly. Modern boards with dual BIOS or BIOS Flashback can usually recover – the secondary chip handles boot and lets you re-flash the primary. Check your board’s manual for “BIOS recovery” instructions specific to your model.

Do I need to clear CMOS after updating?

Most boards do this automatically during flash. If you see boot issues after the update, clear CMOS manually – either by jumper (consult the manual) or by removing the CR2032 battery for 5 minutes with the PSU unplugged. That’s a clean slate.

Can I downgrade BIOS to an older version?

Usually yes, unless the maker has locked it. Intel-based boards sometimes block downgrades past a microcode revision for security reasons. AMD boards generally allow free up/down between versions. The flash utility will warn you if the target is older – confirm if you understand why you’re going back.

How often should I update BIOS?

Once per year is plenty if everything works. Update sooner if you’re installing a new CPU the board didn’t originally ship to support, or if a security advisory affects your chipset. Don’t chase every monthly release – “if it ain’t broke” applies hard to firmware.