# Enabling software longevity **URL:** \ **Category:** Blog\ **Created:** [April 16, 2024, 4:18pm UTC](https://community.frame.work/t/enabling-software-longevity/49041 "2024-04-16T16:18:41Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\ **Post date:** [April 17, 2024, 12:17am UTC](https://community.frame.work/t/enabling-software-longevity/49041/22 "2024-04-17T00:17:26Z")
@James_Rome and @Aaron_Baff , thanks for the suggestion! We have shared the release dates for BIOS and Driver Packages [here](https://www.reddit.com/r/framework/comments/1c5uotv/framework_laptop_bios_and_driver_releases/) and we will be updating the Knowledge Base Articles soon. ---
**Author:** ![Azure](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/azure/32/18838_2.png) [@Azure](https://community.frame.work/u/Azure)\ **Post date:** [April 17, 2024, 1:16am UTC](https://community.frame.work/t/enabling-software-longevity/49041/23 "2024-04-17T01:16:01Z")
You are able to download the whole bundle, then unzip the exe to access the separate driver updates. It’s still downloading all of them, but that does keep it simple for Framework to just upload one packaged file. ---
**Author:** ![Stephen\_Micheals](https://avatars.discourse-cdn.com/v4/letter/s/94ad74/32.png) [@Stephen\_Micheals](https://community.frame.work/u/Stephen_Micheals)\ **Post date:** [April 17, 2024, 6:27am UTC](https://community.frame.work/t/enabling-software-longevity/49041/24 "2024-04-17T06:27:43Z")
Has the download link for the 3.08 bios not been updated on the page yet? the download page still links to what seems to the the beta version: [https://downloads.frame.work/bios/Framework\_Laptop\_12th\_Gen\_Intel\_Core\_BIOS\_\_3.08b.msi](https://downloads.frame.work/bios/Framework_Laptop_12th_Gen_Intel_Core_BIOS__3.08b.msi) the bios posts elsewhere link to: [https://downloads.frame.work/bios/Framework\_Laptop\_12th\_Gen\_Intel\_Core\_BIOS\_\_3.08.msi](https://downloads.frame.work/bios/Framework_Laptop_12th_Gen_Intel_Core_BIOS__3.08.msi) ---
**Author:** ![Adrian\_Joachim](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/adrian_joachim/32/9949_2.png) [@Adrian\_Joachim](https://community.frame.work/u/Adrian_Joachim)\ **Post date:** [April 17, 2024, 6:48am UTC](https://community.frame.work/t/enabling-software-longevity/49041/25 "2024-04-17T06:48:54Z")
> [@Ray519](#): > > Similar for stuff like the PD fixes for the FW13 AMD. The intel platform never had that specific set of problems. > [@D.H](#): > > I have somewhat mixed feelings reading this post. The mea culpa is appreciated, the changes outlined have a glimmer of hope in them, but words are easy to say. However, actual change via concrete actions count far far far more. Having an actual team for it is definitely a pretty good start, now we’ll have to wait and see what they actually do. ---
**Author:** ![Ray519](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@Ray519](https://community.frame.work/u/Ray519)\ **Post date:** [April 17, 2024, 7:27am UTC](https://community.frame.work/t/enabling-software-longevity/49041/26 "2024-04-17T07:27:27Z")
Not a beta version (depending how you look at it). B is newer and includes a fix more in the installer. The update itself is identical. One of the errors Framework made in rushing the 3.08 “release”. Because they first linked the older, buggier version, because it seems they did not actually look at the feedback since January. That is why I asked for an explanation of that above. ---
**Author:** ![Andreas\_Zapfl](https://avatars.discourse-cdn.com/v4/letter/a/a8b319/32.png) [@Andreas\_Zapfl](https://community.frame.work/u/Andreas_Zapfl)\ **Post date:** [April 17, 2024, 9:56am UTC](https://community.frame.work/t/enabling-software-longevity/49041/27 "2024-04-17T09:56:16Z")
Googled “Frame Work Drivers” Got to [this site](https://knowledgebase.frame.work/en_us/how-do-i-download-drivers-for-my-framework-laptop-SyHOJGwCu) first clicked [this link](https://knowledgebase.frame.work/de/bios-und-treiber-zum-herunterladen-rJ3PaCexh) which led me to the [download site](https://knowledgebase.frame.work/de/framework-laptop-bios-and-driver-releases-(amd-ryzentm-7040-series)-r1rXGVL16). EDIT: The problem is the setting to German. On the German site there is very old data 🤠 ![image](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/2/f/2f6569817d028da7a218a3c91fb0dd95bad404e7.png) ![image](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/f/e/fe0ed233761bdda793736f8c081ef679abbc40a2.png) ---
**Author:** ![Mar\_gin](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@Mar\_gin](https://community.frame.work/u/Mar_gin)\ **Post date:** [April 17, 2024, 1:18pm UTC](https://community.frame.work/t/enabling-software-longevity/49041/28 "2024-04-17T13:18:46Z")
Ah, supporting delivery to Poland is a dream come true, even though I have already ordered my Framework laptop 16 to the friend from Germany. I wonder if I could use Polish address in case of any problems/warranty issues later on? ---
**Author:** ![TheTRUEAsian](https://avatars.discourse-cdn.com/v4/letter/t/da6949/32.png) [@TheTRUEAsian](https://community.frame.work/u/TheTRUEAsian)\ **Post date:** [April 17, 2024, 2:47pm UTC](https://community.frame.work/t/enabling-software-longevity/49041/29 "2024-04-17T14:47:32Z")
Yes, you can use your Polish address as warranty is transferrable between individuals and supported regions. ---
**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\ **Post date:** [April 17, 2024, 4:27pm UTC](https://community.frame.work/t/enabling-software-longevity/49041/30 "2024-04-17T16:27:29Z")
It should be updated, can you please check it again? (might not be up to date if you are not checking the English version, I believe we have not updated the translated versions yet) ---
**Author:** ![Ray519](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@Ray519](https://community.frame.work/u/Ray519)\ **Post date:** [April 17, 2024, 4:39pm UTC](https://community.frame.work/t/enabling-software-longevity/49041/31 "2024-04-17T16:39:58Z")
I read that post as the official release (knowledge-base) page saying “3.08”, but linking to an executable called 3.08b, while the forum thread for the release still links to the “3.08” (non-b) executable. And that caused confusion. And leads to some people assuming the “b” is there for beta or sth. So I think they already saw the current state that Framework intended. It is just somewhat chaotic for people that look a little bit deeper into it. ---
**Author:** ![anarcat](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/anarcat/32/11774_2.png) [@anarcat](https://community.frame.work/u/anarcat)\ **Post date:** [April 18, 2024, 2:12am UTC](https://community.frame.work/t/enabling-software-longevity/49041/33 "2024-04-18T02:12:21Z")
> [@Destroya](#): > > for Linux we’re developing a new updater to handle the specific firmware regions involved. Could we get a little clarification on what we’re talking about here? Is this improvements to the EFI updater, or do we still have some hope of a working LVFS update for the 12th gen? This matters. There’s a standard way to deploy firmware updates on Linux computers now, and it’s LVFS. Everything else basically means you’re going to miss a _lot_ of users who will _not_ come here or in some dark corner of the knowledge base frantically reloading pages to see if, by chance, one year in the future, some BIOS upgrade will pop out. If you’re lucky, they have automated upgrades configured in their distribution. If you’re luckier, they _also_ have automated firmware upgrades. So there’s just no way this “new updater” will scale to an actual significant userbase, so this will hurt our users (and I say this as a Debian developer with years of experience, we sadly know a thing or two about hurting users). Defaults matter. ---
**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\ **Post date:** [April 18, 2024, 2:49am UTC](https://community.frame.work/t/enabling-software-longevity/49041/34 "2024-04-18T02:49:08Z")
I see that you have already found Pixelforest’s comment : [12th Gen Intel Core BIOS 3.08 Release - #338 by pixelforest](http://community.frame.work/t/12th-gen-intel-core-bios-3-08-release/43244/338) linking it here one more time for folks who might have missed it. ---
**Author:** ![Michal\_Kabzinski](https://avatars.discourse-cdn.com/v4/letter/m/8dc957/32.png) [@Michal\_Kabzinski](https://community.frame.work/u/Michal_Kabzinski)\ **Post date:** [April 19, 2024, 2:16pm UTC](https://community.frame.work/t/enabling-software-longevity/49041/35 "2024-04-19T14:16:28Z")
Have You ordered yours yet? 🙂 ---
**Author:** ![Beata\_Maka](https://avatars.discourse-cdn.com/v4/letter/b/c37758/32.png) [@Beata\_Maka](https://community.frame.work/u/Beata_Maka)\ **Post date:** [April 20, 2024, 2:01am UTC](https://community.frame.work/t/enabling-software-longevity/49041/36 "2024-04-20T02:01:10Z")
Yea, I did it as fast as I could, batch 19 😄 ---
**Author:** ![takaides](https://avatars.discourse-cdn.com/v4/letter/t/ac8455/32.png) [@takaides](https://community.frame.work/u/takaides)\ **Post date:** [November 18, 2024, 7:13am UTC](https://community.frame.work/t/enabling-software-longevity/49041/37 "2024-11-18T07:13:02Z")
Any updates on this? ---
**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\ **Post date:** [November 18, 2024, 11:46pm UTC](https://community.frame.work/t/enabling-software-longevity/49041/38 "2024-11-18T23:46:59Z")
We have released BIOS updates for each of our products this year and more updates are on the way. Any specific unit you are looking for? ---
**Author:** ![takaides](https://avatars.discourse-cdn.com/v4/letter/t/ac8455/32.png) [@takaides](https://community.frame.work/u/takaides)\ **Post date:** [November 19, 2024, 2:40am UTC](https://community.frame.work/t/enabling-software-longevity/49041/39 "2024-11-19T02:40:31Z")
> [@Destroya](#): > > **We strongly recommend always running the latest released BIOS and drivers** , as there are both security and bug fixes incorporated: > > > **List of BIOS updates** > > > > - [Framework Laptop 13 (11th Gen Intel Core)](https://knowledgebase.frame.work/framework-laptop-bios-releases-S1dMQt6F) - 3.19 is the latest release. We’ll be doing a further release with additional security updates. > > - [Framework Laptop 13 (12th Gen Intel Core)](https://knowledgebase.frame.work/framework-laptop-bios-and-driver-releases-12th-gen-intel-core-Bkx2kosqq) - 3.08 is the latest release. This incorporates fixes for all known UEFI security issues, including LogoFAIL, and adds support for the 61Wh Battery. This is released for Windows, and for Linux we’re developing a new updater to handle the specific firmware regions involved. > > - [Framework Laptop 13 (13th Gen Intel Core)](https://knowledgebase.frame.work/en_us/framework-laptop-bios-and-driver-releases-13th-gen-intel-core-BkQBvKWr3) - We’re currently in development on a release that incorporates both bug fixes and security fixes. > > - [Framework Laptop 13 (AMD Ryzen 7040 Series)](https://knowledgebase.frame.work/framework-laptop-bios-and-driver-releases-amd-ryzen-7040-series-r1rXGVL16) - 3.05 is the latest release, which we published earlier this week. This includes fixes for LogoFAIL along with assorted bug fixes. You can also pick up our latest driver bundle from that page. > > - [Framework Laptop 16 (AMD Ryzen 7040 Series)](https://knowledgebase.frame.work/en_us/framework-laptop-16-bios-and-driver-releases-BkeqkVovp) - 3.03 is the latest release, which we also published earlier this week. You can pick up the driver bundle there too. > > With each of these complete, we’ve resolved both infrastructure and process issues that **now make it faster for us to iterate on BIOS and driver updates** on each platform. **Obviously, our words here are not enough. We need to and commit to demonstrating this by actually improving both our iteration speed on software updates and our communication** processes around them. | Product | Driver Bundle Release Date | Current Driver “Age” | | --- | --- | --- | | Framework 13 11th Gen Intel | 2024/06/25 | 4 months, 24 days | | Framework 13 12th Gen Intel | 2022/07/26 | **2 years, 3 months, 23 days** | | Framework 13 13th Gen Intel | 2024/06/25 | 4 months, 24 days | | Framework 13 7040 AMD | 2024/04/02\* | **7 months, 16 days** | | Framework 13 Intel Core Ultra | 2024/07/26 | 3 months, 23 days | | Framework 16 7040 AMD | 2024/04/02\* | **7 months, 16 days** | \*An updated driver package installer is available, but the drivers included haven’t been updated As for me, I have a Framework 16. I love this machine, don’t get me wrong. But Framework strongly discourages using component manufacturer supplied drivers, and AMD, for example, puts out updated graphics drivers nearly every month, many of which add significant features or improvements. No Framework approved drivers have been offered since then. And the [latest beta BIOS available (3.04)](http://community.frame.work/t/laptop-16-amd-ryzen-7040-bios-3-04-beta-release/55051) was released July 23; 3 months and 26 days ago. Many folks had issues, and it’s wide release was put on hold while the issues were investigated and tracked down; I completely support that plan, and have no issue with it. BUT after a week of good, solid communication, @Kieran_Levin[’s last post on the topic was July 31.](http://community.frame.work/t/laptop-16-amd-ryzen-7040-bios-3-04-beta-release/55051/27) Since then, you (@Destroya ) [replied once](http://community.frame.work/t/laptop-16-amd-ryzen-7040-bios-3-04-beta-release/55051/47) (quoting a single sentence from one of Kieran’s earlier replies) to someone asking a clarifying question. And then crickets. There hasn’t been any Framework provided communication on the matter since, effectively, the end of July. Given that the update was primarily one focused on patching known security vulnerabilities, personally, I have interest in getting a functional update to patch the known security issues. From my position, armchair-sleuthing, Kieran often seems to be the primary/only Framework employee chiming in on driver/bios posts. I assume that he is the main, if not sole, current Framework employee tasked with said drivers packages and BIOS updates. Given that Framework is currently listing an open position for a firmware engineer, I can’t say Framework isn’t trying to improve and can only hope that more engineers are going to be hired to share the workload. (I haven’t cyber-sleuthed very hard, for all I know, Kieran’s LinkedIn could say he’s the manager of the firmware team 🤷 ) But we don’t know what’s going on, primarily due to a lack of communication. Which was one of the 2 main things that blog post seemed to say was changing; improving iteration speed and communication. So, from my point of view, **since the iteration speed hasn’t significantly improved, nor has the communication significantly improved, I assume the priorities that were communicated in the post have changed or updated**. Policies and priorities change all the time. Stagnation in business, and especially technology companies, can lead to a quick and brutal death (of the company). Maybe I misunderstood the post. Maybe Framework has done a bunch of work that I haven’t noticed (which, given that I don’t have a 13, admittedly I don’t pay nearly as much attention there). Or maybe Framework dropped the ball here, as they spent the first two paragraphs of the post explaining how they had previously. I don’t know what’s going on. In isolation, I don’t need to. But I keep seeing other posts echoing my thoughts. I feel like more and more of the previously upbeat and positive community are sharing posts of doom and gloom. Maybe it’s just in the Framework 16 community tag. Maybe I’m reading into that too much as well. Has Framework kept up with what they described in the post? Have the policies or plans regarding iteration speed or communication changed? I don’t mean to nitpick or imply that you very fine folk haven’t been working or doing good jobs doing any of the many other things that I know you all must be doing, but I just don’t feel like the action plan described in this post have been followed through. That’s what I meant when I asked for updates. ---
**Author:** ![Azure](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/azure/32/18838_2.png) [@Azure](https://community.frame.work/u/Azure)\ **Post date:** [November 19, 2024, 5:24am UTC](https://community.frame.work/t/enabling-software-longevity/49041/40 "2024-11-19T05:24:19Z")
> [@takaides](#): > > No Framework approved drivers have been offered since then. While your concerns about BIOS issues are fair and should be answered, it has been said many times on this forum that the driver packages on the Framework website are for getting your laptop set up, and once you have installed those all future driver updates will come through Windows Update. New driver packages are only released if there are new drivers necessary for setting up the laptop for the first time. As for BIOS updates, I agree that hopefully there is still lots of work happening in the background and results coming soon. I’ve been following the 12th gen laptop BIOS thread, and there still seem to be lots of issues. Additionally while I haven’t heard of any new security issues, I can’t help but feel that we haven’t seen new BIOS betas for a while and I hope that just means they haven’t been necessary. I also agree with you that the general tone of the forums and the reddit has grown more hostile since compared to the earlier years, and I hope that it’s just me reading more new posts than going back through old posts. I don’t know if it’s the addition of the Community Support topic that has led to more issues talked about, but I feel like I haven’t been able to enjoy going on the forums or answering questions as much because I don’t have answers other than “Framework hasn’t commented on that and we won’t know the answer until they do” or “that seems like a question you should ask support” ---
**Author:** ![takaides](https://avatars.discourse-cdn.com/v4/letter/t/ac8455/32.png) [@takaides](https://community.frame.work/u/takaides)\ **Post date:** [November 19, 2024, 6:16am UTC](https://community.frame.work/t/enabling-software-longevity/49041/41 "2024-11-19T06:16:01Z")
> [@Azure](#): > > While your concerns about BIOS issues are fair and should be answered, it has been said many times on this forum that the driver packages on the Framework website are for getting your laptop set up, and once you have installed those all future driver updates will come through Windows Update. New driver packages are only released if there are new drivers necessary for setting up the laptop for the first time. Again, I could be reading into things incorrectly, but… > [@FRWK16 - AMD Software: Adrenalin Edition 24.9.1 - ISSUES](https://community.frame.work/t/frwk16-amd-software-adrenalin-edition-24-9-1-issues/58567/8): > > I believe the driver bundle was released back in April, we just patched it so that it works with 24H2. We should be releasing a new driver bundle but I don’t have the ETA yet. This was said on Oct 3, in response to new graphical drivers released for AMD APUs and GPUs that seem to be causing significant crashes for many, but frustratingly (from a troubleshooting standpoint) not all, Framework 16 users. Seems to imply to me that regular driver updates are supposed to be a thing. ---
**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\ **Post date:** [November 19, 2024, 7:09am UTC](https://community.frame.work/t/enabling-software-longevity/49041/42 "2024-11-19T07:09:53Z")
Thanks for your reply and for sharing your concerns in detail. Kieran, our Lead System Architect and manager of the firmware team (yes, we do have a team and are currently hiring a new member), typically shares the BIOS and driver bundle updates. I try to assist as much as possible, but I’m not a firmware engineer and, therefore, cannot provide technical assistance here. Regarding the Framework Laptop 16 BIOS, we haven’t shared any updates primarily because there hasn’t been anything new to share. The issues are still being tracked and investigated, and we are conducting extensive internal testing. (In hindsight, perhaps we could have communicated that we’re still investigating and working on the BIOS update—do you think that would have helped?) On the Framework Laptop 16 side, this is where things stand. For the Framework Laptop 13, we released new BIOS versions this summer for the Intel Core 13th Gen and Intel Core 11th Gen models, as well as the first BIOS update last week for the Intel Core Ultra Series 1. Additionally, we issued a minor update for the AMD platform driver bundles, fixing compatibility issues with Windows 24H2 (though there were no new drivers). Apart from Intel Core 12th Gen, we’ve released new driver bundles for each of our products this year. We’re also working on new projects to improve awareness of driver bundle and BIOS updates. This includes sending email updates and improving the quality of our release notes. There’s still a lot of room for improvement, and feedback like yours is invaluable in helping us refine our processes and communication. I really appreciate it! As for the “doom and gloom” on the community forums, I’ve noticed it too. I suspect it’s mainly because we don’t have any new products to announce right now—no upcoming pre-orders, reviews, or major updates. Earlier this year, the forums were buzzing with activity as people received their Framework Laptop 16 units and had plenty to discuss. It will be like that again in the future. 🙂 [Previous page](https://community.frame.work/t/enabling-software-longevity/49041.md?page=1) [Next page](https://community.frame.work/t/enabling-software-longevity/49041.md?page=3)