FrameworkがBIOSアップデートで一部の旧モデルがブリックする問題に対応中Framework says it’s addressing a BIOS update that bricked some of its older laptops

Framework, the company known for its user-repairable and upgradeable laptops, is working through a firmware problem that has left some customers with unusable machines. Owners of the Framework Laptop 13 fitted with last-generation AMD Ryzen chips have reported that a recent BIOS update is bricking their systems, an outcome that matters both because bricked hardware is difficult to recover and because firmware reliability is central to Framework's promise of long-lived, serviceable devices.

According to the reports, the culprit is BIOS version 3.20 for Ryzen 7040-series mainboards, which Framework released in July and, per the source, remained available for download afterward. Affected users say the failure occurs regardless of operating system, with laptops running both Windows and Linux going dark after applying the update. That cross-platform behavior is notable because it points toward a problem at the firmware level rather than something tied to a particular OS driver, update tool, or software environment.

Bricking refers to a device becoming completely non-functional, akin to a brick, typically because low-level firmware that the hardware needs in order to start has been corrupted or improperly written. BIOS, or more precisely UEFI firmware on modern systems, is the code that initializes the processor, memory, and other components before an operating system loads. When a BIOS update is interrupted or contains a defect, the machine can fail to complete this early boot process, which often leaves few options for recovery through normal means. Some systems include a backup firmware image or a recovery mode, but whether and how those mechanisms help in this case appears to depend on the specifics of the failure.

The Ryzen 7040 series, based on AMD's mobile silicon, powered Framework's earlier AMD-based configurations of the Laptop 13 before newer chip generations arrived. Framework's modular design allows customers to swap the mainboard, so a range of processor options has shipped in the same chassis over time. That flexibility is one of the company's main selling points, but it also means Framework maintains firmware for multiple mainboard generations, and an update targeted at one specific board, as version 3.20 is, can affect a defined subset of the installed base rather than every Framework Laptop 13 in the wild.

Framework has acknowledged the issue and is said to be addressing it, though the full scope, root cause, and remediation path were not detailed in the initial reports. For users who have not yet installed version 3.20, the cautious approach is generally to hold off on applying a firmware update that is associated with failures until the vendor provides guidance or a corrected release. Owners whose machines are already affected will likely need to follow whatever recovery or repair process Framework outlines, which could involve a replacement component or a service intervention depending on the nature of the fault.

This episode sits within a broader context that has long challenged Framework and the wider PC industry. Delivering timely, reliable BIOS updates across different processor generations and operating systems is a recurring difficulty, and Framework in particular has previously faced criticism over the pace of its firmware releases. On Linux, many hardware makers distribute firmware through the Linux Vendor Firmware Service and the fwupd tooling, which streamlines updates outside of Windows; the fact that both Windows and Linux users are reporting the same outcome suggests the defect is in the firmware payload itself rather than in any single delivery channel.

For a company whose identity is built on repairability and longevity, firmware stability is more than a routine engineering concern. Framework has positioned itself against the trend of disposable electronics by letting customers upgrade mainboards, replace ports, and keep a laptop in service for years, and it has drawn a dedicated following among enthusiasts and Linux users for that stance. A bricking bug undercuts that value proposition in a visible way, which raises the stakes for a clear explanation and a dependable fix.

At this stage, the practical takeaways are straightforward. The problem is tied specifically to BIOS version 3.20 on Ryzen 7040-series mainboards in the Framework Laptop 13, it affects both Windows and Linux installations, and Framework has said it is working on a response. Affected and at-risk users should watch for official communications from the company before taking further action.