The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Error 80090030 (0x80090030) usually means Windows could not complete a TPM-related authentication operation. Teams may be the app displaying the message, but the cause can be Windows sign-in tokens, the Microsoft Entra authentication broker, device or firmware state, or an organization’s security policy. Try the low-risk checks first; do not clear the TPM as an initial fix.
What does Teams error 80090030 mean?
Microsoft maps 0x80090030 to NTE_DEVICE_NOT_READY: the TPM device is not ready for a requested cryptographic operation. The code is sometimes displayed without the 0x prefix. It does not, by itself, prove that the TPM hardware is broken. Microsoft 365 sign-in can also be disrupted by stale or damaged authentication tokens, Windows Web Account Manager (WAM), the Microsoft Entra ID Authentication Broker Plugin (Microsoft.AAD.BrokerPlugin), security software, network controls, firmware, or device-registration problems. Microsoft’s Windows error-code reference identifies the TPM-related code; its Microsoft 365 guidance covers related authentication troubleshooting.
Because Teams can rely on Windows authentication, Outlook, OneDrive, Word, or Excel may fail at the same time. If they do, treat this as a broader Microsoft 365 or Windows sign-in issue rather than repeatedly reinstalling Teams.
First determine whether the problem is local or broader
- Try Teams in a browser at teams.microsoft.com.
- Check whether Outlook or another Microsoft 365 desktop app also fails to sign in.
- If practical, test the same account on another device, or another Windows profile on the affected computer.
- Ask whether other people in the same organization are affected.
| What you find | What it suggests |
|---|---|
| Teams web works but desktop Teams does not | Look first at the local Teams client, its cache, WAM, or Windows credentials. |
| Teams and other Office apps fail on this PC | Investigate Windows authentication, BrokerPlugin tokens, TPM status, device registration, or policy. |
| Several users are affected at once | An organization-wide service incident, network issue, tenant setting, or Conditional Access policy may be involved. Ask an administrator to check service health. |
| Only one Windows profile fails | A profile-specific cache or token-store problem is more likely. |
| The same account fails on multiple devices | Check the account, password, licensing, sign-in policy, or service with your administrator. |
On a work- or school-managed PC, contact IT before changing authentication data, device registration, or security settings. Those changes may trigger MFA or compliance checks.
#1 Best Overall
- Compatible with TPM-M R2.0
- Chipset: Infineon SLB9665
- PIN DEFINE:14Pin
- Interface:LPC
- Please check the Pinout of mainboard at the official website and make sure it compatible with the pinout of TPM module before purchasing, thank you.
Six ways to fix error 80090030
1. Sign out, quit Teams, restart Windows, and test the web app
- In Teams, select your profile picture and choose Sign out.
- Close Teams completely. If it remains open, right-click its taskbar icon and select Quit.
- Restart Windows, then try Teams on the web.
- If the web app works, open desktop Teams and sign in again.
This can clear a temporary app, process, or connection problem without deleting stored data. If the same error appears in multiple Microsoft 365 apps, move on to the authentication steps below rather than repeating restarts. Microsoft also recommends restarting Teams and trying the web client for sign-in and reconnection problems. See its Teams reconnection guidance.
2. Reset or clear the Teams cache for the client you actually use
New Teams and Classic Teams do not use the same cache location. Try the Windows app reset first for New Teams:
- Open Settings > Apps > Installed apps.
- Find Microsoft Teams, select the More options (…) button, then select Advanced options.
- Under Reset, select Reset.
- Restart Teams and sign in again.
Resetting removes local app data and preferences, so you may need to sign in and reapply local settings. Alternatively, to clear the New Teams cache manually, quit Teams, press Windows key + R, enter the path below, and delete the folder contents:
Rank #2
- TPM 2.0 module for Asus motherboard.
- TPM 2.0 module chip 2.0mm pitch, 2x7P, 14 pin security module
- LPC 14 Pin for AsusTPM chip is better compatible with DDR4 memory module of motherboard, built in support memory type higher than DDR3! Supported states may vary by motherboard specification.
- Note: Don't support laptops and motherboards prior to X99; Don't support DDR3 memory.
- Packing list:1x TPM 2.0 Module for ASUS
%userprofile%appdatalocalPackagesMSTeams_8wekyb3d8bbweLocalCacheMicrosoftMSTeamsFor an older Classic Teams installation, quit Teams and clear the contents of:
%appdata%MicrosoftTeamsDo not delete both paths indiscriminately: use the one that matches the installed client. Cache clearing can help with corrupted client data, but it will not repair a TPM or a broken Windows authentication broker. Microsoft documents the New Teams cache and reset procedure, and its support page covers Classic Teams cache clearing.
3. Clear the Microsoft Entra BrokerPlugin token data
If the error appears during work or school account sign-in—especially in more than one Microsoft 365 app—corrupted broker token data may be involved. This step removes authentication tokens, so expect to sign in again and possibly complete MFA. On a managed computer, ask IT first.
Rank #3
- TPM 2.0 module for ASROCK motherboard.
- TPM 2.0 module chip 2.0mm pitch, 2x9P, 18 pin security module for ASROCK
- LPC 18 Pin for TPM chip is better compatible with DDR4 memory module of motherboard, built in support memory type higher than DDR3! Supported states may vary by motherboard specification.
- Note: Don't support laptops and motherboards prior to X99; Don't support DDR3 memory.
- Packing list:1x TPM 2.0 Module for ASROCK
- Close Teams, Outlook, Word, Excel, OneDrive, and other Microsoft 365 apps.
- In File Explorer’s address bar, enter:
%LOCALAPPDATA%PackagesMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewyACTokenBrokerAccounts- Delete the contents of the Accounts folder, then restart Windows and try signing in.
Microsoft also documents a token location associated with Windows Cloud Experience Host:
Free tools Windows power users keep installed
One-click scans. No signup required.
%LOCALAPPDATA%PackagesMicrosoft.Windows.CloudExperienceHost_cw5n1h2txyewyACTokenBrokerAccountsUse this only as part of the documented troubleshooting path when appropriate; it is not a required cleanup for every user. If a folder is absent, do not create it manually. Continue to the next step or ask IT. A successful cleanup should lead to a fresh Microsoft 365 sign-in, after which the error may disappear. See Microsoft’s TPM-malfunction troubleshooting steps.
4. Re-register the Microsoft Entra WAM plugin
If clearing token data does not help, a damaged or missing BrokerPlugin package may need repair. Open PowerShell under the affected Windows user account and run:
Rank #4
- Compatible with ASUS motherboards with 20-1 pin TPM header; Please check your motherboard manual to confirm the presence of a 20-1pin TPM header before purchasing. Not compatible with ASUS X570-P or other models with other TPM header
- TPM 2.0 module 2.54mm pitch, 2x10P, 20-1 pin security module
- LPC 20-1Pin for AsusTPM chip is better compatible with DDR4 memory module of motherboard, built in support memory type higher than DDR3! Supported states may vary by motherboard specification.
- Note: Don't support laptops and motherboards prior to X99; Don't support DDR3 memory.If you are unsure whether your motherboard is compatible with our TPM module, please verify with us before making a purchase. Thank you.
- Packing list:1x TPM 2.0 Module for ASUS (Doesn't fit the connector on a ASUS Prime X570-P motherboard)
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) {
Add-AppxPackage -Register `
"$env:windirSystemAppsMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewyAppxmanifest.xml" `
-DisableDevelopmentMode `
-ForceApplicationShutdown
}
Get-AppxPackage Microsoft.AAD.BrokerPluginThe first block registers the package if Windows does not find it; the last command checks whether it is present. Depending on the computer’s configuration, you may need IT or local administrator help. If PowerShell reports a package or deployment error, save the exact message rather than trying unrelated registry edits. Microsoft documents this WAM/BrokerPlugin approach for automatic-authentication failures.
Security software, a proxy, or a firewall can also block the broker. Microsoft identifies these as possible causes. Do not permanently disable modern authentication, WAM, antivirus, firewall, or Conditional Access to work around the error.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →5. Check TPM status, Windows and firmware updates, and network controls
To inspect TPM status, press Windows key + R, enter tpm.msc, and review the TPM Management console. Note whether Windows reports the TPM as ready and record its specification version. Microsoft recommends TPM 2.0 where supported; a status problem is a reason to involve IT or the device manufacturer, not proof that hardware replacement is needed.
Best Value
- TPM modules are suitable for GIGABYTE for Windows 11 motherboards.
- Some motherboards require a TPM module inserted or an update to the latest BIOS to enable the TPM option.
- 12Pin Remote Card Encryption Security Module Is Easy To Use, No Complicated Procedures Are Required, And It Can Be Used Immediately After Installation.
- Interface: LPC
- Packing list:1x TPM 2.0 Module for GIGABYTE
Install pending Windows and Microsoft 365 updates, and check the computer manufacturer’s support page for applicable BIOS, firmware, or TPM updates. Restart and test again. On a managed device, ask IT to review whether a VPN, proxy, firewall, or endpoint-security rule is interfering with the authentication broker. Do not bypass organizational protections without authorization.
Do not clear the TPM as a routine fix. Clearing it can affect BitLocker, Windows Hello, certificates, and other protected credentials. Before any TPM reset, an administrator should confirm the BitLocker recovery key is available and assess the effect on the device’s credentials and registration.
6. Reinstall Teams or escalate the authentication issue
If Teams alone remains broken after the client and token checks, reinstalling it may help with damaged application files:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Uninstall Microsoft Teams from Settings > Apps > Installed apps.
- Check
%appdata%Microsoftfor a remaining Teams folder and remove it if present. - Install Teams again from Microsoft’s official download source and sign in.
A reinstall will not normally repair WAM, TPM, device-registration, Conditional Access, account, or tenant problems, so it is not a reason to repeat the cycle if the error persists. Microsoft’s Teams sign-in guidance also describes reinstall and administrator diagnostic options.
A Microsoft 365 administrator can run the Teams Sign-in diagnostic in the Microsoft 365 admin center. Availability can differ in government and other special Microsoft 365 environments. An administrator can also check Microsoft 365 service health and review tenant sign-in policies. If local repair has failed, take these details to IT:
Quick Recap
- Exact error text and code, plus any correlation ID, request ID, and timestamp shown.
- Whether Teams web works and whether Outlook or other Office apps also fail.
- Whether another Windows profile, device, or user is affected.
- Windows version/build and whether the client is New Teams or Classic Teams.
- The result shown by
tpm.msc, and any PowerShell package-registration error. - Whether the device is organization-managed and whether the issue began after a Windows, firmware, security-software, or policy change.
What not to do
- Do not clear the TPM casually. First plan for BitLocker recovery and Windows Hello or certificate impacts.
- Do not disable modern authentication or WAM permanently. That can weaken or break organizational sign-in and hide the underlying problem.
- Do not delete your whole Windows profile or remove device registration as a first-line fix. Ask IT before changing managed-device state.
- Do not assume a Teams reinstall is a universal repair. A Windows authentication or tenant problem can survive it.
Quick symptom guide
| Symptom | Best next move |
|---|---|
| Desktop Teams fails, but Teams web works | Reset New Teams or clear the cache for the installed Teams client. |
| Teams and Outlook both fail on one PC | Investigate BrokerPlugin token data, WAM, TPM status, and device policy. |
| Error returns after cleanup or every restart | Ask IT to review security software, device registration, firmware, and sign-in policy. |
| Several users fail at once | Check Microsoft 365 service health, tenant policy, and network conditions before local cache changes. |
| Reinstalling Teams changes nothing | Escalate: the cause is likely outside the Teams application files. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
