› UKTH forums › 💻 Computers › Desktops › fTPM NV Corrupted or fTPM Structure Changed” Message After CPU Swap If you’ve just installed a new CPU and your system suddenly throws this alarming BIOS message: —- New CPU installed, fTPM NV corrupted or fTPM N structure changed. Press Y...
- This topic has 0 replies, 1 voice, and was last updated 1 month, 1 week ago by
UK Sentinel.
- AuthorPosts
- March 18, 2026 at 7:38 pm #42191
If you’ve just installed a new CPU and your system suddenly throws this alarming BIOS message:
—-
New CPU installed, fTPM NV corrupted or fTPM N structure changed.
Press Y to reset fTPM. If you have BitLocker or encryption enabled,
fTPM will NOT be able to unlock the system with the new CPU, and the system will require a recovery key.
Press N to keep previous fTPM record and continue system boot. You can swap back to the old CPU to recover TPM-related keys and data.—–
What that message actually means
Your motherboard uses fTPM (firmware TPM) to store security keys — things like BitLocker keys, Windows Hello data, and other encrypted info. When you swap a CPU, the fTPM data stored in the motherboard may no longer match what the system expects. So the BIOS basically says:
“Hey, the CPU changed. The TPM data doesn’t match anymore. Do you want to reset it or keep the old data?”
This is normal when changing CPUs on systems that use fTPM.
Why it warns about BitLocker
If BitLocker or any encryption is enabled, the TPM holds the keys. If you reset the TPM (press Y), those keys are wiped. If BitLocker was active, Windows would normally ask for a recovery key on next boot.
The message is basically trying to prevent you from accidentally locking yourself out.
Why pressing N didn’t help
Pressing N tells the system:
“Keep the old TPM data.”
But because the CPU changed, the system keeps detecting a mismatch and re‑prompts you. It loops until you either:
- put the old CPU back, or
- reset the TPM (press Y)
So your experience is exactly what usually happens.
Why pressing Y fixed it
Pressing Y resets the TPM and clears the mismatch. If you didn’t have BitLocker enabled, there’s no harm done — Windows just boots normally.
That’s why everything worked afterward.
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
- AuthorPosts
- You must be logged in to reply to this topic.
