Wondering if anyone has seen this before. I have a relatively new Framework 13 Ryzen AI 350, set up to dual boot Windows 11 and Fedora 42. Everything was working for a couple weeks, BIOS is up to date, able to switch OSs. I’m also using a USB4 eGPU successfully in both OSs.
But after a random reboot from Linux, with no updates or anything, clean shutdown, at post I get this message:
Press Y to reset fTPM, if you have BitLocker or encryption-enabled syste, the system will not boot without a recovery key Press N to keep previous fTPM record and continue system boot. fTPM will Not be enabled with new CPU unless fTPM is reset (reinitialized). you could swap back to the old CPU to recover TPM related keys and data ----------------------------- Yes No
Obviously I haven’t switched CPUs, so I don’t know what could have caused this.
My windows partition is bitlocker, and I stupidly didn’t get a chance to get the recovery key before this happened so I can’t boot that OS, though Linux still works. I opened a support ticket and they’re telling me I shouldn’t dual boot, which would making this not a usable machine for me. Ultimately they have not been particularly helpful.
If I have to wipe windows, I’ll deal with that. But I don’t want this to happen again if I don’t know what the cause is. Is there seriously a way dual booting can corrupt fTPM? Or am I looking at a hardware failure of some sort?
Don’t have any answers for you, but I’ve never seen that happen on my year-and-a-bit-old FW16, which I’ve had set up for dual-booting the entire time. I don’t often boot into the Windows (11) partition, but I do still have it.
I am not an expert, but that message is really odd.
The fTPM is embedded in the CPU chip, so how could it possibly think the CPU has changed but the fTPM has not and needs wiping.
All I would suggest is power off and remove the PSU, and wait 2 minutes (resets the EC), then plug the PSU back in and see if you still get that message.
I updated a week before it happened. I’m on 3.40. It was working on the new bios for a few days before it happened. I just randomly shutdown one day, and when I booted it got this error.
I have the same problem as you on a Framework13 AMD Ryzen 5 7640U. It happened about the same time as you too. I’m not dual booting, only linux on Fedora 42. I update my system whenever an update is available. Did you manage to fix this ?
A bit of searching finds some other manufacturer bios expand on the message. It can be due to a cpu swap, but also may be due to a corrupt TPM module.
I think the fix is to either know your bitlocker recovery code, or disable/remove bitlocker, and any other os that uses TPM (e.g. linux luks can use TPM), then say yes, it clears the TPM, and then you can turn bitlocker on again.
The question I have is how my TPM module got corrupted in the first place, and how to prevent it from happening again. The fear I have is that this is faulty hardware causing TPM to get corrupted. My hope is that this is something configuration dependent I can prevent.
The TPM can get corrupted just like any other memory device. It just does not happen nearly as often. Windows is particularly fussy about seeing anything change from the last state it saw things in and flags an issue straight away. Great from a security standpoint but not so great for common users.
These are my suggestions:
Backup your Bitlocker Key in TWO places
Backup what is important to you in Windows
Turn OFF bitlocker (unless you really need that level of security)
Reset the BIOS to defaults
Reboot
Reset the TPM
Reboot and if the stars align Windows will boot without issue
Otherwise, a fresh install of Windows might be a good idea (installing over the top of the existing installation is ok too)
If the machine is not running Windows 11 24H2 or later just download the latest Windows build, make a flash drive with Rufus and it should ask to “update and keep applications/files”
My fTPM has apparently changed, but I haven’t changed any hardware. Pressing N my system boots to the Windows 11 login screen (I’m not dual booting). My fingerprint sensor is now disabled and PIN isn’t available (“something happened" message). My Windows password isn’t recognized as correct.
I have just submitted a support request. Did you ever resolve your issues?
