How to disable the automatic repair loop in Windows 10

In Windows 10, the Auto Repair feature is a handy feature that looks for and fixes common problems that can prevent your device from booting properly.

If the computer fails to boot twice in a row, the auto-reboot mechanism kicks in on the third boot. During this process, the system runs a series of diagnostic tests to identify and resolve common boot problems.

However, if you prefer to fix boot problems manually or if auto-recovery causes unexpected cycles, you can disable this feature in Windows 10.

In this Windows 10 guide by Techquack, we’ll walk you through how to disable automatic device diagnostics and repairs. If the auto repair was previously disabled or if you want to undo the changes, we’ll also describe the steps to re-enable the feature.

What causes the Windows 10 auto-repair cycle

There is no single cause of the Windows 10 auto-recovery cycle, but several situations are likely to trigger it. Missing or corrupted system files are one of the most common reasons why Windows doesn’t start (or doesn’t recover) because the important files it needs to run are not available.

The Windows kernel (ntoskrnl.exe) and other important Windows services may not be fully loaded, making it impossible to use the PC. Another problem that can cause a repair stub is a recently installed component or connected device that is missing a device driver (or just not working properly).

If you have recently upgraded your PC, your new components need Windows device drivers in order to use them. If the drivers are missing, outdated, or unsupported, this can cause a repair loop, especially for critical components such as a new video card.

Other problems, such as faulty components, malware infection, corrupted registry, or even corrupted installation files are all possible causes. Fortunately, many of the solutions listed below work for most causes of the Windows 10 auto repair loop.

How do I fix the Windows 10 auto repair loop

Use a disk utility

Plugin your Windows installation media or system restore/restore disk to your computer, select your language settings, and click Next to continue.

  1. In the bottom pane, click Restore computer.
  2. Select Troubleshooting -> Advanced Options -> Set.
  3. Type chkdsk /f /r C: and press enter.
  4. Type exit and hit enter.
  5. Restart your computer to see if the problem is resolved or not.

Restore boot and restore BCD using the command line

  1. Open a command line and follow the instructions of method 1.
  2. Type exe /rebuildbcd and press Enter.
  3. Type exe /fixmbr and press Enter.
  4. Type exe /fixboot and press Enter.
  5. Type exit and press Enter after each command is successful.
  6. Reboot your computer. If you’re still stuck in an automatic Windows restore cycle, try the following method.

Restore Windows Registry

  1. From the Windows Startup Options menu, choose Troubleshooting -> Advanced Options -> Command Prompt.
  2. At the command prompt, type the following command and press Enter. cd C:windowssystem32logfilessrt (change the drive letter accordingly)
  3. Type text to open the file in Notepad.
  4. Press CTRL + O.
  5. Under File Type, select “All Files” and navigate to C:windowssystem32.
  6. Right-click on CMD and select “Run as administrator”.
  7. Type cd C:windowssystem32config and press Enter.
  8. Back up these files by renaming the Default, Software, SAM, System, and Security files to .bak.
  9. Enter the following commands in sequence and press Enter:
  10. Rename DEFAULT DEFAULT.bakrename SAM SAM.bak
  11. Rename SECURITY SECURITY.bak
  13. Rename SYSTEM SYSTEM.bak
  14. Type copyc:windowssystem32configRegBack c:windowssystem32config and press Enter.
  15. Reboot your computer.

Delete the problem file

  1. Call the command line again and enter the following command:
  2. CD C:WindowsSystem32LogFilesSrt
  3. SrtTrail.txt.
  4. After that, you will see the following message: “The critical file c:windowssystem32drivers mel.sys has been corrupted”.
  5. Now type the following command into the problem file.
  6. cd c:windowssystem32drivers
  7. Delvstock.sys.
  8. Finally, reboot your computer. If these solutions do not help you, try the following troubleshooting steps to solve your Windows auto-repair problem.

Disable auto-repair at startup

  1. At the command prompt, type bcdedit /set {default} recoveryenabled No and press Enter.
  2. Reboot your computer, automatic restore at startup should be disabled and you should be able to access Windows 10 again.
  3. If you need to enable it again, you can type bcdedit /set {default} recovery enabled Yes in CMD and press Enter.

Frequently Asked Questions

  1. At the command line, type bcdedit /set {default} recoveryenabled No and press Enter.
  2. Reboot your computer, automatic repair should be disabled at startup, and you should be able to access Windows 10 again.
  3. If you need to enable it again, you can type CMD bcdedit /set {default} recovery enabled Yes and press Enter.

  1. From the Start menu, select Troubleshooting -> Advanced -> Command Prompt.
  2. Now run from the command line:
  3. This will disable boot recovery.

The main cause of the Windows 10 auto repair cycle problem may be corrupt or faulty Windows 10 ISO files. More specifically, other factors such as defective hard drives, missing registry keys, or even complex malicious rootkits can also cause the problem.

Accessing the Windows 10 Advanced Startup Options menu On many laptops, pressing the F11 key after powering on accesses the Windows 10 Advanced Startup Options menu. If you boot from the installation disk and click Next, Restore, the second option is available.

Website | + posts

Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog,, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.