If you’re an IT professional and managing Office 365 for your clients, this article may help you to resolve a Trusted Platform Module (TPM) error which your clients may see. Some of the clients while sychronization of email or contacts, will be asked for credentials. After the credentials are entered, they’re asked for same again. And following error happens then:
Something went wrong. Your computer’s Trusted Platform Module has malfunctioned. If this error persists, contact your system administrator with the error code 80090016.
In this case, the server message is ‘Keyset does not exist Keyset does not exist‘. The common cause for this issue may be that TPM chip or firmware is not up-to-date. You should upgrade TPM firmware and this should help. Else, you can below mentioned fixes.
FIX 1 – Uninstall TPM And Check
1. Press + R and type devmgmt. msc in the Run, hit Enter key to open Device Manager snap-in.
2. In the Device Manager window, under Security devices, right click on Trusted Platform Module [X.0], where X.0 is the version number and select Uninstall device. Confirm the uninstall operation on confirmation prompt.
3. Close Device Manager, reboot and check the status of problem.
If after rebooting the machine, the issue is resolved, it means the TPM chip is really corrupted and you need to seek for its hardware replacement.
If issue still persists, try FIX 2 mentioned next.
FIX 2 – Rename Azure Active Directory Authentication Plugin
By default, Outlook or rather should I say Office 365 on Windows 10 V1703 or later uses Azure Active Directory Authentication Library (ADAL) framework-based authentication. Microsoft says, Office build 16.0.7967 or later, uses Web Account Manager (WAM) for sign-in workflows. This issue can be fixed by renaming the plugin used for the authentication purpose. You need to sign in with different account or perform this workaround from a network share and make sure the client facing this account is signed off. Then try these steps:
1. Press + R and type %appdata%\Local\Packages and press Enter key or click OK.
3. Note that Microsoft. AAD. BrokerPlugin_cw5n1h2txyewy folder will be automatically recreated as soon as the affected client log in. Start Outlook and allow organization to manage the device. If you get any TPM error, ignore it and continue using Outlook. The error may no longer appearing then.
About Kapil Arya
Kapil is presently a Microsoft MVP in Windows IT Pro expertise. He is Windows Insider MVP as well, and author of ‘Windows Group Policy Troubleshooting’ book. In 2015, Microsoft India accomplished him as ‘Windows 10 Champion’. Being passionate Windows blogger, he loves to help others on fixing their system issues. You can follow him for news/updates and fixes for Windows.
Hi Kapil, thanks for this. I followed your steps – but I’m facing the same issues all over again. I’ve been recommended to create a new profile, failing which, I should reformat windows. I’ve read multiple articles here a new profile has not solved the problem.
I started facing this issue of credentials after the latest windows 10 feature update 2 weeks back.
What do you recommend?
we had to replace a motherboard in a staff members laptop and started to receive this error after the new one was installed. Basically just had to rename a AAD Broker folder.
Fix Error Code 0x80090016 for PIN and Microsoft Store
Error Code 0x80090016 which a user may receive on his Windows 10 computer could be while creating a PIN or when using the Microsoft Store. There have been reports of the Windows 10 Login PIN failing the users to sign in or being not able to be set up. The solutions to fix this error in both the scenarios are totally different.
The error message for the PIN related error reads-
Something went wrong, We weren’t able to set up your PIN. Sometimes it helps to try again or you can skip for now and do this later.
The error message for the Microsoft Store related error reads-
Try that again, Something happened on our end and we couldn’t sign you in.
We will be covering the fixes for each of the components separately so that there is no confusion.
Error Code 0x80090016 Microsoft Store
1] Sync Date and Time
You need to have a correct Date and Time set on your computer to access various Windows 10 services.
For this, start by hitting the WINKEY + I button combinations on the keyboard to start the Settings app.
Now, navigate to Time & Language > Date & time.
On the right side panel, turn the toggle On for Set time automatically and Set time zone automatically.
Next, click on Region & language on the left side panel. Make sure that the Country or region on the right side panel is set to the country that you live in.
Close the Settings app and Reboot your computer for the changes to take effect.
2] Re-register the Microsoft Store app using Powershell
Start by pressing WINKEY + X button combo or right-click on the Start button and click on Windows Powershell (Admin) or search for Powershell in the Cortana search box, right click on the Command Prompt icon and click on Run as Administrator. Click on Yes for the UAC or User Account Control prompt that you get. Then, the Windows Powershell window will finally be open. Now, type in the following command to re-register the Microsoft Store app and then hit Enter.
Let the process complete and then check if your issue is fixed or not.
3] Reset the Microsoft Store
You can try to Reset Microsoft Store and check if any cached files or folders are causing a conflict to your Store being connected to the Microsoft Servers.
4] Run Microsoft Store Apps Troubleshooter
Microsoft has also released a dedicated Microsoft Store apps Troubleshooter. You need to download and run it.
Error Code 0x80090016 for PIN
The cause behind the issue is the corruption of the contents of the NGC folder. The NGC folder is responsible for storing certain files which are crucial for the system’s security. The most probable reason behind the corruption of the folder is when a third-party software modifies the files. Other than this, third-party software products induce certain background processes which could cause this error.
We will proceed with the solutions in the following sequence:
1] Uninstall any recently installed third-party software
Usually, freeware products aren’t always free. Such products come along with extensions and other malware. If you have installed any such software recently, please uninstall them from the Control Panel.
2] Empty contents of NGC Folder
You need to delete all the contents of the NGC Folder – for that you will need to take ownership of this folder first-
Once done, just permanently delete all the contents of that folder and reboot your computer normally.
The AppData folder might be hidden so you may need to show hidden files & folders.
2] Use Group Policy Editor
Hit the WINKEY + R button combination to launch the Run utility, type in gpedit. msc and hit Enter. Once Group Policy Editor opens, navigate to the following setting-
Computer Configuration > Administrative Templates > System > Logon
Now, on the right side panel and double click on Turn on convenience PIN Sign-in and set the radio button to Enabled for it.
This policy setting allows you to control whether a domain user can sign in using a convenience PIN. If you enable this policy setting, a domain user can set up and sign in with a convenience PIN. If you disable or don’t configure this policy setting, a domain user can’t set up and use a convenience PIN. Note: The user’s domain password will be cached in the system vault when using this feature. To configure Windows Hello for Business, use the Administrative Template policies under Windows Hello for Business.
This will turn on the Logins using PIN. Setting the radio button as Disabled or Not Configured will turn off the Logins using PIN.
Exit the Group Policy Editor and then reboot your computer for the changes to take effect.
Date: February 23, 2019 Tags: Errors, Windows Store
What are Runtime Errors? Their causes and How to fix them?
Fix File System Error (-2147219195) on Windows 10
Fix BIOS Power-On Self-Test (POST) errors on Windows 10 systems
Ayush has been a Windows enthusiast since the day he got his first PC with Windows 98SE. He is an active Windows Insider since Day 1 and is now a Windows Insider MVP. He has been testing pre-release services on his Windows 10 PC, Lumia, and Android devices.