Solved - Outlook 365 Trusted Platform Module Error Code 80090016

 Download Now    Buy Now

When a window is unable to set up a pin, then it results in Error Code 80090016 or can give a message "something went wrong". This error usually happens due to the corruption of the NGC file folder which is located in the system. You may receive this error if you have replaced your system board. If your computer’s trusted platform module has malfunctioned. This can also be a reason to give an Error Code 80090016.

You should avoid using the same password for signing in to the system for a long time. You can use a pin instead of a password, as the pin is more secure than a password.

How Error code 80090016 looks like?


You can easily overcome these types of issues by performing a few simple steps. Before moving to the solutions, let’s know the reason behind the error code "Something went wrong."

Why Error Code 80090016 appear?

Corruption of NGC Folder

The Corrupted/Damaged data of the NGC folder will lead to an occurrence of error code 80090016 or "Something went wrong" statement.

Third-Party Application

This is another factor for the appearance of Error code 80090016. The backend process interferes with the request, due to which Windows is unable to set a PIN for the device.

Corrupt PST File

Sometimes an error code 80090016 or "Something went wrong" statement occurs when you are using corrupted PST files.

Different Solutions for Error Code 80090016 or "Something went wrong" Error

Solution 1: Delete the files of the NGC Folder

Damaged files of NGC folders are the most predictable cause of displaying the error. To deal with the error follow the below-described steps:

  • First of all, go to the Window Explorer and browse the directory- C:∖Windows∖ServiceProfiles∖LocalService∖AppData∖Local∖Microsoft∖
  • If you do not find the AppData folder, then click on the "File" and choose Change folder and search options to enable the hidden folder. Now, open the view tab and confirm the Show hidden Folders, Files, and drives option are picked. Click on the Apply option and hit the Ok button.
  • Next, right-click on the folder and click on the Properties option to take ownership of the NGC folder.

Note: Without taking ownership, users cannot open the NGC folder.

  • Now, move to the Security tab and tap on the Advanced option.
  • Then, tap on the Change option available in front of the Owner.
  • Now, enter the Username of your account that you are using right now.
  • Next, click on the Check names and hit on the Ok button.
  • Now, confirm that the "Replace owner on subcontainers and objects" box is picked.
  • Then, tap on Apply and hit the Ok button.
  • Open the NGC folder and delete all the data available in the folder.
  • Finally, try entering the PIN again.

Solution 2:

This method won’t affect the users who are subjected to MFA (Multi-Factor Authentication)

  • On the affected machine, you have to Navigate: C:∖users∖%username%∖AppData∖Local∖Packages∖Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
  • Now you have to rename that folder to Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy.old
  • After this, you can log out and use it again.

Also Read: How To Fix MS Outlook Error 0x800ccc92?

Solution 3:

  • On the affected machine you have to run Regedit and then Navigate to:
    HKEY_CURRENT_USER > Software > Microsoft > Office > 16.0 > Common > Identity
  • Now, you have to create a new DWORD entry
  • Name-EnableADAL
  • Enable-o(zero)

This helps to disable Modern authentication.

Method 4:- Repair Corrupt PST Files

Sometimes due to corrupted PST files, it leads to error code 80090016 or "Something went wrong" statement. So, to fix this error, repair your corrupt PST file using SysInfo PST Repair Tool.


Within the blog, I have concluded about the error code 80090016 or "Something went wrong" statement. This is generally caused due to a corrupted NGC folder, corrupted PST file, and usage of a third-party application. Also, I have mentioned various solutions to solve the problem of error code 80090016 in a step by step manner. Due to the usage of a corrupted PST file, it causes the error.

I hope you found a related solution to this error and resolve this issue.

  • At Service Since 2010
  • Trusted by Millions
  • SSL Secure
  • McAfee SECURE
  • DMCA Protection