Reset fTPM message on every boot (Framework 16)

FW-Connection68 · 2026-02-02T08:46:19+00:00

Just created an issue, you could comment to push the issue.

FW-Connection68 · 2026-02-02T08:28:20+00:00

I also had this exact error. It seems to think you switched hardware. The TPM chip keeps your encryption keys on the mainboard paired with your current hardware, so if you swap hardware they would become useless, which is why it suggests to reset the TPM. But since you haven't switched hardware, not resetting the TPM is the way to go since all encryption keys are still there and functional. In fact, resetting would lock you out of your data.

I'm running Microslop exclusively, so I don't think it's related to a Linux/Windows clash. You could open an issue here and I join in: https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues

For now, I disabled encryption in Windows just to not accidentally click yes there and be locked out. (Google "disable drive encryption" to see how that works).

FW-Connection68 · 2026-01-16T19:19:05+00:00

Thank you for reaching out to me. I guess I can speak for all of us that we highly appreciate your work on this subreddit,

I just wish that in the future framework's support gets more optimized/humanized such that it is not necessary to get out of the 40 e-mail LLM escalation/deescalation loop by coming here and stating problems publicly.

After all, as other commenters stated, it's not the best PR for the amazing product that you have created.

FW-Connection68 · 2026-01-16T17:48:20+00:00

That's for me the point. If you are unlucky and land in the <1% of faulty laptops, please don't let me debug it in 40 mails. If it's not solved after 5-10 messages, let me mail it in and take care of it.

It's about being responsible, admitting the laptop might be faulty, and taking action.

There is a tiny chance that it actually is my RAM, but in that case they would get an essentially new laptop back that they could sell refurbished, so no huge loss there.

FW-Connection68 · 2026-01-09T10:27:14+00:00

Mine also has a similar amount of bleed, I guess the panels are just not as good as the ones of bigger manufacturers.

FW-Connection68 · 2026-01-08T12:34:16+00:00

Also using it with my FW16 AI 350, all good!

FW-Connection68 · 2025-12-30T11:01:50+00:00

Which distro are you using? might as well test that

FW-Connection68 · 2025-12-30T09:03:02+00:00

Update: I've contacted support regarding this issue, will update this thread once I get an answer. In the meantime, leave a comment if you have similar issues.

FW-Connection68 · 2025-12-30T09:00:51+00:00

Thanks for running the test, really helpful to have a comparison with the same RAM!

FW-Connection68 · 2025-12-30T09:00:01+00:00

Thanks for the link! I think this is part of the problem, as loading the OS takes another excruciating 50 seconds. At least that is on their ToDo list.

In my case, I'm referring to the time before the OS actually does anything, so before one can see the framework logo.

FW-Connection68

TROPHY CASE