BIOS Updates: When, and When Not To

Update when you have a reason you can name, and not otherwise. A new CPU the board does not support, a listed fix for a fault you actually have, an applicable security advisory — those are reasons. "Staying current" is not one.

The failure mode here is not a bad afternoon. It is a machine that will not start.

A note on this guide: this rests on how board firmware and its update mechanisms work rather than on boards flashed here. See how we test.

The problem, as it appears

A utility tells you an update is available. The board is a year old, the release notes mention stability and compatibility, and updating things is generally what you do.

The instinct is exactly the one that serves you well everywhere else in computing, and this is the place it does not.

Why "keep it updated" disappoints

Because firmware is not software, and three things about it are different.

There is often no way back. Applications roll back. Firmware sometimes cannot, because vendors block downgrades past versions containing security fixes. If the new version behaves worse on your hardware, you may be living with it.

The failure mode is total. The board is rewriting the code it uses to start itself. An interruption during that write leaves nothing capable of running, and unless the board has a recovery mechanism, the outcome is a replacement.

The benefit is usually zero for you specifically. Release notes describe fixes for faults across an entire product line. Unless one of them describes something you are experiencing, you are accepting a small risk in exchange for nothing measurable.

That asymmetry is the whole argument. Not "never update" — update on purpose.

What actually matters

The reasons that justify it

Five, and they share a shape: something you need that the current firmware does not do.

• A CPU the board does not yet support. The most common legitimate reason by a wide margin. A newer processor in an older board needs microcode the board does not have, and no other route supplies it.
• A listed fix for a symptom you actually have. Read the notes; if a described fault matches yours, that is a reason.
• Memory stability with a specific kit. Training and compatibility improvements are real, and this is a genuine cause of instability people chase elsewhere.
• A feature or device the board cannot currently handle — a security requirement for an operating system, a standard a new card needs.
• A security advisory that applies to your situation. Applies, rather than exists.

Power is the risk that matters

Everything else on the risk list is smaller than losing mains part-way through the write.

A desktop has no battery. A brief cut, a tripped breaker, or someone switching off the wrong socket during the two minutes that matter produces the one outcome you cannot fix with another attempt.

This is the single situation where recommending a UPS to a desktop owner is not overkill — it is covering the exact scenario that turns a maintenance task into a replacement.

This page contains affiliate links. If you buy through them, Ugly Fixes may earn a commission at no extra cost to you. Products are selected independently.

A unit that has been sitting for years may not do the job when asked, which is the point of when to replace a UPS battery.

The method changes the odds

Prefer the board's own built-in updater, run from a USB stick, over a vendor utility inside the operating system.

The built-in route has almost nothing running around it. The in-Windows route has drivers, background software, an antivirus and an operating system that might decide to install its own update — all of which are things that can interrupt at the wrong moment.

Format the stick as the board's documentation specifies, put the file in the location it expects, and follow the vendor's own procedure rather than a forum's summary of it.

Some boards can flash with no processor installed at all, which is precisely what makes the CPU-support case workable. If your board has that, it is the safest route available for that particular job.

The wrong file is the other real hazard

Boards sold under the same model name can exist in different hardware revisions, and firmware is not interchangeable between them.

The revision is usually printed on the board itself. Checking it against the download page takes a minute, and getting it wrong produces the same outcome as losing power.

Expect to lose your settings

Not a risk, just a certainty people forget: memory profiles, fan curves, boot order, undervolt offsets and secure boot state commonly revert.

Photograph the screens you have changed before starting. Reinstating an undervolt from memory is guesswork, and a machine that suddenly runs hot or loud after an update is usually a fan curve that went back to default rather than anything the firmware did — which is why building a fan curve that is not the default and undervolting to cut fan speed are worth re-reading afterwards rather than before.

If it will not start afterwards

Usually not the disaster it feels like. Clearing the stored settings resolves a large share of post-update no-boot cases, because the new firmware and the old saved configuration disagree.

The ordered approach to a machine that will not start — and why the CPU power connector comes first — is in a PC that will not post.

The thing that is not a firmware problem

A board that forgets the time and its settings every time mains power is removed has a flat coin cell, not a firmware fault.

It is one of the cheapest parts in the machine and it takes minutes, and it gets misdiagnosed as something serious surprisingly often.

The order to work in

1. Write down the reason. If you cannot, stop here.
2. Read the release notes for your exact version gap, including any downgrade restriction.
3. Check the board revision against the download.
4. Photograph your settings screens.
5. Get the machine onto battery-backed power.
6. Use the built-in updater from a correctly prepared USB stick.
7. Leave it alone until it says it is finished.
8. Reinstate memory profile, fan curve and boot order.

The mistake to avoid

Updating because an update exists. The vendor utility exists to tell you about releases, not to tell you whether one is relevant to you, and a release fixing a fault on a board configuration you do not have is a small risk taken for no return. The question that decides it is whether you can state what this version does for your machine — and if the honest answer is that it sounds newer, that is a reason not to.

The second mistake is doing it inside Windows because it is easier. That route puts an operating system, its drivers and everything running on it alongside the one operation you least want interrupted, and the convenience is a few minutes against a failure mode with no recovery. The board's own updater is less pleasant and much less exciting, which is what you want here — the same reasoning that makes the unglamorous checks in gaming PC problems after year one worth doing before the interesting ones.