As amoun said the BIOS update doesn’t fix the CMOS problem because that is a sillicon defect in 11th gen chips. 
BIOS update 3.08 was supposed to fix power down state drainage but I’m not sure if that carried over to 3.10, I think it did though, so it’s strange that you experience drain while shutdown.
Also amoun just shoutout to you for being so active on the forum- kudos to you for remaining informative.
I’ve owned/used many, many laptops over the years and Framework has the distinction of having the absolute worst battery drain I’ve ever seen in a laptop that sits fully powered off.
I have my old mid-2015 Macbook pro sitting in my closet. I stored it away over a year ago with a 50% charge on the battery. I just powered it on and battery is at 48%…
Sadly that does come with a new laptop 
Hopefully it’ll be fixed over time.
A fully powered down device should not be taking any power so that is why your other laptops all performed so well- Framework just needs to fix some bugs and it’ll be fine.
Apparently, you haven’t read through the forums about this issue. It’s not fixable. It’s part an 11th gen Intel CPU issue and the Framework USB-4 module design. Framework released an official statement saying that the problem is not ultimately fixable, where the 3.10 bios was supposed to help minimize battery drain, not cure it.
So if you’re aware that the problem is “not fixable”, what is this post even about?
Battery issue / behaviour with the Framework Laptop (Intel 11th gen, at least) comes in so many shapes and forms…left, right and centre:
We’re in the desktop replacement laptop market…we just didn’t know about it. 
@ParticleCannon This post is to let users know that the 3.10 bios doesn’t improve battery drain in a shutdown state. This post also serves as a cautionary tale for anyone considering purchasing a Framework laptop, that only uses the product occasionally.
@Stephen_Manis, I think your particular scenario is that the RTC battery is drained…and not able to initiate power up. (Not so much about the main battery, as it still has charge)
i.e. Your RTC battery wasn’t fully charged / plugged in for 24 hours to begin with.
@Second_Coming I’m on the 3.10 bios, which is supposed to prevent CMOS battery drain (unless the main battery is totally drained, and then you’re screwed anyway and have to disassemble the damn laptop again).
I charged the laptop overnight to 100% prior to storing it away.
In short, we’ve all paid Framework to beta test some questionable hardware design. For my use case, a Framework laptop sucks and still has the worst battery drain I’ve every experienced in a laptop that is fully powered down.
No.
3.09 fixed this (which got carried into 3.10):
“Reduce main battery drain in off state by turning off analog reference in charger IC.”
@Second_Coming I’m on 3.10 and the problem is clearly not “fixed”. The offcial statement from Framework is that the problem really isn’t fixable as it’s partly based on an Intel 11th gen CPU bug and on their USB-4 module design.
Their recommendation is to always leave your laptop plugged in. Otherwise, the batteries will drain, and you’ll have to crack open the laptop, unplug both batteries, wait a minute, plug then back in, reassemble, and charge overnight. That… sucks…
Exactly. RTC battery drain is not fixable on the 11th gen. Nor was there mention of “reduce” RTC battery drain in the BIOS release note.
i.e. You STILL need to charge the laptop for an initial 24 hours…specifically for the RTC battery.
The crack it open scenario is only needed when you have a drained / low RTC battery, in combination with running into the silicon bug.
Regardless, I’m done wasting my time here. I’ll sell off the Framework, steer anyone who will listen away from Framework laptops, and consider paying the Apple tax again. (or a cheap, commodity laptop and slap Linux on it).
I get your frustration…totally. I’ve been there. Been there for months.
But people convinced me to hold onto the ‘platform’…until future hardware fixes / improvements come along. Meanwhile…for me, back to ThinkPads.
On the brighter side of things: The 12th gen mainboard seems to have better suspend drain, and additional circuitry to deal with / avoid the battery pull situation.
It seems like multiple issues are being conflated in this discussion. BIOS 3.08 and newer resolved all known issues we’ve seen around battery drain while shut down. Both our internal testing and the community beta testing confirmed that. However, this is clearly a report of a scenario where a BIOS 3.10 system has drain while shut down, which means there is an unknown issue around it. Please reach out to our Support team. We definitely want to understand what the root cause of this is on this system.
@Stephen_Manis What operation system are you using?
By default windows has an option called “fast startup” enabled, that does not really turn the laptop off, even when shutting it down.
To check right click on the battery icon in the system tray → “power options” → “choose what the power options do” and on the bottom should be a checkbox "Turn on fast start-up (recommended)
I dont have a framework (yet, waiting for Batch 2) and i am not reading this forum for too long, so i dont know, what effect this setting even has on the framework… but maybe there is a chance
@Simon_F I’m running Linux (Fedora 36). Regardless, I’m done here. I’m selling off my Framework laptop and cutting my losses. I need a machine that’s ready to go when I pull it out of its bag.
@nrp Will you please delete my Framework account and any personal information stored on your systems? I don’t want to receive any further emails from this forum. Your site doesn’t allow me to remove my email address from my account.
Sorry to hear that
Is there a bios option to keep any usb port running for power delivery?
Havent seen it in the original bios guide, but maybe it is outdated.
My last guess would be to enter the bios → Exit → load optimal defaults.
Dont know how that could help, but on each bios update of my current laptop, it gets recommended.
Please submit a ticket to Framework Support for this request. Thanks.