sodcalculator

10 Tech How-To

Fix Automatic Startup Repair Not Working on Windows 11

Guide 10-51178 · Updated · Step by step

If Windows 11’s Automatic Startup Repair gets stuck in a loop, fails to load, or simply does nothing, the problem is usually a corrupted Boot Configuration Data (BCD), a damaged system file, or a failed recent update. The most reliable fix is to use the Command Prompt from the Windows Recovery Environment to rebuild the BCD and run the System File Checker, which resolves the majority of cases in about 15 minutes.

Why Automatic Startup Repair Fails

Automatic Startup Repair is a built-in Windows 11 recovery tool that tries to diagnose and fix problems preventing the OS from booting. It works by scanning the boot sector, the BCD store, and critical system files, then attempting repairs. However, it has a well-known weakness: it often fails when the issue is deeper than a simple missing boot file. Common reasons it fails include:

  • Corrupted BCD store – the boot configuration data is damaged or points to a nonexistent partition.
  • Recent Windows Update – a partially installed update can leave the system in an unstable state that the repair tool cannot roll back.
  • Disk errors – bad sectors on the system drive can prevent the repair tool from reading or writing the files it needs.
  • Third-party software – antivirus tools, disk encryption, or boot managers from other OSes can interfere with the repair process.
  • Insufficient repair environment – the Windows Recovery Environment (WinRE) itself may be corrupted or missing.

Before You Start: What You Need

To attempt the manual fixes below, you need access to the Windows Recovery Environment. If your PC repeatedly fails to boot, Windows 11 should automatically enter WinRE after a few failed attempts. If not, you can force it by turning the PC off and on three times, interrupting the boot process at the Windows logo. Alternatively, you can boot from a Windows 11 installation USB drive and select “Repair your computer” on the setup screen.

You will also need to know your Windows 11 edition (Home, Pro, etc.) and whether your system uses UEFI or Legacy BIOS. Most modern PCs use UEFI, which affects the commands you use later. You can check this in the BIOS/UEFI setup screen, but if you are already in the recovery environment, the commands below work for both, with a note for legacy systems.

Step-by-Step: Rebuild the Boot Configuration Data (BCD)

The most effective first fix is to rebuild the BCD store manually. This clears out corrupted boot entries and recreates them from scratch. Here is how to do it from the Command Prompt in WinRE:

  1. In the Windows Recovery Environment, click Troubleshoot > Advanced options > Command Prompt.
  2. Type diskpart and press Enter.
  3. Type list volume and press Enter. Note the drive letter of the partition labeled System Reserved (usually 100 MB or 260 MB) and the drive letter of your Windows installation (usually C:). If you do not see a System Reserved partition, your system may use EFI – in that case, note the EFI partition (usually 100 MB, FAT32).
  4. Type exit to leave diskpart.
  5. Type the following commands one by one, pressing Enter after each. Replace E: with the drive letter of your System Reserved or EFI partition, and C: with your Windows drive if they differ.
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

If bootrec /fixboot gives an “Access is denied” error, your system uses UEFI and you need to format the EFI partition first. Run these commands instead:

diskpart
list volume
select volume <EFI partition number>
format fs=fat32 quick
exit
bootrec /fixboot

After all commands complete, type exit and restart your PC. If the BCD was the issue, Windows 11 should boot normally.

If That Fails: Run System File Checker and DISM

If rebuilding the BCD does not work, the problem may be corrupted system files. From the same Command Prompt, run the System File Checker (SFC) and the Deployment Imaging Service and Management Tool (DISM).

  1. Type sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows and press Enter. Replace C: with your actual Windows drive letter.
  2. Wait for the scan to complete. It may take 10-20 minutes.
  3. If SFC reports errors it cannot fix, run DISM: DISM /Online /Cleanup-Image /RestoreHealth – but note that this requires internet access and may not work in the recovery environment. A better alternative is to use the Windows installation media as the source: DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim (replace E: with your USB drive letter).
  4. Restart after the commands finish.

When Manual Fixes Don’t Work: Reset or Restore

If BCD rebuild and SFC/DISM fail, the next options are more drastic but often necessary:

  • System Restore – if you have a restore point from before the issue started, go to Troubleshoot > Advanced options > System Restore and pick a point. This is the least invasive option and preserves your files.
  • Startup Repair from installation media – boot from a Windows 11 USB, click “Repair your computer”, and choose Startup Repair. This sometimes works when the built-in one fails because it uses a fresh copy of the recovery tools.
  • Reset this PC – in the recovery environment, choose Troubleshoot > Reset this PC. You can choose to keep your files or remove everything. This reinstalls Windows 11 but keeps your personal files if you select that option. It is a last resort because it removes installed applications.

Preventing Future Startup Repair Loops

Once your PC boots again, take steps to reduce the risk of this happening again:

  • Create a system restore point regularly, especially before installing drivers or major updates.
  • Keep Windows Update healthy – if an update caused the issue, pause updates for a few weeks and install them manually one at a time.
  • Check disk health – run chkdsk /f /r from an elevated Command Prompt to find and fix bad sectors.
  • Disable Fast Startup – this Windows feature can sometimes cause boot issues. Go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable, then uncheck “Turn on fast startup”.
  • Back up your data – use File History or a third-party backup tool so that even a catastrophic failure does not mean data loss.

Frequently Asked Questions

Will I lose my files if I use these commands?

No. The bootrec, sfc, and DISM commands only repair system files and boot configuration. They do not touch your personal documents, photos, or installed programs. Only the “Reset this PC” option with “Remove everything” deletes your files, and even then you can choose to keep them.

Why does Startup Repair say “Your PC could not be repaired”?

This generic message means the tool could not automatically fix the problem. It does not tell you what is wrong. That is why manual commands are often necessary – they give you specific error messages that point to the actual cause, such as a missing boot file or a corrupted registry hive.

Can I run these commands from a normal Command Prompt in Windows?

Some commands like sfc /scannow and DISM can run from an elevated Command Prompt in Windows, but bootrec must be run from the recovery environment because the boot files are locked while Windows is running. If you can boot into Windows, try running sfc /scannow first – it may fix the issue without needing the recovery environment.

What if I don’t have a System Reserved or EFI partition?

On some older systems or after a misconfigured installation, the boot files may be on the same partition as Windows (C:). In that case, use C: as the drive letter in the bootrec commands. If you are unsure, run diskpart and list volume – look for a partition with the “System” or “EFI” label. If none exists, use your Windows partition.

Is it safe to format the EFI partition?

Yes, but only if you are certain it is the EFI partition (FAT32, 100-260 MB, labeled EFI). Formatting it erases the boot loader, but the bootrec /fixboot command will recreate it. Do not format any partition labeled “System Reserved” if it is NTFS – that is a different type and formatting it will make things worse.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →