Having trouble using the Windows 10 password manager to log in? You've come to the right place if you're having trouble logging in and getting an error message that says “Trusted Platform Module has failed.”
Even though an easy fix like “restart” may work for most errors, it won't fix the TPM error 80090030 in teams.
Don't worry, we'll take care of you. This guide takes a close look at the problem and lists all of the possible ways to fix it.
Here are the steps to fix error 80090030 in Microsoft Teams:
1.Take away access to the Teams account
The first and best way to fix error 80090030 is to remove or stop the login information for your account from the credential manager.
- Start up the Control Panel
- Click on User Accounts at the top of the user settings
- Go to the Credential Manager
- Type “Credential Manager” into the search box in Windows and press “Enter” to open it.
- On the window where you can manage your passwords, click Windows passwords.
- Click on the log-in information for your MS Teams account in the list of “Generic Credentials.” You can see msteams_adalsso/adal_context_segments passwords.
- Click the Remove button to get rid of your login information for your MS Teams account.
- Try to sign in again after you restart your machine.
2.Update TPM Firmware
If the problem still continues. there may be some trouble with your TPM module. Hence, you should consider changing the TPM Firmware.
You can update the Trusted Platform Module in any of the following ways:
- By downloading the latest Windows Update
- By installing the firmware changes from the manufacturer’s website
How do I fix malfunctioned TPM?
- Open Settings > Update & Security > Windows Security > Device Security.
- Under Security processor > Select Security processor details > Security processor troubleshooting.
- Click on clear TPM
- Restart the device
- Try to activate microsoft 365 again.
3.Create EnableADAL Key On Registry Setting
Another effective way is creating an EnableADAL key in your registry setting. Make sure you make a system restore point before moving forward.
- Type run on the Windows search bar and press Enter button to start the Windows Run program. Or, Press Windows Key + R on your keyboard to open the Windows Run app.
- Type regedit and press the Enter button to start the Registry Editor.
- Navigate to HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity
- Right-click on an empty space on the right side.
- Go to New and select DWORD Value to make a new key.
- Enter EnableADAL name for this key.
- Right-click and pick Modify to edit the DWORD Value. Or, Double click to change the DWORD Value.
- Enter the number 0 in the number data field.
- Click on Ok to save the changes.
After making the EnableADAL key in your registry settings, restart your computer. Now, try to log in to your Microsoft Outlook or Teams account to see whether your problem is fixed.
4. Create A New User Account
If your Microsoft account is old, it might cause you to get the MS Teams 80090030 problem. So, make a new account and sign in with that new account.
- To open Settings, press Windows + I on your computer.
- Click on Accounts.
- Select Family & other people from the menu on the left.
- Choose Add another person to this computer.
- Click on I don't know how to sign in as this person.
- Click Add a person who doesn't already have a Microsoft account.
- Follow the directions on the screen and type in your user name, password, and password again.
- To turn on the new user account, click the Next button.
5. Login with Incognito Mode
You can sign in to your MS Teams account through the web app. You can try signing in to your MS Teams account in “incognito mode.”
Open a browser and use an incognito or secret tab to go to teams.microsoft.com. Check to see if you can get in or not.
Final Words
Since many teams users were getting this error, we looked into it and gave our solutions after trying them thoroughly.
The problem happens when Microsoft credentials can't be saved or retrieved, the TPM firmware is out of date, or there are settings that don't work together. This mistake means that the encryption provider's device isn't ready to be used yet.
