Framework Laptop 13 Ryzen 7040 BIOS 3.17 Release STABLE

Framework Laptop 13
,
1

Highlights

  1. Fixed an issue where the BIOS update process could run on the wrong platform, resulting in the system being bricked.
  2. Fixed an issue where the Supervisor Password incorrectly displayed “Not Installed” after the user had successfully set the password.
  3. Fixed an issue where the system always displayed an “invalid supervisor password” error when the user set TPM to Hidden and set the supervisor password within the same BIOS session.
  4. Fixed an issue where the Wooting 80HE Keyboard did not function while in the BIOS.

Note:

  1. Once you update to 3.17, you can only downgrade to 3.06 or above.

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_Ryzen7040_BIOS_3.17.exe A0E32F71C94F8D6E4D170B40D0F995D93F4FD305376152ABB25D531CE872D858

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

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_Ryzen7040_BIOS_3.17_EFI.zip 1C8F9DE3CCFBFCFF74FB9A09D6C7D051E13624A33329FA5611FC4FF078984878

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.

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.

990026ff1e71573f31a2ed63da1fa64b65b9ed5e_2_1248x702
990026ff1e71573f31a2ed63da1fa64b65b9ed5e_2_1248x7021248×702 34.5 KB

The Updater will update the PD controller that is not connected to the power source.

177cd75aacfeb773be66f39f2e9cda722aae79a0_2_1248x702
177cd75aacfeb773be66f39f2e9cda722aae79a0_2_1248x7021248×702 31.9 KB

You will see one PD controller will fail the update with the X, and “update complete” is displayed, but the bios will restart.

b1bb702a4b3b42ae95aafe3926cf798733f1922f_2_1248x702
b1bb702a4b3b42ae95aafe3926cf798733f1922f_2_1248x7021248×702 34 KB

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.

d5bee9cba02a7d86a465fcad73fa59df59173975_2_1380x776
d5bee9cba02a7d86a465fcad73fa59df59173975_2_1380x7761380×776 21.5 KB

Press the power button, and the second PD update will complete.

ff92c92b4edb366c27c0207b0419e74c6eff39ab_2_1248x702
ff92c92b4edb366c27c0207b0419e74c6eff39ab_2_1248x7021248×702 31.1 KB

After this, the system will reboot, and your bios update is complete.

Security Fixes

N/A

Enhancements

N/A

Fixes

  1. Fixed an issue where the BIOS update process could run on the wrong platform, resulting in the system being bricked.
  2. Fixed an issue where the Supervisor Password incorrectly displayed “Not Installed” after the user had successfully set the password.
  3. Fixed an issue where the system always displayed an “invalid supervisor password” error when the user set TPM to Hidden and set the supervisor password within the same BIOS session.
  4. Fixed an issue where the Wooting 80HE Keyboard did not function while in the BIOS.

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.17 Updated
EC ec_317_03829 Updated
PD 0.0.1C Same
AMD PI 1.2.0.0c 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 support.

Known Issues

  • BIOS display output may not show up in standalone mode when booting the first time. To work around this issue we suggest booting into the OS and then restarting and pressing F2 to enter the setup menu.
  • When updating in standalone mode, there may be no display output after updating one side’s PD firmware. Suggest connecting power and display on the same side when performing a BIOS update in standalone mode.
  • Connecting with iPhones over type-c may be unstable.
5 Likes
Swollen battery! It’s a shame it happened, but
2

When are we getting the updated ec code on the public repo?

3 Likes
3

I crossed my fingers and toes (for luck) and flashed this.
No problems yet. But I only do fairly simple straightforward things, in Windows 11, with my laptop.

4

Smart App Control for windows is blocking it. I’ve submitted this to MSFT to unblock but I’m not holding my breath!

Update: Microsoft unblocked both the BIOS and driver updates. Install went fine! No issues noted!

1 Like
5

A lot of people tell me they were completely blocked from installing something I installed with no trouble at all.

Are you failing to click on more info when the blocked message appears? If you do that you should be offered the option to ignore the warning and continue.

6

There isn’t an option when you are using Smart App Control (enabled by default in Win 11 24H2 I believe) - you need to submit it to Microsoft so they can run it through a sandbox and A/V. When it blocks something from running the user is presented with methods to report it.

It should work for folks now after I submitted it (driver bundle too).

1 Like
7

It’s been 11 days — was there a major problem and hence not yet STABLE?

8

Last time I checked, 11 days was less than the normal 14 days Framework leaves updates as Beta.

9

If I had 3.16 installed, is there any benefits by installing 3.17?

10

Thanks for the insider info. I guess I read this a little too literally

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.

11

Good point! :flushed_face:

12

I will begin working on the release process by the end of this week, immediately following the stable release.

2 Likes
13

Not seeing 3.17 on LVFS yet as of 3:50pm PST 12/9/2025

14

It is stable for at least more then an hour.
You should force refresh all of the available updates in the official GUI app or in terminal using sudo fwupdmgr refresh --force.

15

Upgraded successfully with fwupdm :smiley:

16

Same here, went perfectly smooth :+1: No issues so far.