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.

Thank you, Thank you, Thank you. You saved me. How did Microsoft didn't fix this by now???

just an update on Windows Security & PIN setup issue - after a few weeks of searching my system I, for no real reason, clicked to open credential mgr. and it didnt open. I checked and the service was stopped, and further inspection (properties) showed startup was somehow disabled. Changed to automatic and restarted service and voila! I was able to setup my Windows Hello PIN and that pesky little red X over windows security icon (system tray and in settings) was gone and I was able to now access all of the apps that required authentication with my PIN that wouldn't work since the diagnostic mode disaster. If you followed the steps listed and were successful wonderful, but if you now have any issues with Win. Security or Hello PIN take a look if credential mgr is running.

This worked brilliantly though I made a few minor modifications to your steps on my PC running Windows 11: I have 6 drives on my PC and was having trouble finding utilman.exe despite having found the windows\system32 folder. Turns out that the file type it's looking for by default are setup files. In the box with the file name, simply type "utilman*.exe" and you'll find it. I had to do the same to find cmd.exe. To rename utilman.exe back to cmd.exe, and utilman1.exe back to utilman.exe, I took a different route. Rather than run through all 12 steps again, I simply ran the command line from recovery mode. I was then able to navigate to the right folder and rename the files. In this mode the files weren't in use as they are when the Windows GUI is running, so it was easy.

I was in the same boat. I found a workaround for renaming the files, and I posted the details below. I was completely bricked, and this got me back to normal without losing anything.

This solution really pointed me in the right direction, but I could not complete step 8. When I followed the directions after clicking "Install a driver", I went to my boot drive c:\windows\system32 and only folders and one file showed up. I knew there were many files, but since I couldn't see utilman.exe, I had to find another way to rename it. So, I got back to the blue screen, selected Troubleshoot -> Advanced Options -> Cmd Prompt In the Cmd window, I typed "cd d/ c:\windows\system32" (no quotes). The prompt changed to c:\windows\system 32 At that prompt, I typed "rename utilman.exe utilman1.exe" Pressing ENTER went back to c:\windows\system32. The file name had been changed. When the prompt returned, I typed "rename cmd.exe utilman.exe" Pressing ENTER went back to c:\windows\system32 prompt. The filename had been changed. I typed EXIT to close the Cmd window, and restarted the computer. After it showed the startup screen, I followed step #13 above to get into msconfig and change it to "normal startup" Next problem: When I went to rename cmd.exe and utilman.exe in Windows Explorer, it said I did not have permission. So, I restarted and got back to the blue screen by holding Shift while restarting. I went to Troubleshoot->Advanced Options -> Cmd Prompt again and renamed the files like the first time: "cd d/ c:\windows\system32" "rename utilman.exe cmd.exe" "rename utilman1.exe utilman.exe" "exit" Restarted the computer, and everything was back to normal. I don't know why I couldn't rename the files with the method in the original post, but I simply could not see utilman.exe even though I was in \windows\system32. But this workaround did it for me. Hope it helps someone.

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

2023-07-27T12:49:53+00:00

Thank you, Thank you, Thank you.

You saved me.

How did Microsoft didn't fix this by now???
Was this answer helpful?

0 comments No comments
Anonymous

2023-07-20T10:21:00+00:00

just an update on Windows Security & PIN setup issue - after a few weeks of searching my system I, for no real reason, clicked to open credential mgr. and it didnt open. I checked and the service was stopped, and further inspection (properties) showed startup was somehow disabled. Changed to automatic and restarted service and voila! I was able to setup my Windows Hello PIN and that pesky little red X over windows security icon (system tray and in settings) was gone and I was able to now access all of the apps that required authentication with my PIN that wouldn't work since the diagnostic mode disaster.

If you followed the steps listed and were successful wonderful, but if you now have any issues with Win. Security or Hello PIN take a look if credential mgr is running.
Was this answer helpful?

0 comments No comments
Anonymous

2023-07-20T08:55:05+00:00
This worked brilliantly though I made a few minor modifications to your steps on my PC running Windows 11:
1. I have 6 drives on my PC and was having trouble finding utilman.exe despite having found the windows\system32 folder. Turns out that the file type it's looking for by default are setup files. In the box with the file name, simply type "utilman*.exe" and you'll find it. I had to do the same to find cmd.exe.
2. To rename utilman.exe back to cmd.exe, and utilman1.exe back to utilman.exe, I took a different route. Rather than run through all 12 steps again, I simply ran the command line from recovery mode. I was then able to navigate to the right folder and rename the files. In this mode the files weren't in use as they are when the Windows GUI is running, so it was easy.
Was this answer helpful?

0 comments No comments
Anonymous

2023-07-14T19:29:33+00:00

I was in the same boat. I found a workaround for renaming the files, and I posted the details below. I was completely bricked, and this got me back to normal without losing anything.
Was this answer helpful?

0 comments No comments
Anonymous

2023-07-14T19:25:58+00:00

This solution really pointed me in the right direction, but I could not complete step 8. When I followed the directions after clicking "Install a driver", I went to my boot drive c:\windows\system32 and only folders and one file showed up. I knew there were many files, but since I couldn't see utilman.exe, I had to find another way to rename it. So, I got back to the blue screen, selected Troubleshoot -> Advanced Options -> Cmd Prompt

In the Cmd window, I typed "cd d/ c:\windows\system32" (no quotes). The prompt changed to c:\windows\system 32

At that prompt, I typed "rename utilman.exe utilman1.exe" Pressing ENTER went back to c:\windows\system32. The file name had been changed.

When the prompt returned, I typed "rename cmd.exe utilman.exe" Pressing ENTER went back to c:\windows\system32 prompt. The filename had been changed.

I typed EXIT to close the Cmd window, and restarted the computer.

After it showed the startup screen, I followed step #13 above to get into msconfig and change it to "normal startup"

Next problem: When I went to rename cmd.exe and utilman.exe in Windows Explorer, it said I did not have permission.

So, I restarted and got back to the blue screen by holding Shift while restarting.

I went to Troubleshoot->Advanced Options -> Cmd Prompt again and renamed the files like the first time:

"cd d/ c:\windows\system32"

"rename utilman.exe cmd.exe"

"rename utilman1.exe utilman.exe"

"exit"

Restarted the computer, and everything was back to normal. I don't know why I couldn't rename the files with the method in the original post, but I simply could not see utilman.exe even though I was in \windows\system32. But this workaround did it for me. Hope it helps someone.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments