The steps were only slightly different for me, requiring me to select an account, then sign in using my password after selecting System Image Recovery.
This saved me so much headache, thanks OP
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.
The steps were only slightly different for me, requiring me to select an account, then sign in using my password after selecting System Image Recovery.
This saved me so much headache, thanks OP
I’m stuck on step 8. I can’t find where Utilman is, or cmd. There’s only folders, and there’s no search option. Please tell me there’s a specific location, and that I don’t have to click through every single file, because there are hundreds.
Edit!!! Look for Harschal’s responses. Find the command prompt instead of entering the image recovery. Follow those steps and it’ll work.
Thank you sooooooo much.🤩❤️❤️❤️❤️❤️🤩
After more than 12 Hours of trying everything, but kept being forced to enter a non functional password.
Im soo glad I bookmarked this sometime earlier ingenious way of renaming utilman.exe :D
Maybe you get all the luck and goodies in this world. You just saved my **** and 10+ years of files i can't lose.
Its quite shocking how there is no warning at all, when choosing msconfig diagnostic or selective boot option. The fact that some people don't have a local account hasn't been taken into account, sad.
Hello,
I'm sad to report that this bug continues on Win 11 Home ver 23H2 OS 22631.3527 in 2024(.
I didn't want to use external executables as anything could be hacked then compromised and there are no verification files checksum posted here. Didn't feel that it can remain safe.
However, I found another way around MS new explorer restrictions.
I don't know if someone else has posted it and I don't have time to read all these posts as I've fixed mine. It does not involve take ownership work arounds. If it verified by reply here that file permissions are the only other method posted presently for a fix I will post what I found here after confirmation.
Thanks to all!
Great solution! I appreciate it a lot. Although the last part with changing back the names didn’t work for me (it says I don’t have enough space but I do). What happens if I skip changing the names? Greetings!