A BIOS update is the one job on a PC where a small mistake can stop the machine from starting at all. Done in the right order it is a calm ten-minute task. This page is that order - every check that prevents a brick, in the sequence a careful technician follows.
The BIOS (or UEFI firmware) is the first software your motherboard runs - it wakes the hardware and hands over to Windows. Updating it can add support for a new CPU, fix real bugs and patch security holes. It is also the update people fear, because a wrong file or a power cut in the middle can leave a board that will not start. Almost every bricked board traces back to one of three causes: the wrong file, lost power, or a BitLocker lockout nobody prepared for. This routine removes all three before the flash ever begins.
Never update just because a newer version exists. Good reasons: the new CPU you are fitting needs it, the release notes name a bug you actually have, a security fix, or a stability problem the maker says it solves. If none of those apply, the safest update is no update - other pages in this series cover the decision in depth.
msinfo32 and press EnterThe update file must match your exact motherboard model and board revision - a revision 1.0 board and a revision 1.1 board can take different files. Get it from the motherboard or laptop maker's own support page for your model, and read the release notes: some boards must be updated in steps, through an intermediate version first.
This is the step whose absence causes the most panic. The TPM chip measures the firmware every boot, and a BIOS update changes those measurements - so a PC with BitLocker or device encryption can boot straight into a recovery key screen after the update. The data is safe; you just need the key you saved beforehand.
manage-bde -status C:manage-bde -protectors -get C: -type RecoveryPassword. Keep it on paper and on your phone, not only on this PCmanage-bde -protectors -disable C: (on Windows 11 you can add -RebootCount 2)A power cut during the two-to-ten minutes of writing is the classic way boards die. On a desktop, use a UPS if you have one and pick a time with stable mains - not during a storm or a known outage window. On a laptop, plug in the charger AND keep the battery charged; many laptop updaters refuse to run on battery alone, and that refusal is protecting you.
Restart and enter the BIOS setup (usually Del or F2 at power-on). Open the built-in flashing tool - the names differ by brand, EZ Flash, M-FLASH, Q-Flash and Instant Flash are the common ones - select your file from the USB stick, confirm the version it shows, and start. The built-in tool verifies the file against your board before writing, which is one reason it is safer than flashing from Windows.
A successful flash often loads factory defaults, so treat the first boot as a checklist, not a finish line.
msinfo32 again and confirm the new BIOS version is shownmanage-bde -protectors -enable C: and confirm normal statusThe full update shown live on a real machine - finding the right file, flashing and the first-boot checks, step-by-step.
Watch Full VideoIt carries more risk than a normal software update because the firmware is what starts the machine - a wrong file or a power cut mid-write can leave a board that will not boot. The risk becomes small when you follow the routine on this page: exact file, stable power, recovery key saved, built-in flasher, no interruptions. Skipping the preparation is what makes it dangerous, not the update itself.
No. The update only rewrites the motherboard firmware chip; your drives, Windows and files are untouched. The one trap is encryption: if BitLocker asks for its recovery key after the update and you never saved it, your files become unreachable even though they still exist. That is a preparation problem, not data loss - save the key first.
Usually not. Firmware updates commonly reboot more than once, run fans at full speed and retrain the memory on the first start, which can look like a hang for several minutes. Leave the power connected and wait at least 10 to 15 minutes before suspecting failure - interrupting a slow-but-alive update is how a recoverable situation becomes a brick.