Skip to content

Framework Laptop 16 AMD Ryzen™ 7040 Series — BIOS 3.06

File Release Date
Windows BIOS v3.06 Installer 2025-08-04 Framework_Laptop_16_Amd_Ryzen7040_BIOS_3.06.exe SHA256 · 8D8FC08C25A27B848D2C4A40E656A780016F12D8222656589F1688A2272EA46C
Windows Driver Bundle v2.05 2025-07-18 Framework_Laptop_13_and_16_AMD_Ryzen_7040_driver_bundle_W11_v2.05_2025_07_18.exe SHA256 · 4A7B345C8A0779E8605E84BF9A5E3F274ECAFEE8CDA12D53CB0CFFCF8DC3FE04
Wi-Fi Driver for use during Windows Installation 2026-06-18 Framework_W11_OOBE_Wifi_Driver_Package.zip SHA256 · 13d7286531f7fc354bf345ea6f465c76cbba79f783a44b45d4803743022b574a
EFI Shell Update (BIOS v3.06) 2025-08-04 Framework_Laptop_16_Amd_Ryzen7040_BIOS_3.06.zip SHA256 · 5E249CE606FEAE29D4E289A49ECE21444A5E79B0187C0401D3529A33F55AF5EA
3.06
Released 2025-08-04
Stable
Highlights
  • After updating to 3.06, downgrading beyond the previous version is not supported.
  • Install driver bundle 2.05 alongside this update. Without it, the Framework EC device will show a yellow bang in Windows, though system functionality is unaffected.
  • Added Framework's dbx key and updated the default CA of Windows Secure Boot to Microsoft UEFI CA 2023.
  • Introduced Battery Extender functionality — automatically limits maximum state of charge if the system is left plugged in for more than 5 days.
  • Introduced Battery Charge Limiting status functionality to support Windows Smart Charging.
  • Introduced the Framework EC device to enable the Framework tool on Windows.
  • Updated to AMD PI 1.2.0.0c.
  • Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
  • Fixed battery drain issues occurring with the Balanced Power Profile.
  • Fixed CPU power limits to prevent unnecessary limitation when the GPU is in BOCO mode.
  • Fixed 'Force Power for Input Modules' setting not working.
  • Security fix: CVE-2024-21925 — Improper input validation in AmdPspP2CmboxV2 may allow privileged attacker to overwrite SMRAM (CVSS 8.2).
  • Security fix: CVE-2024-0179 — SMM Callout vulnerability in AmdCpmDisplayFeatureSMM could allow locally authenticated attackers to overwrite SMRAM (CVSS 8.2).
  • Security fix: CVE-2025-4275 — Digital signature verification bypass via non-authenticated NVRAM variable (CVSS 7.8).
  • Security fix: CVE-2025-2884 — Out-of-bounds read in TCG TPM2.0 CryptHmacSign (CVSS 6.6).
  • Security fix: CVE-2024-36347 — Improper signature verification in AMD CPU ROM microcode patch loader (CVSS 6.4).
  • Security fix: CVE-2024-49200 — Potential DXE memory corruption in AcpiS3SaveDxe/ChipsetSvcDxe in InsydeH2O (CVSS 6.4).
  • Security fix: CVE-2024-36350 — Transient execution vulnerability allowing data inference from previous stores (CVSS 5.6).
  • Security fix: CVE-2024-36357 — Transient execution vulnerability allowing L1D cache data inference (CVSS 5.6).
  • Security fix: CVE-2024-36348 — Transient execution vulnerability allowing control register inference (CVSS 3.8).
  • Security fix: CVE-2024-36349 — Transient execution vulnerability allowing TSC_AUX inference (CVSS 3.8).

This BIOS update is a bundle of updates to multiple embedded components in the system. Not all of them use the same version number.

ComponentVersion
ECec_306_cf6b79
Updated
PD0.0.1E
AMD PI1.2.0.0c
Updated
DriverVersion
AMD Chipset Driver7.02.24.1120
AMD Graphics Driver24.20.60.01
Realtek Audio Driver6.0.9859
Updated
Realtek Audio Console1.53.374.0
Updated
RZ616 WiFi Driver3.4.0.1268
Updated
RZ616 Bluetooth Driver1.1043.0.543
Updated
Goodix Fingerprint Driver3.12804.0.270
Updated
Realtek MEP Driver10.2000.10003
Updated
AMD MEP Driver32.1.0.0
Updated
Microsoft MEP Driver1.0.42.0
Updated
Framework EC Driver0.0.0.6
Updated
Realtek Ethernet11013_20_07272023_08042023
SD Card Readerv4_5_10_201
2nd Gen uSD Card Readerv4_5_10_202

With the high energy density on the 61Wh battery, leaving it at 100% state of charge for an extended period of time can shorten the lifetime of the battery. To prevent this, we have added a new feature that automatically limits the maximum state of charge if the system is left plugged into power for more than 5 days. The timer is reset after the system is disconnected from a power adapter for more than 30 minutes.

Battery Extender Duration Battery State of Charge
0-5< Days 99% → 100%
5-7 Days 90% → 95%
>7+ Days 85% → 87%

This functionality also reduces cycling of the battery by allowing the battery to discharge by several percent before charging again. Note that in addition to this automatic setting, you can also manually set a lower charge limit on your battery in BIOS to further preserve battery longevity.

This feature can be disabled or enabled in the BIOS Advanced menu.

  • Battery Extender: This option is enabled by default. If disabled, the system will always keep the battery fully charged.
  • Battery Extender Trigger: This option sets the number of days that must pass before the battery state of charge is reduced automatically to extend the battery life.
  • Battery Extender Reset: This option sets the number of minutes that the system is running on battery before the extender is reset, causing the system to charge to 100% when attached to power again.

This release modifies the battery charge limit functionality to add a 5% float range. This allows us to reduce the number of microcycles on the battery when the CPU turbos.

Previously, the battery would be held at the target state of charge, so if a large power draw happened for a short time, such as when the CPU turbos, the battery would drain slightly and then charge again. Introduced in this version, the battery will not start to charge until the battery has dropped 5% below the charge limit.

As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on.

If this is activated while the battery state of charge is above the limit, the battery will discharge without drawing power from the adapter until the upper limit is reached.

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

Framework firmware is published to LVFS and updates via fwupd, which ships by default on most modern distributions.

Terminal window
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
  1. Download the Framework Laptop 16 AMD Ryzen™ 7040 Series BIOS 3.06 Windows Installer.
  2. Run the .exe and click "Yes" when prompted to reboot.
  3. Wait for the firmware progress bar to complete — the system will reboot automatically. Do not interrupt.
  4. Download and install the Windows Driver Bundle v2.05 for your system if you are currently using a previous Driver Bundle release, or you are installing the Driver Bundle for the first time.
  1. Download the EFI Shell Update v3.06.
  2. 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.
  3. Attach a charger to your device while updating.
  4. Boot your system while pressing F12 and boot from the thumb drive.
  5. Let startup.nsh run automatically.
  6. Follow the instructions to install the update.
  • Type-C connection may be unstable with some Apple phones.
  • Cannot negotiate charging for certain portable EPR power banks.
  • 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, then power on to recover). This issue has an occasional failure rate.

Please use the public issue tracker on GitHub to report issues.

If you 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.

Please contact support if you have an issue regarding hardware, broken devices, returns, etc.