Why does Windows 11 keep going into automatic repair?

The most common trigger is a failed Windows Update that corrupted boot files during the apply phase. The machine tries to boot, fails, enters Automatic Repair, repair fails because it can't fix what the update broke, and the cycle repeats. KB5034441 and several 24H2 cumulative updates are known offenders. From the recovery screen, go to Advanced options and Uninstall latest quality update — this rolls back the bad update in about five minutes.

Why does bootrec /fixboot say Access Denied?

On UEFI systems with GPT disks — which is every machine made in roughly the last eight years — bootrec /fixboot does not work. It returns Access is denied regardless of permissions. Use bcdboot instead: open diskpart, find your EFI partition (100-500MB, FAT32), assign it a letter, then run bcdboot C:\Windows /s S: /f UEFI with the correct drive letters for your system.

How long should CHKDSK take in recovery mode?

On a healthy 500GB drive, chkdsk /r typically finishes in 20 to 40 minutes. If it runs beyond two hours or keeps getting stuck at the same percentage, the drive likely has physical damage. Triple-digit bad sector counts on an SSD mean the drive is failing and you should prioritize recovering files over repairing Windows.

Automatic Repair Loop on Windows 11? Fix It

If you’re staring at “Preparing Automatic Repair” for the fourth time in a row — the machine isn’t fixing itself. It tried, it failed, and it’s going to keep failing until you intervene. Hold the power button for ten seconds to force it off. Turn it back on. When “Choose an option” appears on the blue screen, that’s the Windows Recovery Environment, and that’s where you work from.

If BitLocker prompts for a recovery key before you can do anything, go to microsoft.com/recoverykey on your phone, log in with the Microsoft account tied to this PC, grab the 48-digit key. Without it, every recovery option bounces you right back.

The Update That Broke It

A large share of automatic repair loops start right after a Windows Update. The machine installed something, tried to reboot, botched the apply phase, and now it can’t boot forward or roll back. KB5034441 was notorious for this — corrupted the recovery partition on machines where it was undersized. More recently, 24H2 cumulative updates have been trapping machines with small EFI partitions — the same partition math that makes 24H2 refuse to install in the first place.

From the recovery screen: Advanced options, Uninstall updates, Uninstall latest quality update. If the loop started after an update, this rolls it back. Five minutes. A common case: an HP Envy x360 stuck in the loop for days after an update — uninstalling the last quality update is often enough to boot straight to the desktop. That option is buried three menus deep in recovery and nobody finds it on their own.

If that doesn’t work, try System Restore from the same Advanced options menu. Windows creates restore points before updates. Pick the one dated right before the loop started.

bootrec and the Access Denied Wall

Open Command Prompt from Advanced options in recovery. Run:

bootrec /fixmbr
bootrec /rebuildbcd

Skip bootrec /fixboot — on UEFI systems, which is every machine from the last eight years, it returns “Access is denied.” Use bcdboot instead:

bcdboot C:\Windows /s S: /f UEFI

You need the EFI partition letter first. In Command Prompt:

diskpart
list volume

Find the volume that’s 100-500MB, FAT32, labeled “System” or “EFI”. Note the volume number. If it doesn’t have a drive letter assigned:

select volume [number]
assign letter=S
exit

Then run bcdboot with whatever letter you assigned.

Your Windows drive might not be C: in recovery — the recovery environment assigns C: to the system partition, so Windows could be on D: or E:. Run dir C:\Windows to check. If it says “File Not Found”, try the other letters until you find your actual Windows installation. SFC from recovery has the same drive letter problem, which is why people run it and it reports zero issues when the whole OS is corrupted — it scanned the wrong partition.

When the Drive Is Dying

Run CHKDSK from the recovery Command Prompt — chkdsk C: /r (or whatever letter your Windows drive turned out to be). A healthy 500GB drive finishes in 20-40 minutes. If it’s still going after two hours, or it keeps getting stuck at the same percentage and restarting, the drive has physical damage that no boot repair will fix.

Typical scenario: a two-year-old ASUS VivoBook with an NVMe SSD goes into an automatic repair loop with no update trigger — it just starts one morning. CHKDSK reports hundreds of bad sectors on what’s supposed to be a wear-leveled flash drive. That drive is close to dead; copy what you can to an external USB right away, because an SSD in that state can fail completely within days. Triple-digit bad sector counts on an SSD mean stop trying to repair and start trying to save files.

The Nuclear Options

System Restore didn’t work, boot repair didn’t work, drive checks out fine but Windows won’t come back.

“Reset this PC” from the recovery screen, choose “Keep my files” — this does a factory reset that preserves documents and photos but wipes every installed program. Every single one. If Reset itself fails — it can freeze partway (64% is a common sticking point) and loop right back into automatic repair — you need a clean install from USB. Create bootable media with the Media Creation Tool on another computer, boot from it, custom install, format the Windows partition. Your files are gone at that point unless you got them off the drive first.

If you’re sitting in the recovery Command Prompt and not sure which partition is which, or bcdboot reports success but the machine still loops — we walk people through this over WhatsApp while looking at the recovery screen, to figure out whether it’s a BCD problem, a driver conflict, or a drive that needs replacing.