Your motherboard’s BIOS has had a busy 2026. AMD’s Zen 6 desktop trickle-down, Intel’s ongoing Core Ultra refresh, and a DDR5 memory market where prices climbed roughly 63% this year have pushed more PC owners into their UEFI settings than at any point since the DDR4-to-DDR5 transition. Search interest in “how to update bios” now clears 27,000 monthly searches, and the question that dominates Reddit threads and Discord servers hasn’t changed: will flashing the BIOS brick my PC?
The short answer is no, not if you follow the process in order. A BIOS update is a firmware write, not a Windows installer, so it rewards patience over speed. This tutorial walks through the full 12-step process for flashing a desktop motherboard BIOS in 2026, covering the individual tools built by ASUS, MSI, Gigabyte, and ASRock, the no-CPU “flashback” method now standard on most gaming boards, and the ten most common failure points that turn a routine update into a support ticket.
Budget about 45 minutes for the whole process: roughly ten minutes for research and downloads, five for the actual flash, and the rest for the settings cleanup that most guides skip entirely.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Is a BIOS Update, and Why It Matters in 2026
BIOS stands for Basic Input/Output System, though nearly every board sold since around 2015 actually runs UEFI (Unified Extensible Firmware Interface), a faster, mouse-driven successor that kept the old name out of habit. It’s the small piece of firmware that boots before Windows loads at all. It initializes your CPU, RAM, and storage controllers, runs the Power-On Self-Test, and hands control to your operating system once everything checks out.
Updating it isn’t optional busywork this year. Three separate forces are pushing update volume higher than usual. First, AMD’s Zen 6 desktop rollout means older AM5 boards need new AGESA (AMD Generic Encapsulated Software Architecture) code to recognize the newest chips, the same mechanism that let existing AM4 and AM5 boards add support for chips like the Ryzen 7 5800X3D Anniversary Edition without a socket change. Second, Intel’s 600-, 700-, and now 800-series chipsets require a BIOS update to boot certain 13th- and 14th-generation Core desktop processors, and again when moving between generations, according to Intel’s own support documentation; MSI underscored how active that lineup still is by shipping a fresh BIOS 3.90 package across its Intel 600-, 700-, and 800-series boards in June 2026. AMD’s support documentation describes the same requirement for its own socket: a compatible board may still need a BIOS update before it will boot a newly released desktop processor. Third, DDR5 prices jumped roughly 63% this year as chip shortages hit the market, and with memory that expensive, pulling full EXPO-rated speed out of every module instead of falling back to slow JEDEC defaults now requires a BIOS that actually recognizes your kit’s timings.
Security matters too. AMD’s AGESA 1.2.0.3e update has been reported to patch a vulnerability in the chip’s Trusted Platform Module capable of exposing data stored there, a reminder that BIOS updates aren’t only about new hardware support. XDA Developers also reported that an earlier AGESA 1.2.0.2 update added an official 105W TDP mode for the Ryzen 5 9600X and Ryzen 7 9700X, improving multi-threaded performance while keeping warranty coverage intact. That AGESA churn isn’t limited to current-gen boards, either: ASRock pushed the ComboAM4v2 1.2.0.12 microcode to a wide swath of older AM4 boards in August 2026, including BIOS 10.70P for the B450M Steel Legend and BIOS 4.00 for the B550M WiFi on August 25, 2026, plus BIOS 4.10 for the A520M/ac on August 20, 2026, proof that even budget last-gen boards keep getting firmware attention years after launch. Neither change happens without a firmware flash.
Prerequisites: What You Need Before You Update Your BIOS
Gather everything below before you touch the BIOS menu. Half of all failed flashes trace back to a missing item on this list, not a hardware fault.
| Requirement | Recommended Spec | Why It Matters |
|---|---|---|
| Operating system | Windows 10 (22H2) or Windows 11 | Most brand flashing utilities and live-update tools are Windows-only |
| USB drive | 4GB-32GB, FAT32 formatted | Larger drives or NTFS/exFAT formatting fail in UEFI flash utilities |
| Power source | Wall outlet, UPS if you have one | A single power interruption mid-flash can corrupt the firmware chip |
| Exact board model and revision | Full model number, e.g. “Rev 1.0” vs “Rev 1.1” | Wrong-revision files are the single biggest cause of failed flashes |
| Current BIOS version | Recorded before you start | You need a before-and-after comparison to confirm the update installed |
| Internet connection | Stable, wired if possible | Interrupted downloads produce corrupt firmware files that fail checksum checks |
| Time set aside | About 45 minutes | Covers prep, backup, the flash itself, and post-update reconfiguration |
One more thing worth doing before you start: if your case is already open for a CPU or cooler swap, this is a good moment to also check your fan airflow direction and confirm your thermal paste application, since you’ll want to reboot into a stable, fully assembled system before you start flashing.
Step 1-2: Check Your Current BIOS Version and Motherboard Model
Step 1 is deciding whether you actually need this update at all. Open your motherboard’s support page, find the BIOS/firmware section, and compare the latest listed version against what you’re currently running. Update if you’re installing a CPU the board didn’t originally support, chasing full-speed EXPO or XMP on new RAM, or the changelog lists a security fix. Skip it if your system is stable, your CPU already works fine, and the newer version only lists changes that don’t apply to you.
Step 2 is confirming your exact model, revision, and current version from inside Windows rather than guessing from memory. Open PowerShell and run:
Get-CimInstance -ClassName Win32_BIOS | Select-Object SMBIOSBIOSVersion, Manufacturer, ReleaseDate
Get-CimInstance -ClassName Win32_BaseBoard | Select-Object Manufacturer, Product, VersionExample output (yours will differ):
SMBIOSBIOSVersion Manufacturer ReleaseDate
----------------- ------------ -----------
2203 American Megatrends International, LLC 20260212000000.000000+000
Manufacturer Product Version
------------ ------- -------
ASUSTeK COMPUTER INC. ROG STRIX B650E-E GAMING WIFI Rev 1.xxWrite both values down. You’ll need the exact product string to find the correct download, and you’ll need the version number again at the very end to confirm the flash actually took effect.
Step 3-4: Back Up Your Settings and Download the Correct BIOS File
Step 3 is backing up your current configuration. A BIOS flash typically resets custom settings to factory defaults, so before you start, write down (or photograph) your boot order, any manually set fan curves, your EXPO/XMP profile selection, and any voltage or clock offsets you’ve applied. Most UEFI menus also include a “Save Profile” option under an Overclocking or Tools tab that exports these settings to a USB drive, which is faster and less error-prone than copying values by hand.
Step 4 is downloading the firmware file, and this is where most bricked boards actually go wrong, well before anyone touches the flash button. Go directly to your motherboard maker’s official support page, search by your exact model number, and download only the file matching your specific revision.
Only install the file that matches your exact model.
Syncro Secure, Technical writing team (syncrosecure.com)
That warning applies just as much to laptops as desktops. HP’s own update guidance walks through the same standard pattern most vendors follow: download the firmware from your product’s official support page, extract the archive if needed, transfer it to a properly formatted USB drive, and boot into the BIOS menu to complete the install. Do not download BIOS files from third-party mirror sites or forum attachments, even if they claim to be faster. A single corrupted byte in that file is enough to fail the flash midway through.
Step 5-6: Verify the File and Prepare a Bootable USB Drive
Step 5 is confirming the file downloaded correctly before you trust it anywhere near your motherboard. Most manufacturer support pages publish a SHA256 or MD5 checksum next to the download link. Verify it in PowerShell:
certutil -hashfile "C:\Downloads\ROG-STRIX-B650E-E-GAMING-WIFI-ASUS-3602.CAP" SHA256Example output:
SHA256 hash of ROG-STRIX-B650E-E-GAMING-WIFI-ASUS-3602.CAP:
a1 3f 9c e2 7b 4d 8a 11 5c 6e 90 22 d4 f7 b8 3a
1e c5 07 44 9b 2f 6a d8 c1 03 7e 5b 8f 4c a9 22
CertUtil: -hashfile command completed successfully.Compare the output against the published hash. If they don’t match exactly, re-download the file rather than proceeding. A mismatched checksum almost always means an incomplete or corrupted download, not a hardware problem, and flashing it anyway is how routine updates turn into RMA tickets.
Step 6 is formatting a USB drive the way flash utilities actually expect: a single FAT32 partition, nothing else on the drive. Use Diskpart rather than Windows’ built-in formatter, since it avoids the multi-partition or exFAT defaults that trip up UEFI flash tools:
diskpart
list disk
select disk 2
clean
create partition primary
format fs=fat32 quick
active
assign
exitDouble-check the disk number before running clean, since Diskpart will erase whatever drive you select without a confirmation prompt. Copy the BIOS file to the root of the drive, not inside a folder, and rename it to match the exact filename your manufacturer’s support page specifies if the instructions call for it.
Brand-by-Brand: How ASUS, MSI, Gigabyte, and ASRock Flash a BIOS
Every major board maker uses its own name for the same basic function, and it’s worth knowing which one applies to your hardware before you start Step 7.
| Brand | In-BIOS Flash Tool | No-CPU / Flashback Method | Typical Flash Time | Notes |
|---|---|---|---|---|
| ASUS | EZ Flash | BIOS FlashBack (dedicated USB port + button) | 3-6 minutes | LED blinks during flashback and stops when finished |
| MSI | M-Flash (via Click BIOS 5) | Flash BIOS Button (select boards) | 3-5 minutes | Some boards require renaming the file to MSI’s expected format |
| Gigabyte | Q-Flash | Q-Flash Plus | 3-8 minutes | Q-Flash Plus works with the system fully powered off |
| ASRock | Instant Flash | BIOS Flashback | 3-6 minutes | Instant Flash reads FAT32 USB drives directly from the UEFI menu |
| Laptop OEMs (Dell, HP, Lenovo) | Vendor utility (Dell Command Update, HP Support Assistant, Lenovo Vantage) | Rare, model-dependent | 5-10 minutes | Battery should stay above roughly 20% with the charger connected |
ASUS documents EZ Flash as the standard in-UEFI update path across its consumer boards, while ASRock’s support pages describe Instant Flash the same way for its lineup. Both tools have gotten faster and safer recently: ASUS’s EZ Flash 4 revision added cloud-based Wi-Fi updates and trimmed typical flash times to 3-7 minutes, and by February 2025 both ASUS Live Update and MSI Center 6.0 had added automatic checksum validation on top, catching a corrupted download before it ever reaches the chip. The naming differs, but functionally they all do the same three things: read a firmware file off a USB drive, verify it matches your board, and write it to the chip.
Step 7-9: Flashing BIOS From Windows vs. the UEFI Menu
You now have two realistic paths to actually apply the update, and which one you choose depends on how much risk you’re comfortable with.
Step 7 is making sure your power supply is stable before you commit to either path. Plug a desktop directly into a wall outlet, skip power strips with surge protection features that can cut power unexpectedly, and use a UPS if you own one. For a laptop, keep the charger connected the entire time, even if the battery shows a full charge.
Step 8 is choosing your flashing method. The UEFI-menu route is the traditional path: restart your PC, tap Delete or F2 during boot to enter the BIOS menu, and launch your brand’s tool (EZ Flash, M-Flash, Q-Flash, or Instant Flash) from there. Intel’s own gaming guide describes the general version of this process plainly:
One common method is to: Download new driver files from the BIOS tab on your product’s support page. Extract them using a utility like WinRAR. Transfer them onto a properly-formatted USB drive. Restart the PC and access the BIOS menu during POST.
Intel, Official documentation (intel.com)
The alternative, if you’d rather skip the USB drive entirely, is a Windows-based live-update tool: ASUS Armoury Crate’s update panel, MSI Center’s Live Update, or Gigabyte’s APP Center all download and flash the firmware directly from within Windows over an internet connection. This answers the “how to update bios without usb” question directly, and it works well on a wired connection, but it introduces one extra point of failure (your internet connection) that the USB method avoids. On a laptop or any system without a wired Ethernet port nearby, the USB method remains the safer default.
Step 9 is selecting the correct file inside the flash utility and confirming the write. The tool will typically re-verify the file against your board model one more time before it lets you proceed, which is your last checkpoint before the actual flash begins.
Step 10: How to Update BIOS Without a CPU Installed
If you’re building a new PC and want to confirm your board supports your CPU before you ever seat it, or if a previous flash failed and left you without video output, USB BIOS Flashback solves both problems. It’s the no-CPU, no-RAM, no-GPU flashing method built into nearly every gaming motherboard sold in the past several years, and several board makers now consider it the safer default method precisely because fewer components are involved in the process.
The process is largely identical across brands. Rename your BIOS file to the exact string your manufacturer specifies (this matters more here than in the in-UEFI method), copy it to the root of a FAT32 USB drive, and plug that drive into the specific USB port on the rear I/O panel labeled for flashback, not just any USB port. Connect the power supply and switch it on at the back, but leave the system itself powered off. Press and hold the dedicated BIOS Flashback button (ASUS), or trigger Q-Flash Plus (Gigabyte) the same way, for a few seconds until an LED near the port starts blinking.
Walk away and let it finish. The LED blinks steadily during the write and stops (or switches to solid) once the flash completes, typically within three to ten minutes depending on file size and brand. Do not press the button again, unplug the drive, or cut power while that LED is active.
Desktop vs. Laptop BIOS Updates: What’s Different
Everything above covers desktop motherboards, where BIOS Flashback and dual-BIOS recovery chips give you a real safety net. Laptops work differently, and treating a laptop update exactly like a desktop update is a common way people end up in a support forum asking how to update bios on a Dell or HP machine that won’t boot.
Laptop makers replace the brand-specific in-BIOS tools with their own Windows utilities: Dell Command | Update, HP Support Assistant, and Lenovo Vantage all detect your exact model automatically and download the matching firmware, which removes the “wrong file” risk that causes most desktop flashing failures. That convenience comes with a tradeoff. Most laptops ship with a single BIOS chip and no backup, so there’s no dual-BIOS fallback to lean on if the update is interrupted.
Three rules matter more on a laptop than a desktop. Keep the charger plugged in for the entire update, regardless of what the battery percentage shows, since manufacturers frequently block the update from starting at all below a minimum charge threshold (commonly around 20-50%, depending on the model). Close every other application first, since a laptop is more likely than a desktop to throttle or sleep mid-update if something else is using significant CPU or disk resources. And avoid doing this over a hotel or public Wi-Fi network. The download itself rarely fails, but a dropped connection during an in-progress live update on some models can leave the process in a bad state. A wired connection or a stable home network removes that variable entirely.
If a laptop update does fail and the machine won’t boot, check your model’s support page for a hardware-level recovery combo before assuming the worst. Several vendors build in a key-combination recovery mode (often holding a specific function key while connecting the charger) that reflashes from a recovery file on the drive itself, similar in spirit to a desktop’s flashback port even without the dedicated hardware.
Complete Walkthrough: Updating BIOS on a Real AM5 Gaming PC
Here’s how all twelve steps look end to end on an actual build: an AM5 gaming PC running an older Ryzen chip, upgrading to add support for a newer CPU and unlock full EXPO speed on a recently installed DDR5 kit.
Before You Begin: Building a Reusable BIOS Update Toolkit
Rather than treating this as a one-time task, set up a small toolkit you can reuse for every future update: a dedicated 8GB USB drive, labeled, kept in the same drawer as your other PC tools. On it, save a simple PowerShell script that snapshots your system’s state before and after every flash, so you have a record instead of relying on memory.
# BIOS Update Toolkit - system snapshot
# Save as snapshot.ps1 on your BIOS update USB drive
# Run it once before the flash and once after
$bios = Get-CimInstance Win32_BIOS
$board = Get-CimInstance Win32_BaseBoard
$mem = Get-CimInstance Win32_PhysicalMemory | Select-Object DeviceLocator, ConfiguredClockSpeed
Write-Host "=== Current System Snapshot ===" -ForegroundColor Cyan
Write-Host "Board: $($board.Manufacturer) $($board.Product) $($board.Version)"
Write-Host "BIOS version: $($bios.SMBIOSBIOSVersion)"
Write-Host "BIOS date: $($bios.ReleaseDate)"
Write-Host "Memory modules:"
$mem | Format-Table -AutoSize
$log = "$env:USERPROFILE\Desktop\bios-update-log.txt"
"$(Get-Date) - Snapshot: $($board.Product), BIOS $($bios.SMBIOSBIOSVersion), RAM speed $($mem[0].ConfiguredClockSpeed)MHz" | Out-File -Append $log
Write-Host "Snapshot appended to $log" -ForegroundColor GreenRun this script, note the output, and move on to the actual update. It takes thirty seconds and gives you a plain-text log you can compare against after the flash instead of guessing whether anything actually changed.
During and After the Flash
With the snapshot saved, the walkthrough follows Steps 1 through 12 in order: confirm the update is actually needed, download and checksum-verify the correct file for the exact board revision, back up custom settings, format the USB drive, enter EZ Flash (or the equivalent brand tool) from the UEFI menu, select the file, and confirm. The flash itself runs for roughly four minutes on a typical AM5 board, during which the screen stays on a progress bar and the system must not lose power.
Once the board reboots on its own, it lands back in the UEFI menu with settings reset to default, which is expected. From there: load optimized defaults explicitly, re-enable the EXPO profile under the memory settings tab, restore the boot drive order, and save with F10. Run the snapshot script again once Windows loads, and compare the new log line against the one from before the flash. A version number that changed and a RAM speed that matches your kit’s rating both confirm success in about the same amount of time it took to read this paragraph.
Step 11-12: After the Flash, Reconfigure and Verify Your BIOS Update
Step 11 is the reconfiguration pass most tutorials skip, and it’s the reason people report “my RAM got slower” or “my fans are loud now” after an otherwise successful update. A BIOS flash resets nearly every customized setting to factory default. Go back through the backup you made in Step 3: re-enable EXPO or XMP, restore custom fan curves, re-enable Resizable BAR and Above 4G Decoding if you had them on, and fix your boot drive order so Windows starts without a manual drive selection.
Step 12 is verifying the update actually took effect, from inside Windows rather than trusting the UEFI splash screen alone. Run the same command from Step 2 again:
Get-CimInstance -ClassName Win32_BIOS | Select-Object SMBIOSBIOSVersion
Get-CimInstance -ClassName Win32_PhysicalMemory | Select-Object DeviceLocator, Speed, ConfiguredClockSpeedExample output after a successful update and EXPO re-enable:
SMBIOSBIOSVersion
-----------------
2402
DeviceLocator Speed ConfiguredClockSpeed
------------- ----- ---------------------
DIMM_A2 6000 6000
DIMM_B2 6000 6000If SMBIOSBIOSVersion matches the new number from your manufacturer’s support page and ConfiguredClockSpeed matches your memory kit’s rated speed rather than a slower JEDEC fallback like 4800, the update succeeded end to end. Follow up with a short stability check, since firmware changes occasionally shift voltage defaults. A GPU and CPU stress test for 20-30 minutes is enough to catch anything unstable before you trust the system with real work.
8 Common Pitfalls That Brick Motherboards During a BIOS Update
Bricked boards are rare relative to the number of successful updates completed every day, but nearly every reported case traces back to one of these eight mistakes.
The one rule that matters most: never interrupt the flash.
Syncro Secure, Technical writing team (syncrosecure.com)
- Interrupting power mid-flash. A blip from an unstable outlet, a laptop battery that dies, or someone bumping the power switch during the write can corrupt the firmware chip entirely.
- Downloading the wrong file. Same board name, wrong revision, and the flash tool either rejects the file outright or, worse, writes it anyway and leaves the board unable to POST.
- Skipping the settings backup. Not fatal to the hardware, but losing a carefully tuned fan curve or memory profile turns a 45-minute update into a much longer afternoon.
- Using an NTFS or exFAT USB drive. Most UEFI flash utilities only read FAT32. The drive will simply not appear in the file browser, which looks like a bigger problem than it is.
- Flashing a laptop on battery alone. Even a battery reading 80% can behave unpredictably under the power draw of a firmware write. Keep the charger plugged in regardless of the displayed charge level.
- Installing a beta BIOS on a daily-driver PC. Beta firmware often ships with known issues clearly listed in the changelog. Great for testing on a secondary system, risky for the machine you need working tomorrow.
- Forgetting to clear CMOS after a downgrade. Rolling back to an older version can leave incompatible settings in the CMOS. A quick clear (jumper or button) after a downgrade avoids a no-boot loop.
- Assuming EXPO and Resizable BAR survive the update. They almost never do. Plan on re-enabling both manually every time, not just the first.
That last point is worth repeating in its own words, since it’s the single most common source of “my BIOS update made things worse” reports online.
A power loss or a forced restart during the update can corrupt the firmware and leave the device bricked, so secure power and let it finish.
Syncro Secure, Technical writing team (syncrosecure.com)
Troubleshooting Guide: 10 Fixes for Common BIOS Update Problems
Most post-update problems fall into one of ten categories, and nearly all of them fix in under ten minutes.
| Symptom | Likely Cause | Fix |
|---|---|---|
| No display after the update | Monitor cable plugged into the wrong output (integrated vs. dedicated GPU) | Move the cable to the correct port, reseat the GPU, clear CMOS if it persists |
| Stuck on “Flashing…” past 15 minutes | Corrupted download or a failing USB drive | Do not power off. If genuinely frozen, use the flashback recovery method once safe to do so |
| USB drive not detected by the flash tool | Drive formatted as NTFS/exFAT, or has multiple partitions | Reformat as a single-partition FAT32 drive using Diskpart |
| “BIOS capsule not compatible” error | Wrong board revision or wrong socket file downloaded | Re-check the exact model and revision, then re-download from the official page |
| RAM running below rated speed post-update | EXPO/XMP profile reset to JEDEC defaults | Re-enable the EXPO or XMP profile manually in BIOS memory settings |
| Boot order keeps resetting after every restart | Low CMOS battery, or settings not explicitly saved | Save with F10 before exiting, check CMOS battery voltage if it recurs |
| Fans running at full speed constantly | Fan curves reset to a default silent or full-speed profile | Reconfigure fan curves in BIOS or your vendor’s fan-control software |
| Dual-BIOS switched to the backup chip | Primary chip’s flash failed mid-write | Reflash the primary chip using the backup as a source, per your board’s manual |
| Flashback LED blinks indefinitely | Wrong filename, or file not saved to the drive’s root folder | Confirm the exact filename format from the support page and place it in the root directory |
| Resizable BAR or Above 4G Decoding disabled | Setting reverted to default after the flash | Re-enable manually under Advanced or PCI settings before your first Windows boot |
Microsoft’s own community support threads confirm a pattern worth remembering here: the vast majority of “my PC won’t boot after a BIOS update” reports resolve through a CMOS clear and a fresh load of optimized defaults, not a motherboard replacement. Panic is the most common reason a fixable problem turns into an unnecessary RMA.
Advanced Tips: AGESA, Resizable BAR, and EXPO Memory Profiles
Once you’re comfortable with the basic process, a few deeper details separate a routine update from one that actually improves your system.
Read the AGESA changelog, not just the version number. AMD’s AGESA code sits underneath the BIOS your motherboard vendor ships, and different vendors package the same AGESA release with different default settings. Two boards on the “same” AGESA version can still behave differently depending on what each manufacturer changed around it. Check your specific board’s changelog rather than assuming a version bump means the same fix across every brand.
Resizable BAR needs a matching GPU driver, not just a BIOS setting. Enabling Resizable BAR (AMD calls its version Smart Access Memory) in the BIOS is only half the requirement. Your GPU driver needs to support it too, and Windows needs Above 4G Decoding enabled in the same BIOS menu for the feature to actually activate. Check all three after every update, since a flash can silently disable any of them.
EXPO and XMP are not interchangeable, but modern boards read both. XMP is Intel’s memory overclocking profile format. EXPO is AMD’s equivalent, introduced for DDR5. Most current boards from either camp can read both profile types regardless of which CPU brand you’re running, but a BIOS update occasionally changes which one loads by default. If your RAM kit lists both an XMP and EXPO speed, confirm you’re using the correct profile for your actual CPU platform after any update.
Consider a security-only update even if you don’t need new features. Not every BIOS revision adds CPU support or performance changes. Some exist purely to patch a firmware-level vulnerability, the way AMD’s AGESA 1.2.0.3e reportedly addressed a TPM exposure issue. Those are worth installing even on a system that otherwise runs perfectly, since no antivirus or Windows update can reach a vulnerability that lives below the operating system.
Multi-BIOS boards double as a safe testing ground. If your motherboard has dual BIOS chips, use the secondary chip to test a new firmware version while keeping your known-good configuration on the primary chip as a fallback. Gigabyte reinforced that exact workflow on March 26, 2026, when it detailed new firmware built around parallel Q-Flash and Q-Flash Plus update paths, and the approach showed up in a real release on July 20, 2026, when the B650 Gaming X AX V2 got BIOS F42c, a 15.2MB update. It turns an update from a one-way decision into one you can reverse in minutes.
Check firmware version right after buying a used board or a pre-built PC. Boards that sat in a warehouse or a retailer’s shelf for months often ship with whatever version was current at manufacturing time, sometimes a year or more behind. ASRock’s own changelogs show exactly why that matters: its B860M-STX board jumped to BIOS 6.01 on August 19, 2026, updating the Intel Management Engine firmware to version 19.0.5.2175, while the B760M Pro RS moved to BIOS 13.01 on July 3, 2026, to set CPU microcode at 0x133, the kind of update a shelf-stale board could easily be missing. It’s one of the first things worth checking on any new-to-you system, before you invest time tuning settings that a pending update might reset anyway.
Frequently Asked Questions About Updating Your BIOS
How do I know if I actually need to update my BIOS?
Compare your current version against the latest one listed on your motherboard’s support page. Update if you’re installing a new CPU the board didn’t originally support, want full EXPO/XMP speed on new RAM, or the changelog lists a security fix. Skip it if your system is already stable and the new version doesn’t change anything relevant to you.
Is it safe to update BIOS without a CPU installed?
Yes. That’s exactly what USB BIOS Flashback, Q-Flash Plus, and similar brand-specific features exist for. They read the firmware file directly off a USB drive using standby power, before the CPU, RAM, or GPU ever enter the process, which is why several manufacturers treat it as the safer default rather than a last resort.
Can updating a laptop’s BIOS brick it?
Yes, and in some ways more easily than a desktop, since most laptops lack a dual-BIOS recovery chip. Keep the charger connected throughout, confirm the battery sits above roughly 20%, and avoid interrupting the process once it starts.
What’s the actual difference between BIOS and UEFI?
BIOS is the older, keyboard-only firmware standard dating back to the 1980s, limited to booting drives under roughly 2.2TB. UEFI is the modern replacement, with mouse support, boot drives beyond that limit, faster startup times, and Secure Boot. Almost every board sold since around 2015 runs UEFI, but “BIOS” stuck around as the everyday name out of habit.
Do I need to update BIOS every time a new CPU launches?
Only if you or someone using your board is installing that specific new CPU. Chips you’re already running don’t stop working because a newer AGESA or microcode version exists. Updates mainly matter when you’re adding new hardware or chasing a documented fix that affects your setup.
How long does a BIOS update actually take?
The flash itself typically runs three to eight minutes depending on brand and file size. Budget closer to 45 minutes in total once you include downloading the file, verifying its checksum, formatting a USB drive, and reconfiguring EXPO/XMP and boot order afterward.
Will a BIOS update erase my files or my Windows installation?
No. BIOS firmware lives on a separate chip from your storage drives and has no access to your operating system or personal files. The only things at risk are settings stored in the BIOS itself, like boot order and fan curves, which typically reset to default after a flash.
What do I do if the flash fails and my board doesn’t have dual BIOS?
Try the brand’s no-CPU flashback method first, since it often succeeds even after a failed in-BIOS flash. If that also fails, check whether your motherboard maker offers a mail-in BIOS chip reflashing or replacement service. ASUS, MSI, Gigabyte, and ASRock all run programs for exactly this situation, and it’s typically far cheaper and faster than replacing the entire board.
Should I update BIOS on Windows 11 differently than on Windows 10?
No. The flashing process itself, whether through the UEFI menu or a Windows-based live-update tool, works the same on both. The one practical difference is that Windows 11’s stricter TPM and Secure Boot requirements mean a security-focused BIOS update is more likely to affect a setting you’re actively relying on, so it’s worth confirming Secure Boot and TPM are still enabled after any flash on a Windows 11 system.
Related Coverage
- How to Apply Thermal Paste: 12 Steps, 45 Min [2026]
- Fix PC Fan Airflow Direction: 12 Steps, 45 Min [2026]
- How to Stress Test a GPU and CPU: 12 Steps, 60 Min [2026]
- Flash QMK/VIA Firmware on a Keyboard: 12 Steps, 90 Min [2026]
- RAM Prices Jump 63% as DRAM Hits Record $20 a Chip [2026]
- Ryzen 7 5800X3D Anniversary Chip Scalped at $600+ [2026]
