# Framework Laptop 13 - 11th Gen Intel Core BIOS 3.24 Release STABLE

**URL:** <https://community.frame.work/t/framework-laptop-13-11th-gen-intel-core-bios-3-24-release-stable/75534>\
**Category:** Framework Laptop 13\
**Tags:** bios-announcement, intel-11th\
**Created:** [September 25, 2025, 6:11am UTC](https://community.frame.work/t/framework-laptop-13-11th-gen-intel-core-bios-3-24-release-stable/75534 "2025-09-25T06:11:34Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![Kyle\_Farnung](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kyle_farnung/32/17460_2.png) [@Kyle\_Farnung](https://community.frame.work/u/Kyle_Farnung)\
**Post date:** [April 18, 2026, 7:18am UTC](https://community.frame.work/t/framework-laptop-13-11th-gen-intel-core-bios-3-24-release-stable/75534/31 "2026-04-18T07:18:40Z")

</div>

Oddly enough, I managed to find the fix here as well, but it was a lot more complicated. My 11th gen is a bare board, so I needed to pull the battery out of my laptop to do the update to 3.24. After I got there I ended up in the same state. Out of deparation I tried clearing the secure boot keys and resetting to factory defaults, but that just resulted in broken Secure Boot. Then I stumbled upon [Framework Laptop 13 - 11th Gen Intel Core BIOS 3.22 Release Stable](https://community.frame.work/t/framework-laptop-13-11th-gen-intel-core-bios-3-22-release-stable/69340) , specifically Note #1 about broken secure boot.

So what I ended up doing was this:

1. Upgrade 3.19 → 3.23 → 3.24
2. Realize that secure boot wasn’t fully updated, try factory settings, but still no 2023 KEK
3. **This will required your Bitlocker recovery key, best to go find it now.** You can run `manage-bde -protectors -get [DriveLetter]:` if the machine still boots fine.
4. (Probably Optional) Out of desparation, delete all secure boot keys and break secure boot completely. I don’t think this is necessary since the 3.22 ClearVars update should reset them anyway. Windows will still boot after a recovery key entry, but secure boot will be disabled.
5. Stumble on the 3.22 update notes [Framework Laptop 13 - 11th Gen Intel Core BIOS 3.22 Release Stable](https://community.frame.work/t/framework-laptop-13-11th-gen-intel-core-bios-3-22-release-stable/69340) and realize that it’s the same issue
6. Downgrade 3.24 → 3.22 **ClearVars**
7. Enter the BIOS and reset Secure Boot to factory settings again, now I have the 2011 KEK and secure boot sort of works.
8. Realize that Windows didn’t want to boot anymore (probably because of the missing 2023 keys). I could boot the Windows installer, probably due to the 2011 key being trusted.
9. Switch to the EFI Shell updater to upgrade 3.22 → 3.23 → 3.24. This was my first time using it, but since Windows didn’t boot it automatically booted the updater and finished both upgrades automatically.
10. Enter the BIOS again and reset Secure Boot to factory settings again. After reboot you should have the 2023 keys back and Windows should boot again (after another recovery key entry).
11. Windows still hadn’t finished the migration itself, but at that point you have the necessary keys and should be all set when they pull the trigger.
12. (Optional) I ended up running commands to suspend bitlocker, set the update registry key, and force the scheduled task to run. This shouldn’t be necessary in the long term, but after this my Secure Boot was fully upgraded. I ran the instructions from Check-UEFI.bat from [GitHub - garlin-cant-code/SecureBoot-CA-2023-Updates: PowerShell scripts for checking and applying Secure Boot CA 2023 updates for Windows. · GitHub](https://github.com/garlin-cant-code/SecureBoot-CA-2023-Updates/)

---

_[View the full topic](https://community.frame.work/t/framework-laptop-13-11th-gen-intel-core-bios-3-24-release-stable/75534)._