After windows 10 update today, one gets an error code 0x80090016 and can not use the computer and the other user does not get a code and all is working fine. Resources for IT Professionals Sign in. United States (English). When creating or changing the PIN for a user account on a Windows 10 computer, one of the errors 0x8009002d, 0x8007139f, 0x80090030, 0x80090032 or 0x80090016 may appear. Here are the full symptoms: If there is already a PIN configured, you may be able to sign-in using the PIN. When signing in using the PIN, errors “ The PIN is incorrect. The error code might change accordingly but you will get the text as keyset does not exist while trying to update the application pool identity with a custom account or while trying to specify a connect as user in the basic settings of a site. You might also get the below error codes 0x80090016 0x80090005. 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) &nb.
This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.
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 |
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'?
Microsoft Mail Error Code 0x80090016
Cause:
Looks like the keys themselves were in corrupted state.
Recommendation:
To fix this issue follow the below steps:
Microsoft Error Code 0x80090016
- 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'
- Run the commands in below folders:
C:WindowsMicrosoft.NETFramework64v2.0.50727
C:WindowsMicrosoft.NETFramework64v4.0.30319
C:WindowsMicrosoft.NETFrameworkv2.0.50727
C:WindowsMicrosoft.NETFrameworkv4.0.30319
- 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):
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
- Now, regenerate the machine key providers once again using the command “exe /install SharedLibraries”.
Resolution Steps:
Something Went Wrong 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