BIOS Flashback lets you write a fresh firmware image to a motherboard that cannot boot, or to a board with no CPU installed at all. You copy one file to a USB stick, plug it into a marked port, press a button, and watch an LED. ASRock’s Flashback instructions put the finish line in one sentence: wait until the LED stops blinking, because that means the flash is done.
This tutorial covers the whole job in 13 steps and roughly 30 minutes of hands-on time, whether your board carries an ASUS, Gigabyte, MSI or ASRock badge. If your PC still boots and the setup menu works, a normal in-BIOS update carries less risk, and our 12-step guide to updating BIOS safely walks through that route. Flashback earns its keep when a new CPU will not post on an older board, or when a failed update left the machine dark.
As of October 22, 2026, ASUS, Gigabyte and MSI all still document the feature under their own names, and none of the vendor pages we checked announce a rename or retirement. You will leave with a working USB recovery stick, a pre-flight checklist, a troubleshooting table with 10 entries, and a PowerShell script that prepares and verifies the stick for you.
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 BIOS Flashback Actually Does
A motherboard stores its firmware (the BIOS or UEFI image) on a small flash chip. Normally the CPU runs a flashing routine from inside the setup menu, which is why a regular update needs a working processor, memory and often a graphics output. BIOS Flashback moves that job to a small standalone controller on the board. It reads a file from the USB stick and writes it to the chip using only standby power from the PSU.
That design explains every rule you will see below. The controller looks for a specific file name in the root folder of the stick. It reads from one marked USB port and ignores the rest. It needs the PSU switched on at the wall and the board powered in standby, while the PC itself stays off. Gigabyte describes its version, Q-Flash Plus, as a way to update the BIOS without installing the CPU, memory or graphics card, and ASUS and MSI make the same promise for their supported boards.
Flashback does not fix a broken board, a bad CPU or a dead PSU. It rewrites firmware and nothing else. If the LED never reacts, the cause is nearly always the file name, the stick format, the port, or a board that does not have the feature. The Adamant IT channel gives the quick test in a video on BIOS Flashback support. The host says the board needs to support it, and the usual signs are a specifically marked USB port on the back plus a button.
Treat the feature as model-specific. ASUS does not offer it on every board, and MSI’s own material treats BIOS ROM capacity and the Flash BIOS Button as separate specifications, so a big ROM chip does not imply a button. Check your spec sheet before you plan around it.
Do You Need Flashback or the In-BIOS Tools? Three Scenarios
The first scenario is the classic one. You bought a newer CPU for an older socket, the board shipped with a BIOS that predates it, and the PC shows no picture. Without Flashback you would need an older supported CPU to borrow. With it, you flash the new BIOS and boot the new chip. Builders on AM5 run into this often, and our breakdown of B850, X870 and X870E boards shows how many chipset tiers share the same socket and therefore the same early-BIOS risk.
The second scenario is a failed or interrupted update. If a power cut hit mid-flash and the board now loops or stays black, Flashback can overwrite the damaged image. The third scenario is cautious preparation. If you plan a CPU swap next week, flashing the board first (while it still boots) removes a whole category of surprises.
Gigabyte reportedly announced day-one support for upcoming LGA1700 processors across its B760 and H610 lineup in early October 2026. That kind of announcement usually arrives as a BIOS release, which makes Flashback the safety net if you pair a new chip with an older stock board. If your board is current and everything works, though, Gigabyte itself cautions that flashing carries some risk and recommends against updating a BIOS that runs correctly.
Unusual boards may lack the feature entirely, so read the spec sheet instead of assuming a button exists. No button and no marked port means this tutorial does not apply, and you should plan on the in-BIOS route or the vendor’s service channel.
Every vendor ships two update paths. The in-BIOS tools (ASUS EZ Flash, Gigabyte Q-Flash, MSI M-FLASH) run from the setup menu and need a booting system. Flashback runs from the outside. Pick based on the state of the machine, not on habit.
| Situation | Best route | Why |
|---|---|---|
| PC boots and setup menu opens | In-BIOS tool (EZ Flash, Q-Flash, M-FLASH) | The tool can read the file from inside the firmware and the CPU, RAM and GPU are all proven to work |
| New CPU installed, no picture | BIOS Flashback | The old firmware cannot recognize the chip, so the menu is unreachable |
| Update failed and the board loops | BIOS Flashback | It rewrites the image without needing the damaged firmware to run |
| Brand-new board, no CPU yet | BIOS Flashback | You can update before the first install, which avoids a borrowed CPU |
| Board has no marked port or button | In-BIOS tool or vendor service | No Flashback controller means nothing to trigger |
ASUS has pointed users toward both EZ Flash and BIOS Flashback when advising on stability updates for its AMD 800-series boards, according to an ASUS statement from earlier in 2026. The practical lesson is that the two tools overlap, and Flashback simply works in more situations.
Prerequisites, Versions and a Pre-Flight Checklist
You need less than most tutorials suggest, but each item matters. Gather everything before you open the case, since you will want the PC powered down and the PSU switch within reach.
- A motherboard with a Flashback feature. Look for a labeled USB port on the rear I/O and a button (on the I/O panel or on the PCB). Confirm on the vendor spec sheet for your exact model and revision.
- A second computer running Windows 10 or Windows 11, Linux or macOS, to download and prepare the file. The project script later in this article needs Windows PowerShell 5.1 (included with Windows) or the latest PowerShell 7.
- A USB flash drive of 1 GB or more. ASUS lists a capacity of at least 1 GB and a single-sector drive in FAT16 or FAT32 with an MBR layout. A small, older stick often behaves better than a large new one.
- The latest version of 7-Zip (or any archive tool) to unpack the BIOS download.
- The vendor renaming tool, if your vendor uses one. ASUS provides BIOSRenamer. Download the latest version from the ASUS support page for your board.
- A working PSU with the 24-pin and the CPU 8-pin cables connected. Gigabyte’s documented procedure calls for both cables.
- Your board’s manual as a PDF, open on the second computer, for the exact port label and LED pattern.
- About 30 minutes of hands-on time, plus the flash itself. ASUS support material reportedly puts the flash at up to roughly eight minutes depending on file size.
You do not need a CPU, RAM, a GPU, a monitor or a keyboard. In fact, taking the CPU and GPU out of the picture removes variables when you troubleshoot. If the CPU is already installed and the board boots, leave it in place. Nothing in this procedure requires removing parts.
Flashback Names and Rules by Vendor
Every vendor uses its own branding, file name rule and port label. The table below lists what the vendors publish today. Where a rule varies by model, the table tells you to check your manual instead of guessing, because a wrong file name is the number one reason a flash never starts.
| Vendor | Feature name | File rule | USB format | Works with no CPU or RAM |
|---|---|---|---|---|
| ASUS | USB BIOS FlashBack | Run BIOSRenamer to produce a board-specific .CAP file | FAT16 or FAT32, MBR, 1 GB or more | Yes, on boards that list the feature |
| Gigabyte | Q-Flash Plus | Rename the BIOS file to gigabyte.bin | FAT-formatted USB drive | Yes, no CPU, memory or graphics card needed |
| MSI | Flash BIOS Button | Check the MSI page for your exact model | Check the MSI page for your exact model | Yes, on supported boards |
| ASRock | BIOS Flashback | Follow the ASRock Flashback guide for your board | Check the guide | Yes, wait for the LED to stop blinking |
Two details deserve emphasis. First, ASUS publishes the 1 GB minimum and the single-sector requirement, which rules out a few odd drives that report unusual sector sizes. Second, Gigabyte wants the exact BIOS file for the exact board revision, and the revision lives on a sticker or silkscreen on the PCB (for example “Rev. 1.3”). Two boards with the same name but different revisions can take different BIOS files.
For MSI, one forum support reply from early October 2026 tells users to format the stick as FAT32 and rename the extracted file to MSI.ROM. Treat that as community guidance. MSI’s own page for your model is the authority, and the file name can differ.
Run through this list before step 1. Each line prevents a specific failure that appears later in the troubleshooting table. Skipping it saves two minutes and can cost an evening.
| Check | Pass condition | Prevents |
|---|---|---|
| Port and button located | You found both on the board or in the manual | Wasted time on a board without the feature |
| Revision confirmed | Sticker or silkscreen matches the download page | Flashing an image meant for another revision |
| Release notes read | You know if it is beta and what it adds | Surprise rollback limits |
| Stick is small and empty | FAT32, MBR, nothing but one file | Silent LED, unreadable media |
| PSU cables seated | 24-pin and 8-pin connected, PSU switch on | No standby power for the controller |
| Recovery key saved | BitLocker key stored off the PC | Locked boot after a firmware change |
| Ten minutes free | No need to touch the PC during the flash | Interrupting a running write |
Steps 1 to 3: Identify the Board, Read the BIOS Version, Study the Release Notes
Step 1: Identify the exact model and revision. If the PC still runs, ask Windows. Open PowerShell and run the commands below. If the board is already out of the case or dead, read the model name from the silkscreen and the revision from the sticker near the PCI Express slots or from the box.
Get-CimInstance Win32_BaseBoard | Select-Object Manufacturer, Product, Version
Get-CimInstance Win32_BIOS | Select-Object Manufacturer, SMBIOSBIOSVersion, ReleaseDateExample output (your values will differ):
Manufacturer Product Version
------------ ------- -------
Gigabyte B650M D2H x.x
Manufacturer SMBIOSBIOSVersion ReleaseDate
------------ ----------------- -----------
American Megatrends F5 2/14/2025 12:00:00 AMOn Linux, sudo dmidecode -t baseboard and sudo dmidecode -s bios-version give the same information. The revision does not always appear in software. The “Version” field often shows a placeholder, so trust the physical label.
Step 2: Record the current BIOS version. Write it down next to the board revision. If the update goes sideways you will want a record of what was installed before. Also photograph your current BIOS settings if the PC boots, since a flash usually resets them to defaults. MSI’s own guide tells users to restore customized BIOS settings to defaults before updating, so a clean slate is normal.
Step 3: Read the release notes for the target version. Open the vendor’s support page for your exact model and revision. ASUS’s BIOS download pages flag beta builds and list changes such as AGESA ComboAM5 PI 1.3.0.1d, better memory performance and CXMT-memory compatibility. Gigabyte pages list microcode and AGESA updates the same way. Read three things: whether the release is beta, which CPUs it adds, and whether it carries a warning about rollback.
Rollback warnings are real. On several Intel boards, ASUS says the BIOS update also updates the Intel Management Engine, and that the ME version stays updated even if you later roll back the BIOS. For 11th-generation Intel CPU support on some boards, ASUS states the ME firmware inside the UEFI BIOS must be version 14.1.51.1528 or newer. Read those notes before you flash, not after. Our 13-step BIOS update guide explains how to decide whether a given release is worth installing at all.
Steps 4 and 5: Download the Right File and Rename It
Step 4: Download from the vendor only. Use the support or download page for your board. Avoid mirror sites, forum attachments and “BIOS packs.” A BIOS image is code that runs before your operating system, and firmware signing exists for a reason. You want the file the vendor published for your board revision, with nothing in between.
Pick the newest stable release unless you need a beta for a specific CPU. Unpack the archive with 7-Zip into an empty folder. Inside you will usually find the image file plus a text file or small utility. Keep the folder name short and free of spaces to avoid typos later.
Step 5: Rename according to your vendor’s rule. This is where most failed attempts start. The rules differ:
- ASUS: run BIOSRenamer on the extracted file. It outputs a board-specific .CAP name (one workstation board listing reportedly shows A5720.CAP, for instance). Do not rename it by hand, because the tool picks the name the board expects.
- Gigabyte: rename the file to
gigabyte.binin lowercase. Gigabyte’s own procedure also requires the 24-pin and 8-pin power cables connected. - MSI: follow the MSI page for your model. Community guidance points to MSI.ROM, which you should confirm before relying on it.
- ASRock: follow ASRock’s Flashback guide, which specifies the file name for the board.
Show file extensions in Windows Explorer before you rename (View, Show, File name extensions). Otherwise you can end up with gigabyte.bin.bin, a classic mistake that leaves the LED silent. You can confirm what you have from PowerShell:
Get-ChildItem .\bios-work | Select-Object Name, Length
Get-FileHash .\bios-work\gigabyte.bin -Algorithm SHA256Example output:
Name Length
---- ------
gigabyte.bin 33554432
Algorithm Hash Path
--------- ---- ----
SHA256 3F1C...9A7E C:\bios-work\gigabyte.binThe hash serves one purpose here. Later you compare it with the copy on the stick, which catches a corrupted transfer. Vendors do not always publish checksums, so do not expect to match an official value.
Steps 6 and 7: Format the USB Stick and Copy the File
Step 6: Format the stick as FAT32 with an MBR layout. ASUS asks for FAT16 or FAT32 with MBR. FAT32 is the safe common denominator across vendors. Windows refuses to format FAT32 above 32 GB with its built-in tools, which is one more reason to reach for a small stick. Back up anything on the drive first, since this erases it.
On Windows, use diskpart. Read the disk list carefully. Selecting the wrong disk wipes it, and diskpart will not ask twice.
diskpart
list disk
select disk 2
clean
convert mbr
create partition primary
format fs=fat32 quick label=FLASH
assign
exitReplace 2 with the number of your USB stick, which you identify by size. On Linux the equivalent is:
lsblk -f
sudo parted /dev/sdX --script mklabel msdos mkpart primary fat32 1MiB 100%
sudo mkfs.vfat -F 32 -n FLASH /dev/sdX1Swap sdX for the real device. A typo here can erase the wrong drive, so double-check with lsblk before pressing Enter. On macOS, Disk Utility can create a “MS-DOS (FAT)” volume with a Master Boot Record scheme, which gives the same result.
Step 7: Copy only the renamed file to the root of the stick. Root means the top level, not inside a folder. Do not add the release notes, the original archive or the vendor utility. One file, correct name, nothing else. Then safely eject the drive from the operating system, because an unflushed copy is a quiet cause of a flash that does nothing.
Verify before you walk away. Open the stick and confirm the file appears exactly once with the right name and a size that matches the original. If you want certainty, run Get-FileHash on the copy and compare it with the hash from step 5. The project section below automates this check.
Steps 8 and 9: Set Up Power and the Correct USB Port
Step 8: Prepare the power state. Shut the PC down completely and leave the PSU plugged in and switched on. The flash controller runs on standby power, so unplugging the PSU kills the procedure. Gigabyte’s documentation specifies connecting both the 24-pin motherboard connector and the 8-pin CPU connector, so do that on every brand to be safe. If you work on an open bench, make sure nothing metal sits under the board.
Disconnect anything you do not need. A keyboard and mouse are fine, but extra drives, capture cards and RGB controllers only add noise. You do not need a display. If a CPU and GPU are already installed, leave them where they are.
Step 9: Find the marked Flashback port and plug in the stick. The port sits on the rear I/O panel, usually labeled “BIOS,” “Flash BIOS,” “Q-Flash Plus” or “FlashBack.” Many boards mark it with a different color or a printed label. Plain USB ports will not work, since the controller only reads from the one it is wired to. Use the board manual to confirm which port, and watch for boards where the label sits on the PCB edge and not on the panel.
Insert the stick firmly. A half-seated drive is invisible to the controller. If the stick has its own activity light, expect it to flicker once you press the button.
Steps 10 and 11: Trigger the Flash and Wait for the LED
Step 10: Press the button. The button sits on the rear I/O or on the PCB near the port. ASUS support material reportedly says to hold it for about three seconds until the indicator starts blinking. Gigabyte and MSI describe pressing the Q-Flash Plus or Flash BIOS button with the system powered off. Read your manual for the exact press length, because it varies by model.
After you press it, the LED changes behavior. The exact pattern is vendor and model specific. ASRock’s guide says the LED starts to blink once the flash begins. If nothing happens within a few seconds, do not keep pressing. Stop and jump to the troubleshooting table.
Step 11: Wait, and do nothing else. This step costs you the most patience. According to ASUS support, the flash can take up to about eight minutes depending on file size, and it finishes when the FlashBack light turns off. An MSI forum support reply puts the blinking at roughly 5 to 8 minutes before the board reboots, and warns that unusually short or very long activity may mean the flash failed. Both figures are guidance, not guarantees.
ASRock gives the finish condition in its published steps: “Wait until the LED stops blinking, indicating that BIOS flashing has been completed.” ASUS states the prohibition in the sternest terms. Its support documentation says: “Please do not remove the USB flash drive, unplug the power supply, turn on the power or press the CLR_CMOS button during the execution.” Those four actions interrupt the update and can leave the system unable to boot.
Set a timer for ten minutes and leave the room if you must. The most expensive mistake in this whole process is impatience. A board that looks idle may still be erasing and rewriting the chip.
Steps 12 and 13: First Boot, Verification and Settings Recovery
Step 12: Boot and verify the new version. Once the LED goes dark or the board reboots by itself, remove the stick, install your CPU, RAM and GPU if you removed them, and power on. The first boot after a flash often takes longer than usual, because the board retrains memory. Give it a few minutes before you assume a failure.
Enter setup (usually Delete or F2) and read the BIOS version on the main screen. It should match the file you flashed. You can also confirm from Windows:
Get-CimInstance Win32_BIOS | Select-Object SMBIOSBIOSVersion, ReleaseDateExample output after a successful flash (version text will differ by board):
SMBIOSBIOSVersion ReleaseDate
----------------- -----------
F6 9/23/2026 12:00:00 AMStep 13: Restore your settings in a deliberate order. Load defaults first, save, and confirm the system is stable. Then re-enable your memory profile (XMP or EXPO), fan curves, boot order and any virtualization options one at a time. Gigabyte reportedly shipped an A620M H release in September 2026 that improved AMD EXPO performance, so memory behavior can change between versions even when your profile name stays the same.
Finish with a stress test if you changed the CPU or memory. Run a memory test and a CPU load for 20 to 30 minutes and watch for crashes. Store the stick in an anti-static bag with a label showing the board model and BIOS version, so you own a ready recovery tool for next time.
Common Pitfalls That Waste an Evening
Almost every failed Flashback attempt traces back to one of the mistakes below. Skim them before you start, and again if the LED misbehaves.
- Wrong board revision. Boards with the same name and different revisions can use different files. Verify the sticker. Gigabyte documents its procedures per exact revision, and the page for another revision may differ.
- Skipping the rename. The controller searches for one name. A file called
B650M-D2H.F5is invisible to it, and so isgigabyte.bin.bin. - Using the wrong USB port. Only the labeled port feeds the controller. A front-panel header or a standard rear port will not trigger a flash.
- Formatting as exFAT or NTFS, or using GPT. ASUS specifies FAT16 or FAT32 with MBR. A stick that opens fine in Windows can still be unreadable to the firmware.
- Interrupting the flash. Turning the PC on, pressing CLR_CMOS, pulling the stick or cutting the PSU mid-flash is the fastest way to a dead board. Our guide on how to clear CMOS shows the right moment to use that button, which is after the flash and never during it.
- Flashing a beta without reading the notes. ASUS flags beta builds, and for one AM5 board it reportedly warned that an earlier related version cannot be rolled back. Use stable releases unless you need the beta for a CPU.
- Putting several files on the stick. Extra files, including a second BIOS image, can confuse some controllers. Keep the stick to one file.
- Ignoring the Intel ME note. On certain ASUS Intel boards the ME update stays after a BIOS rollback, so a downgrade does not fully restore the earlier state.
Troubleshooting: 10 Flashback Problems and Fixes
Indicator behavior varies by vendor and board, so treat the symptom column as a pattern to match against your manual. The fixes run in order from cheapest to most drastic.
| # | Symptom | Likely cause | Fix |
|---|---|---|---|
| 1 | LED does nothing after the button press | Wrong file name or wrong port | Recheck the rename rule and the labeled port, then reseat the stick and try again |
| 2 | LED stays solid and never blinks | Stick not recognized, wrong format or file not in root | Reformat as FAT32 with MBR, copy one file to the root, try a different small stick |
| 3 | LED blinks for only a few seconds, then stops with no reboot | Corrupt file or file for another board | Download again from the vendor page for your exact revision and compare hashes |
| 4 | LED blinks far longer than expected | Flash still running or stalled | Wait the documented time. If it clearly hangs well beyond that, power off at the PSU and retry from step 8 |
| 5 | Board reboots but shows the old BIOS version | Flash did not take, or a different image booted | Repeat with the file fully renamed, and check for a dual BIOS switch on the board |
| 6 | No picture after a successful flash | Memory retraining after the update | Wait several minutes, then try one RAM stick in the slot the manual recommends |
| 7 | System boots but settings are gone | Normal reset to defaults | Re-enter settings in the order described in step 13 |
| 8 | Windows asks for the BitLocker recovery key | Firmware change altered measured boot values | Enter the recovery key, then suspend BitLocker before future flashes |
| 9 | New CPU still will not post | BIOS version does not support the CPU yet | Check the CPU support list for your board and flash a version that adds it |
| 10 | Flash completes but the PC crashes under load | Memory or voltage defaults changed | Reset to defaults, run a memory test, then reapply XMP or EXPO |
A deeper look at problem 2. A solid LED usually means the controller never found a valid file. Start with the stick. Swap it for a smaller one if you can, and format it from scratch with the diskpart sequence above. Then verify the file name character by character, including case. Windows hides extensions by default, so a name that looks right in Explorer can be wrong underneath.
A deeper look at problem 3. A flash that ends too quickly often means the controller rejected the image. Common reasons are a BIOS for a different revision, a partial download, or an archive that was not fully extracted. Download again and unpack with 7-Zip. Compare the file size to the vendor listing if one is shown.
A deeper look at problem 9. This one catches people who flash successfully but pick the wrong version. Support lists show the minimum BIOS for each CPU. For 11th-generation Intel on some ASUS boards, the Intel ME firmware in the BIOS must be version 14.1.51.1528 or newer, per ASUS’s own FAQ, so a BIOS that predates that will not run the chip. If you flashed an older release, repeat the process with the newer one.
If you work through all ten items and the LED stays dead, the board may not have a working Flashback controller, or the flash chip may have failed. At that point, contact the vendor with your model, revision and a description of the LED behavior. Do not keep flashing in a loop.
Advanced Tips for Repeat Flashers
Roll back with the Intel ME caveat in mind
Flashback can install an older BIOS as easily as a newer one, which makes it a handy downgrade tool when a release introduces a regression. On certain ASUS Intel boards, though, the vendor says the ME update persists after the BIOS goes back. Read the note on the download page before you downgrade, and never assume a rollback restores every firmware component.
Stage a CPU upgrade in the right order
If you plan a new CPU, flash first while the old CPU still boots, confirm the version, and only then swap the chip. When the old CPU is gone, Flashback is your fallback. Check the vendor’s CPU support table for the minimum BIOS and flash that version or newer. Gigabyte’s support listings for some B760 boards reportedly mention a September 2026 microcode update and preparation for upcoming processor support, so release notes often tell you which chips a version adds.
Keep a labeled recovery stick per board
Keep one small stick per machine, each holding only the file for that board. Put a strip of tape on it with the model, revision and BIOS version. When something breaks at 11 p.m., you will not need to search for downloads. If you build or tune several systems, you will find more hardware how-tos in our hardware section.
Also consider suspending BitLocker or device encryption before any firmware change. Windows can treat a new BIOS as a hardware change and demand the recovery key on the next boot. Save that key somewhere safe before you start.
Complete Working Project: A Flashback Stick Preparation Script
The script below turns steps 5 to 7 into one command. It checks the drive format, partition style and bus type, applies the vendor file name, copies the file, compares SHA256 hashes of source and copy, and writes a short report to your desktop. It refuses to run when the stick fails a check, which stops you from discovering the problem at the board.
Save it as New-FlashbackStick.ps1. It needs Windows PowerShell 5.1 or the latest PowerShell 7 and an elevated prompt for the storage cmdlets. It does not format anything, so it cannot erase a drive.
#requires -Version 5.1
[CmdletBinding()]
param(
[Parameter(Mandatory)][string]$BiosFile,
[Parameter(Mandatory)][ValidateSet('asus','gigabyte','msi','asrock')][string]$Vendor,
[Parameter(Mandatory)][ValidatePattern('^[A-Za-z]$')][string]$DriveLetter,
[string]$TargetName
)
$ErrorActionPreference = 'Stop'
$defaults = @{ gigabyte = 'gigabyte.bin'; msi = 'MSI.ROM' }
if (-not (Test-Path -LiteralPath $BiosFile)) { throw "BIOS file not found: $BiosFile" }
$src = Get-Item -LiteralPath $BiosFile
if (-not $TargetName) {
if ($defaults.ContainsKey($Vendor)) { $TargetName = $defaults[$Vendor] }
elseif ($Vendor -eq 'asus') { $TargetName = $src.Name }
else { throw "Pass -TargetName for $Vendor (see the vendor Flashback guide)." }
}
$problems = @()
$warnings = @()
if ($Vendor -eq 'asus' -and $src.Extension -ine '.CAP') {
$problems += 'ASUS needs the .CAP file produced by BIOSRenamer'
}
$vol = Get-Volume -DriveLetter $DriveLetter
$part = Get-Partition -DriveLetter $DriveLetter
$disk = Get-Disk -Number $part.DiskNumber
if ($vol.FileSystem -ne 'FAT32') { $problems += "File system is $($vol.FileSystem), need FAT32" }
if ($disk.PartitionStyle -ne 'MBR') { $problems += "Partition style is $($disk.PartitionStyle), need MBR" }
if ($disk.BusType -ne 'USB') { $problems += "Drive is on the $($disk.BusType) bus, not USB" }
if ($vol.Size -lt 1GB) { $problems += 'Drive is smaller than 1 GB' }
if ($vol.Size -gt 32GB) { $warnings += 'Drive is over 32 GB, a smaller stick is safer' }
$root = "${DriveLetter}:\"
$extra = Get-ChildItem -LiteralPath $root -Force |
Where-Object { $_.Name -ne $TargetName -and $_.Name -notlike 'System Volume*' }
if ($extra) { $warnings += "Extra items in root: $($extra.Name -join ', ')" }
if ($problems) {
$problems | ForEach-Object { Write-Host "FAIL $_" -ForegroundColor Red }
exit 1
}
$dest = Join-Path $root $TargetName
Copy-Item -LiteralPath $src.FullName -Destination $dest -Force
$h1 = (Get-FileHash -LiteralPath $src.FullName -Algorithm SHA256).Hash
$h2 = (Get-FileHash -LiteralPath $dest -Algorithm SHA256).Hash
if ($h1 -ne $h2) { throw 'Hash mismatch after copy. Try another stick.' }
$stamp = Get-Date -Format 'yyyyMMdd-HHmm'
$report = Join-Path ([Environment]::GetFolderPath('Desktop')) "flashback-prep-$stamp.txt"
@(
"Vendor : $Vendor"
"Source : $($src.FullName)"
"Copied as : $dest"
"Size (bytes): $($src.Length)"
"SHA256 : $h1"
"Drive : $($vol.FileSystem), $($disk.PartitionStyle), $([math]::Round($vol.Size/1GB,1)) GB"
"Warnings : $($warnings -join ' | ')"
) | Set-Content -LiteralPath $report
Write-Host "PASS Stick ready. Report: $report" -ForegroundColor Green
$warnings | ForEach-Object { Write-Host "WARN $_" -ForegroundColor Yellow }
Write-Host 'Next: eject the stick, plug it into the Flashback port with the PC off and PSU on.'Run it like this for a Gigabyte board, with the stick mounted as drive E:
.\New-FlashbackStick.ps1 -BiosFile C:\bios-work\B650MD2H.F5 -Vendor gigabyte -DriveLetter EExample output on success:
PASS Stick ready. Report: C:\Users\you\Desktop\flashback-prep-20261022-2014.txt
Next: eject the stick, plug it into the Flashback port with the PC off and PSU on.Example output when the stick fails a check:
FAIL File system is exFAT, need FAT32
FAIL Partition style is GPT, need MBRThree parts of the script carry the weight. The vendor table at the top maps each brand to its file name, and the -TargetName switch overrides it when your manual says otherwise. The drive checks mirror the prerequisites list, so a stick that passes here meets the ASUS format requirement and the common FAT32 baseline. The hash comparison catches the rare corrupted copy that would otherwise show up as a silent LED.
For ASUS, run BIOSRenamer first and pass the resulting .CAP file, since the script keeps its name. For ASRock, pass -TargetName with the name from the ASRock Flashback guide for your board. For MSI, confirm the default MSI.ROM against your model’s support page, and override it if the page says something different.
The script keeps to one job. It prepares and verifies the stick, and everything that touches the board stays manual. That split is deliberate, because the risky part of the process is the physical flash, and no script should press that button for you.
Frequently Asked Questions
Does BIOS Flashback work without a CPU installed?
Yes, on boards that carry the feature. Gigabyte describes Q-Flash Plus as updating the BIOS without the CPU, memory or graphics card, and ASUS and MSI make the same claim for supported models. The board still needs standby power from a connected PSU.
Is BIOS Flashback safer than updating inside the BIOS menu?
Neither route is risk-free. The in-menu tools (EZ Flash, M-FLASH, Q-Flash) are fine when the PC boots normally. Flashback is the rescue route when the PC cannot boot. Use the menu when you can and Flashback when you must.
What USB format and size should I use?
Use FAT32 with an MBR partition table. ASUS lists a minimum of 1 GB and FAT16 or FAT32 with MBR. A small, older stick of 32 GB or less avoids the FAT32 size limits in Windows and tends to behave predictably.
How long does a Flashback update take?
Plan for up to about eight minutes. ASUS support material reportedly gives that upper figure, and an MSI forum reply describes roughly 5 to 8 minutes of blinking. Your manual has the authoritative number for your model.
Can I use any USB port for Flashback?
No. Only the port the manual labels for Flashback feeds the flash controller. Using another port is a frequent reason the LED never reacts.
Will a Flashback update erase my BIOS settings?
Expect a reset to defaults. MSI’s guide even advises restoring customized settings to defaults before updating. Photograph your settings first, then reapply them one at a time after the first successful boot.
Does every motherboard have BIOS Flashback?
No. The feature is model-specific, and vendors list it only on boards that include it. Look for a marked USB port and a button, and confirm on the spec sheet for your exact revision.
