If you have some experience with Windows operating systems it is likely that you have ever come across system repair attempts that never end, preventing the equipment from starting. It is known as the automatic repair loop; In this article we will learn something more about it and what we can do to solve the problems it produces.

What is the automatic repair loop?

Every time Windows starts, dozens of checks are carried out to ensure that everything works as expected. If, for whatever reason, the system detects any error, a repair tool is launched automatically, which usually works in most cases.

However, there are times where the system is not able to fix the error by itself and when resetting the equipment, it launches the repair automation again, causing a loop that prevents us from accessing the computer to solve the problem in another way. The reasons are usually very diverse, from errors in the Windows Registry or a malware infection, interrupted updates or a random shutdown while sensitive system data was being written.

It is important to note that startup repair can take anywhere from a few seconds to hours, and typically it’s a good idea to wait a while to see if it can be completed. If everything fails and after hours the equipment still does not start, we can go to plan B.

How to disable Windows 10 repair loop?

To disable an automatic repair cycle that never ends we will run a command in the command prompt window. Follow the next steps as detailed:

1.- Force the equipment to turn off by pressing and holding the power button (or, if it does not respond, unplugging the current).

2.- Turn it on and press the key repeatedly F11 to start the Troubleshoot menu.

3.- Go to Advanced Options> Command Prompt

4.- In the command prompt window type:

bcdedit / set {default} recoveryenabled no

After restarting, if the system is stable it should start normally. At that point, it is important to find out what caused the loop and repair it. Depending on the problem, updating the computer or repairing the startup from the command console may be sufficient, or a full restore may be required.

Once fixed, it is recommended to reactivate the recovery cycle. To do this, follow the previous steps and type

bcdedit / set {default} recoveryenabled yes

For the changes to take effect, simply restart the computer.

More information | Practical MC


Please enter your comment!
Please enter your name here