Forum Discussion

PS_83's avatar
PS_83
Brass Contributor
Oct 31, 2019

Trusted Platform Module has malfunctioned, error code 80090016

"The server message is “Keyset does not exist Keyset does not exist”   I have a user that just received this error this AM. So far I’ve tried the steps here but nothing has worked. I think I’ll nee...
admin
office 365
security
  • PS_83's avatar
    PS_83
    Oct 31, 2019
    He was waiting for a flight so I only had about 30 min. Cut my losses and created him a new user profile. Working fine but still curious to see what would cause this???
Vadim_Antonov's avatar
Vadim_Antonov
Copper Contributor
Oct 14, 2021
We started facing TPM malfunctioning error when replacing motherboards on AutoPilot machines. No any suggested solutions helped. But we found an easy and effective solution. At least it worked in our case. Rejoining PC to domain. We have a hybrid AD. I did nothing with AAD account or Intune. Just join the affected PC to a workgroup, reset its account in on-prem AD, join the PC back to domain. It resolved the issue.
  • richard1964's avatar
    richard1964
    Copper Contributor
    Nov 22, 2021

    Vadim_Antonov 

    I had this weird problem and it turned out to be Zone Alarm Pro Firewall.

    As soon as I (temporarily) disabled it and ran the Outlook 365 sign-in procedure again everything worked. I did notice that when Outlook started, even with the user signed in there it did not pick up his email account and I had to add it manually using 'Add Account'

    Cheers

  • kev_rev's avatar
    kev_rev
    Copper Contributor
    Oct 03, 2022

    Vadim_Antonov Was the solution for me too! Thanks so much!

     

    I tried renaming and deleting the AAD.Broker and Account.Control folders. I renamed the NGC folder, reset TPM, ran the SARA utility, and no success. Then I unjoined from the AD domain, rejoined, and signed in under the user's AD account. When opening the first O365 app I was prompted to register the device in O365. After that all the apps opened fine.

     

    I will note that about two weeks ago the same error/issue appeared on a laptop that had just had the motherboard replaced, and all it took was renaming the AAD Broker folder to fix it.

     

    Wish I knew more about the underlying connections between a device and O365 to figure out what is causing this, but at least now I have a growing list of things to try.

Resources