Windows 11 Stuck in an “Automatic Repair” Loop: 8 Ways to Break It

Seeing “Preparing Automatic Repair” or “Diagnosing your PC” repeatedly on a Windows 11 computer can be alarming. Instead of reaching the desktop, the PC keeps restarting, attempts Automatic Repair, fails, and then starts the process all over again.

Fortunately, an Automatic Repair loop does not necessarily mean your files are lost or that Windows needs to be reinstalled.

Windows 11 includes several recovery tools designed specifically for computers that cannot boot normally. The trick is knowing which option to try first and when to move to a more advanced repair.

This guide walks through 8 ways to break a Windows 11 Automatic Repair loop, starting with the least disruptive solutions and progressing toward advanced recovery.

Important: If your PC contains important files that are not backed up, avoid immediately choosing Reset this PC or reinstalling Windows. Some recovery procedures can cause data loss.

What Is the Windows 11 Automatic Repair Loop?

Windows Recovery Environment (WinRE) is a built-in recovery system that can automatically appear when Windows fails to start correctly. It contains tools such as Startup Repair, System Restore, Startup Settings, Command Prompt, Uninstall Updates, and Reset this PC.

Normally, Automatic Repair is helpful:

Windows fails to boot → Windows detects the problem → Automatic Repair runs → Windows repairs the problem → PC starts normally

The problem occurs when the repair itself cannot resolve the underlying issue:

Windows fails to boot → Automatic Repair → repair fails → restart → Automatic Repair → repair fails → restart

That repeating cycle is commonly called an Automatic Repair loop.

Common symptoms include:

• “Preparing Automatic Repair” appearing repeatedly
• “Diagnosing your PC” appearing after every restart
• A message saying “Automatic Repair couldn’t repair your PC”
• The PC repeatedly restarting
• Windows never reaching the login screen
• Advanced options appearing but normal startup failing
• A recent Windows update being followed by boot problems
• A blue or black screen appearing before Automatic Repair

The cause can range from corrupted system files and boot configuration problems to problematic updates, drivers, disk errors, or other startup failures. Microsoft specifically identifies damaged system files, corrupted BCD, damaged MBR, incompatible drivers, and registry problems among issues Startup Repair can attempt to address.

Before You Start: Protect Your Data

If you can access your files through another computer, a backup, or a bootable environment, back up important documents before performing aggressive repairs.

Also be aware that if BitLocker/device encryption is enabled, Windows may ask for your BitLocker recovery key when you use recovery tools. Microsoft notes that the recovery key may be required for several WinRE operations.

If you don’t have the key, don’t randomly delete partitions or reinstall Windows.

How to Enter Windows Recovery Environment

If you’re already seeing Automatic Repair, choose:

Advanced options → Troubleshoot → Advanced options

You should see several recovery tools.

If Windows isn’t displaying the recovery screen, Microsoft explains that you can force Windows into WinRE by interrupting startup. Start the PC and, when the Windows or manufacturer logo appears, hold the power button to shut it down. Repeat this twice; on the third startup, Windows should enter recovery.

Once you reach the Choose an option screen, select:

Troubleshoot → Advanced options

Now you can work through the following fixes.

Fix 1: Run Startup Repair Again

It may seem obvious, but Startup Repair is the first built-in tool you should try if you haven’t already used it from the Advanced Options menu.

Go to:

Troubleshoot → Advanced options → Startup Repair

Then select your Windows account if prompted and enter your password.

Windows will scan the installation and attempt to correct startup problems automatically.

Microsoft says Startup Repair can address problems involving things such as:

• Missing or damaged system files
• Corrupted Boot Configuration Data (BCD)
• Damaged master boot records
• Incompatible drivers
• Certain registry errors

What if Startup Repair says it couldn’t repair your PC?

Don’t keep running it repeatedly.

If Startup Repair has already failed, move to the next method rather than restarting the same repair over and over.

You can also find the Startup Repair log at:

%windir%\System32\LogFiles\Srt\SrtTrail.txt

Microsoft documents this log as a way to investigate startup problems and the repairs attempted.

Fix 2: Boot Windows 11 Into Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. That makes it useful for determining whether a recently installed driver, service, or startup component is preventing normal boot.

From WinRE, go to:

Troubleshoot → Advanced options → Startup Settings → Restart

After the computer restarts, you’ll see a list of startup choices.

Choose:

