Framework Laptop 12 Intel® Core™ 13th Gen BIOS 3.05 Release BETA -Held

Framework Laptop 12
1

We have identified the root causes of fan not found issue. We plan to hold the 3.05 release, and then release the 3.06 beta next week.

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.

Please note: With BIOS 3.05, you can downgrade to a previous version.

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_12_13th_Gen_Intel_Core_BIOS_3.05.exe 38DEBAAAF35F6FF70D467971D1072BB8C870CBDAA44F4BB9A947BA4577C380D5

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

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_12_13th_Gen_Intel_Core_BIOS_3.05_EFI.zip 65624985B647C8140E12C4F1C9CE9D8755F77203299500E8493D6260D428F544

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

BIOS 3.05 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_305_8a5df08 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

None

6 Likes
2

@Quin_Chou Thank you for your BIOS update! Could you use the bios-announcement tag rather than the bios tag to align with other past BIOS announcements?

@catastrophic There may be no “bios-announcement” tag in the Framework Laptop 12 category, unlike Framework Laptop 13 and 16 categories. Could you check it and add it if it is necessary?

3 Likes
3

Updated via LVFS with no issues. The "fan not found” at boot issue is still present if the bios is set to max battery. Otherwise so far so good.

2 Likes
4

The bios-announcement tag is not shown in the Framework Laptop 12, so I cannot select it. I am waiting for internal team to check it, then will add it for bios release.

1 Like
5

Do you see a ‘fan not found’ error at boot when set to max battery? We’re asking for more details because we’ve encountered a similar, difficult-to-reproduce issue in our testing, which is preventing further debugging.

6

Yes. It happened on my first machine as well as the replacement one - replaced due to the bottom case cracking. It’s an i3, 64gb crucial ram, 2tb 2230 drive, booted off of a 1tb expansion card in the top right slot. Other cards are 2x usb-c upper left and lower right, 1x usb-a lower left with a fingerprint reader plugged into it.

7

This should be updated, thanks! Also updated Desktop as well. @Quin_Chou you should be able to add the tag now.

1 Like
8

Thanks for detail. We will try to use the same configuration to see whether it can be reproduced or not. When you see the error, the fan is spinning, right?

9

A note for Bazzite (and presumably other Universal Blue images) users, and for @Quin_Chou:

TL;DR:

  • ujust update saw the new firmware but did not apply it. Manual update with fwupdmgr update worked.
  • It’s easy to miss the “Device requires AC power to be connected” error in ujust update.

The long version:

(note that I’m on a slightly modified version of bazzite-dx, but I doubt my changes or the -dx changes would affect this - maybe someone else with a “normal” Bazzite install can comment on whether they experience the same issues)

In my case at least, ujust update did not apply the update. It did show the available update in the “Firmware upgrades” section (same output as fwupdmgr get-updates), but did not apply it (even after a reboot). There was no error reported, and it said “Firmware upgrades: OK” in the summary at the end. That’s after enabling lvfs-testing of course (see first post), otherwise there’s just no update available as this is still in beta. I ran it again, same thing.

Running fwupdmgr update manually from the command line did successfully download and queue the update for installation at the next reboot, and the laptop is now on BIOS 3.05 (confirmed with ujust bios-info after rebooting).

Also: If you’re not on AC power (or presumably if the battery is at 100% and AC power is reported as “off” to fwupdmgr), there’s a message about that in the “Firmware upgrades” section but it scrolls by pretty fast as part of the whole ujust update process, and in the summary it still says “Firmware upgrades: OK”. So even if the update worked with ujust update, you could still easily miss the fact that it’s not being applied because of the AC status.

These 2 issues mean you can easily think you’re keeping your BIOS up to date along with everything else

(I’ll have a look at the ujust update “recipe”, but I’m no expert so expectations are low :slightly_smiling_face:)

10

I’ll check on that next reboot and get back to you.

Ok - rebooted. It does sound like the fan is on, but it is pretty quiet, not cranking full blast or anything like that.

11

To trigger the “CPU fan not fund” error in this BIOS version (3.05) start from default settings then:

  • select the max non-turbo boot option

  • turn off the hypertreading

  • exit & save the settings

  • power off when the boot screen appears

  • wait 30s

  • turn laptop on

The error screen should appear. Do the reverse to get rid of the error.
Turning off virtualization options will likely trigger this as well. I found that turning most options off will trigger this error.
Note: I never touched the other power saving related settings .

I observed this error on 3.04 first and by playing with various settings I managed to get make it appear/disappear in almost consistent fashion.

In case this is not enough below are the other settings deviating from defaults:

  • wait 5s on boot selection

  • limit 60% batt charge

  • set powerbutton led to ultra low

This was tried on an i3 1315U variant. I doubt the RAM or SSD matter but here are the specs anyway: 48G and 1TB.

Edit: I forgot to mention that the fan works just fine despite the error being shown, even during the error screen if it needs to.

Ignoring the error and booting an OS seems to work just as well.

1 Like
12

There is a failure rate associated with this issue; not every system experiences it. We have identified the root causes of this issue. We plan to hold the 3.05 release, and then release the 3.06 beta next week.

3 Likes
13

We release 3.06 beta to resolve the Fan Not Found issue. You can try to update and verify again.