Windows 10 Pin Sign In
Pin login is a new way for Windows users to quickly log in their computers since Windows 8, and this method is widely recommended by Microsoft. Whereas, users are always meet with the problem that their pin login doesn’t work in Windows 10, how to fix this problem? Let’s take a look at this article and find the solution.
Part 1: How to Fix Windows 10 Cannot Add Pin Issue
- If you are unable to Sign-In to Windows using the PIN because of error messages, then click on the Sign-In Options link on the Windows log-in screen and select the option Microsoft Account Password to sign in to the system for further troubleshooting. You can remove the existing PIN and add a new PIN from inside the operating system.
- Sign in with last password used in your device' even though I am online. The device logins with my Microsoft Account Password but not with the PIN. I have tried everything, signing in, signing out, restarting, resetting my Microsoft Account on the device, deleting contents from the 'C: Windows ServiceProfiles LocalService AppData Local.
- If you are unable to Sign-In to Windows using the PIN because of error messages, then click on the Sign-In Options link on the Windows log-in screen and select the option Microsoft Account Password to sign in to the system for further troubleshooting. You can remove the existing PIN and add a new PIN from inside the operating system.
Signing in to your device with a four-digit PIN is the easiest way to unlock your Windows 10 device, rather than entering a big password every time you want to log in. But some Windows 10 users are facing a problem as they are unable to use this login feature. If you are facing the same problem, don’t worry.
In most of the case, users will meet this the pin login problem after update, even for users who can enter their computer that find it impossible to delete the new local pin account, unless they have already set it when their computer was Windows 8.
For those who cannot use pin login, it is generally because the IPsec Policy Agent service hasn’t been turned on. What we need to do is to set the service to automatically and manually open the resume. Firstly, enter your Windows 10 computer with an available account, and look the procedures as follow:
1. Enter “service” in the taskbar search box and open “View local services” in the search result;
2. Local the “IPsec Policy Agent” in the service and double-click to open its properties;
3. Set the service startup type to “Automatic” and click “OK” to save the settings.
4. Finally, manually open the service. And you can restart your Windows 10 computer and try it out to check the pin login service is normal or not.
Part 2: What to Do When Windows 10 Computer Cannot Normally Start
Whereas, exceptions are always exist. If you happened to forget the password and have no idea to start your Windows 10 computer, what can we do? Windows Password Key will help you out of trouble. It can help to recover or reset all user and administrator passwords, reset domain administrator password as well as reset passwords for movable devices.
Free DownloadBuy Now($19.95)1. Download the install Windows Password Key on an available computer, run the program and use it to burn a “Reset Disk”, it can be an empty DVD/CD or USB flash drive.
2. Insert the reset disk and restart your password-lost Windows 10 computer, press F2/F10/Delete key to enter the BIOS settings, choose the target device by changing the “Boot Menu”;
3. You will see the Windows Password Key program after seconds. And you can choose a password protected account to remove or change its password;
4. Click “Next” to confirm the operation, exit the program and restart your Windows 10 computer again.
5. Turn to the first part of this article and turn on the “IPsec Policy Agent” service.
After you read to this paragraph, you must have solved the Windows 10 pin login not available issue. Once you lost password for Windows 10/8.1/8/7/Vista/XP, you can also use the solution of part 2 to fix.
- Related Articles
- Top 3 Free Ways to Fix Windows 10 Update Error
- 3 Ways to Fix the Start Menu Stopped Working or Not Open in Windows 10
- Free Way to Recover Lost Data after Upgrade to Windows 10
Please enable JavaScript to view the comments powered by Disqus.comments powered by Disqus-->
Applies to
- Windows 10
When you set up Windows Hello in Windows 10, you may get an error during the Create a PIN step. This topic lists some of the error codes with recommendations for mitigating the problem. If you get an error code that is not listed here, contact Microsoft Support.
Where is the error code?
The following image shows an example of an error during Create a PIN.
Error mitigations
When a user encounters an error when creating the work PIN, advise the user to try the following steps. Many errors can be mitigated by one of these steps.
- Try to create the PIN again. Some errors are transient and resolve themselves.
- Sign out, sign in, and try to create the PIN again.
- Reboot the device and then try to create the PIN again.
- Unjoin the device from Azure Active Directory (Azure AD), rejoin, and then try to create the PIN again. To unjoin a desktop PC, go to Settings > System > About and select Disconnect from organization. To unjoin a device running Windows 10 Mobile, you must reset the device.
- On mobile devices, if you are unable to setup a PIN after multiple attempts, reset your device and start over. For help on how to reset your phone go to Reset my phone.If the error occurs again, check the error code against the following table to see if there is another mitigation for that error. When no mitigation is listed in the table, contact Microsoft Support for assistance.
| Hex | Cause | Mitigation |
|---|---|---|
| 0x80090005 | NTE_BAD_DATA | Unjoin the device from Azure AD and rejoin. |
| 0x8009000F | The container or key already exists. | Unjoin the device from Azure AD and rejoin. |
| 0x80090011 | The container or key was not found. | Unjoin the device from Azure AD and rejoin. |
| 0x80090029 | TPM is not set up. | Sign on with an administrator account. Click Start, type 'tpm.msc', and select tpm.msc Microsoft Common Console Document. In the Actions pane, select Prepare the TPM. |
| 0x8009002A | NTE_NO_MEMORY | Close programs which are taking up memory and try again. |
| 0x80090031 | NTE_AUTHENTICATION_IGNORED | Reboot the device. If the error occurs again after rebooting, reset the TPM or run Clear-TPM. |
| 0x80090035 | Policy requires TPM and the device does not have TPM. | Change the Windows Hello for Business policy to not require a TPM. |
| 0x80090036 | User canceled an interactive dialog. | User will be asked to try again. |
| 0x801C0003 | User is not authorized to enroll. | Check if the user has permission to perform the operation. |
| 0x801C000E | Registration quota reached. | Unjoin some other device that is currently joined using the same account or increase the maximum number of devices per user. |
| 0x801C000F | Operation successful, but the device requires a reboot. | Reboot the device. |
| 0x801C0010 | The AIK certificate is not valid or trusted. | Sign out and then sign in again. |
| 0x801C0011 | The attestation statement of the transport key is invalid. | Sign out and then sign in again. |
| 0x801C0012 | Discovery request is not in a valid format. | Sign out and then sign in again. |
| 0x801C0015 | The device is required to be joined to an Active Directory domain. | Join the device to an Active Directory domain. |
| 0x801C0016 | The federation provider configuration is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the file is not empty. |
| 0x801C0017 | The federation provider domain is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the FPDOMAINNAME element is not empty. |
| 0x801C0018 | The federation provider client configuration URL is empty | Go to http://clientconfig.microsoftonline-p.net/FPURL.xml and verify that the CLIENTCONFIG element contains a valid URL. |
| 0x801C03E9 | Server response message is invalid | Sign out and then sign in again. |
| 0x801C03EA | Server failed to authorize user or device. | Check if the token is valid and user has permission to register Windows Hello for Business keys. |
| 0x801C03EB | Server response http status is not valid | Sign out and then sign in again. |
| 0x801C03EC | Unhandled exception from server. | sign out and then sign in again. |
| 0x801C03ED | Multi-factor authentication is required for a 'ProvisionKey' operation, but was not performed. -or- Token was not found in the Authorization header. -or- Failed to read one or more objects. -or- The request sent to the server was invalid. | Sign out and then sign in again. If that doesn't resolve the issue, unjoin the device from Azure Active Directory (Azure AD) and rejoin. |
| 0x801C03EE | Attestation failed. | Sign out and then sign in again. |
| 0x801C03EF | The AIK certificate is no longer valid. | Sign out and then sign in again. |
| 0x801C03F2 | Windows Hello key registration failed. | ERROR_BAD_DIRECTORY_REQUEST. Another object with the same value for property proxyAddresses already exists. To resolve the issue, refer to Duplicate Attributes Prevent Dirsync. Also, if no sync conflict exists, please verify that the 'Mail/Email address' in AAD and the Primary SMTP address are the same in the proxy address. |
| 0x801C044D | Authorization token does not contain device ID. | Unjoin the device from Azure AD and rejoin. |
| Unable to obtain user token. | Sign out and then sign in again. Check network and credentials. | |
| 0x801C044E | Failed to receive user credentials input. | Sign out and then sign in again. |
Errors with unknown mitigation
Windows 10 Pin Login Error Password
For errors listed in this table, contact Microsoft Support for assistance.
| Hex | Cause |
|---|---|
| 0X80072F0C | Unknown |
| 0x80070057 | Invalid parameter or argument is passed. |
| 0x80090020 | NTE_FAIL |
| 0x80090027 | Caller provided a wrong parameter. If third-party code receives this error, they must change their code. |
| 0x8009002D | NTE_INTERNAL_ERROR |
| 0x801C0001 | ADRS server response is not in a valid format. |
| 0x801C0002 | Server failed to authenticate the user. |
| 0x801C0006 | Unhandled exception from server. |
| 0x801C000B | Redirection is needed and redirected location is not a well known server. |
| 0x801C000C | Discovery failed. |
| 0x801C0013 | Tenant ID is not found in the token. |
| 0x801C0014 | User SID is not found in the token. |
| 0x801C0019 | The federation provider client configuration is empty |
| 0x801C001A | The DRS endpoint in the federation provider client configuration is empty. |
| 0x801C001B | The device certificate is not found. |
| 0x801C03F0 | There is no key registered for the user. |
| 0x801C03F1 | There is no UPN in the token. |
| 0x801C044C | There is no core window for the current thread. |
| 0x801c004D | DSREG_NO_DEFAULT_ACCOUNT: NGC provisioning is unable to find the default WAM account to use to request AAD token for provisioning. Unable to enroll a device to use a PIN for login. |