4 or F4 — Enable Safe Mode

Or:

5 or F5 — Enable Safe Mode with Networking

If Windows successfully reaches Safe Mode, that’s a useful sign.

What to do once you’re in Safe Mode

Think about what changed immediately before the Automatic Repair loop began.

For example:

• Did you install a graphics driver?
• Did you install new hardware?
• Did you install a utility?
• Did Windows recently update?
• Did you change a system configuration?
• Did you install security software?

If the problem started after a driver installation, uninstalling or rolling back that driver may resolve the problem.

You can also remove recently installed software or troubleshoot startup applications.

Why Safe Mode matters

If Windows works in Safe Mode but not normal mode, the problem is more likely related to something loaded during a normal startup rather than Windows being completely unable to boot.

Fix 3: Use System Restore

If the Automatic Repair loop started after a driver installation, software installation, Windows configuration change, or another recent modification, System Restore is one of the best options to try before using command-line repairs.

Go to:

Troubleshoot → Advanced options → System Restore

Choose a restore point created before the problem began.

System Restore can roll system files, registry settings, drivers, and installed programs back to an earlier state while not affecting your personal files.

For example

Suppose:

• Monday: Windows works normally
• Tuesday: You install a graphics driver
• Wednesday: Windows enters an Automatic Repair loop

If a restore point from Monday exists, restoring to it could undo the problematic system change.

Important limitation

System Restore only works if an appropriate restore point exists.

If no restore point is available, move to another solution.

Fix 4: Uninstall the Latest Windows Update

Sometimes a boot problem begins shortly after Windows installs an update.

If the Automatic Repair loop started immediately following a Windows update, try removing the most recent update.

From WinRE:

Troubleshoot → Advanced options → Uninstall Updates

You’ll generally be offered options for removing a recent update, depending on what Windows has available.

Microsoft specifically recommends uninstalling a recent update when an update appears to be responsible for new problems, and Windows RE provides an option to do this when you cannot access Windows normally.

When should you try this?

This solution makes the most sense when:

• Windows worked before an update
• The loop began immediately after updating
• You see other problems that appeared at the same time
• System Restore isn’t available

Don’t uninstall updates randomly

If there’s no connection between the update and the boot problem, another repair method may be more appropriate.

Also remember that some updates cannot be uninstalled.

Fix 5: Repair Windows System Files With SFC and DISM

Corrupted Windows system files can cause serious startup problems.

Microsoft recommends using DISM and System File Checker (SFC) to repair missing or corrupted Windows components.

Because Windows isn’t booting normally, you’ll need to use Command Prompt from Windows Recovery Environment.

Go to:

Troubleshoot → Advanced options → Command Prompt

Step 1: Find the Windows drive letter

This is extremely important.

Inside normal Windows, your installation is usually on C:. However, when you’re working from WinRE, Windows can assign different drive letters.

Don’t blindly assume that C: contains your Windows installation.

Try:

dir C:\Windows

If you see folders and files associated with Windows, you may have found the correct partition.

If not, try:

dir D:\Windows

and then:

dir E:\Windows

until you find the Windows directory.

For the examples below, let’s assume Windows is installed on C:.

Step 2: Check the disk

You can use Check Disk to look for file-system errors:

chkdsk C: /f

Depending on the condition and size of the drive, this may take some time.

If Windows is actually installed on another drive letter, substitute that letter.

Step 3: Run System File Checker offline

From WinRE, an offline SFC scan can be more complicated than the normal command used inside Windows because you need to specify the Windows and boot locations correctly.

A common starting point is:

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

Replace C: if your Windows installation uses a different drive letter.

If SFC reports that it repaired corrupted files, restart the computer and test Windows.

Why this fix can work

Critical Windows files can become damaged or missing. Microsoft explains that SFC checks protected system files and can replace corrupted files with cached copies.

Fix 6: Repair the Boot Configuration

If Windows itself appears to be intact but the computer cannot properly locate or load it, the problem may involve the boot configuration.

Microsoft’s Windows startup troubleshooting documentation includes boot-code and BCD troubleshooting as part of advanced startup repair.

Open:

Troubleshoot → Advanced options → Command Prompt

You can first inspect the boot configuration with:

bcdedit

If Windows is repeatedly being sent back into recovery, Microsoft documents this command for disabling automatic recovery for the default boot entry:

