Something happened and your PIN isn’t available [SOLVED]

Ivan Jenic
by Ivan Jenic
Troubleshooting Expert
Last update:
Affiliate Disclosure

  • Windows 10 has brought many improvements including improved security via PIN and face recognition.
  • PIN is stored locally and is tied to a TPM chip, changes to the chip will result in the PIN not recognized.
  • Check out the Windows Hello section for more great articles with guides and recommendations.
  • If you want to solve any Windows issues, check out the Windows 10 Errors Troubleshooting Hub.
fix PIN not available windows 10
To fix various PC problems, we recommend Restoro PC Repair Tool: This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:
  1. Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
  2. Click Start Scan to find Windows issues that could be causing PC problems.
  3. Click Repair All to fix issues affecting your computer's security and performance
  • Restoro has been downloaded by 0 readers this month.

7. Change your account password

  1. Go to Settings > Accounts.
  2. From the left menu, select Sign-in options.
  3. Then go to Password section and select Change.
  4. Change your account password.
  5. Then go to the PIN section in Sign-in options and choose I forgot my PIN or add a PIN number if you don’t have one already.

Note: Remember, after changing your account password, you’ll have to use the new password for all your Microsoft services.


8. Create a new Administrator account

  1. Open the Settings and go to the Accounts section.
  2. Select Family & other people from the menu on the left. In the right pane.
  3. Click on Add someone else to this PC.
  4. Select I don’t have this person’s sign-in information.
    Windows 10 won't let me add a PIN
  5. Now click on Add a user without a Microsoft account.
    Windows 10 sign in options not showing
  6. Enter the desired account name and click Next.

Note: If PIN sign-in isn’t available for your account, you might be able to fix the problem by creating a new administrator account. 

After creating a new administrator account, switch to it and set a PIN for it. We showed you how to set up a PIN code in one of our previous solutions, so be sure to check it out for detailed instructions.

Once you set the PIN code for the new account, try accessing your old account to see if the PIN code works. According to users, after setting a new administrator account the issue was completely resolved, so feel free to try this solution.


9. Modify your registry

  1. Press Windows Key + R and enter regedit, then press Enter or click OK.
    PIN sign in Windows 10 greyed out
  2. In the left panel, navigate to
    ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAuthenticationLogonUITestHooks

     

  3. Now locate Threshold DWORD and double click it.
  4. If it’s not available, you can create it by right-clicking the right panel and choosing New > DWORD (32-bit) Value.
  5. Now enter Threshold as the name of the new DWORD.
  6. Change the Value data of the Threshold DWORD to 0 and click on OK to save changes.
  7. After making these changes, you just need to delete all files from the following directory:
C:WindowsServiceProfilesLocalServiceAppDataLocalMicrosoftNGC

Note: This might be a slightly advanced solution, but several users reported that it worked for them, so feel free to try it out. If you can’t edit your Windows 10’s registry, read this handy guide and find the quickest solutions to the issue.


10. Check if CNG Key Isolation service (KeyIso) is running

  1. Press Windows Key + R and enter services.msc, then press Enter or click OK.
    Windows 10 won't let me add a PIN
  2. When Services window opens, locate CNG Key Isolation service and double click it.
  3. When the Properties window opens, change the Startup type to Manual
  4. Check if the service is running. If not, click the Start button to start it.PIN sign in Windows 10 greyed out 
  5. Now click Apply and OK to save changes.

Note: According to users, sometimes PIN sign in can become unavailable if CNG Key Isolation Service (KeyIso) service is disabled. Windows relies on this service for PIN sign in, and if this service isn’t running, you’ll experience problems with PIN login.


All of the above solutions should help you solve all of the common PIN login issues you might face. You should now be able to login with a PIN.

If you have any other questions or suggestions, don’t hesitate to leave them in the comments section below and we’ll be sure to check them out.

Frequently Asked Questions

Leave a comment below!
18 comments

add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

I CANNOT LOG IN TO MY ACCOUNT YET I AM NOT LOCK OUT. IT’S ASKING ME TO ENTER AN SMS CODE FROM A PHONE NUMBER THAT I DON’T HAVE ANYMORE. MY LAPTOP IS NOT DELL.

IS THERE ANY OTHER WAY TO LOG IN, LIKE A COMMAND LINE OPTION?

I fogot my pin. After trying a few times, i now have to enter a “challenge phrase”. Takes me back to pin entry screen. No log in option is available, or any other option. If i do try the pin, and fail, i have to reboot and start again. Wtf

Hello, Edgar I am trying to back up my windows 10 to Windows 7 and then reverse it back to make it run more efficiently

Hello!

Thank you for this information! We hope that other users will see this comment and it will help them. We will also give this information to our authors.

Cheers!

Tried all no luck and yeah I don’t have the AppData folder either. Was actually starting to like Win10 too. Knew Microsoft couldn’t leave well enough alone

After I go to C:Windows then ServiceProfiles then LocalService there is no file or folder called AppData. What should I do?

In File Explorer select the view tab and click on ‘hidden items’, then you can see AppData.

Good info, no PIN option even visible on my machine. Turned out to be because I was accessing the system remotely via RDP. Logging in locally fixed this. Probably by design.