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

Anonymous
2021-06-29T20:44:40+00:00

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:

  1. 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.
  2. If prompted, press F1 to enter Recovery Environment. If not, proceed to next step.
  3. Select Troubleshoot and/or Advanced Options until you get to a screen with a System Image Recovery option.
  4. Click System Image Recovery.
  5. Click Cancel on the "Re-image Your Computer" window.
  6. Ensure "Select a system image" is selected and click Next
  7. Click Advanced, then select Install a Driver and click OK. This gets you access to a Windows Explorer-type folder structure.
  8. 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).
  9. Rename Utilman to Utilman1. In this folder mode, you'll need to right-click and select Refresh to see the changes.
  10. Rename cmd to Utilman (refresh view to confirm both files are named properly).
  11. Close/cancel all of the open windows (close the Open window, click Cancel on the Add a Driver window, then close the last window)
  12. Click Continue from blue screen to reboot to your login screen.
  13. 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)
  14. Type: "start msconfig" without quotes and press enter.
  15. The msconfig window should now appear. Select Normal Boot from the first tab and click Ok.
  16. Confirm restarting your system.
  17. At the next login screen, you should be able to enter your PIN and everything should be back to normal!!
  18. 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.

0 comments

327 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-05-28T16:54:00+00:00

    Hello, I just want to provide an important note for Windows 11 users in 2024. Using System Image Recovery from Step 4 does not let you see file extensions nor does it allow you to see all file types. Therefore, this method is not working. However, there is a workaround for Windows 11 users. You can use the command prompt directly in the recovery mode, and rename the file using commands. This can be done twice to ensure you don't get problems with cmd disappearing as some users have noted. Therefore, the below updated guide should work for all Windows 11 users in 2024:

    1-3: Get into recovery mode per the original guide. Once in recovery mode, locate Command Prompt as below:

    1. Trouble Shoot, Advanced Options, select Command Prompt
      4a. If you have bitlocker, enter your bitlocker recovery seed when prompted for the drive that houses Windows
    2. When command prompt is open, type:

    *c:*

    Press enter

    Type again
    rename c:\windows\system32\utilman.exe utilman1.exe
    Press enter

    Type again
    rename c:\windows\system32\cmd.exe utilman.exe

    Press enter

    Type again

    exit

    1. Restart your computer
    2. On the windows sign-in screen, click on the accessibility icon
    3. command prompt opens. Type:
      start msconfig

    Press enter

    1. The msconfig window should now appear. Select Normal Boot from the first tab and click Ok.
    2. Confirm restarting your system
    3. Confirm after restart that your pin can be typed, but DO NOT TYPE IT YET
    4. Restart your system
    5. Boot back into recovery mode
    6. Go again to Trouble Shoot, Advanced Options, select Command Prompt

    14a. Enter your bitlocker recovery seed again if prompted for the drive that houses Windows

    1. When command prompt is open, type:

    *c:*

    Press enter

    Type again
    rename c:\windows\system32\utilman.exe cmd.exe
    Press enter

    Type again
    rename c:\windows\system32\utilman1.exe utilman.exe

    Press enter

    Type again

    exit

    1. Restart your computer, you can login like normal, utilman works like normal, and command prompt works like normal. Good luck and thanks to the original poster for the write-up! You helped me a ton!!!

    **Note on bitlocker:**Pay attention when you are prompted to enter your recovery key/seed. Bitlocker tells you which drive it is for. You only need to enter the recovery key for the drive that houses windows. My first option was enter the recovery key for Windows. After clicking enter, bitlocker will prompt you again to enter the seed for the next drive that it protects. If it isn't your windows drive, simply click "skip" in the bottom right. We only need to unlock the windows c:\ drive so that we can execute the commands in command prompt.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-05-29T16:28:09+00:00

    SOLVED!! Perfect writeup. If ever in Utah I will buy you lunch or dinner. YOUR AWESOME. FIXED

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-06-02T12:34:51+00:00

    Sir you were a damn genius. No the only way to say it is you are a one-of-a-kind God damn genius holy **** I have tried forever to fix this problem I have tried everything went to every website talk to support so many times not one of them had a thing that could help me not one of them, Dell themselves didn't have a way to fix it Microsoft people Microsoft did not have a way to fix this nobody had a way to fix this. But you sir you are a God among men. I don't know who you are I may never meet you but know this I owe a lot to you. The frustration that I went through the absolute hair pulling feet stomping eyeball popping out of my head frustration hundreds of times I tried to fix this but you sir you fixed it your instructions were spot on they were easy to read easy to follow and it fixed the problem when I was able to log in with my PIN I screamed as loud as I could I was so happy, sir may your life forever be blessed.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-06-04T19:55:40+00:00

    So great, thank you so much. Although I ran into some trouble. My cmd file is back with a black icon C:/ but utilman is nowhere to be found following the first path or your command. When I am logged in, I receive the system notification: “The system cannot find message number 0x2350 in the message file for Application.”

    Any suggestion on how to deal with that?

    Best regards,

    Karolina

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-06-05T09:12:04+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

    There is no ultimate.exe though. Here is windows 11 pro version screen shot from cmd window:

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments