First try to see if you can login to a different account. It could be that it is having trobule with that account.
Diagnostic Mode "Something happened and your PIN isn't available" Boot Loop - Cannot Login (SOLUTION)
Problems:
- At the Windows login screen the message "Something happened and your PIN isn't available. Click to setup your PIN again." appeared. Clicking this did nothing, it would just return me to the same login screen. There was no alternative option to Sign in with Password like there normally is. Effectively, login is impossible and the PC appeared bricked.
Process to get error:
- I went to msconfig (Win+R>msconfig) and selected Diagnostic Startup with all default settings. I immediately restarted my PC to find that I could not log in.
- (Unrelated?) I tried diagnostic startup b/c one of my mice started randomly highlighting stuff - as if Click Lock or sticky keys were on (all were off).
Research: I found reports of this back to 2018. I also ran into System Restore errors which I found instances of back to 2017. The dozens of other forums usually dead-ended or resulted in a "Refresh your PC" or "Do a clean install of Windows." Unacceptable! I was about to give up until I pieced this solution together.
Solution: Force boot mode back to Normal via command prompt and restart.
Skill level: Intermediate
Time estimate: 10 minutes
Solution notes:
- I did this with a bootable USB drive plugged in - I don't think that was necessary but try plugging one in if this fails without it.
- If you can successfully boot into safe mode with command prompt (option 5 from Startup Settings blue screen), then try Steps 14-17 below and see if it works. If it does, you're good to go. If not, go through all steps.
- Tested on Windows 10 and 11.
Steps:
- Get into Recovery Mode (blue screen): At the login screen, click the bottom-right corner Power Button. Then, before doing anything, hold down the Shift key. While holding Shift key down, click on Restart. This should reboot the computer and take you to the “Choose an Option” Recovery screen.
- If this doesn't work, see alternate later in post.
- If prompted, press F1 to enter Recovery Environment. If not, proceed to next step.
- Select Troubleshoot and/or Advanced Options until you get to a screen with a System Image Recovery option.
- Click System Image Recovery.
- Click Cancel on the "Re-image Your Computer" window.
- Ensure "Select a system image" is selected and click Next
- Click Advanced, then select Install a Driver and click OK. This gets you access to a Windows Explorer-type folder structure.
- Click This PC on the left side and find which drive has utilman.exe in the [drive letter]\Windows\System32 folder. The drive letter may not match your normal letters - this doesn't matter. Only one drive will have utilman.exe so you know you are in the correct one once you find it (my letters happened to match, except I had an X drive that wasn't useful).
- Rename Utilman to Utilman1. In this folder mode, you'll need to right-click and select Refresh to see the changes.
- Rename cmd to Utilman (refresh view to confirm both files are named properly).
- Close/cancel all of the open windows (close the Open window, click Cancel on the Add a Driver window, then close the last window)
- Click Continue from blue screen to reboot to your login screen.
- Click the Accessibility button on the login screen. A command prompt should open. (icon is a dashed clock at 3 o'clock for Win 10 or a person for Win 11)
- Type: "start msconfig" without quotes and press enter.
- The msconfig window should now appear. Select Normal Boot from the first tab and click Ok.
- Confirm restarting your system.
- At the next login screen, you should be able to enter your PIN and everything should be back to normal!!
- Now, you need to go back and rename Utilman to cmd and Utilman1 to Utilman (I had to follow steps 1-12 since Windows wouldn't let me edit the files while logged in). After re-completing step 12, you should be done.
Other useful info:
- The default command prompt directory should be C:\Windows\System32. If that's not what's displayed, type "cd /d c:" without the quotes and press enter. Then type "cd c:\windows\system32" without quotes and press enter.
- Step 1 Alternate: Shut down your PC. Once powered off, boot it back up, then as soon as you see the Windows loading dots or windows logo, hold down your power button 5-10 seconds to turn off your PC. Repeat this at least once until the Recovery menu appears (big blue screen).
Unsuccessful attempts before discovering solution:
- Restarting 5,000 times.
- Startup repair numerous times, with and without bootable USB (no repairs were found)
- Tried options 1, 2, 4, 5, and 6 from the Startup Settings blue screen (available by holding shift while selecting the power button and the restart button from the login screen)
- System Restore (failed because it failed to extract WindowsApps, error code 0x80070026) - this seems like a permissions error?
- I tried using using Safe Mode with Command Prompt and using takeown to get permission. Most operations listed as Success, but I received an error as the last output line from step 3 of thisArchived Forum I used. I tried Step 4 anyways but it didn't work.
- Booting from Windows usb (nothing worked except I could install a fresh version of Windows - no thanks)
- Booting into safe mode (same PIN error in all three modes - safe mode, SM with command prompt, and SM with networking). None of the modes looked different from the Diagnostic Mode except the command prompt option obviously displayed a command prompt.
Windows for home | Windows 10 | Windows Hello, lock screen and sign-in
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
327 answers
Sort by: Oldest
-
Anonymous
2022-05-17T12:06:16+00:00 -
Anonymous
2022-05-31T15:03:11+00:00 Thank you!!! Great write-up. Worked like a charm on my Windows 11 Lenovo laptop.
I can't believe Microsoft hasn't fixed this issue yet.
-
Anonymous
2022-06-07T17:18:06+00:00 Hey when you get this issue can tell me 3 things, because these 3 things can tell you if the solution I give will actually work.
- Have you signed into the account and always locked the account instead of signing out? in other words does the account profile disappear when you sign it out via task manger? If so make note of Microsoft account email and account name shown with the user account.
- Did it ever show you a screen with a message like "Your Credentials Could Not Be Verified"? in other words did it ever say something along the lines of your login cannot beconfirmed.
- Was the account having issues created with a Microsoft login, and if so is that Microsoft part of a family group?
If so create a Microsoft account user for a different Microsoft account in the family group, create it with admin rights. Login into the Microsoft account login user account that just made (set it up if needed). Restart the device. Then open settings go to Accounts. Go to Family and other users. Check under the Family section and check the Microsoft emails below the "Your Family" section but above the "Add a Member". Look for the Microsoft account email in that section and see if it says "Can't sign in". If it shows that for the Microsoft account email you took note of, then "Allow Sign In" and click the "Allow" button on the when you get a prompt. (If you get any UAC prompt's just click the "Yes" option on the UAC prompt, if it requires a pin/password enter an admin pin/password as needed.) After this sign out using ctrl alt delete. Look at the account list and see if the account name for the Microsoft user account that you took note of. Try to login into the account and it should work and let you sign into the account. Sorry if it is long but this is everything when I forgot to sign out and left it locked after disabling sign in.
-
Anonymous
2022-06-12T05:13:39+00:00 This really helped, thank you so much!
My only issue is that when I went to rename the files again Utilman was missing, so now I don't have a cmd... I'll live though.
-
Anonymous
2022-06-21T02:48:41+00:00 YOU SIR, ARE A HERO!!
Thanks so goddamn much I thought my PC was done for. Hallelujah brother, thanks thanks thanks!!