The SrtTrail.txt error is Windows 11’s way of admitting defeat: “Automatic Repair couldn’t repair your PC,” with a pointer to a log file at C:\Windows\System32\Logfiles\Srt\SrtTrail.txt. After a Windows update, this almost always means the update damaged your boot files — the Boot Configuration Data, the bootloader, or the disk structures Windows needs to start.

You’re not stuck, though. Automatic Repair failing just means you need to run the repairs manually — the same tools, with you giving the orders. Every fix below uses the recovery environment’s Command Prompt, and none of them touch your personal files.

Why this happens

  • The update corrupted the Boot Configuration Data (BCD). The BCD tells Windows where and how to boot; update-time writes can leave it broken.
  • Bootloader files were damaged. An interrupted update can leave winload.efi or bootmgr in a half-written state.
  • Disk errors in the boot partition. Bad sectors or file system corruption in the EFI or system partition break the boot chain.
  • The update conflicted with the disk layout. Dual-boot setups, BitLocker encryption, or unusual partitioning can confuse the update’s boot modifications.
  • Corrupted system files. Damage to core Windows files that Automatic Repair’s automated checks can’t fix.
  • A failing drive. If the storage itself is dying, boot files keep corrupting no matter how many times they’re repaired.

How to fix it

Work through these in order, from the quickest and safest fixes to the deeper ones. Stop once Windows boots normally.

Fix 1: Break the loop and try the simple exits first

Before running commands, make sure you’re not missing an easy out.

  1. On the Automatic Repair screen, click Advanced options.
  2. Try Continue (exit and continue to Windows 11) — occasionally the loop is a one-time glitch and Windows boots fine.
  3. If it loops back, go to Troubleshoot > Advanced options > Startup Settings > Restart and try Safe Mode (press 4). If Safe Mode works, uninstall the recent update from Settings > Windows Update > Update history > Uninstall updates and restart.
  4. If neither works, continue below — you’ll be using Troubleshoot > Advanced options > Command Prompt.

Fix 2: Rebuild the boot files with bootrec

This repairs the most common update-caused boot damage.

  1. Open Command Prompt from Troubleshoot > Advanced options.
  2. Run these commands one at a time, pressing Enter after each: bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
  3. If fixboot returns “Access is denied,” run these first: diskpart list vol Note the volume number of the EFI partition (FAT32, ~100MB), then: sel vol <number> assign letter=Z: exit bcdboot C:\Windows /s Z: /f UEFI
  4. Type exit, choose Continue, and test the boot. Our Startup Repair guide explains what these commands do in more detail.

Fix 3: Check the disk for errors

Rule out disk corruption as the reason boot files keep breaking.

  1. Open the recovery Command Prompt again.
  2. Run chkdsk C: /f /r — the /r flag finds bad sectors and recovers readable data. This can take a while on large drives; let it finish.
  3. If chkdsk reports unrecoverable errors or bad sectors, back up your data as soon as you can boot — the drive may be failing, and no boot repair will hold on dying storage.
  4. After chkdsk completes, type exit and try booting.

Fix 4: Run offline SFC and DISM repairs

Fix corrupted Windows system files from outside the broken installation.

  1. In the recovery Command Prompt, run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
  2. Then run: DISM /Image:C:\ /Cleanup-Image /RestoreHealth
  3. Type exit and choose Continue to boot. These offline repairs fix the system-file damage that Automatic Repair’s automated pass misses.

Fix 5: Restore the registry from backup or use System Restore

Roll back to before the update broke things.

  1. In the recovery environment, go to Troubleshoot > Advanced options > System Restore.
  2. Choose a restore point dated before the update and let it run — this restores system files, drivers, and registry without touching personal files. Our System Restore walkthrough covers what to do when restore points are missing.
  3. If System Restore isn’t available, you can restore the registry manually from the backup in C:\Windows\System32\config\RegBack (if present) — but try System Restore first; it’s safer.

Fix 6: Disable the automatic repair loop

If Windows itself is fine but keeps triggering the repair screen, stop the trigger.

  1. Open the recovery Command Prompt.
  2. Run: bcdedit /set {default} recoveryenabled No
  3. Also try: bcdedit /set {default} bootstatuspolicy ignoreallfailures
  4. Type exit and boot. If Windows starts normally now, the loop was a false trigger — but still run Fix 4’s repairs, since something originally tripped the detector.

Fix 7: Reset Windows or clean-install from USB media

When the boot structures are damaged beyond command-line repair.

  1. Back up your files first — boot from a Linux USB or connect the drive to another PC if Windows won’t start at all.
  2. In the recovery environment, go to Troubleshoot > Reset this PC > Keep my files with Cloud download.
  3. If the reset fails, create Windows 11 installation media on another computer from the Windows 11 download page , boot from the USB, and choose Install now with a clean install.
  4. Persistent boot failure after a clean install means the drive itself is likely failing — replace it. Microsoft’s Windows support hub has the full recovery documentation.

Closing

The SrtTrail.txt screen looks like a dead end, but it’s really just Automatic Repair asking for manual help. Rebuilding the BCD with bootrec, checking the disk, and running offline SFC repairs resolve it for the large majority of people — all without touching personal files. And if the repairs keep failing on the same drive, believe the evidence: back up and replace the storage before it takes your data with it.

Frequently asked questions

What is the SrtTrail.txt error?
It’s not a blue screen in the classic sense — it’s the ‘Automatic Repair couldn’t repair your PC’ screen, which points you to the log file at C:\Windows\System32\Logfiles\Srt\SrtTrail.txt. It means Windows tried to fix a boot problem automatically and failed, usually after an update damaged the boot files or disk.
Why does it happen after a Windows 11 update?
Updates rewrite boot-critical files and the Boot Configuration Data (BCD). If the update is interrupted, or if it conflicts with your disk layout (especially dual-boot or encrypted setups), the boot files end up broken and Automatic Repair can’t piece them back together on its own.
Will fixing this delete my files?
No. The boot repair commands (bootrec, bcdedit, chkdsk) only touch boot and system files — your documents, photos, and apps are untouched. Only a full Reset with ‘Remove everything’ deletes data, and that’s clearly labeled as a separate, last-resort option.
What if Automatic Repair keeps looping no matter what?
Break the loop by booting from Windows installation media (USB) instead of the built-in recovery — it gives you the same Command Prompt tools without relying on the damaged recovery partition. The steps below work identically from either.