How to fix the TPM has malfunctioned error 80090034
This Trusted Platform Module error means the authentication data is mismatched or malformed, so sign-in to Office apps fails. Rebuilding that data resolves it. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~6 min Updated Jun 2026 88% found this helpful
Error message
80090034. Your computer's Trusted Platform Module has malfunctioned. The TPM authentication data is mismatched or malformed.
Summary
Error 80090034 is a Trusted Platform Module has malfunctioned error meaning the authentication data is mismatched or malformed, so Office apps, Teams or Outlook cannot complete sign-in. The data the app holds no longer matches what the TPM expects, typically because cached credentials or the Windows Hello data got out of step after a password change, a sync issue or a profile problem. The fix is to rebuild that data: clear the stale Office and Windows credentials in Credential Manager, rebuild the NGC folder behind the Windows Hello PIN, and reset the Office activation, so fresh, matching authentication data is created. Clearing the TPM and updating its firmware handle the deeper cases. As with the other TPM errors, this is rarely a hardware failure, it is mismatched data that regenerating clears.
What this error means
Sign-in to Microsoft 365 relies on authentication data that is tied to the TPM. 80090034 means that data is malformed or no longer matches, so the TPM rejects it and the app cannot authenticate. The data, not the chip, is the problem.
Data gets out of step after a password change, a profile or sync issue, or a corrupt Windows Hello store. Regenerating it, by clearing the cached credentials and rebuilding the NGC folder, gives the app and the TPM matching data again, which is why those steps resolve most cases.
Common causes
Mismatched or malformed cached authentication data.
A corrupt NGC folder behind the Windows Hello PIN.
A recent password change that left credentials stale.
A user profile or sync problem.
Outdated or mismatched TPM firmware.
A stuck TPM state needing a clear.
Expert insight
“80090034 is the TPM saying the credentials you handed me are garbled, they do not match. That usually happens after a password change or a Windows Hello hiccup leaves the stored data out of step. So I regenerate it: clear the old Office credentials, rebuild the NGC folder so Windows Hello starts fresh, and reset the Office activation. New matching data, problem gone. Clearing the TPM and updating firmware are there for the stubborn cases, but I rarely need them.”
2Restart, then set up the PIN again under Settings, Accounts, Sign-in options.
3This regenerates the Windows Hello authentication data.
Method 3
Reset the Microsoft 365 activation
1Run Microsoft's Support and Recovery Assistant to reset the Office activation, then re-activate with a fresh sign-in.
2This clears stale activation data tied to the error.
Method 4
Reconnect your work or school account
1Open Settings, Accounts, Access work or school.
2Disconnect the affected account, restart, then add it back and sign in.
3This re-registers the device and refreshes the TPM-backed keys.
Method 5
Clear the TPM
1Open Settings, Device security, Security processor details, Security processor troubleshooting, and choose Clear TPM (or run tpm.msc, Clear TPM).
2This removes corrupt TPM-stored keys; back up anything protected by the TPM first.
3Restart and sign in again.
Method 6
Update the TPM firmware and BIOS
1Install the latest BIOS or UEFI firmware from your PC or motherboard maker, which includes TPM firmware updates.
2An outdated or mismatched TPM firmware causes these errors.
3Confirm the TPM is ready afterwards in tpm.msc.
80090034 is mismatched authentication data, not a dead chip, so the fix is to regenerate it: clear the stale Office credentials, rebuild the NGC folder for Windows Hello, and reset the Office activation. Clear the TPM and update its firmware only if regenerating the data does not resolve it.
Frequently asked questions
What does TPM error 80090034 mean?
It is a Trusted Platform Module has malfunctioned error meaning the authentication data is mismatched or malformed, so Office apps, Teams or Outlook cannot complete sign-in.
How do I fix 80090034?
Clear the stale Office credentials in Credential Manager, rebuild the NGC folder behind the Windows Hello PIN, and reset the Office activation, so fresh matching authentication data is created.
Why did the data become malformed?
Usually after a password change, a profile or sync problem, or a corrupt Windows Hello store left the cached data out of step with what the TPM expects.
Is the TPM chip faulty?
Rarely. This is almost always mismatched data rather than a hardware failure. Regenerating the credentials and Windows Hello data fixes most cases without touching the chip.
What is the NGC folder?
It stores the Windows Hello PIN and related authentication data. If it is corrupt, sign-in fails with TPM errors. Rebuilding it makes Windows create fresh data, after which you set up the PIN again.
When should I clear the TPM?
Only if clearing credentials and rebuilding the NGC folder do not help. Clearing the TPM removes its keys, so back up first and note your BitLocker recovery key.
Still not working?
If regenerating the credentials and Windows Hello data does not clear 80090034, clear the TPM and update its firmware, then set up Windows Hello again. If it still fails on a fresh local profile, the TPM firmware may be faulty and worth a vendor check. You can also submit your error to us for a tailored fix.