bcdedit /set {default} recoveryenabled no
``` :chatgpt-content-reference{index="13"}


### Important warning

This is an **advanced troubleshooting step**, not a universal fix.

Automatic recovery exists for a reason. Disabling it can change what happens when Windows encounters another startup failure.

If you're not comfortable working with BCD entries, don't randomly change or delete them.

### What about BOOTREC?

Microsoft's startup troubleshooting documentation also discusses commands such as:

```text
BOOTREC /FIXMBR

and:

BOOTREC /FIXBOOT

for specific boot-code problems.

However, modern Windows 11 systems commonly use UEFI/GPT configurations, so blindly running every boot-repair command you find online is not recommended.

Use boot-repair commands when the symptoms point toward a boot configuration problem rather than treating them as a universal solution.

Fix 7: Disconnect Recently Added Hardware

Hardware changes can sometimes trigger startup failures.

If the Automatic Repair loop began after you connected or installed something new, shut down the PC and disconnect unnecessary external hardware.

Try removing:

• USB drives
• External hard drives
• USB hubs
• Printers
• Docking stations
• Recently installed peripherals
• Other nonessential devices

Then restart.

Microsoft’s troubleshooting guidance for repeated Windows startup failures also recommends removing newly added hardware as an initial troubleshooting step.

Why this helps

A problematic peripheral, driver, or hardware change can interfere with the startup process.

If Windows boots normally after disconnecting a device, reconnect devices one at a time to identify the likely culprit.

Fix 8: Reset Windows 11 or Reinstall Windows

This should generally be your last resort, especially if important files haven’t been backed up.

If the previous methods fail, Windows Recovery Environment provides Reset this PC.

Go to:

Troubleshoot → Reset this PC

Windows provides options that can allow you to keep personal files or remove everything, depending on the recovery path and configuration. Microsoft’s recovery guidance lists Reset this PC as an option when a Windows 11 PC won’t start.

Keep my files vs. Remove everything

The exact options shown can vary, but conceptually:

Keep my files

Attempts to reinstall/reset Windows while retaining personal files.

Remove everything

Removes personal files, apps, and settings.

If your files are important and you haven’t backed them up, don’t choose the destructive option just because you’re frustrated with the repair loop.

What if Reset doesn’t work?

Microsoft also supports reinstalling Windows using installation media. A bootable USB created on another working PC can be used to access recovery tools or reinstall Windows.

A clean installation is considerably more destructive than the earlier troubleshooting options, so make sure you’ve considered data recovery first.

Bonus: Windows 11 24H2 Users May Have Another Recovery Option

There’s an important newer Windows 11 recovery feature worth knowing about.

Microsoft’s current recovery documentation says Quick Machine Recovery is available on Windows 11 version 24H2 and later. It can help devices recover from certain repeated startup failures caused by known widespread issues by connecting to Windows Update and applying a Microsoft-provided fix when one is available. On supported configurations, this can potentially resolve certain boot failures without you manually reinstalling Windows.

It’s not a solution for every Automatic Repair loop, but if your PC supports it, it’s another reason to avoid immediately jumping to a destructive reset.

What Causes an Automatic Repair Loop in Windows 11?

There isn’t one single cause.

Common possibilities include:

1. Corrupted system files

Windows may fail to start if critical operating-system files are damaged.

2. Boot configuration problems

Issues with BCD or other boot components can prevent Windows from finding or loading the operating system correctly.

3. Failed Windows updates

A problematic update can sometimes leave a system unable to boot correctly.

4. Driver problems

A faulty or incompatible driver can cause startup failures, particularly after recent hardware or driver changes.

5. File-system errors

Problems with the Windows partition can interfere with reading required system files.

6. Hardware problems

A failing SSD/HDD, memory problem, or other hardware fault can produce symptoms that look like a Windows software problem.

7. Improper shutdowns

Repeated forced shutdowns or power interruptions can sometimes contribute to file-system or system-file corruption.

8. Recent system changes

New software, security utilities, drivers, or configuration changes can sometimes trigger boot problems.

Which Fix Should You Try First?

Don’t randomly try all eight methods.

Use this escalation order:

This approach follows the general principle Microsoft uses in its recovery guidance: start with the least disruptive recovery option and escalate when necessary.

How to Tell If the Problem Is Software or Hardware

An Automatic Repair loop doesn’t automatically mean your SSD is failing.

However, hardware becomes more suspicious when you notice symptoms such as:

