Trusted Platform Module has malfunctioned....

Anonymous
2019-04-17T08:54:32+00:00

Outlook 2016 with Office 365 account keeps prompting for password. After entering it, an error pops up "Your computer's Trusted Platform Module has malfunctioned. If this error persists, contact your system administrator with the error code 80090030. It affects Outlook login only. 

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 No comments
Answer accepted by question author
Anonymous
2019-05-10T06:05:20+00:00

The word on the street is that Outlook is wanting MFA.  So either you have to turn on MFA or disable ADAL

Fix get them onto MFA or

Close Outlook

Open Regedit

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity

Create REG_DWORD

EnableADAL

0

Was this answer helpful?

700+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2019-04-18T04:15:09+00:00

Hi Sam,

Based on the error message, the issue is related to Trusted Platform Module(TPM). You need to check whether your TPM works correctly. You try to back up your data and clear TPM. It will reset your security processor to its default settings. For your reference:

https://support.microsoft.com/en-us/help/4096339/windows-10-device-protection-in-windows-defender-security-center#clearTPM

For more details about TPM, you can follow the link below:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-vista/cc749022(v=ws.10)

Regards,

Carlos

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments

120 additional answers

Sort by: Oldest
  1. Anonymous
    2021-11-02T02:33:18+00:00

    I was able to fix this issue by disconnecting my Work account and then reconnecting it. I was receiving the exact same error message and I had tried clearing the TPM and other fixes to no avail.

    Below are the steps I used to remedy the issue:

    1. Navigate to the “Accounts” section of the Settings app and navigate to the “Access work or school” page. Click the account you want to unlink and press the “Disconnect” button. Follow the prompts to complete the account removal process.
    2. Navigate to the “Accounts” section of the Settings app and navigate back to the “Access work or school” page. Click the "+" icon to associate an account.
    3. Enter your credentials and wait for the process to complete.
    4. Launch Outlook and all should be functioning properly.

    Thank you Timothy_P, this fixed my issue. I fought this for 5 hours today. Tried Reinstalling, updates, registries, etc. then I did as you suggested and it fixed it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-11-02T08:53:05+00:00

    WARNING, this works but it's not the solution. MS and hardware manufacturers need to bang their heads. We cannot have a situation where we migrate a profile and render it useless because of some user account and hardware link. Think of all those AD migration projects that are happening right now!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-11-23T12:44:18+00:00

    I was able to fix this issue by disconnecting my Work account and then reconnecting it. I was receiving the exact same error message and I had tried clearing the TPM and other fixes to no avail.

    Below are the steps I used to remedy the issue:

    1. Navigate to the “Accounts” section of the Settings app and navigate to the “Access work or school” page. Click the account you want to unlink and press the “Disconnect” button. Follow the prompts to complete the account removal process.
    2. Navigate to the “Accounts” section of the Settings app and navigate back to the “Access work or school” page. Click the "+" icon to associate an account.
    3. Enter your credentials and wait for the process to complete.
    4. Launch Outlook and all should be functioning properly.

    This worked for me, after hours of searching and trying different methods

    Was this answer helpful?

    0 comments No comments