// ARS TECHNICA — HARDWARE & GADGET
Framework responds to complaints that BIOS update bricks Ryzen 7040 laptops
Framework says it’s replacing some out-of-warranty AMD mainboards.
A BIOS update for the Framework Laptop 13 with AMD Ryzen 7040-series processors is bricking the systems, multiple users have reported online.
Framework started shipping pre-built Ryzen 7040-based Framework Laptop 13 computers and compatible motherboards in 2023. In June 2026, Framework released BIOS 3.20 for the devices. The update adds mainboard support for features, including a haptic touchpad and new speakers, for the higher-end Framework Laptop 13 Pro and fixes issues, including one “where the Battery Extender status was reported incorrectly following a reboot, hibernation, or shutdown after the timer had expired,” per a post on Framework’s forum from an employee.
Some users say that they installed the update successfully.
Numerous others, however, claim that the installation stalls, bricking the laptop.
“[T]he update process seems to have stalled,” a Framework forum user named Sven posted in July. “What I see is a black screen and a progress bar with 2 dots and then the Framework logo. The progress bar is not moving for about 3 hours now. Also, I can’t turn off the Framework using the power button, no matter how long I hold it down. Now the BIOS update is stuck, and I can not power down or reboot the machine.”
Ars Technica contacted Framework, asking how many customers are affected. In a company statement, Framework said it has “received reports of a small percentage of Framework Laptop 13 7040 Series BIOS updates resulting in non-bootable boards.” Framework is investigating the root cause of the issue, the statement said.
There are reports of users having problems with BIOS upgrades on Ryzen 7040-based Framework Laptop 13 devices going back to at least March 2025.
After the most recent BIOS update, some users reported that Framework support told them they needed a new motherboard, but Framework wouldn’t provide it for free because the customer was past warranty.
… in addition to replacing in-warranty Mainboards, we are making exceptions for out-of-warranty replacements where we can confirm a stable-release BIOS update caused the board to become non-bootable.