Error Code 80090016

Error Code 80090016

Error Code 80090016 occurs when Windows is unable to create a PIN, and a notice reading “something went wrong” may also be displayed. There is likely corruption in the folder containing NGC files on your machine, which is causing this problem.

If you have just replaced your system board, you may be met with this problem. Your computer’s trusted platform module may be broken. An Error Code 80090016 could also be displayed for this reason.

Do not log in to the system with the same password for an extended period of time. Your PIN is more secure than your password, so you can use it instead.

Error Code 80090016

What does the Error Code 80090016 Mean When an Error Occurs?

In most cases, the solution to such problems is as easy as taking a few precautions. We need to understand the root cause of the error message before we can move on to potential fixes. There was an error.

What Causes Error Code 80090016?

A Broken NGC Folder

Error Code 80090016, often known as the “Something went wrong” message, is caused by corrupted or damaged data in the NGC folder.

An External Program

Error Code 80090016 occurs for multiple reasons, and this is one of them. Windows is unable to configure a PIN because of an issue with the backend procedure.

PST File Is Corrupt

Corrupted PST files can lead to the occurrence of Error Code 80090016 or the “Something went wrong” message.

Alternatives to the “Something went wrong” or “Error Code 80090016” Initial Troubleshooting Step

Method 1. A Common Reason of this Problem is Corrupted NGC Folder Files.

Here are the actions to take to fix the problem:

  • To begin, open Window Explorer and navigate to
  • C:WindowsServiceProfilesLocalServiceAppDataLocalMicrosoft.
  • Click “File” and select “Change folder and search options” if you are unable to locate the AppData folder. Click the View menu’s Tab and check that the option to “Show hidden Folders, Files, and drives” is selected. Then, choose the checkbox next to Apply and click Ok.
  • Take ownership of the NGC folder by right-clicking on it and selecting the Properties menu item.
  • Go ahead and click the Security tab’s Advanced button now.
  • Choose the Owner option, and then select Change.
  • Please enter the current Username you are logged into.
  • Then, select Check names and press the Ok button.
  • Please double-check that the option to “Replace owner on subcontainers and objects” is selected.
  • Follow it with an Ok or Apply tap.
  • Simply erase anything in the NGC folder by opening it.
  • After that, you can try reentering the PIN once more.

Method 2. Multi-Factor Authentication

Users required to use MFA won’t be impacted by this approach (Multi-Factor Authentication)

  • To fix the afflicted computer, go to:
  • C:∖users∖%username%∖AppData∖Local∖Packages∖AAD.BrokerPlugin cw5n1h2txyewy
  • The folder must now be renamed to Microsoft.AAD.BrokerPlugin cw5n1h2txyewy.old.

Now that you’ve finished, you can log out and return later.

Method 3. Regedit on the Compromised Computer

  • Starting Regedit on the compromised computer is the first step in fixing the issue. HKEY CURRENT USER > Program Files (x86) > Microsoft > Office > 16.0 > Common > Identity
  • Currently, you must make a new DWORD entry called “Name-EnableADAL Enable-o” (zero)
  • If you do this, Modern authentication will be disabled.

Method 4. Restoring Damaged PST Files

Error Code 80090016, often known as the “Something went wrong” message, can be caused by a damaged PST file. So, to fix this error, repair your corrupt PST file using SysInfo PST Repair Tool.

Conclusion

Within the blog, I have concluded on the Error Code 80090016 or “Something went wrong” remark. In most cases, this happens when the NGC folder, the PST file, or both become damaged or corrupted while being utilised in conjunction with a third-party programme.

Also, I have mentioned numerous strategies to address the problem of Error Code 80090016 in a step by step manner. Due to the usage of a corrupted PST file, it creates the error.

My best wishes are with you while you seek a resolution to this error.