I turned off my laptop (after charging it to 96%) and put it in my bag about 4.5 hours ago, I just pulled it out and turned it on and it’s still at 96%… I know that isn’t that long but it’s a good sign yes?
Hmm, sad that they still haven’t finished 21 days later. Hopefully you all manage to find some firmware engineers soon! 
I noticed you were looking for them.
If waiting on patches from Insyde is the only thing holding up release of 3.08 (no showstopping bugs), then I agree with releasing it now and putting out 3.09 whenever Insyde turns the code outside!
Or is the deleting boot entries problem still persisting in 3.08?
This is their address: 16F., No.120, Sec.2, Jianguo N. Rd., Zhongshan District. Taipei, Taiwan, R. O. C.
Feel free to send them my best wishes as well.
*Joke
1 Like
Still no news on this from Framework, nor Insyde?
4 Likes
Yeah, how about throwing us a bone, guys! I mean, months after a beta version leaks not even a word about when we might expect this? Or if things aren’t going well how about just an explanation about what’s going on?
3 Likes
Yes…
Wait, no. News = good, good = sated, sate = not want more. At least for reasonable people that is!
2 Likes
This is quite something… The CVEs were released publicly more than 3 months ago…and still no fixes. If this were Lenovo, Dell, or HP… certain environment would have failed these devices security audit.
(i.e. Conceptually, there’s this subjective time period where you’re still ‘ok’ with know CVE exposure…but the more time passes, the more likely that you’re exposed)
2 Likes
This is a good point. If the reason the BIOS release is delayed is because they need to usher in a patch for a security vulnerability, it would seem like there should be more of a sense of urgency to getting the update finalized.
The fact that the rest of the code is sitting around more or less finished but we’re waiting on an “urgent” security patch that is for some reason taking months…well, I just feel like I must be missing something… 
1 Like
From bad RAM module , to a bad motherboard and now what is essentially a new version of the DIY laptop I bought batch 2 all using Windows 10.
I have gone from 3.02 originally to the replacement motherboard which is 3.0. I have held off on all the BIOS updates as I saw the various problems with all the incremental updates in the hope that some day a 3.08 would go legal. As everyone here as said, 3 months and counting.
It has been an interesting experiment, buying this Framework laptop.
I have to agree with the sentiments here, new features/fixes are great to have but security vulnerabilities are a far higher priority and 3 months is too long.
This needs to be addressed.
3 Likes
Just upgrade to 3.07 lol, it’s basically completely stable.
1 Like
Yup, definetly. Although I can’t bring myself to blame Framework considering Insyde is the one making it take so long.
2 Likes
So Insyde placed Framework in the backseat?
Dell got their updates…months ago.
https://www.dell.com/support/kbdoc/en-ca/000195969/dsa-2022-032
So has Lenovo for majority of the units on the list:
…To be fair…HP is stuck in pending:
Insyde, WTH?
2 Likes
My thoughts exactly.
It seems so based on Nirav’s earlier comment?
Well, since BIOS updates need to be tailored to every hardware configuration it’s no surprise that Dell (with probably the largest install base) was 1st out of the gate. No idea how big Insyde is and what their bandwidth is … I just want my candy!
No hard feelings on Framework, that’s for sure, just wish they could notice this conversation and at least tell us what’s going on. Information is kind of like mirrors in an elevator lobby – doesn’t make the wait any shorter but gives you something to distract yourself with while you wait.
2 Likes
Potentially dumb question but what does CVE stand for?
1 Like
Don’t forget, as far as I am aware, Framework still hasn’t had Thunderbolt certification from Intel. Patience is a virtue, they say!