Share via

Keyset does not exist - TPM

Anonymous
2020-04-24T15:16:13+00:00

Windows 10 Pro

Domain Joined

Microsoft 365 Business Standard - 32-bit

A user gets the following error when opening Office apps. 

We have tried: 

Clearing the TPM chip 

Uninstalling the TPM driver in device manager

Repairing Office 

Uninstalling/re-installing Office 

Adding the reg key from this thread - https://answers.microsoft.com/en-us/msoffice/forum/all/keyset-does-not-exist-outlook-throw-an-error-if-i/4205d705-10ca-4dbf-acca-a851c45bd212

Deleting this folder - AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

Office is completely unusable. 

We have tried disabling the TPM chip but we're now getting this error 

I suspect it's due to the fact we 'allowed my organisation to manage this device' but we are unable to disconnect it as the option is greyed out

What is the official solution for removing the TPM association and re-configuring for this user.

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

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

12 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-04-30T06:52:41+00:00

    Hello Dave,

    According to my experience, the issue should be related to MFA and disabling ADAL will not work. A new windows profile might be able to help.

    If the issue persists, I suggest you create add the following register key: [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]

    "DisableADALatopWAMOverride"=dword:1

    Regards,

    Rick

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-05-11T15:19:56+00:00

    If you were able to move the HDD to another machine without issues, then the TPM chip is not doing it's job. I thought that the TPM registration was there to preventidentity theft.

    Thanks for you input. Hopefully MS can shed some light

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-04-28T14:11:43+00:00

    Hi Rick,

    I don't think you are reading my posts or comments as I have already stated I have cleared the TPM chip.

    I will try and create a new Windows profile.

    Thanks

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-04-27T02:28:04+00:00

    Hello Dave,

    Thank you for letting me know what troubleshooting steps you have done.

    May I know the version of your Windows server? Based on what you have done, I suggest you can follow the instructions in this article to clear the TPM or Turn the TPM off to see if there is any difference.

    Note: The articles above apply to Windows server 2008.

    The error code 80090016 means TPM operation failed or was invalid. It is likely due to a bad sysprep image. Ensure the machine from which the sysprep image was created is not Azure AD joined, hybrid Azure AD joined, or Azure AD registered. For your reference: Troubleshooting hybrid Azure Active Directory joined devices

    Besides, please sign in Azure AD portal -> Device, check if the device has been registered here, remove it. Then test issue again.

    Regards,

    Rick

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-04-27T07:27:18+00:00

    May I know the version of your Windows server? - Windows 10 Pro (see my post)

    Based on what you have done, I suggest you can follow the instructions in this article to clear the TPM or Turn the TPM off to see if there is any difference - I have done both (see my post)

    Besides, please sign in Azure AD portal -> already removed the device and getting the same issue.

    How can I unlink the device from within Windows? 

    Edit: we did not deploy this image from Sysprep.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments