Windows 10’s version of the SrtTrail.txt nightmare is identical in spirit to Windows 11’s: Automatic Repair runs, fails, logs its failure to SrtTrail.txt, and reboots into the same failure. The screens look slightly different on Windows 10, but every fix below works on 10 exactly as described.

If you are staring at “Automatic Repair couldn’t repair your PC” right now, start at Fix 1.

Why this happens

  • Corrupted boot configuration data: Failed updates, power cuts, or bad shutdowns damage the BCD store so the bootloader cannot find Windows.
  • Damaged system files: Corrupted copies of winload.exe, registry hives, or boot drivers halt startup before the login screen.
  • Disk errors or failing drive: Bad sectors on the system partition are the most common hardware cause of a repeating SrtTrail loop.
  • Broken driver update: A faulty storage, chipset, or graphics driver that loads at boot blue-screens the machine every time.
  • Interrupted Windows 10 update: Feature updates (like 22H2) rewrite boot components; an interrupted update leaves the system unbootable.
  • Partition changes: Resizing partitions or removing a dual-boot OS breaks Windows boot entries.
  • Fast Startup corruption: Windows 10’s hybrid shutdown can preserve a corrupted session state across reboots, jamming the boot cycle.

How to fix it

Work through these in order, starting at Fix 1.

Fix 1: Stop the Automatic Repair loop

Break the cycle so you can attempt repairs and normal boots.

  1. On the “Automatic Repair couldn’t repair your PC” screen, click Advanced options.
  2. Go to Troubleshoot > Advanced options > Command Prompt.
  3. Run bcdedit /set {default} recoveryenabled No and press Enter.
  4. Type exit, press Enter, and choose Continue to restart.
  5. If Windows boots, still run Fixes 3 and 4 afterward — the underlying corruption remains. If not, continue to Fix 2.

The Windows 11 variant of this same loop is covered in our SrtTrail.txt after Windows 11 update guide if you have a dual-boot or upgraded machine.

Fix 2: Rebuild the boot configuration

The single most effective repair for this error.

  1. Return to Troubleshoot > Advanced options > Command Prompt.
  2. Run these one at a time: bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
  3. Answer Y when asked to add the installation to the boot list.
  4. If fixboot reports “Access is denied”: run diskpart → list vol → find the FAT32 EFI partition → select vol N → assign letter=Z: → exit → then bcdboot C:\Windows /s Z: /f UEFI.
  5. Restart and test.

Fix 3: Run CHKDSK on the Windows drive

Disk-level errors are a leading cause — verify the drive’s health.

  1. In the recovery Command Prompt, confirm the Windows drive letter: diskpart → list vol → exit. In recovery mode it is often D: or E:, not C:.
  2. Run chkdsk C: /f /r (use the correct letter).
  3. Let it finish completely — large drives can take over an hour. Never interrupt it.
  4. Restart and attempt a normal boot.

Fix 4: Repair system files offline with SFC and DISM

For corrupted Windows components that survive a boot-record rebuild.

  1. From the recovery Command Prompt: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (Adjust the drive letter to your Windows volume.)
  2. Then: DISM /Image:C:\ /Cleanup-Image /RestoreHealth
  3. Restart. If Windows boots but behaves oddly, our Safe Mode boot guide — the steps are the same on Windows 10 — helps you continue troubleshooting from a minimal environment.

Fix 5: Try Safe Mode and uninstall the culprit update or driver

If Windows boots in Safe Mode, the core OS is fine and something loading at startup is the problem.

  1. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode.
  2. If Safe Mode works, open Settings > Update & Security > Windows Update > View update history > Uninstall updates and remove the most recent update.
  3. Open Device Manager (Win + X > Device Manager) and roll back any driver updated around the time the problem started (Properties > Driver > Roll Back Driver).
  4. Restart normally.

Fix 6: Use System Restore

Rolls system files and drivers back to a known-good point without touching personal files.

  1. Go to Troubleshoot > Advanced options > System Restore.
  2. Choose a restore point dated before the loop began.
  3. Let it complete and restart. Your documents are preserved; installed programs from after the restore point may need reinstalling.
  4. If no restore points exist, enable System Protection afterward (Control Panel > System > System Protection) so you have this safety net next time.

Fix 7: Reset Windows 10 keeping your files

The last resort before a clean install.

  1. From Troubleshoot, choose Reset this PC > Keep my files.
  2. Pick Cloud download for fresh Windows files (needs internet) or Local reinstall otherwise.
  3. Follow the prompts — expect 30-90 minutes.
  4. Afterward, install updates from Settings > Update & Security > Windows Update and check the Microsoft Windows support page if any update misbehaves.

Fix 8: Disable Fast Startup and rebuild from installation media

If the on-disk recovery environment is damaged, boot from Windows 10 installation media for a clean repair environment.

  1. On another PC, create Windows 10 installation media with Microsoft’s official Media Creation Tool for Windows 10.
  2. Boot the broken laptop from the USB (tap F12, F9, or Esc at power-on for the boot menu, depending on brand) and choose Repair your computer instead of Install.
  3. Open Command Prompt and re-run the boot rebuild: bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd.
  4. While you are there, disable Fast Startup’s hibernation state, which can jam reboots: run powercfg /h off to delete the hibernation file entirely.
  5. Remove the USB, restart, and let Windows boot normally. If it boots, re-enable hibernation later with powercfg /h on only if you actually use Hibernate — most laptop users do not need it.

Closing

Windows 10’s SrtTrail.txt loop is a solved problem with a clear playbook: disable the looping repair tool, rebuild the boot records, check the disk, and repair system files. Those four steps resolve the overwhelming majority of cases without touching your data. If the loop returns within days of a successful repair, stop and check the drive’s health seriously — a repeating SrtTrail loop is one of the classic early warnings of a drive that is about to fail outright.

Frequently asked questions

Can I fix SrtTrail.txt on Windows 10 without installation media?
Yes, in most cases. The recovery environment built into Windows 10 (reached via Advanced options on the repair screen) includes Command Prompt with bootrec, SFC, DISM, and CHKDSK — everything the main fixes need. Installation media is only required if the recovery partition itself is damaged or you need to do a fully clean reinstall.
Where is the SrtTrail.txt log file?
At C:\Windows\System32\Logfiles\Srt\SrtTrail.txt. From a recovery Command Prompt, open it with notepad C:\Windows\System32\Logfiles\Srt\SrtTrail.txt. The log lists which repair tests failed, but it rarely names the true root cause, so use it as a hint alongside the fixes in this guide.
How do I boot Windows 10 into Safe Mode from the repair screen?
Click Advanced options, then Troubleshoot, Advanced options, Startup Settings, and Restart. When the menu appears, press 4 for Safe Mode or 5 for Safe Mode with Networking. If Windows boots in Safe Mode, the problem is almost certainly a driver or startup program rather than core system damage.
Will 'Reset this PC' keep my files on Windows 10?
Yes, if you choose Keep my files. The reset reinstalls Windows 10 and removes your installed programs and settings, but preserves documents, photos, and other personal files in your user folders. It is the right last resort before a fully clean install — but try the command-line repairs first.