Framework Laptop 16 Ryzen 7040 BIOS 4.05 Release BETA

Framework Laptop 16
, , , ,
1

Updating from 3.0x

Update sequence for AMD Ryzen™ 7040 Series Mainboard and the NVIDIA® GeForce RTX™ 5070 Graphics Module:

  1. If you are planning to use your Keyboard (1st Gen), RGB Macropad (1st Gen), or Numpad (1st Gen), you’ll first need to update your keyboard firmware using this link.
  2. Update your Framework Laptop 16 (AMD Ryzen 7040 Series) BIOS to the latest by following the instructions on this link.
  3. Replace the Graphics Module using this guide: Expansion Bay Module Swap.
  4. Update your driver bundle using this link.

This release includes two major updates:

  1. We’ve changed the keyboard standby/lid-close behavior to suspend the input device when the lid is closed, preventing unintended waking. Before updating your laptop to BIOS 4.05 from 3.0x, you’ll need to update Keyboard/Numpad/MacroPad firmware to 0.3.1, following the instructions here. If you already performed this and are on 4.0x there is no need to update again
  2. This release includes support for NVIDIA® GeForce RTX™ 5070, which also needs Driver Bundle 3.02 or newer. The BIOS version 4.0x is a mandatory requirement to support the NVIDIA® GeForce RTX™ 5070.

Highlights

  1. Updated AMD AGESA to PhoenixPI-FP8-FP7_1.2.0.0f
  2. Updated input module app to 0.3.16.
  3. Update G-Sync VK key for NVIDIA 5070 12G Graphic Module.
  4. Fixed an issue that unexpected 35W CPU power limit when AMD dGPU is in BOCO mode.
  5. Security Fixes - CVE-2024-36343, CVE-2024-36345, CVE-2025-54502.

Note:

  • The BIOS version 4.0x is a mandatory requirement to support the NVIDIA® GeForce RTX™ 5070.
  • Once you update to version 4.05, the only compatible downgrade path is to BIOS 3.05 or any newer version (this restriction applies only if you are using UMA graphics or the AMD RX7700).

You can check your current BIOS version following the steps here to determine if you are on the latest release.

After the beta release, we will monitor community feedback, and publish this release to our stable release channel after approximately one week if no major issues are reported.

Subscribing to release notifications

If you want to subscribe to new release notifications you can now opt in through this link to receive an email when we release a new BIOS or driver update for your Framework Laptop.

Downloads

Windows

Download Link SHA256
Framework_Laptop_16_Amd_Ryzen7040_BIOS_4.05.exe 1D2CDB356F3140A44581262ED958D20D777BA575D4E0CBC85C198A635C817A48

|

Instructions for Windows Installer:

  1. Run the .exe.
  2. Click yes to reboot.
  3. Wait for the firmware progress bar to complete, and then the system will reboot.
  4. If you are updating a system in standalone mode, please pay careful attention to the standalone update process below.

Please note that you must update with a charger attached.

Linux/LVFS

Updating via LVFS is available in the testing channel during the beta period.
You can enable updates from testing by running

fwupdmgr enable-remote lvfs-testing

Please note that you must update with a charger attached, then run:

fwupdmgr refresh --force

then

fwupdmgr get-updates

then

fwupdmgr update

Please note that you must update with a charger attached.

LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.

Linux/Other/UEFI Shell update

Download Link SHA256
Framework_Laptop_16_Amd_Ryzen7040_BIOS_4.05_EFI.zip FE161F4894D565A3ACE3E7D9640AEAAAE872DB440DC17D39B3A3A4EAA53DBA93

Note that if you use the EFI shell update with Windows, you should suspend Bitlocker if enabled before updating using the EFI updater.

Instructions for EFI shell update:

  1. Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.
  2. Attach a charger to your device while updating.
  3. Boot your system while pressing F12 and boot from the thumb drive.
  4. Let startup.nsh run automatically.
  5. Follow the instructions to install the update.

Security Fixes

Module Name Vulnerability Score (CVSS 3.x)
CVE-2024-36343 Improper input validation in the System Management Mode (SMM) communications buffer could allow a privileged attacker to perform an out of bounds read or write to a limited section of the Top of Memory Segment (TSEG) memory region, potentially resulting in loss of confidentiality or integrity. N/A
CVE-2024-36345 Improper input validation in the AMD OverDrive (AOD) System Management Mode (SMM) module could allow a privileged attacker to perform an out-of-bounds read, potentially resulting in loss of confidentiality. N/A
CVE-2025-54502 Incorrect use of boot service in the AMD Platform Configuration Blob (APCB) SMM driver could allow a privileged attacker with local access (Ring 0) to achieve privilege escalation potentially resulting in arbitrary code execution. N/A

Enhancements

  1. Updated AMD AGESA to PhoenixPI-FP8-FP7_1.2.0.0f
  2. Updated input module app to 0.3.16.
  3. Update G-Sync VK key for NVIDIA 5070 12G Graphic Module.

Fixes

  1. Fixed an issue that unexpected 35W CPU power limit when AMD dGPU is in BOCO mode.

Component Versions

This BIOS update is a bundle of updates to multiple embedded components in the system.

Not all of them use the same version number.

BIOS 4.05 Updated
EC ec_405_2246d58 Updated
PD 0.0.21 Same
NVIDIA® GeForce RTX™ 5070 PD 0.0.22 Same
AMD PI 1.2.0.0e Same

Reporting Issues

To report issues we have created a public issue tracker on github. Issues · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub We hope that this is a better way to track issues with community involvement moving forward as we have found it difficult to both gather relevant information about issues people are reporting on the forums, and track the issues through their lifecycle in a transparent way.
If you do experience an issue with the update that is related to your system firmware, please post as complete a description as you can, including relevant system information, and external peripherals. Please note that we do not currently have a SLA for responding to issues on github, but we will be reviewing them through the bios release process, and will review them for future updates as well.

If you have an issue regarding hardware, broken devices, returns, etc, this is not the place, please contact support.

Known Issues

  1. Type-c connection may be unstable with some Apple phones.
  2. Cannot negotiate charging for certain portable EPR power banks.
  3. If a device is plugged into an expansion card slot during the update, all USB3/DP functionality will be lost until the device is removed and reinstalled, or the system is fully shut down and powered on again. (Power off, unplug the charger, wait 90 seconds, and then power on again to recover). This issue has an occasional failure rate.
  4. Intermittent CPU frequency lock at 545MHz following S3/Modern Standby resume.
1 Like
2

is it 1.2.0.0e or 1.2.0.0.f?
if user does not have dedicated GPU is there any reason to update to the latest bios form 4.04?

3

This is confusing, as this behavior change is not new in 4.05, it was introduced in 4.00 or 4.01. Users like me who already have the 4.0x series installed are not getting new lid-closed behavior by upgrading to 4.05.