The automatic startup repair loop has to be one of the most frustrating situations a Windows user can find themselves in. Your computer infinitely reboots, errors, BSODs and continues in a loop without you being able to do anything. There is a way you can fix automatic startup repair loop in Windows 10 and I’ll show you how here.
Windows 10 has an auto repair feature built into it that initiates after two failed boots. It will automatically begin repairing itself in the hope that it can then boot normally. Occasionally, this process begins but never ends and is referred to as the ‘startup repair loop’.
Fix the automatic startup repair loop in Windows 10
There is a sure fire way to get your computer out of the startup repair loop. You will need either a DVD or USB with Windows 10 installation files on it for this to work.
1. Set up your BIOS to boot from DVD or USB, whichever you have.
2. Boot from the installation media and select ‘Repair your computer’ instead of ‘Install now’.
3. Select Troubleshoot, Advanced options and Command Prompt to access the Windows Recovery Environment.
4. When the CMD windows appears, type or paste ‘bcdedit’ and hit Enter.
5. Look for ‘resumeobject’ and note the GUID number next to it.
6. Type or paste ‘bcdedit /set GUID recoveryenabled No’. Where GUID is the number noted above.
Now when you reboot, you should be able to load Windows 10 as normal. However, this step only stops the reboot loop, not the reason it was happening. To address the root cause, run a disk check and/or a system file check.
1. Open a CMD window as an administrator.
2. Type or paste ‘chkdsk /f /r’ and hit Enter.
3. Allow the process to complete.
Then perform a system file check.
1. Open a CMD window as an administrator.
2. Type or paste ‘sfc /scannow’ and hit Enter.
3. Allow the process to complete.
If the error reoccurs, you will need to perform a system refresh to make it go away.
More fixes to common Windows 10 problems here:
How to fix 100% disk usage in Windows 10
How to fix unexpected store exception error message
How to fix Runtime Broker high CPU usage