Error code 80090016 Trusted Platform Module has malfunctioned.

Hi,

I have noticed the replies from WJfromATand PrzemyslawJanus that after using DisableADALatopWAMOverride and DisableAADWAM the issue was fixed but unfortunately this is not recommended and you can see the reason why in: 

Disabling ADAL or WAM to fix Office sign-in or activation issues not recommended - Office 365 | Microsoft Docs.

I have asked for an update and I will let you know. In the meantime, can you confirm if using those 2 registry keys as a workaround fixes the issue?

Hi unfortunately what i states earlier does not fix the issue, the problem is still there, microsoft support is absolutely required

please advise what to do

thanks!

Absolutely agree

Dear Microsoft, please help ordinary users (not pros) to solve the issue.

thanks!

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.

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?

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.