Windows Hello is an authentication process for Windows 10 that integrates biometric authentication like face recognition, fingerprint scanning etc. Just like any other biometric authentication process, Windows Hello also calls for providing a PIN that is used in case any of the biometric authentication set fails. If such issue occurs, then the user can use the PIN to sign in to their Windows 10 device. However, in some versions of Windows 10, the process of generating PIN for Windows Hello meets with several errors. This error is described by certain error codes. Not everyone will face similar issues, but if anyone does, he/she can refer to the error codes to find out the pertaining issue.
You will get an error message something like this: “Something went wrong, and we couldn’t set up your PIN, Error 0x80070032”.
There are different types of errors and all these errors have various troubleshoot processes.
Below are the complete list of Windows Hello PIN generation error codes.
Error Codes Solvable By Sign Out and Sign In Again
There are certain codes which can be solved by the simple process of Sign Out and Sign In once again. These are as follows:
- 0x801C044E: When the device has failed to receive user credential input
- 0x801C03EF: Invalid AIK certificate
- 0x801C03EE: Attestation failed
- 0x801C03EC: Unhandled exception from server
- 0x801C03EB: Invalid server response HTTP status
- 0x801C03E9: Invalid server response message
- 0x801C0010: When the AIK certificate is not valid or trusted
- 0x801C0011: The attestation statement of the transport key is invalid
- 0x801C0012: Incorrect discovery request
TPM Issues on Windows Hello PIN Generation Error
0x80090029: The error occurs when the TPM Setup is not complete on the machine. The step to solve this issue is very simple. All you need to do is
Sign in to your Windows 10 device with admin account., open Microsoft Common COnsole Document, and prepare the TPM.
Here, there are two plausible errors:
0x80090031: The error displays “NTE_AUTHENTICATION_IGNORED.” The solution is quite simple. Restart the machine, reset the TPM or run Clear TPM.
0x80090035: If any business organization makes TPM mandatory, and the device doesn’t have a TPM, then this error can occur. The solution in that case it to remove the restriction of TPM and join AD.
Unjoin the Windows 10 Device From Azure AD and then Rejoin It
When any error associated with Active Directory occurs, then the best solution is to unjoin the machine and rejoin it. The process is quite simple. All you need to do is go to Settings, then go to System, select About and Disconnect from the organization. The errors are 0x801C03ED, 0x801C03EA, 0x801C0015, 0x801C000E, 0x80090005,0x80090011, 0x8009000F,0x801C044D, etc.
Configuration Issues During Windows Hello PIN Generation
Configuration issues can arise when the federation provider domain or configuration is empty. You have to check if the client configuration element is valid of not. The errors for this issue are 0x801C0016, 0x801C0017 and 0x801C0018.
Errors For Which Microsoft Support Is The Only Solution
There are certain errors, returned during Windows Hello PIN generation issue, which can be only solved by Microsoft support team. These are:
- 0x80072f0c: Unknown error
- 0x80070057: Invalid parameter or argument
- 0x80090027: Caller provided the wrong parameter.
- 0x8009002D: NTE_INTERNAL_ERROR
- 0x80090020: NTE_FAIL
- 0x801C0001: Invalid ADRS server response
- 0x801C0002: Server failed to authenticate the user
- 0x801C0006: Unhandled exception from server
- 0x801C000C: Discovery failed
Some other types of errors may pop up due to memory shortage, unauthorized user access, user token access, etc. Hope this article has helped you!