Few things feel worse than turning on your laptop and watching it loop forever through “Preparing Automatic Repair” before landing on a blue screen mentioning SrtTrail.txt. That file is just the log of Automatic Repair’s failed attempt, but the loop it represents is real: Windows cannot start, and its built-in repair cannot fix whatever is stopping it.

The good news is that this error is very repairable. The vast majority of SrtTrail.txt loops are caused by a damaged boot configuration or corrupt system files, both of which you can fix from the recovery environment with a handful of commands. Work through these fixes in order, and back up first if the drive might be failing.

Why this happens

  • Corrupted Boot Configuration Data (BCD). The BCD tells Windows where and how to start; if it is damaged by a failed update or power cut, booting is impossible.
  • Damaged boot sector or EFI partition. Disk errors in the boot area produce the exact symptoms you are seeing.
  • Corrupt system files. If files Windows needs during startup are damaged, Automatic Repair detects the failure but cannot always repair it.
  • Failing hard drive or SSD. Bad sectors in critical areas cause repeated, unfixable boot failures; this is the case to rule out early.
  • Interrupted Windows update. A feature update that was cut off mid-install can leave the system in a half-updated, unbootable state.
  • Driver conflicts at boot. A bad storage or display driver loaded at startup can crash the boot process before the desktop appears.
  • Malware damage to boot files. Some infections deliberately damage boot components, leaving repair tools chasing their tails.

How to fix it

Work through these in order, testing for stability after each fix before moving on.

Fix 1: Rebuild the BCD and repair boot files from recovery

This fixes the majority of SrtTrail.txt loops.

  1. On the blue Automatic Repair screen, click Advanced options.
  2. Choose Troubleshoot then Advanced options then Command Prompt.
  3. Run these commands one at a time, pressing Enter after each: bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd
  4. If fixboot reports access denied, run bcdboot C:\Windows /s S: /f UEFI after identifying your EFI partition letter with diskpart then list vol.
  5. Type exit, choose Continue to restart, and see whether Windows boots.

Fix 2: Run CHKDSK to repair disk errors

Bad sectors in the boot area will defeat every other repair until they are handled.

  1. From the recovery Command Prompt, run chkdsk C: /f /r /x.
  2. The scan can take a long time on large drives; let it finish without interrupting it.
  3. If CHKDSK reports bad sectors it could not repair, treat the drive as failing and prioritize data backup.
  4. Restart normally after the scan completes.

Fix 3: Run SFC and DISM from the recovery environment

Repair corrupted system files while Windows is offline.

  1. In the recovery Command Prompt, run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows.
  2. Wait for the scan to complete; it checks the offline Windows installation.
  3. If SFC cannot repair everything, run DISM /Image:C:\ /Cleanup-Image /RestoreHealth (this needs internet or a Windows ISO as source in some cases).
  4. Type exit and restart.

Fix 4: Disable early-launch anti-malware and automatic restart

Sometimes a driver loaded at boot is the actual crasher.

  1. From Advanced options, choose Startup Settings then Restart.
  2. Press 8 to Disable early launch anti-malware protection and test booting.
  3. If that fails, return to Startup Settings and press 4 for Safe Mode.
  4. In Safe Mode, open Device Manager and roll back or uninstall the most recently updated driver, especially storage or display drivers.
  5. Restart normally.

Fix 5: Use System Restore to roll back

If a restore point exists from before the loop began, this is the fastest fix.

  1. From Advanced options, choose System Restore.
  2. Pick the most recent restore point dated before the problem started.
  3. Let the restore complete; the laptop will restart.
  4. If no restore points exist, move on to the next fix.

Fix 6: Check the drive’s health decisively

A dying drive explains loops that survive every repair.

  1. From the recovery Command Prompt, run wmic diskdrive get status (or check SMART data via your manufacturer’s diagnostic boot tool).
  2. Download your drive maker’s bootable diagnostic if you have another PC available.
  3. If the drive reports failing health, stop repairing and back up immediately: connect the drive to another PC via a USB adapter and copy your files.
  4. Replace the drive, then reinstall Windows from the Windows 11 download page .

Fix 7: Reset or clean-install Windows

When the boot files are damaged beyond repair, a fresh start is the reliable path.

  1. From Advanced options, choose Troubleshoot then Reset this PC.
  2. Try Keep my files first if the option is available in your recovery environment.
  3. If the reset fails or the loop persists, create installation media on another PC and perform a clean install.
  4. After reinstalling, update drivers from your laptop maker’s site; for Microsoft’s own recovery guidance, see Windows support .

Related reading: our guide to SrtTrail.txt errors after a Windows 11 update and the general blue screen after a Windows 11 update walkthrough cover overlapping territory.

Closing

The SrtTrail.txt loop looks catastrophic, but it is usually just a broken boot configuration waiting for three commands to set it right. Start with the BCD rebuild, check the disk, repair the system files, and only reach for a reinstall when the hardware and repairs both tell you there is no other way. And once you are booting again, set up regular backups, because the one lesson every Automatic Repair loop teaches is that a bootable system is never guaranteed.

Frequently asked questions

What is the SrtTrail.txt error on Windows 11?
It is the log file Automatic Repair writes when it tries, and fails, to fix a startup problem. Seeing a message about SrtTrail.txt means Windows could not boot normally and its self-repair also failed. The log itself is not the problem; it is a record of the failure. The real cause is usually a damaged boot configuration, corrupt system files, or a failing drive.
Why is my PC stuck in an Automatic Repair loop?
Automatic Repair runs, cannot fix the underlying damage, and reboots back into itself on every start. This happens when the Boot Configuration Data is broken, critical boot files are corrupt, or the disk has bad sectors in the system partition. Breaking the loop requires repairing the boot files manually from the recovery environment.
Will fixing SrtTrail.txt delete my files?
The repair steps themselves, such as rebuilding the BCD or running SFC from recovery, do not touch your personal files. They only rewrite boot and system files. However, if the cause is a dying drive, your data is already at risk, so back up what you can from the recovery command prompt or by connecting the drive to another PC before attempting aggressive repairs.
What if Startup Repair says it couldn't repair my PC?
That message just confirms Automatic Repair failed, which is exactly the SrtTrail.txt situation. Move past it: choose Advanced options, open Command Prompt, and run the boot repair commands in Fix 1 below. Most loops resolve at that stage without a reinstall.