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 this<a href="https://social.technet.microsoft.com/Forums/lync/en-US/3ca0980f-a345-453f-b3e4-5bcf82a5f5c7/system-restore-not-working-in-windows-10-system-restore-failed-source-appxstaging-error?forum=win10itproapps" title="https://social.technet.microsoft.com/Forums/lync/en-US/3ca0980f-a345-453f-b3e4-5bcf82a5f5c7/system-restore-not-working-in-windows-10-system-restore-failed-source-appxstaging-error?forum=win10itproapps" rel="ugc nofollow">Archived 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.

not_a_bot1001, you are sincerely amazing. I cannot thank you enough for this writeup! Fellow weeb Dad and I were chatting about some ways to figure out what might be causing some Win10 slowness that's crept up and he casually suggested "Boot in diagnostic to get rid of all the background noise and see if it's quicker". So, I think--sure thing, sounds simple enough. And well, as we all know... the rest is history :) Happy Holidays, Merry Thanksgiving, and all that jazz! Hope you have a nice, bug & infinite-loop-free December!

Couldn't find the utilman.exe, any help?

Here are some things to check. =>The file may not have the extension and show up as "Utilman" instead of "Utilman.exe". =>You don't give much info about how far you got with the process. If you have gotten to the System32 folder, the Utilman file should be there. =>You have to scroll way, way down, past all the folders into the (alphabetical) list of files. Then keep scrolling until you see files starting with "U". Look closely. I had trouble finding it the first time. =>Also make sure you have gotten to the right Explorer/Windows/System32 folder from the System Image Recovery button (on the blue system repair window). =>Do you feel comfortable that you have followed the instructions or is there some confusion? More detail could help. Are you running Windows 10 or Windows 11? Let us know if this helps or send details and I will try to respond again. The WizardGrimm

This solution worked for me, and I want to thank you from the bottom of my heart. Fyi, because of my situation I was unable to get a Windows-style File window to perform my name changes. I required to use a Command Line console window. Because of this, the file name changes you mention required the file suffixes (.exe), and I had to brush up on my DOS commands (like ren) and syntax, which people can easily look up. Also of note was that I booted from a thumb drive, which was my X: drive, so I had to use the cd command to get into my C: drive and the c:/Windows/System32 path. Thank you again.

Maam, Sir--whoever you are--you are a genius. I spent an hour and a half scouring the internet trying to resolve this issue. And believe you me, I was doubtful this would work. It was about the 10th hack I'd tried. However, as they say, 10 times the charm. Thank you, thank you, thank you. I was honestly contemplating a factory reset.

Diagnostic Mode "Something happened and your PIN isn't available" Boot Loop - Cannot Login (SOLUTION)

Anonymous

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.

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.

0 comments

327 answers

Anonymous

2021-12-11T00:02:25+00:00

not_a_bot1001, you are sincerely amazing. I cannot thank you enough for this writeup!

Fellow weeb Dad and I were chatting about some ways to figure out what might be causing some Win10 slowness that's crept up and he casually suggested "Boot in diagnostic to get rid of all the background noise and see if it's quicker". So, I think--sure thing, sounds simple enough. And well, as we all know... the rest is history :)

Happy Holidays, Merry Thanksgiving, and all that jazz! Hope you have a nice, bug & infinite-loop-free December!
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-18T14:29:51+00:00

Couldn't find the utilman.exe, any help?
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-18T18:50:41+00:00

Here are some things to check.

=>The file may not have the extension and show up as "Utilman" instead of "Utilman.exe".

=>You don't give much info about how far you got with the process. If you have gotten to the System32 folder, the Utilman file should be there.

=>You have to scroll way, way down, past all the folders into the (alphabetical) list of files. Then keep scrolling until you see files starting with "U". Look closely. I had trouble finding it the first time.

=>Also make sure you have gotten to the right Explorer/Windows/System32 folder from the System Image Recovery button (on the blue system repair window).

=>Do you feel comfortable that you have followed the instructions or is there some confusion? More detail could help. Are you running Windows 10 or Windows 11?

Let us know if this helps or send details and I will try to respond again.

The WizardGrimm
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-12-26T21:03:24+00:00

This solution worked for me, and I want to thank you from the bottom of my heart. Fyi, because of my situation I was unable to get a Windows-style File window to perform my name changes. I required to use a Command Line console window. Because of this, the file name changes you mention required the file suffixes (.exe), and I had to brush up on my DOS commands (like ren) and syntax, which people can easily look up. Also of note was that I booted from a thumb drive, which was my X: drive, so I had to use the cd command to get into my C: drive and the c:/Windows/System32 path. Thank you again.
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-29T19:01:19+00:00

Maam, Sir--whoever you are--you are a genius. I spent an hour and a half scouring the internet trying to resolve this issue. And believe you me, I was doubtful this would work. It was about the 10th hack I'd tried. However, as they say, 10 times the charm. Thank you, thank you, thank you. I was honestly contemplating a factory reset.
Was this answer helpful?

0 comments No comments