Still this thread is rolling!
I've done everything to the letter and when restarting in normal boot from MSConfig, I'm still in the pin loop. Not sure what to try differently...
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Problems:
Process to get error:
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:
Steps:
Other useful info:
Unsuccessful attempts before discovering solution:
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.
Still this thread is rolling!
I've done everything to the letter and when restarting in normal boot from MSConfig, I'm still in the pin loop. Not sure what to try differently...
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.
I have a very similar situation as far as the original problem is concerned
(Set msconfig to Diagnostic Startup by mistake). But I can't get into
recovery mode. If I hold down the shift key and press Restart I end up
with a normal boot followed by "Something happened and your pin isn't
available" as soon as I click the mouse key. I've pressed the power button
1 to 4 times as soon as the first boot message appeared and never ended
up in recovery mode. Any suggestions on how to get into Recovery mode
so I can attempt to fic the original problem?
You may create a bootable USB Windows Setup disk and access WinRE.
Some time cmd.exe is auto deleted then copy file from boot drive and paste in system 32 in explore menu open from re image your computer [ [ step 5]
Thank you so much. Its best troubleshooting article I came across so far. It saved a lots of time for me.