Protect your files before deep recovery work
Keep the laptop connected to power and disconnect unnecessary USB devices. If BitLocker asks for a recovery key, do not guess or format the drive. Retrieve the correct key from the Microsoft, work or school account that manages the device. Back up important files whenever recovery tools still provide access.
Identify the exact Automatic Repair failure
| What you see | What it usually tells you |
|---|---|
| “Preparing Automatic Repair” never finishes | Recovery itself may be hanging because of storage, file-system, update or hardware trouble. |
| “Diagnosing your PC” returns to the same screen | Windows detects repeated startup failure but cannot correct the underlying cause. |
| “Startup Repair couldn’t repair your PC” | Automatic fixes were attempted; targeted recovery is now required. |
| Recovery appears after an update | A recent quality update, driver or incomplete servicing operation is a strong lead. |
| The SSD disappears or recovery also freezes | Storage, memory, overheating or power instability becomes more likely. |
1. Power-cycle once and remove external devices
Shut the PC down, disconnect docks, external drives, printers, adapters and non-essential USB devices, then hold the power button for about 15 seconds while it is off. Reconnect only power and try one normal start.
If Windows starts, reconnect devices one at a time. Do not repeatedly force shutdowns during a clearly active update; use this step when the machine is genuinely trapped in the same recovery cycle.
2. Open the correct Windows Recovery options
From the Automatic Repair screen, select Advanced options → Troubleshoot → Advanced options. If the screen never appears, repeated failed starts may trigger Windows Recovery Environment, or you can boot from official Windows 11 installation media and choose Repair your computer.
Run Startup Repair once. If it gives the same result again, stop repeating it and continue with the targeted options below.
3. Remove the update that triggered the loop
Select Uninstall Updates, then try Uninstall latest quality update first when the problem began after a normal cumulative update. A feature-update rollback is appropriate only when the failure started immediately after a Windows version upgrade and the option is available.
Do not remove updates randomly when the timing does not match. If removal fails, note the message rather than cycling through the same option.
4. Use System Restore when a suitable point exists
Choose System Restore, select the Windows installation and use a restore point from before the startup failure. Review the affected programs before confirming. System Restore rolls back system files, drivers, registry state and installed applications; it is not intended to delete personal documents.
5. Test Safe Mode and remove the recent cause
- Choose Startup Settings → Restart.
- Press the key for Enable Safe Mode.
- If Windows opens, uninstall the driver, antivirus, disk utility or application added immediately before the failure.
- Check that the Windows drive has usable free space and restart normally.
If Safe Mode works but normal startup does not, the core installation can boot and a non-essential driver, service or startup program becomes a stronger suspect.
6. Repair system files from Safe Mode
When Safe Mode opens, run an elevated Terminal:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Let both commands finish and record their final messages. Online commands are safer here than blindly copying offline commands whose drive letters may differ inside recovery.
7. Check the Windows volume without risky guessing
In recovery, Windows may not use the drive letter you normally see. Use Command Prompt, enter diskpart, then list volume to identify the Windows volume by size, label and contents. Enter exit before other commands.
Run chkdsk C: /scan only after confirming the correct letter and when that mode is supported. Avoid immediately using aggressive repair switches on a drive that is clicking, disappearing, extremely slow or holding unbacked-up data; hardware failure needs a backup-first approach.
8. Repair boot configuration only when evidence points there
From recovery Command Prompt, bootrec /scanos can check whether Windows installations are detected. Modern UEFI systems store boot files on an EFI partition, so generic legacy-era command lists can be wrong for the machine.
If the Windows installation is detected but boot files are missing, follow Microsoft or the PC manufacturer’s UEFI-specific procedure. Do not format an EFI partition or run destructive partition commands as a trial-and-error fix.
9. Recognise when this is probably hardware
- The SSD is absent intermittently in BIOS/UEFI or recovery.
- Automatic Repair, installation media and diagnostics all freeze or restart.
- The device reports SMART, memory or storage errors.
- The problem began after a drop, liquid exposure, RAM/SSD change or overheating event.
Run the manufacturer’s built-in storage and memory diagnostics. Reinstalling Windows cannot stabilise failing storage, memory or power.
10. Reset or reinstall only as the final software step
Reset this PC → Keep my files aims to retain personal files but removes applications and resets settings. Cloud download needs a reliable connection and still does not replace a backup. If Reset fails repeatedly, clean installation may be considered after data backup and hardware checks.
A reset that freezes, restarts or cannot see the drive is evidence to stop treating the issue as ordinary Windows corruption.
Avoid these common mistakes
- Do not keep running Startup Repair when it returns the identical failure.
- Do not format EFI, recovery or BitLocker-protected partitions to “make them work.”
- Do not paste offline repair commands without confirming the Windows drive letter.
- Do not reset the PC before considering backup and drive health.
Frequently asked questions
Why is Windows 11 stuck in Automatic Repair?
Common causes include an interrupted update, damaged system files, a boot configuration problem, a faulty driver, file-system corruption, low free space or a failing SSD.
What does SrtTrail.txt mean?
SrtTrail.txt is a Startup Repair diagnostic log. Its presence does not prove one specific cause; use any named file or error alongside recent changes and hardware symptoms.
Will Startup Repair delete my files?
Startup Repair is intended to repair startup components without deleting personal files, but important data should still be backed up before reset, reinstall or disk repair.
Technical steps align with Microsoft guidance for Windows Recovery Environment, Startup Repair, Startup Settings, update removal, System Restore, DISM, SFC and Reset this PC.
Official references
For platform-specific behavior and recovery options, compare this guide with the current documentation from the relevant official source.