Seeing the message “Automatic Repair couldn’t repair your PC” with a mention of SrtTrail.txt means two things went wrong in sequence: Windows failed to boot, and then Windows’s own self-repair failed too. The file SrtTrail.txt is the log that the failed repair left behind, sitting at C:\Windows\System32\Logfiles\Srt\SrtTrail.txt — and it usually contains the single most useful clue in the whole situation.

That log typically names a specific failure. Common entries include “Boot critical file is corrupt” with an error code like 0x32 (a corrupted system file), 0x490 (a corrupted boot file), or a named driver that failed to load. Each code points at a different fix, so reading the log first beats trying repair commands at random.

The reason this error traps people in a loop is structural: after a failed Automatic Repair, Windows reboots, tries to boot again, fails again, and lands right back in the same blue repair screen. Breaking the cycle means stepping outside it — booting into the Windows Recovery Environment (WinRE) from installation media and repairing the boot components by hand. If the laptop never reaches the repair screen on its own, force WinRE by holding the power button to interrupt boot three times in a row. For the broader picture of crashes that appear at power-on, see our guide on blue screen on startup in Windows 11 .

Why this happens

  • Corrupted Boot Configuration Data (BCD): The BCD store tells Windows where and how to start. If it gets damaged by a failed update, a power cut during shutdown, or disk corruption, Windows can’t find its own boot path and Automatic Repair can’t rebuild it automatically.
  • Damaged or missing boot files: Files like winload.exe and the EFI boot manager can be corrupted by bad updates or failing storage. Automatic Repair detects the damage but often lacks the pieces to reconstruct them.
  • Disk errors or a failing drive: Bad sectors in the boot partition produce exactly the errors logged in SrtTrail.txt. A drive that is physically degrading will defeat every software repair until the drive itself is replaced.
  • A faulty driver or Windows update: A new driver or cumulative update that writes bad data into the boot chain can prevent startup. This is the classic “it was fine yesterday” scenario.
  • Corrupted system files: Damage to the registry hives or core kernel files stops the boot early. The log usually flags these with 0x32-style codes.
  • Changed firmware settings: Switching SATA mode between AHCI and RAID, disabling Secure Boot, or a BIOS update that resets settings can make a previously working boot configuration unreadable.
  • Malware damage to boot components: Some infections deliberately damage the boot chain to survive. If the loop started after a suspicious download, treat the boot repair as necessary but also scan the system afterward.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Read the SrtTrail.txt log

Don’t skip this — the log tells you which fix to prioritize.

  1. From the Automatic Repair screen, click Advanced options > Troubleshoot > Advanced options > Command Prompt.
  2. Type notepad and press Enter to open Notepad with a GUI.
  3. In Notepad, use File > Open and navigate to C:\Windows\System32\Logfiles\Srt\SrtTrail.txt. (Your drive letter may differ in WinRE — try D: or E: if C: doesn’t have Windows.)
  4. Open the file and scroll to the bottom. Look for the test result lines — the failed test name and error code (e.g., 0x490, 0x32) tell you whether you’re dealing with boot files, system files, or disk corruption.
  5. Note the error code, then close Notepad. You’ll use the command prompt again for the fixes below.

Fix 2: Run Startup Repair from installation media

The on-disk repair may be using corrupted repair tools. Fresh ones from USB media work better.

  1. On another PC, create Windows 11 installation media using the Windows 11 download page .
  2. Boot the problem laptop from the USB stick (change boot order in BIOS/UEFI, usually F12 for the boot menu).
  3. Choose your language, then click Repair your computer instead of installing.
  4. Go to Troubleshoot > Advanced options > Startup Repair and let it run once.
  5. If it succeeds, remove the USB and boot normally. If it fails, continue to Fix 3 — you now have a working WinRE command prompt from the media.

Fix 3: Rebuild the Boot Configuration Data

This fixes the most common SrtTrail.txt cause — a corrupted BCD.

  1. In the WinRE Command Prompt, run:

    bootrec /fixmbr
bootrec /fixboot

  2. If /fixboot returns “Access is denied” (common on UEFI systems), rebuild manually:

    diskpart
list disk
sel disk 0
list vol

  3. Find the FAT32 partition labeled EFI (usually 100–500 MB), note its volume number, then:

    sel vol <number>
