Skip to content

How to Fix the Automatic Repair Loop in Windows 11

Windows 11 repeatedly entering Automatic Repair usually points to a failed update, damaged system files, boot-configuration trouble, or a storage problem. This guide explains what to try first, what to avoid, and when professional data-preserving diagnostics are safer.

When Windows 11 starts, displays “Preparing Automatic Repair” or “Diagnosing your PC,” and then restarts into the same screen, the computer is caught in an Automatic Repair loop. Windows is detecting a startup problem, but its built-in recovery process is not resolving it.

The cause may be relatively minor, such as an interrupted update or corrupted startup file. It can also indicate a failing SSD, damaged Windows installation, unexpected shutdown, driver problem, or encryption-related recovery issue. The steps below move from the least disruptive options to more involved repairs.

Before you start: protect your files

If the files on this computer are important, avoid choosing Reset this PC, deleting partitions, formatting a drive, or reinstalling Windows until your data has been backed up or assessed. Some repairs are safe, but repeated failed boot attempts can complicate diagnosis if the storage device is deteriorating.

If you can reach the Windows desktop even briefly, copy important documents, photos, and business files to an external drive or approved cloud backup. If Windows never reaches the desktop, consider professional data-preserving diagnostics before running extensive disk repairs.

On a BitLocker-encrypted computer, recovery tools may request the BitLocker recovery key. Find the key through the Microsoft account or organization that manages the device before proceeding. Do not try to bypass BitLocker or another security control. Without the correct recovery key, some repair and recovery options may not be available.

1. Disconnect external devices and perform a controlled restart

Shut down the computer completely. Disconnect USB storage devices, memory cards, external hard drives, docks, and nonessential printers. Leave the keyboard, mouse, display, and power connected. A removable drive or peripheral can sometimes affect the boot order or cause a driver-related failure.

Turn the computer back on once. Do not repeatedly force it off while Windows is writing to the drive. If the loop began immediately after connecting a device, leave that device disconnected while testing.

2. Open the Windows Recovery Environment

Automatic Repair normally opens the Windows Recovery Environment, often called WinRE. Select Advanced options rather than simply allowing the restart cycle to continue. Then choose Troubleshoot.

If the recovery menu does not appear, you may need a Windows 11 installation USB created on another working computer. Booting from installation media should be done carefully: choose Repair your computer, not Install now. On some systems, the boot-menu key varies by manufacturer. If the internal drive is encrypted or the computer is managed by an employer, stop and confirm the recovery process with the responsible administrator.

3. Try Startup Repair once

From Troubleshoot > Advanced options, select Startup Repair. This tool checks common boot configuration and startup problems automatically.

Startup Repair is worth trying, but it is not a general Windows repair tool. If it reports that it could not repair the PC, return to Advanced options and continue with the less destructive choices below. Repeating the same failed repair is unlikely to provide new information.

4. Remove a recent update

A Windows update, driver update, or related restart can expose an existing hardware or software problem. In Advanced options, select Uninstall Updates. Depending on what Windows has recorded, you may see options to remove the latest quality update or the latest feature update.

  • Try the latest quality update first because it is generally the smaller, more recent change.
  • If the loop began during or immediately after a major version upgrade, the feature-update option may be relevant.
  • Do not interrupt the process, even if the screen appears unchanged for several minutes.

Removing an update is a diagnostic step, not proof that the update itself was defective. If the loop continues, another cause may be involved.

5. Use System Restore if a restore point is available

Select System Restore from Advanced options. Choose a restore point from before the startup problem began, if one is available. System Restore normally affects Windows system files, drivers, and settings rather than personal documents, but it is not a substitute for a backup.

Some applications or updates may be removed or rolled back. Read the confirmation screen carefully. If System Restore fails, reports that the drive is unavailable, or asks for credentials you do not have, stop rather than guessing.

6. Test Safe Mode to separate drivers from deeper boot problems

Go to Startup Settings > Restart. After the restart, press the number for Safe Mode or Safe Mode with Networking. Safe Mode loads a limited set of drivers and services.

If Windows starts in Safe Mode, remove recently installed hardware utilities, third-party antivirus software, graphics drivers, or other programs added shortly before the loop began. Device Manager can help identify a recently changed driver, but avoid removing essential storage or chipset drivers without a clear reason.

