What kind of operation are you running over there?
I finally find time to update my old board. Wasted couple of hours because of misleading post information. There is a large section in the middle “Updating a Mainboard outside of a laptop” which assumes one can update to 3.23 and 3.24 outside of the laptop (I am running my board in external case). This does NOT work - CapsuleApp won’t do any update without battery attach without any specific error message. It just won’t do update. And only in the bottom there is a note “This update requires a battery present to complete the update.“ which actually mean no outside update possible.
So what was the “Updating a Mainboard outside of a laptop” section about then? If it needs battery, it is not “outside of laptop“. “This release supports standalone updates without a battery attached only when updating using the EFI shell method only.“ - not working due to CapsuleApp.efi doesn’t work without battery attached.
If someone having same issues I described here please note - you HAVE TO CONNECT BATTERY if you want to install 3.23 and 3.24. Once you connect battery, everything going smooth, you will get 3.23 first, 3.24 next. Now, if Framework do release new version in future, it might be possible to install it without battery. However taking into account age of the board, I won’t count on it.
1 Like
Hi Everyone,
Just powered on my 11th gen intel framework (i7-1165G7), running BIOS 3.24. A few months ago I updated to 3.23 before updating to 3.24 (as suggested in the bios update notification).
Today Windows Security gave the notification “Actions Recommended”, when clicked it gives the “Secure Boot; Secure Boot is on, but your device does not support the automated Secure Boot certificate update due to hardware or firmware limitations. Contact your device manufacturer for assistance”.
Anyone any clue how to fix this?
Try this
Hi,
Thank you for the suggestion. I had already tried that one (without suspension, have acces recovery key), no effect. Did it again but this time with the suspension of Bitlocker, again nothing changes. I did however get an error message a black screen with white text, also got it the first time but went away too quick to read.
This is what it read; “Your device ran into a problem and needs to restart. We’ll restart for you. Stop Code: DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)”.
After doing a quick search online this opened up a whole load of pandora’s boxes for me. Any idea what to do for framework specifically or is this one of those problems where it’s basically try all the different steps suggested in other forums to see what might actually fix this?
I wonder if we’ll be getting another BIOS update for this board. It’s been 6 months since this version was released. I guess it does depends on what’s there to fix.
No idea where to go from there tbh but I wish you luck.
Just went into Event Viewer and discovered the following 2 errors during the reboot;
-
Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection.
1.Q - Any clue what Framework has for this? -
A PK-signed Key Exchange Key (KEK) cannot be found for this device. Check with the device manufacturer for proper key provisioning.
2.Q - This sounds like a ‘contact support’ but feels like it might be something else, any idea?
I guess it will mostly depend on other downstream suppliers (chip manufactures etc) if they still support the chips in the board I would assume we’ll be getting other updates. Maybe no big updates but I would assume security updates are here to stay for as long as all suppliers support their components in this board.