If your laptop boots into Automatic Repair, fails, and mentions SrtTrail.txt, you are in a boot loop — Windows cannot start, and its self-repair could not fix whatever is stopping it. The good news is that the log file usually names the problem, and the repair commands are straightforward. If your laptop boots into Automatic Repair, fails, and mentions SrtTrail.txt, you are in a boot loop — Windows cannot start, and its self-repair could not fix whatever is stopping it. The good news is that the log file usually names the problem, and the repair commands are straightforward.

Everything below runs from the recovery environment, which you can reach even though Windows will not boot. Your files are almost certainly intact; it is the boot machinery that needs fixing. Everything below runs from the recovery environment, which you can reach even though Windows will not boot. Your files are almost certainly intact; it is the boot machinery that needs fixing.

Why this happens

  • Corrupted Boot Configuration Data (BCD). The BCD store tells Windows how to boot; damage here stops startup cold.
  • Damaged boot files. Corruption in the EFI partition or bootmgr breaks the boot chain.
  • A failed Windows update. Interrupted updates leave the system half-migrated and unbootable.
  • Failing system drive. Bad sectors on boot-critical files produce exactly this loop.
  • Corrupted system files. Damage to drivers Windows loads at boot halts startup.
  • New hardware or driver conflict. A storage driver change can make the boot drive unreachable.

How to fix it

Work through these in order, from the quickest and most likely fixes to the deeper ones. Stop as soon as the crashes stop.

Fix 1: Reach the recovery command prompt

Every fix below starts here — this is your workshop. Every fix below starts here — this is your workshop, and reaching it is the only hard part of the whole process.

  1. On the Automatic Repair screen, click Advanced options > Troubleshoot > Advanced options > Command Prompt.
  2. If the laptop just loops without offering options, force it: hold the power button during the Windows logo three times in a row.
  3. The command prompt opens at X:\Sources — your Windows drive may be D: or E: here, not C:. Find it with diskpart, then list volume.

Fix 2: Read the SrtTrail.txt log

The log often names the exact broken component — five minutes here can save an hour. The log often names the exact broken component — five minutes here can save an hour of blind repair attempts.

  1. Run notepad C:\Windows\System32\LogFiles\Srt\SrtTrail.txt (adjust the drive letter to your Windows drive).
  2. Scroll to the bottom and look for the root-cause section — phrases like ‘Boot critical file c:\windows\system32\drivers*.sys is corrupt’ name your target.
  3. Write down any filenames mentioned; they guide which repairs matter most.

Fix 3: Rebuild the BCD and boot files

The most common fix for this loop — reconstructs the entire boot configuration. The most common fix for this loop — reconstructs the entire boot configuration from scratch, which is what Automatic Repair was trying and failing to do.

  1. In the recovery command prompt, run these in order:
  2. bootrec /fixmbr
  3. bootrec /fixboot (if ‘Access denied’, use the bcdboot method below instead)
  4. bootrec /rebuildbcd
  5. If fixboot fails, run bcdboot C:\Windows /s S: /f UEFI where S: is your EFI partition letter (find it in diskpart > list volume, looking for the FAT32 partition).
  6. Type exit and choose Continue to restart.

Fix 4: Run offline SFC and CHKDSK

Repairs corrupted system and boot files from outside the broken Windows. Repairs corrupted system and boot files from outside the broken Windows — SFC is far more effective offline than online for boot-critical files.

  1. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (adjust C: to your Windows drive letter).
  2. Then run chkdsk C: /f /r on the Windows drive and let the full scan complete.
  3. Restart and test. If SFC repaired boot drivers named in the SrtTrail log, the loop often ends here. For background on the underlying stop codes, see our blue screen guide .

Fix 5: Uninstall the latest update from recovery

If the loop started right after an update, remove it surgically. If the loop started right after an update, remove it surgically — the recovery environment lets you uninstall updates without booting.

  1. Go to Troubleshoot > Advanced options > Uninstall Updates.
  2. Choose Uninstall latest quality update first and restart to test.
  3. If still looping, return and Uninstall latest feature update.
  4. Once booted, pause updates for two weeks while the fixed update ships.

Fix 6: Try System Restore

Rolls back system files, drivers, and registry to a working point without touching personal files. Rolls back system files, drivers, and registry to a working point without touching personal files — the gentlest effective repair.

  1. Go to Troubleshoot > Advanced options > System Restore.
  2. Pick the most recent restore point from before the loop began.
  3. Let it complete and restart. If no restore points exist, move to the next fix — and enable System Protection once you are back in Windows so you have them next time.

Fix 7: Check drive health and consider a repair install

When software repairs fail, verify the hardware underneath — Microsoft’s Windows support hub covers the recovery environment options in detail. When software repairs fail, verify the hardware underneath — a dying drive explains every repair that ‘should have worked’.

  1. From the recovery prompt, chkdsk results showing many bad sectors mean the drive is dying — back up via a live USB or by slaving the drive, then replace it.
  2. If the drive is healthy but Windows still will not boot, do an in-place upgrade from installation media (boot the USB, choose Upgrade, keep files) — or a clean install as the final option.
  3. Our Safe Mode guide can help you reach a working desktop for backups if the system partially boots.

Closing

The SrtTrail.txt loop looks dire — Windows cannot boot and its own repair gave up — but it is usually a boot-configuration or file-corruption problem that the recovery command prompt fixes in under an hour. Read the log, rebuild the BCD, repair the files, and your files and Windows are typically both waiting on the other side. Once you are back in Windows, turn on System Protection and create a restore point — the next boot problem will be a ten-minute fix instead of an hour-long one.

Frequently asked questions

What is the SrtTrail.txt error?
It is not a blue screen stop code — it is the log file Windows’ Automatic Repair writes when it fails to fix a boot problem: C:\Windows\System32\LogFiles\Srt\SrtTrail.txt. The ’error’ is that Automatic Repair ran, could not repair the startup issue, and is telling you where it logged the details.
Why is my laptop stuck in an Automatic Repair loop?
Something prevents Windows from booting — corrupted boot files, a damaged BCD store, a failing drive, or a bad update — and Automatic Repair cannot fix it on its own, so it retries every boot. The loop continues until the underlying cause is repaired manually.
Can I fix SrtTrail.txt errors without losing my files?
Almost always, yes. The boot-repair commands below (bootrec, bcdboot, chkdsk, SFC offline) fix the startup machinery without touching your personal files. Only a clean reinstall threatens data — and that is the last resort, not the first step.
How do I read the SrtTrail.txt log itself?
From the recovery command prompt, open it with notepad C:\Windows\System32\LogFiles\Srt\SrtTrail.txt. Near the end, look for lines about the root cause — often a corrupted file name or a failed test like ‘Boot critical file is corrupt’. That name tells you what to repair.