Error code 80090016 Trusted Platform Module has malfunctioned.

Anonymous
2020-03-03T17:45:17+00:00

When I try to add a new Office 365 email to my outlook I get the error below.   I think it's because of my "Work or school account" which I want to remove. I'm not sure how my email was signed up for this second account. I set up this computer for home use only, I won't be using any of the Microsoft Azure features. 

My question is, what will happen when I remove my “work account” and leave my Microsoft account?  Everything is backed up on Onedrive, I just don’t know what to expect because when I went to remove it, it warned me about losing data and settings.

Any help would be appreciated. Thank you!

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

157 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-11-01T18:22:17+00:00

    According to KB3480364 all we can do is uninstall 2004 and revert back to old W10 version for those that haven't been messing with this for a month of Sunday's and not missed to timing out of this option or just wait for MS to correct and issue update

    Known issues in this update

    Symptom Workaround
    Users of the Microsoft Input Method Editor (IME) for Japanese or Chinese languages might experience issues when attempting various tasks. You might have issues with input, receive unexpected results, or might not be able to enter text. For more information about the issues, workaround steps, and the currently resolved issues, please see KB4564002
    System and user certificates might be lost when updating a device from Windows<br> 10, version 1809 or later to<br> a later version of Windows 10. Devices<br> will only be<br> impacted if<br> they have already installed any Latest<br> cumulative update (LCU) released<br> September 16, 2020 or later and then<br> proceed to update to a later version of Windows 10 from media<br> or an installation<br> source which does<br> not have<br> an LCU released October<br> 13, 2020 or<br> later integrated.<br> This primarily<br> happens when managed<br> devices are<br> updated using<br> outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft<br> Endpoint Configuration Manager. This<br> might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.<br><br><br><br><br><br>Note Devices<br> using Windows Update for Business or that connect directly to Windows Update are<br> not impacted. Any device connecting to Windows Update should<br> always receive the latest versions of the<br> feature update, including the latest LCU, without<br> any extra steps. If you have already encountered this issue on your device, you can mitigate it within the<br> uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window<br> might be 10 or 30 days depending on the<br> configuration of your<br> environment and<br> the version you’re updating<br> to. You<br> will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the<br> uninstall window, you<br> can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You<br> must make this change before the<br> default uninstall window<br> has lapsed. For more<br> information, see DISM operating<br> system uninstall command-line options.<br><br><br> <br><br>We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-28T18:50:09+00:00

    My team and I have encountered the "80090016" TPM error many times. Come to find out, the DWORD key of "EnableADAL" needs to be added with a hex value of "0" in the registry under "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common". After this you will need to shutdown (not restart) the computer and power it back up. You will then not encounter this error again.

    This is needed because of the new O365 "Modern Authentication" requirements. O365 and Outlook version 2016 and later require this registry key. You can also deploy it in your network using GPO. That way during a migration you do not get halted by this error.

    "Microsoft | Docs - Modern Authentication configuration requirements for transition from Office 365 dedicated/ITAR to vNext"

    https://docs.microsoft.com/en-us/exchange/troubleshoot/administration/modern-authentication-configuration

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-27T00:14:10+00:00

    George,

    Just create a new user profile.  That's what I did and it seems to be working.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-27T00:13:08+00:00

    I finally seemed to have resolved this issue by creating a new user profile on my system.  No errors, No need to re enter passwords.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-27T00:04:23+00:00

    No luck.  Latest build did nothing :(

    Was this answer helpful?

    0 comments