assign letter=Z:
exit

  4. Then run:

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

    (Replace C: with your Windows drive letter in WinRE if different.)

  5. Type exit, remove the USB, and restart. Many SrtTrail.txt loops end right here.

Fix 4: Check the disk for errors

If the BCD rebuild fails or the loop returns, suspect the drive itself.

  1. Back in the WinRE Command Prompt, run:

    chkdsk C: /f /r

    Use your actual Windows drive letter. The /r flag finds bad sectors and recovers readable data — on large drives this can take hours, so let it finish.

  2. When it completes, check the summary: “bad sectors” found means the drive is degrading. A handful of repaired sectors is tolerable; hundreds is a dying drive.

  3. If chkdsk reports unfixable errors, stop doing software repairs — back up the drive (connect it to another PC if needed) and replace it. No boot command can fix failing hardware.

Fix 5: Repair system files offline

Corrupted kernel files or registry hives need the offline System File Checker.

  1. In the WinRE Command Prompt, run:

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

  2. Let it complete — it will report whether it found and repaired corruption.

  3. If SFC can’t fix everything, run DISM offline:

    DISM /Image:C:\ /Cleanup-Image /RestoreHealth

    This needs either the WinRE network stack or an install.wim source, so it may fail without installation media — retry with the USB media’s sources if needed.

  4. Restart and test. If the log earlier showed a 0x32-style system-file error, this fix targets exactly that.

Fix 6: Undo the last update and restore the system

When the loop started right after an update, roll it back.

  1. From Advanced options, open Uninstall Updates and remove the latest quality update first, then the feature update if the quality removal doesn’t help.
  2. Next, try System Restore from the same Advanced options screen. Pick a restore point dated before the loop began.
  3. If you use third-party driver updaters or recently installed a driver, restore points are the fastest way to unwind driver damage too.
  4. Restart after each change and test — don’t stack changes blindly. See also BAD_SYSTEM_CONFIG_INFO fixes .

Fix 7: Reset Windows while keeping your files

If nothing above works, a reset reinstalls Windows without (usually) touching personal files.

  1. From the repair screen, go to Troubleshoot > Reset this PC.
  2. Choose Keep my files, then Local reinstall if offered (cloud download needs a working network in WinRE).
  3. Let it run — this takes 30–90 minutes and reinstalls all system files, drivers’ base set, and boot components from scratch.
  4. After the reset, install drivers from your manufacturer’s support page (Dell, HP, or Lenovo) rather than restoring old ones, since a bad driver may have caused the original loop.

Closing

The SrtTrail.txt loop looks catastrophic but is usually a boot-configuration problem, not a dead laptop — most cases resolve at Fix 3 or Fix 4. The habit that prevents recurrence is simple: keep regular system restore points enabled, don’t interrupt updates mid-install, and treat repeated disk errors as a hardware warning rather than a software annoyance. If the same loop returns within weeks of a successful repair, that recurrence is telling you the drive is failing, and replacing it is cheaper than fighting it.

Frequently asked questions

What is the SrtTrail.txt file?
SrtTrail.txt is the log Windows Automatic Repair writes when it tries and fails to fix a boot problem. It lives at C:\Windows\System32\Logfiles\Srt\SrtTrail.txt and usually names the culprit — a corrupted boot file, a failing drive, or a bad driver. You can read it from the recovery command prompt.
Can I fix the SrtTrail.txt error without losing my files?
Yes, in most cases. Rebuilding the boot configuration, running chkdsk, and repairing system files don’t touch your personal data. Only a full reset or clean install risks data, and even the reset offers a keep-my-files option. Back up first if you can reach your files from recovery.
Why does Automatic Repair keep looping instead of fixing things?
Automatic Repair only fixes a narrow set of problems — mostly missing or damaged boot files it can rebuild automatically. If the cause is disk corruption, a driver conflict, or a deeper system-file problem, the repair fails silently and Windows reboots back into the same repair screen.
How long does the SrtTrail.txt repair process take?
Reading the log takes minutes. Rebuilding boot files takes five to ten minutes. A chkdsk with the /r flag on a large drive can take several hours. A reset with file preservation usually takes thirty to ninety minutes depending on drive speed and data volume.