Framework Laptop 12 Intel® Core™ 13th Gen BIOS 3.06 Release STABLE

Framework Laptop 12
,
1

Highlights

  1. Added Framework’s dbx key and updated the default CA of Windows Secure Boot.
  2. Introduced Battery Charge Limiting status functionality.
  3. Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
  4. Fixed an issue where the fan was not detected when powering on from S4/S5 with default BIOS settings.

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

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_12_13th_Gen_Intel_Core_BIOS_3.06.exe D538429D548981F8C743757E43C2EF52FD5C5A2B05BDB78793AE3F22B4445BCB

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.

Please note that you must update with a charger attached.

Linux/LVFS

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_12_13th_Gen_Intel_Core_BIOS_3.06_EFI.zip DCD6F0C608268476A076B0C2D0835A72D48D9239B7D3794EE403F4E5449DF7DB

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
CVE-2025-4275 A vulnerability in the digital signature verification process does not properly validate variable attributes which allows an attacker to bypass signature verification by creating a non-authenticated NVRAM variable. 7.8

Enhancements

  1. Added Framework’s dbx key and updated the default CA of Windows Secure Boot to Microsoft UEFI CA 2023.
  2. Introduced Battery Charge Limiting status functionality to support Windows Smart Charging feature.

Fixes

  1. Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
  2. Fixed an issue where the fan was not detected when powering on from S4/S5 with default BIOS settings.
  3. Security Fixed - CVE-2025-4275

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.

Firmware Version Update?
BIOS 3.06 Updated
Intel SIC 0C.01.F4.10 Same
Intel CSME 16.1.32.2473v3 Same
MCU 0x5102 Same
GOP 21.0.1066 Same
EC ec_306_259a1d9 Updated
PD 0.0.12 Same

Reporting Issues

To report issues we have created a public issue tracker on github. GitHub · Where software is built

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 Framework Support. https://frame.work/support

Known Issues

  • The fan is not detected after powering on from S4/S5 if the BIOS setting “Boot Performance Mode” is set to “Max Battery.”
    None
4 Likes
2

Successfully updated on Bazzite using the fwupdmgr commands from @Quin_Chou‘s instructions. No issues so far (and didn’t have any of the fixed issues before either).

(note that just like with 3.05 beta, ujust update saw the new version being available but did not apply it, I really needed to manually run fwupdmgr update for it to work. That’s on a very slightly modified version of bazzite-dx (itself a modified version of bazzite))

3

The only change between 3.05 and 3.06 is “Fixed an issue where “Fan not detected” when powered on from S4/S5.”, right?

The release notes in this post seem to be a mashup of what is in 3.05 and 3.06.

1 Like
4

BIOS update applied via LVFS. Upon setting the bios back to max battery, turning off the machine and unplugging from power for 2+ minutes, and powering back on, the fan not found message is back.

This is an i3 machine, 64gb crucial ram. My first machine was replaced due to cracks on the bottom case and this error being present. Other than this (spurious) error, the machine works fine. I would like to be able to set it to max battery in the bios, though.

5

I updated from 3.05 to 3.06 via EFI and the “CPU fan not detected” error is still triggered by the procedure I described for 3.05. It’s also reversible as before.

The HW is unchanged.

1 Like
6

Could you attempt to reset the EC (Embedded Controller) before re-testing? The underlying issue stemmed from the fan’s startup duty cycle failing to meet its operational specifications. Following our adjustment to the startup fan duty, the fan behavior anomaly that was observed has been resolved.

7

What’s the recommended procedure for EC reset on this laptop?

8

You can press power button over 12 seconds.

9

Thank you for the detailed information. Based on your configuration, we can reproduce the issue with the specific fan. The problem occurs simply by setting the max battery option. We need to investigate why this relates to the fan, as it should only affect the power settings. Could you please check if the issue disappears when you set the system to Turbo Performance or Max Non-Turbo Performance?

10

When the issue occurred, was the Boot Performance Mode also set to Max Battery?

11

I can confirm that when setting the bios to turbo or max non-turbo the fan alert at boot is no longer present.

12

  1. While powered off, I held the power button for ~12s with the lid closed and no charger connected.

  2. Then entered BIOS and switched hyperthreading OFF. Boot Performance Mode already set to Max Non-Turbo Performance. Look in BIOS 3.05 thread for the complete settings deviation from defaults.
    Exit saving changes (F10) and powered off when the logo appeared.
    Waited 30s+.
    Powered on and the message appeared.
    Powered off with short press to ignore error and short press on GRUB menu.

  3. Entered BIOS again and switched hyperthreading ON. Boot Performance Mode already set to Max Non-Turbo Performance.
    Exit saving changes and powered off when the logo appeared.
    Waited 30s+.
    Powered on and continued normally, no error.
    Powered off with short press on GRUB menu.

Repeated once more from 1 after a few minutes. Same result.
I there any way to check if the EC was actually reset?

This is an EFI install over 3.05

13

Installed. Noticed no changes.

LUKS+TPM w/ PIN unlock didn’t fallback to passphrase, so it still has a secure booty.

14

We successfully duplicated this issue based on your report.

The root cause is that the “Max Battery” setting triggers an internal CPU ratio reset. Our EC checks the fan status during its diagnostic phase. Unfortunately, the CPU reset occurs before the diagnostic test completes, which inadvertently resets the fan setting and turns it off. Consequently, the fan is not detected.

We are actively developing a fix and plan to include it in the next BIOS release.

In the meantime, we recommend using one of the other two BIOS settings as a temporary workaround to prevent the fan error message from appearing during power-on.

We appreciate your feedback.

3 Likes
15

Thank you for the follow-up, I am happy to hear that you were able to reproduce the issue, and I look forward to the update to resolve it. Have a great day!

1 Like