This version has now been promoted to Stable. If you already updated to this build during the beta phase, no further action is required.
Highlights
- Update PD firmware to 1.0.0.B.
- Updated Secure Boot screen prompt behavior when an unsigned Linux boot media is detected.
- Updated Power Limit tables and raised Psys Max threshold to 218W.
- Integrated checksum validation into the BIOS Crisis Recovery flow.
- Standardized F1–F12 function key handling to ignore Fn-Lock settings during BIOS POST phase.
- Fixed CPU throttling bug where core frequency remains stuck at LFM (400 MHz).
- Fixed DP Alt Mode fallback negotiation for link partners rejecting SVDM 2.1 protocol structures (PD 1.0.0.B).
- Fixed restricted BIOS boot paths when the “USB Boot” policy is set to Disabled.
- Resolved an issue where corrupted or malformed PD payload data caused the EC to crash.
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_13_Intel_Core_Ultra_S3_BIOS_3.04.exe | 5EB4318950E6C2E629DC17CE36DAD61D24C6BE48A77C9014EF70677EF5F45DCD |
Instructions for Windows Installer:
- Run the .exe.
- Click yes to reboot.
- Wait for the firmware progress bar to complete, and then the system will reboot.
- 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.
Please note that the windows update does not support updating retimer firmware. There is not a functional impact to port functionality if you do not choose to update your retimer firmware.
Windows retimer updates
Please note that retimer updates only need to be done one time. So this is only necessary to do one time. This is optional.
| Download Link | SHA256 |
|---|---|
| Framework_Laptop_13_Intel_Core_Ultra_S3_Retimer01_534530.exe | DAAA8585748950FF944C874C06FC1904170743DC16E45ADF75FD15C1A244F37A |
| Framework_Laptop_13_Intel_Core_Ultra_S3_Retimer23_534530.exe | B2DD9CD149F829708182993168EBF965E170695FABAB8C96D60A3F0B3B3CC91A |
There are 2 retimers on the system. Please follow the instructions to do twice with different executable files.
Retimer update instructions.
- Update the BIOS first.
- Boot into Windows after BIOS update.
- Run the .exe and wait for the firmware update tool to stage the update.
- After initialization, the system will restart and update the retimer firmware.
- Repeat step 3 after rebooting to update the second set of retimers.
Please note that you must update with a charger attached.
Linux/LVFS
Please note that for this platform LVFS supports the updated CSME and Retimer firmware.
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_13_Intel_Core_Ultra_S3_BIOS_3.04_EFI.zip | 05670C849D83990D2D725589FF937F7EA3CA21DE0D36564116245D3B737651ED |
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:
- 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.
- Attach a charger to your device while updating.
- Boot your system while pressing F12 and boot from the thumb drive.
- Let startup.nsh run automatically.
- Follow the instructions to install the update.
Security Fixes
N/A
Enhancements
- Update PD firmware to 1.0.0.B.
- Updated Secure Boot screen prompt behavior when an unsigned Linux boot media is detected.
- Updated Power Limit tables and raised Psys Max threshold to 218W.
- Integrated checksum validation into the BIOS Crisis Recovery flow.
- Standardized F1–F12 function key handling to ignore Fn-Lock settings during BIOS POST phase.
Fixes
- Fixed CPU throttling bug where core frequency remains stuck at LFM (400 MHz).
- Fixed DP Alt Mode fallback negotiation for link partners rejecting SVDM 2.1 protocol structures (PD 1.0.0.B).
- Fixed restricted BIOS boot paths when the “USB Boot” policy is set to Disabled.
- Resolved an issue where corrupted or malformed PD payload data caused the EC to crash.
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.04 | Updated |
|---|---|---|
| Intel CSME | 21.0.6.1503 | Same |
| MCU | 0x11A | Same |
| GOP | 26.0.63 | Same |
| EC | ec_304_34ebc93 | Updated |
| PD | 1.0.0.B | Updated |
| Retimer | 8282 | 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 Framework Support.
Known Issues
N/A
