Error code 80090016 Trusted Platform Module has malfunctioned.

Michael Sen, authentication issues can be classified as TPM-related when you see such errors: NTE_BAD_KEYSET (80090016) or NTE_DEVICE_NOT_READY (80090030) but it doesn't mean that the root cause is the same when TPM chip gets messed up.

How the device is joined to the cloud and the OS version/updates play an important role while troubleshooting TPM that's why on some devices the issues are fixed using some/same workarounds without the need of extreme measures like manual recovery or reimage (https://docs.microsoft.com/en-us/office365/troubleshoot/authentication/connection-issue-when-sign-in-office-2016) and on others not. These are of course not the only cases, reasons, error codes.  

One question, did clearing TPM ever fixed these issues [Troubleshoot the TPM (Windows 10)

• Microsoft 365 Security | Microsoft Docs](https://docs.microsoft.com/en-us/windows/security/information-protection/tpm/initialize-and-configure-ownership-of-the-tpm#clear-all-the-keys-from-the-tpm) ?If it hasn't been tried, it would be helpful to have a confirmation.

Hello,

Thank you for input and sharing what you have found so far. I took that piece about upgrading to 2004 and although it doesn't relate to my environment directly, the piece you mention about it happening intermittently on pre 2004 fits my description a bit more. My last instance with this came from doing a feature update form 1903 to 1909. When the user attempted to log back in he was greeted with the TPM issue. We resolved it but I have also something more to add to this as it relates to TPM. 

Not sure if you've ever experienced this error code or if there is a whole separate thread BUT the symptoms of the error are exactly the same as "80090016 Trusted Platform Module has malfunctioned".

Its Error Code: C0090030 Your computer's Trusted Platform Module has malfunctioned. 

Exact same symptoms and the same fix used for this thread's error code works for the alternate error code I just posted. If microsoft does see this, it would be great if they could add any more input if this falls under the same umbrella or not. As my team and I navigate this extremely irritating issue now into 2021, ill post more updates and findings as they surface on my end. Glad to know this community exists.

Hi Michael

I am glad to see so many new people on board with this issue as it adds credibility to the pain that we have been experiencing due to this issue.  If you look at some of my posts you can see that I have spent a tremendous amount of time and energy trying to diagnose and solve this problem.  At least in my specific situation I have established with 100% certainty what causes the issue to start manifesting.  It is 100% repeatable and reproduceable.  The cause is updating to Windows 10 build 2004 or any update since that one. I won't repeat the steps I have taken to demonstrate that as you can read thru my posts in this thread.  I think that some on this thread may have been experiencing the issue intermittently prior to 2004, but I'm not sure.

I am grateful that Aurelia from Microsoft has submitted this to MS development and is following it for us.  It is the first time since June that I have seen any acknowledgement from Microsoft that this is even a problem worth investigating.  I now have a bit of hope that it will be corrected at some point and we can all get on with using our Microsoft applications the way they are intended to be used.

Hello Everyone, 

Much like all of you in this thread I am here for the same reasons. I am a relatively new admin at my current org. and our department has been trying to get to the bottom of this for some time now. We've exhausted a lot of time and effort and it seems as though much like all of us I've ended up on this thread to no acceptable resolution. 

Im seeing many how-to guides on bandaid fixes for this issue but can anyone truly verify what the cause of this is? One of the first steps in troubleshooting and problem solving is the ability to recreate the issue. My question and input is, has anyone been able to recreate the issue on demand? If so, would you be willing to share how to cause this error or what causes this error? These TPM issues have been happening sporadically across my environment. Our hunch is that its related to a windows update, because I find it hard to believe Dell is sending out computers with ticking time bomb TPM chips. 

Furthermore to add a little bit of value to my post, the steps ive taken to resolve this issue as a band-aid fix, is to rename the ADD Broker folder by appending a .old to the end of it, removing the office creds from control panel, removing a regedit folder, and rejoin the computer to our domain so that the end user can reset their PIN. Any additional information in order to prevent this from happening would be great.

Microsoft anything?

Przemysław Janus & Manuel Carmona (info)thanks for letting me know. I'll pass the feedback further and as mentioned once I get an update, I'll write you back.