Highlights
- AMD StrixKrakenPI-FP8 updated to 1.1.0.0c.
- PD firmware updated to 0.0.E.
- Battery charge limiting status implemented.
- Security Fixed - CVE-2025-4275, CVE-2024-49200, CVE-2024-36347
- Fixed system no charging with Anker GaNPrime 65W adapter.
- Fixed the battery extender setting overriding the battery charge limit on boot.
- Fixed battery charging limit being reset by the battery extender reset timer.
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.
Battery Extender functionality
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.
Battery Charge Limit Functionality
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.
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.
Downloads
Windows
| Download Link | SHA256 |
|---|---|
| Framework_Laptop_13_RyzenAI300_BIOS_3.04.exe | 8984CA845FA2E5897D63B779A921C1AC1AE226F97A358E512512092FE2D4651F |
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.
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_13_RyzenAI300_BIOS_3.04_EFI.zip | F1AE4E4A076C4B3F6ADF4952EF55591C25CF30CD2A334CC98A3AB42F75F81B0B |
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.
Updating a Mainboard outside of a laptop
This release supports standalone updates without a battery attached. After rebooting, please follow the onscreen instructions to update your BIOS when in standalone mode, which will require moving the power source between both sides of the Mainboard to allow PD firmware to update correctly.
Please note that the power and display output must be connected to the same side during standalone updates. Failure to do this may result in no display output during the update process.
We recommend the following update flow for standalone updates:
Part 1
Ensure that standalone operation is enabled in the bios advanced setup menu.
Display connected to upper left port.
Power connected to the lower left port.
Run the updater from EFI/Windows updater.
After rebooting into the updater the update will commence:
The updater will update the BIOS and EC.
The Updater will update the PD controller that is not connected to the power source.
You will see one PD controller will fail the update with the X, and “update complete” is displayed, but the bios will restart.
Part 2
At this screen, the bios update will stop. You must disconnect the display and power source, and move them to the other side.
The display should be connected to the top right.
Power should be connected to the bottom right.
Press the power button, and the second PD update will complete.
After this, the system will reboot, and your bios update is complete.
Security Fixes
| Module Name | Vulnerability | Score |
|---|---|---|
| CVE-2025-4275 | Running the provided utility changes the certificate on any Insyde BIOS and then the attached .efi file can be launched. | 7.8 |
| CVE-2024-49200 | An issue was discovered in AcpiS3SaveDxe and ChipsetSvcDxe in Insyde InsydeH2O with kernel 5.2 though 5.7. A potential DXE memory corruption vulnerability has been identified. | 6.4 |
| CVE-2024-36347 | AMD microcode signature verification vulnerability in which they describe a vulnerability in the AMD microcode signature verification mechanism. | 6.4 |
Enhancements
- AMD StrixKrakenPI-FP8 updated to 1.1.0.0c.
- PD firmware updated to 0.0.E.
- Battery charge limiting status implemented.
- F2 hotkey now enters the BIOS setup menu from the boot manager.
Fixes
- Fixed Power button LED auto-dimming.
- Fixed keyboard backlight works incorrectly with auto-dimming.
- Fixed system no charging with Anker GaNPrime 65W adapter.
- Fixed the battery extender setting overriding the battery charge limit on boot.
- Fixed battery charging limit being reset by the battery extender reset timer.
- Removed unimplemented FN+S key combination.
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 |
|---|---|---|
| EC | ec_304_de3833d | Updated |
| PD | 0.0.E | Updated |
| AMD PI | 1.1.0.0c | Updated |
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 support.
Known Issues
- Setting TPM to hidden may cause systems with WD PC SN740 SSDs to get stuck in automatic repair during boot.
