If your PC keeps bouncing between Preparing Automatic Repair, a black screen, and a fresh round of disappointment, welcome to one of Windows 10’s least charming magic tricks. The good news is that an automatic repair loop does not always mean your computer is doomed, your files are gone, or your laptop has decided to pursue a new career as a paperweight.
In many cases, the loop starts after a failed update, corrupted system files, boot configuration errors, disk issues, driver conflicts, or a rough shutdown that leaves Windows confused about how to start. And when Startup Repair fails, you have to step in and do the troubleshooting manually. Think of it as becoming your PC’s slightly irritated but highly effective emergency mechanic.
This guide walks through the safest fixes first, then moves to more advanced options like Safe Mode, file repair commands, and rebuilding the boot records. By the end, you should know how to fix the Windows 10 automatic repair loop without randomly clicking buttons and hoping for divine intervention.
What causes the Windows 10 automatic repair loop?
Before you fix the problem, it helps to know what may have caused it. The loop usually appears when Windows detects a startup problem, launches Startup Repair, fails to resolve the issue, and then tries again. That cycle can repeat forever, which is not exactly a productivity feature.
Common causes include:
- Corrupted or missing system files
- Damaged boot files or Boot Configuration Data (BCD)
- A failed Windows update or interrupted upgrade
- Disk file system errors or early signs of drive failure
- A bad driver, especially after recent hardware or software changes
- Misconfigured BIOS or UEFI settings
- External devices confusing the boot process
If your system started looping right after an update, driver install, BIOS tweak, or sudden power loss, that clue matters. Windows rarely breaks for no reason. It usually leaves a trail of breadcrumbs. Sometimes they are made of error codes. Sometimes they are made of panic.
Before you start: do these simple things first
Start with the boring stuff. It is boring because it works more often than people expect.
- Disconnect all external devices such as USB drives, printers, docks, SD cards, and extra monitors.
- Force a full shutdown, then turn the PC back on.
- Have your BitLocker recovery key ready if device encryption is enabled.
- Create a Windows 10 installation USB on another computer if you cannot get into recovery tools normally.
External devices can sometimes hijack the boot order or trigger startup confusion. Yes, a harmless-looking USB stick can absolutely become the main character in your disaster story.
Step 1: Enter the Windows Recovery Environment
To fix an endless repair loop, you need to get into Windows Recovery Environment, also called WinRE. This is the repair hub where Windows keeps its emergency tools.
How to get into WinRE
If your PC will not boot normally, Windows often opens WinRE automatically after multiple failed starts. If it does not, you can usually force it:
- Turn the PC on.
- As soon as Windows starts loading, hold the power button to shut it down.
- Repeat this process two or three times.
- On the next boot, Windows should open the recovery screen.
If that does not work, boot from a Windows 10 installation USB and select Repair your computer instead of Install now.
Step 2: Run Startup Repair once, not twelve times
Yes, this article is about what to do when Startup Repair fails, but it is still worth running it manually once from WinRE because the manual route can behave differently than the endless loop.
Path:
Troubleshoot > Advanced options > Startup Repair
Select your Windows 10 account, enter your password if asked, and let the tool run. If it works, fantastic. If it fails again, do not keep rerunning it like a slot machine. Move on.
Step 3: Undo the change that probably caused the loop
If the problem started after a Windows update, driver change, or software install, your best move may be to reverse the latest change before you start using repair commands.
Option 1: Uninstall the latest update
In WinRE, go to:
Troubleshoot > Advanced options > Uninstall Updates
You will usually see two choices:
- Uninstall latest quality update
- Uninstall latest feature update
Start with the latest quality update. It is less invasive and often enough to stop the loop after a bad patch.
Option 2: Use System Restore
If you had restore points enabled before the crash, you may be able to roll Windows back to a working state.
Go to Troubleshoot > Advanced options > System Restore, choose a restore point from before the problem began, and let Windows rewind history a little. It is not time travel, but it is close enough for a Tuesday.
Step 4: Boot into Safe Mode
If Startup Repair fails but Windows can still limp into Safe Mode, you are in much better shape. Safe Mode loads only essential drivers and services, which makes it easier to remove a bad update, broken driver, or startup app.
How to reach Safe Mode from WinRE
Go to:
Troubleshoot > Advanced options > Startup Settings > Restart
After restart, select:
- 4 for Safe Mode
- 5 for Safe Mode with Networking
Once you get in, you can uninstall recent drivers, remove suspicious software, or run repair tools from within Windows.
If Startup Settings will not cooperate
Some systems also let you enable Safe Mode from Command Prompt in recovery by using:
bcdedit /set {default} safeboot minimal
After troubleshooting, remember to turn Safe Mode back off with:
bcdedit /deletevalue {default} safeboot
Step 5: Repair the file system and Windows files
Once you are in Safe Mode, or if you can reach Command Prompt from WinRE, it is time to check the disk and repair corrupted Windows files.
Run CHKDSK
Use this first if the loop may be related to file system damage or a rough shutdown:
chkdsk C: /f /r
This command checks the drive for logical errors and bad sectors. It can take a long time, especially on older hard drives. That is normal. CHKDSK moves at the speed of dramatic suspense.
Run SFC
If you can reach Safe Mode or normal Windows, run:
sfc /scannow
System File Checker scans protected Windows files and replaces corrupted versions.
Run DISM if Windows boots to Safe Mode or desktop
If SFC reports problems it cannot fully repair, follow up with:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Then run sfc /scannow again. DISM repairs the underlying Windows image; SFC then uses that healthier image to replace damaged files. It is basically the operating system equivalent of fixing the toolbox before fixing the house.
Step 6: Rebuild the boot files when the loop is deeper than system corruption
If the system still loops, the problem may be in the boot records or BCD store rather than ordinary Windows files. This is especially common after failed updates, cloning drives, changing partitions, or sudden shutdowns.
Open Command Prompt from WinRE and try the following commands one at a time:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
If Windows installations are found, allow them to be added back to the boot list.
What if “bootrec /fixboot” says Access is denied?
That happens often on UEFI-based systems. In that case, rebuilding the EFI bootloader with bcdboot is usually the smarter move.
Use these steps carefully:
diskpart
select disk 0
list partition
select partition [EFI partition number]
assign letter=S
exit
bcdboot C:\Windows /s S: /f UEFI
If your Windows installation is not on C: in recovery, replace it with the correct drive letter. After the boot files are rebuilt, restart and test the system again.
Step 7: Check BIOS or UEFI settings if the system still will not start
If software fixes are failing, confirm that the firmware settings are not part of the problem.
Check these items:
- Is the internal drive detected in BIOS or UEFI?
- Is the correct boot drive first in the boot order?
- Was the system recently switched between UEFI and Legacy boot modes?
- Did a BIOS update happen right before the loop started?
If the drive is missing entirely, the issue may be hardware-related rather than a Windows repair problem. In plain English, Windows cannot boot from a drive it cannot see.
Step 8: Use Reset this PC if you need a cleaner fix
If you have tried repair, Safe Mode, update rollback, file checks, and bootloader fixes without success, use Reset this PC from WinRE.
Go to Troubleshoot > Reset this PC.
Your main options:
- Keep my files: reinstalls Windows while preserving personal files
- Remove everything: full reset for a deeper cleanup
Choose the least destructive option that fits your situation. If the system has important files and you do not have a backup, start with Keep my files. If the install is badly damaged or infected, a clean reinstall may be the fastest path back to sanity.
Common mistakes to avoid
- Running Startup Repair over and over with no new result
- Ignoring BitLocker prompts and assuming the key is optional
- Typing boot commands without double-checking the drive letter
- Resetting Windows too early before trying update rollback or System Restore
- Assuming every repair loop is caused by software when the drive may be failing
The biggest mistake is panic-clicking. Windows recovery is one of those places where confidence is helpful, but precision is better.
Final thoughts
When Windows 10 Startup Repair fails, the problem usually falls into one of three buckets: damaged updates, corrupted files, or broken boot data. That means the fix is often possible without immediately wiping the machine. Start small, work in order, and use the built-in recovery tools before jumping to a full reset.
If you can access WinRE, you still have leverage. If you can reach Safe Mode, you have options. And if you can rebuild the boot files successfully, your PC may come back to life with surprising speed. It is a frustrating issue, but it is also one of those problems that often looks more catastrophic than it really is.
In other words, the loop may be endless, but your troubleshooting session does not have to be.
Real-world experiences with the Windows 10 automatic repair loop
One reason the Windows 10 automatic repair loop feels so stressful is that it rarely arrives with a clear explanation. For many people, the computer worked fine the night before, then suddenly wakes up trapped in a cycle of Diagnosing your PC, Preparing Automatic Repair, and disappointment. A lot of users first assume the machine is permanently dead, but the actual experience is usually more nuanced.
A common pattern starts after a Windows update. Someone restarts for what should have been a routine patch, grabs coffee, comes back, and finds the laptop looping instead of loading the sign-in screen. In these cases, uninstalling the latest quality update or using System Restore often works better than diving straight into advanced command-line fixes. The lesson is simple: when a problem begins immediately after an update, undoing that update is often the most logical move.
Another frequent experience happens after a hard shutdown or power outage. The PC may have been writing system data, updating the registry, or changing boot files when power vanished. After that, Windows knows something is wrong but cannot always repair itself. Users in this situation often get the best results from chkdsk, sfc, and sometimes a BCD rebuild. It feels dramatic, but in many cases the damage is limited to startup structures rather than the entire system.
There is also the driver-conflict scenario, which is particularly sneaky. A new graphics driver, storage driver, or third-party security tool can leave the system unable to start normally. The machine looks broken, but Safe Mode often opens the door because it loads a stripped-down version of Windows. People are sometimes surprised that the “dead” PC suddenly boots in Safe Mode just fine. That moment is both relieving and slightly insulting.
Then there are the cases where repair commands do not fail because the system is beyond hope, but because the boot setup has changed. UEFI systems, EFI partitions, BitLocker prompts, and multiple storage devices can make old repair habits less reliable. Someone types bootrec /fixboot, gets Access is denied, and assumes the game is over. In reality, that error often just means the next step should be rebuilding the EFI bootloader with bcdboot instead of repeating the same command like it owes you money.
Finally, some experiences point to hardware rather than Windows itself. If the internal drive disappears from BIOS, makes strange noises, or repeatedly throws file-system errors, software repair may only be a temporary bandage. In those cases, the automatic repair loop is not the original problem. It is the symptom that finally got your attention.
The biggest takeaway from real-world troubleshooting is that patience and order matter. The people who fix the problem fastest are usually the ones who stop guessing, start with WinRE, try the least destructive options first, and only escalate when the earlier steps fail. The loop feels chaotic, but the repair process works best when you do the opposite.