Framework BIOS 3.20 bricks Laptop 13 boards, free swaps promised

A routine firmware update that went wrong

Framework built its reputation on the idea that a laptop should outlast its first owner's patience. A flawed firmware release has now tested that promise. BIOS version 3.20 for the Framework Laptop 13's AMD Ryzen 7040-series mainboards has left some machines unable to boot, and owners have reported the failure on both Windows and Linux.1 The affected boards date to 2023, when Framework first sold pre-built Ryzen 7040 laptops and the matching mainboards. That makes this a previous-generation platform, but one with a lot of units still in daily use.2

The failure looks the same in nearly every account. The flash stalls on a black screen showing the Framework logo and a progress bar that never gets past two dots.23 One forum user said in July that the bar had not moved for about three hours, and that holding down the power button would not turn the machine off.2 Some owners say that even after disconnecting the battery and restarting, the laptop still would not boot, which points to corrupted firmware.3

Framework's statement, given to multiple outlets, describes the problem as a "small percentage" of Laptop 13 7040-series BIOS updates producing non-bootable boards. The company says it is still investigating the root cause.12 Asked for a specific failure rate, Framework's external PR representative Jim Redner did not give a number and repeated the "small percentage" wording.1

What Framework is promising

The company's response has two parts. First, it will replace boards that the faulty update killed. In-warranty mainboards are covered, and Framework says it will also make exceptions for out-of-warranty boards when it can confirm that a stable-release BIOS update caused the failure.12 That is a real change from what owners first reported. Forum posters said support sent replacements to people within the one-year warranty but told out-of-warranty owners to buy new boards.13

Second, Framework is adding a "Crisis Recovery Mode" to its firmware, so a failed update can be recovered directly instead of requiring new hardware.1 The feature already ships in the latest Framework Desktop BIOS. The company says it is bringing the feature to the Laptop 12, 13, and 16 in upcoming release cycles and is aiming to finish before the end of the year for each product line.18

The update was not just maintenance. According to a Framework employee's forum post, 3.20 added mainboard support for the higher-end Laptop 13 Pro's haptic touchpad and new speakers, and fixed a bug where Battery Extender status was reported incorrectly after a reboot, hibernation, or shutdown.2 One owner said a Framework newsletter recommended the update because it included security fixes.10 Owners who installed it were therefore following the company's own advice.

Where the coverage diverges

On the main facts, the reporting agrees: the version number, the affected platform, the symptoms, the board-replacement policy, and the recovery-mode plan. The details differ in a few places. The Verge says 3.20 came out in July and was still available on Framework's site when it published.1 Ars Technica and Sportskeeda date the release to June 2026.23 The June date fits better with forum complaints that were already appearing in July, and ExtremeTech also says the trouble started a couple of months before it became news.27

The sources also differ on who spoke. One aggregated account says founder Nirav Patel acknowledged the problem in a statement to The Verge.8 The Verge's own story quotes a company statement and Redner, and does not name Patel.1 The safer reading is that this was a corporate statement given to several outlets at once, not personal comment from the founder.

The stronger disagreement is about tone. Most outlets report Framework's out-of-warranty exception as a welcome reversal.37 Community reaction has been harsher. In mid-September, a public service announcement thread on Framework's forum told owners not to install 3.20 and accused the company of dragging its heels. One poster asked why a recovery path was not built in from the start, given that recovering from bad BIOS updates is not a new idea.15

An old problem, not a new one

This story matters for more than a single bad release because the issue is not isolated. Reports of BIOS upgrade failures on Ryzen 7040-based Laptop 13s go back to at least March 2025.2 Framework's forums also show similar complaints on other models. In late 2025, a Laptop 16 owner with the same AMD 7040 platform described a firmware update that corrupted the screen and left the machine unresponsive.4 Another owner managed to flash a Laptop 16 BIOS onto a Laptop 13, which the updater did not stop.6 An Ars Technica commenter said a BIOS update bricked their Intel Core Ultra-based Laptop 13, and then bricked the replacement board too.9

In this context, the 3.20 incident looks less like a one-off bug and more like the most visible failure in a weak update process. Several sources draw the same conclusion.8

The most damaging technical criticism came from software developer Guanzhong Chen. After support reportedly told him to buy a new mainboard, he recovered his own board with about $20 of tools.102 He argued the cause was a software bug that showed what looked like random memory on screen. He also pointed out that Framework's updater flashes firmware more slowly than a cheap 15 MHz programmer connected with pogo pins.2 Other technically skilled owners have done the same thing, reflashing the Winbond W25Q256JW SPI flash chip with a USB programmer and a level shifter.7 That workaround supports Framework's repairability pitch in one way: the hardware can be fixed. But most buyers do not own a programmer, so it is not a real fix for them.

Why it matters for Framework specifically

A bad firmware push hurts any PC maker. It hurts Framework more because the company sells longevity: long-term BIOS support for every laptop generation, including its original 11th-generation Intel machines.18 That promise only works if owners trust updates enough to install them. If owners decide the safest choice is to stay on old firmware, the security fixes Framework ships stop protecting anyone. Forum posts already show that happening. One owner said the thread had persuaded them to keep two machines on the previous BIOS.15 Another nervously asked about an unrelated Laptop 12 firmware release because of the AMD Laptop 13 problems.16

Warranty policy is the other pressure point. One Ars Technica reader argued that Framework's parts-based model relies heavily on a short warranty to keep costs down.9 That works when failures come from wear or accidents. It works much less well when the company's own recommended update causes the failure. Framework's case-by-case out-of-warranty exception is the right call, in our view. But it depends on Framework confirming that the update caused the failure, and the company has not said how it makes that determination.

The recovery mode is the real test

The board swaps deal with the damage already done. Crisis Recovery Mode is the part that could stop it from happening again, and it deserves the closest attention. Desktop owners already have it, and their experience is mixed. A forum thread titled "Framework Desktop bricked after BIOS 3.06 update" concerns the same Desktop release that introduced BIOS recovery.17 The thread does not prove the feature failed. It does show that adding a safety net can itself create risk.

The end-of-year target leaves Laptop 12, 13, and 16 owners without that safety net for several more months.1 Outlets agree on the practical advice in the meantime. Owners of a Ryzen 7040 Laptop 13 who have not installed 3.20 should hold off until Framework explains the root cause, and anyone whose board has already failed should contact support for a replacement.38 When this coverage was published, Framework had not given a timeline for pulling or patching the update.8

The verdict so far: Framework's response has improved under public pressure, and its fixes are sensible. But the company has been slow to recognize a failure pattern that its own community was documenting more than a year earlier, and it has not yet explained what went wrong. Owners will be watching whether recovery mode ships on time and actually works.