While in Safe Mode, back up important files if possible. Then restart normally to test. If the normal boot still fails, the problem may involve Windows system files, the boot configuration, storage health, or a driver that Safe Mode does not load.

7. Check the Windows drive from Command Prompt

Command Prompt in WinRE is useful, but it is also where a typing mistake can damage a working installation. Before using repair commands, confirm the Windows drive letter. WinRE may assign Windows a letter other than C:.

At Command Prompt, you can check likely volumes with commands such as:

dir C:Windows
dir D:Windows

Use the letter that actually contains the Windows folder in the commands that follow. If the drive is BitLocker-protected and locked, do not attempt to work around the encryption. Unlock it only with the legitimate recovery key or authorized credentials.

To check the file system, a cautious first option is:

chkdsk C: /scan

Replace C: if Windows is on another letter. If the scan reports serious errors, unreadable areas, or unusual delays, consider stopping and arranging data recovery or drive-health diagnostics. A more intensive repair command such as chkdsk /f changes file-system structures and should not be the first response when valuable files have not been backed up or the drive may be failing.

8. Repair Windows system files offline

If the drive appears healthy and the Windows folder is identified correctly, System File Checker can inspect the offline installation:

sfc /scannow /offbootdir=C: /offwindir=C:Windows

Use the correct Windows drive letter. SFC may report that it found and repaired files, found corruption it could not repair, or found no problems. These results help narrow the diagnosis but do not guarantee that Windows will boot.

DISM can sometimes repair the Windows component store, but offline DISM may need a matching Windows installation source. Avoid copying commands from unrelated versions or using an arbitrary ISO. If the repair source does not match the installed Windows version and edition, the command may fail or produce confusing results.

9. Rebuild boot files only when the evidence points there

Boot-configuration commands can help when the Windows partition is present and the boot files are damaged. They can also make the situation harder to interpret if used indiscriminately, especially on systems with multiple operating systems, unusual partition layouts, or UEFI configuration changes.

If Startup Repair, update removal, restore, Safe Mode, and file checks have not resolved the loop, this is a good stopping point for many home users. A technician can identify the EFI system partition, confirm the correct Windows volume, check storage health, and preserve data before rebuilding boot files.

When the problem may be hardware

Suspect the SSD or hard drive when the computer freezes during recovery, reports I/O or disk errors, takes an unusually long time to read folders, disappears from firmware settings, or has experienced recent crashes and file corruption. A failing drive can produce symptoms that look like a Windows software problem.

Enter the manufacturer’s hardware diagnostics or firmware setup only if you know how to exit without changing boot, storage, or security settings. A drive that is missing from firmware may require hardware diagnosis rather than more Windows commands.

When to stop and get help

  • Important files have not been backed up.
  • The drive makes unusual noises, becomes extremely slow, or reports unreadable sectors.
  • BitLocker requests a recovery key you cannot locate.
  • The computer belongs to a business, school, or organization with managed encryption or account policies.
  • WinRE cannot see the Windows volume, or every repair option fails.
  • You are considering Reset this PC, formatting, partition changes, or a clean installation.

For home users and small businesses in Bellevue, Omaha, Papillion, La Vista, Plattsmouth, Ralston, Council Bluffs, and nearby areas, the safest repair path depends on whether the priority is restoring Windows, preserving files, or determining whether the storage device is failing. A careful diagnosis should establish that priority before destructive recovery steps are taken.

What not to do

  • Do not repeatedly power off the computer during updates or disk activity unless it is completely unresponsive and there is no safer option.
  • Do not delete EFI, recovery, or Windows partitions to escape the loop.
  • Do not use registry cleaners or random “boot repair” utilities from unknown sources.
  • Do not assume a successful reset proves the original hardware was healthy; a failing drive can fail again.

Automatic Repair is a symptom, not a diagnosis. Start with backups and low-risk recovery options, use command-line repairs only after confirming the correct drive, and stop before data-destructive steps when the cause remains uncertain.

When to call a professional

If the problem continues, the data is important, or the repair requires work beyond your comfort level, AME Computers can provide professional diagnosis and repair or call 402-505-6600.

Still need help with your computer?

AME Computers provides professional diagnostics and repair in Bellevue, Nebraska. No money down—ever. You pay after the repair is complete.