How to Fix Microsoft 365 Error 80090016 and TPM Keyset Issues
Question details
Users are unable to sign into Microsoft 365 applications due to error code 80090016, which indicates a Trusted Platform Module malfunction or a missing keyset.

- Product
- Microsoft 365
- Device & OS
- Windows
- Scenario
- Attempting to log into Microsoft Teams, Word, or other Microsoft 365 applications after a recent account, password, or organizational change.
- Observed behavior
- The sign-in process fails and displays error 80090016, with an accompanying message stating that the Trusted Platform Module has malfunctioned or a keyset does not exist.
Before attempting to clear your Windows credentials or reset the Trusted Platform Module, ensure you have administrative privileges on your computer and have saved all ongoing work.
Clear Saved Credentials in Windows Credential Manager
Removing old or corrupted authentication tokens allows Microsoft 365 to generate a fresh, functioning keyset for your account.
When you change your account details or switch school organizations, Windows often retains outdated sign-in tokens. Deleting these cached credentials forces the system to perform a clean re-authentication.
Click the Windows Start menu, type 'Credential Manager' into the search bar, and press Enter to launch the application.
Click on the 'Windows Credentials' tab to view the list of saved passwords and authentication tokens for your device.
Scroll through the list and locate any entries related to Microsoft, Office, Teams, or OneDrive. Click the downward arrow next to each relevant entry and select 'Remove'.
Restart your computer. Open the affected Microsoft 365 application and sign in again using your updated account credentials.

Disconnect and Reconnect Your Work or School Account
Re-registering your device with your organization can quickly resolve TPM keyset mismatches.
Clear the Trusted Platform Module (TPM)
Resetting the TPM hardware clears all cryptographic keys, fixing deep system errors. Use this method as a last resort.
Avoid Complex Sign-in Errors with WPS Office
Tired of dealing with frustrating TPM keyset errors and Microsoft 365 sign-in issues? Switch to WPS Office. It provides a lightweight, hassle-free environment to view, edit, and create documents without relying on complex device-level authentication modules or mandatory cloud sign-ins.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package for Windows.
- 2. Install the Software: Run the downloaded installer and follow the quick setup wizard to install the suite on your computer.
- 3. Open Your Files: Right-click your existing Microsoft Word, Excel, or PowerPoint files and choose to open them directly in WPS Office.

Frequently Asked Questions
What exactly causes Microsoft 365 Error 80090016?
Error 80090016 typically occurs when the authentication token stored in Windows does not match the cryptographic keys stored in the computer's Trusted Platform Module (TPM). This frequently happens after replacing a motherboard, updating system firmware, or migrating to a new organizational account.
Will clearing the Credential Manager delete my Office files?
No. The Windows Credential Manager only stores your saved passwords and authentication tokens. Deleting these entries will safely log you out of your applications, but it will never delete or affect your personal documents or data.
What should I do if clearing credentials does not fix the TPM keyset issue?
If clearing credentials fails, try disconnecting and reconnecting your account via the 'Access work or school' menu in Windows Settings. If the error still persists, you may need to clear the TPM, but be sure to consult your IT administrator first to avoid losing BitLocker keys.
Can I use Office apps without a functioning TPM?
Microsoft 365 desktop applications rely heavily on modern authentication tied to the TPM. If your TPM is malfunctioning, you may temporarily use the web versions of Word or Excel, or switch to an alternative local suite like WPS Office that does not require TPM-based authentication.




