Thanks so much for these detailed instructions. I attempted them and got to the System Configuration window where I changed that to Normal startup and restarted however there was no change in behaviour, ie still stuck in 'make a pin' loop.
I attempted it again and noticed in the Boot tab of System Configuration window that the boot options are set to Safe Boot even though I've set a Normal Startup in the General tab.
I attempted uncheck the Safe Boot and it said that BitLocker is enabled and it will enter recovery mode at the next boot, do you want to proceed. Which I hit Yes to. Then it said than it couldn't save the original boot config because a required privilege is not held by the client.
So I'm afraid I'm still stuck in the loop unless anyone has a fix for this?
Thanks
EDIT:
I if he above method doesn't work, this worked for me.
Guys If your problem about "Safe boot" do this first and do chatgpt what said. It works for me!
do Omid hosseini what said first.
Then do this: Chatgpt:
Hey bro, what you're dealing with is a classic Windows boot loop issue — but don’t worry, it’s not hopeless. The reason you’re getting that error is because your system is currently in Safe Boot mode and you're not able to launch Command Prompt with admin privileges. That’s because Diagnostic Startup or Safe Mode disables many essential services. So basically: “A required privilege is not held by the client” = You don’t have admin rights because the system is running in a restricted mode. Here’s how to fix it step-by-step:
- Open Command Prompt from the lock screen If you've already replaced utilman.exe with cmd.exe, click the Accessibility icon on the lock screen to open Command Prompt.
- Manually disable Safe Boot Type the following command:
Copy
bcdedit /deletevalue safeboot
This does the same thing as unchecking “Safe Boot” in msconfig.
Then reboot the system using:
Copy
shutdown /r /t 0 3.
System should now boot normally Once the system starts up normally and you’re able to log in, run this command: sfc /scannow
This will restore the original utilman.exe file and repair any modified system files.
From here: