Why Startup Repair Loops Without Reporting an Error Code on Windows 11

Quick fix: Startup Repair loops because it can’t fix the underlying issue and Windows keeps relaunching it. Boot from a Windows 11 install USB, open Command Prompt from Repair your computer, and check X:\Sources\Panther\srttrail.txt for the actual error — it usually points to a specific driver or BCD entry that needs manual repair.

Your PC tries to boot. The Windows logo appears, then “Preparing Automatic Repair.” Then “Diagnosing your PC.” Then it restarts and does the same thing again. Three loops later you see Automatic Repair couldn’t repair your PC but no specific error code or hint at what failed. The repair process itself ran — you need to find what it tried and why it gave up.

Where Startup Repair logs what it tried

Startup Repair writes a verbose log to %SystemDrive%\Windows\System32\LogFiles\Srt\SrtTrail.txt on the offline Windows install. The log lists every check it ran, what it found, and what (if anything) it tried to fix. The summary at the bottom names the root failure — missing driver, corrupted BCD, registry hive can’t load, etc.

You can’t see this log from inside Windows because Windows isn’t booting. You read it from a recovery environment Command Prompt, which mounts the broken install as a drive letter.

Method 1: Read SrtTrail.txt from recovery Command Prompt

1. Boot from a Windows 11 install USB. Click Next at the Setup screen, then Repair your computer.
2. Choose Troubleshoot → Advanced options → Command Prompt.
3. Identify the Windows drive letter. Run diskpart, then list volume. Note the letter for the Windows partition (usually C: or D: depending on recovery state).
4. Exit diskpart and run:
   
   type C:\Windows\System32\LogFiles\Srt\SrtTrail.txt | more
5. Read carefully. The last few lines name the failing component. Common patterns:
   
     Root cause found: Boot critical file is corrupt: \windows\system32\drivers\X.sys
   
     Root cause: BCD entry is missing
   
     Root cause: Boot manager is missing

The named root cause is what you fix in the next step. Each cause has a specific repair path.

Method 2: Repair based on the named root cause

1. Corrupt driver: Rename the file to a backup, let Windows boot with default driver.
   
   cd C:\Windows\System32\drivers

ren X.sys X.sys.bak
   
   Restart and let Windows reinstall the driver automatically.
2. Missing BCD entry: Rebuild the boot configuration.
   
   bootrec /scanos

bootrec /rebuildbcd
   
   Type Y when prompted to add the installation.
3. Missing boot manager: Reinstall it.
   
   bcdboot C:\Windows /s S: /f UEFI
   
   (S: is your EFI partition; assign a letter via diskpart if needed)
4. Registry hive corruption: Restore from automatic backup.
   
   cd C:\Windows\System32\config

ren SYSTEM SYSTEM.bak

copy RegBack\SYSTEM SYSTEM
   
   (Note: RegBack may be empty on newer Windows builds where automatic registry backup is disabled by default; manual restore from a system restore point is the alternative.)
5. Disk corruption: Run chkdsk against the Windows drive.
   
   chkdsk C: /r /f
6. Restart and let Windows boot.

One repair usually fixes the loop. If the first fix doesn’t work, re-read SrtTrail.txt — a different root cause may surface now that the first one is resolved.

Method 3: Disable Automatic Repair to break the loop temporarily

For users who want to access Safe Mode without going through repair attempts:

1. From the recovery Command Prompt, run:
   
   bcdedit /set {default} recoveryenabled No
2. Restart. Windows will now show its boot error instead of attempting silent repair.
3. Press F8 or hold Shift during boot to enter the Advanced Boot Options menu.
4. Choose Safe Mode and troubleshoot from there.
5. After fixing the underlying issue, re-enable recovery: bcdedit /set {default} recoveryenabled Yes.

Disabling Automatic Repair is a diagnostic step, not a permanent fix — you still need to address the root cause.

How to verify the fix worked

• Windows boots to the sign-in screen without entering recovery.
• Run winver after sign-in — OS reports correct version.
• Open Event Viewer and check the System log around boot time — no Critical or Error entries from boot/winlogon sources.
• Restart again to confirm the fix is stable.

If none of these work

If SrtTrail.txt is missing or empty (some recovery scenarios prevent its creation), the issue is severe enough that Windows can’t even reach the repair step that writes the log. In that case, try an in-place repair upgrade from a Windows 11 install USB: boot the USB, run setup.exe, choose Keep my files and apps. This rewrites the OS while preserving data. If that won’t complete either, your disk may be physically failing — image the drive to a new SSD via a USB enclosure and clean-install on the new disk.

Bottom line: Automatic Repair loops mean Windows can’t fix the issue silently. SrtTrail.txt tells you what failed. Read it, address that one thing, and the loop ends.