Microsoft Error Code 0x80090016

1/6/2022by admin
What does 0x80090016 mean
  • Error code 0x80090016 I've gotten this problem since i had my computer in for repair. I get the error when attempting to log in with pin, attempting to enter X-box live, trying to play Sea of Thieves and at some other occasions.
  • Original product version: Windows Server 2008, Windows Server 2008 R2 Original KB number: 977754. Consider the following scenario: On a server that is running Windows Server 2008 or Windows Server 2008 R2, you enable remote management for IIS. The server has more than one application pool configured in IIS.


From some of the newsgroup postings that we found, this error seems to be related to lack of proper rights or file corruption.
If this error occurs in conjunction with an IIS-based website, see this information from ASPFAQ.COM:
'This error is usually due to permissions problems or, in rare instances, corruption of the metabase. Here are some possible solutions:
- Try removing / re-creating the affected web site(s) / application(s) if your application is running in an isolated process
- Try disabling this feature also try running the application 'out of process'
- Try adding IWAM_MachineName to the web site operators, and giving this account full permissions (using regedt32.exe) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftCryptographyMachineKeysMS IIS DCOM Client. Open regedit.exe, navigate to:
...and delete the subkey 'MS IIS DCOM Client', then open the MMC console for IIS (which will re-create the subkey)
If all else fails, try reinstalling IIS - this will rebuild your metabase, but will require you to configure your web site(s) from scratch
* * *
This error seems to affect many users of asp pages with CDONTS. Here are some suggestions for them:
From a newsgroup post: After backing up the key (select the registry key and save it), remove HKCUsoftwareMicrosoftcryptographyuserkeysMS_IIS_DCOM_CLIENT.
From a newsgroup post: To fix this, I had to click the properties of the site, go to home dir, click REMOVE in the configuration section and re-created it.
From a newsgroup post: The problem is that access to the IIS Admin Objects is made in the context of the process token. For Out of Process IIS applications that process is token is for the IWAM_machinename account. By default, the IWAM_machinename account is not a web site operator and does not have permissions to certain registry keys required for access to the IIS Admin Objects.
You can get around this problem by adding the IWAM_machinename account to
the web site operators and then you must also give the account full permissions
to the HKEY_LOCAL_MACHINESOFTWAREMicrosoftCryptographyMachineKeysMS IIS
DCOM Client registry key. Permissions cannot be set with REGEDIT.EXE. You should use REGEDT32.EXE instead. You may not want to give the IWAM_machinename account these sorts of permissions to your metabase for security reasons. You can accomplish the same results by configuring the MTS package for your Out of Process application to run as a different user than the IWAM_machinename account. You would then need to give this different user the permissions mentioned above.

This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.

The error message ‘ Something went wrong ’ along with the error code 0x80090016 appears when Windows is unable to set up a PIN for your device. This is usually due to the corruption of the Ngc folder which is located in the system volume.

Continuous exceptions ‘Keyset does not exist’ (Exception from HRESULT: 0x80090016) or (Exception from HRESULT: 0x80090005) followed by (Value does not fall within the expected range 0x80070005)

Sometimes we get the below error while committing the application pool identity changes to a domain account in the application pool.

Error Code description:

Error Code Symbolic Name Error Description Header
Hex Dec
0x80090016 -2146893802 NTE_BAD_KEYSET Keyset does not exist winerror.h

Microsoft Mail Error Code 0x80090016

Basically, the machine key providers were corrupted because of which IIS was not able to decrypt the password set for Application pool. Due to this AppPool was throwing the above-mentioned error.

As a workaround we can follow the below article to fix the error by regenerating the machine keys:

But what should I do if I get the below error pop up which fails with “0x80070005” while regenerating the machine key providers using the command 'iissetup.exe /install SharedLibraries'?


Looks like the keys themselves were in corrupted state.


To fix this issue follow the below steps:

  1. Export the keys from a working server of same version using the below commands:

aspnet_regiis.exe -pri -px 'iisConfigurationKey' 'c:iisconfigkey.xml'
aspnet_regiis.exe -pri -px 'NetFrameworkConfigurationKey' 'c:netframework.xml'
aspnet_regiis.exe -pri -px 'iisWasKey' 'c:iiswas.xml'

  1. Run the commands in below folders:
Error code 80090016 trusted platform module


Microsoft Error Code 0x80090016

  1. Once the keys were exported, move them to non-working server and import them using the below commands (we should run these in all the 4 folders mentioned above):
Microsoft Error Code 0x80090016

Something Went Wrong 0x80090016

Microsoft mail error code 0x80090016

aspnet_regiis.exe -pi 'iisConfigurationKey' 'c:iisconfigkey.xml' -exp
aspnet_regiis.exe -pi 'NetFrameworkConfigurationKey' 'c:netframework.xml' -exp
aspnet_regiis.exe -pi 'iisWasKey' 'c:iiswas.xml' -exp

  1. Now, regenerate the machine key providers once again using the command “exe /install SharedLibraries”.

Microsoft Account Error Code 0x80090016

Resolution Steps:

Windows 10 Error Code 0x80090016

- Take the back up of machine key folder
- Run the above mentioned scripts
- Take the backup of applicationHost.config file and remove the <providers> section under <configProtectedData>
- Run the command '%windir%system32inetsrviissetup.exe /install SharedLibraries'
- Now, try to change the credentials for application pool identity

Comments are closed.