• The SSD/HDD intermittently disappears from BIOS/UEFI
• The computer freezes even before Windows starts
• Files were becoming corrupted before the boot problem
• The drive makes unusual noises if it is a mechanical HDD
• Windows repeatedly reports disk errors
• Multiple operating-system repairs fail
• The computer crashes even after a clean Windows installation

If the storage drive is failing, repeatedly repairing Windows may only temporarily mask the underlying problem.

In that situation, data recovery and hardware diagnosis should take priority over repeatedly reinstalling Windows.

What Not to Do During an Automatic Repair Loop

Some popular online fixes can make the situation worse if they’re used without understanding the configuration.

Don’t immediately format the Windows drive

Formatting destroys the existing Windows installation and can make data recovery more difficult.

Don’t delete random BCD entries

Boot configuration commands can affect whether Windows is able to start.

Don’t assume Windows is always on C:

WinRE can assign different drive letters.

Don’t repeatedly force shutdowns

Forced shutdowns are useful for entering WinRE when necessary, but repeatedly interrupting the boot process isn’t a substitute for diagnosing the underlying problem.

Don’t reset the PC before protecting important data

Even a recovery option designed to preserve personal files shouldn’t replace a real backup.

Don’t assume Automatic Repair means Windows is permanently damaged

WinRE contains several recovery tools specifically designed to repair startup problems.

Frequently Asked Questions

Why is Windows 11 stuck on “Preparing Automatic Repair”?

It usually means Windows has detected a startup problem and has entered Windows Recovery Environment to diagnose or repair it. If the repair cannot resolve the problem, the computer can repeatedly return to the same recovery process.

How do I get out of Automatic Repair in Windows 11?

Start with Advanced options and work through Startup Repair, Safe Mode, System Restore, update removal, and other recovery tools. Avoid immediately resetting the PC unless less destructive methods have failed.

Does Automatic Repair delete files?

The Automatic Repair process itself is designed to repair startup problems rather than erase your personal files. However, some later recovery choices—particularly Reset this PC or a clean Windows installation—can result in data loss.

Can Safe Mode fix an Automatic Repair loop?

Safe Mode can help if a driver, service, startup application, or recently installed software is responsible. If Windows successfully boots in Safe Mode, use that opportunity to remove or troubleshoot recent changes.

Will System Restore delete my personal files?

Microsoft says System Restore rolls system files and settings back to an earlier point without affecting personal files. It can, however, reverse applications, drivers, and system changes made after the selected restore point.

Should I use bootrec to fix the loop?

Only when the symptoms indicate a boot-code or boot-configuration problem. Modern Windows 11 systems often use UEFI/GPT, so blindly applying commands from generic Windows repair guides isn’t recommended.

What if none of these fixes work?

If all software recovery methods fail, investigate the storage drive and other hardware. You can then consider Reset this PC or reinstalling Windows. If important files aren’t backed up, consider data recovery before performing a clean installation.

Do I need a BitLocker recovery key?

Possibly. Microsoft notes that BitLocker-encrypted devices may require the recovery key when using recovery tools in Windows RE.

Quick Checklist: Windows 11 Automatic Repair Loop

If you need the short version, follow this order:

1. Open Advanced options
2. Run Startup Repair
3. Try Safe Mode
4. Use System Restore
5. Uninstall a recently installed Windows update
6. Use Command Prompt to check the disk and repair system files
7. Investigate boot configuration or recently added hardware
8. Reset or reinstall Windows only as a last resort

For Windows 11 24H2 or later, also pay attention to Microsoft’s Quick Machine Recovery capability if it is available on your device.

Final Thoughts

A Windows 11 Automatic Repair loop looks serious because the computer appears trapped in a cycle, but it doesn’t automatically mean that Windows needs to be erased.

The safest strategy is to escalate gradually.

Start with Startup Repair. If that fails, try Safe Mode or System Restore depending on what changed before the problem started. If an update appears responsible, remove it. For deeper corruption, use the recovery Command Prompt to investigate the Windows partition and repair system files. Boot configuration repair is appropriate when the evidence points toward a boot problem.

Only after those options fail should you consider resetting or reinstalling Windows.

Most importantly, protect important data before using destructive recovery options. Windows Recovery Environment provides multiple ways to troubleshoot a system that won’t boot, so there’s usually no reason to jump directly from an Automatic Repair loop to a clean installation.