Fixes / Windows · Checked September 30, 2026

Windows Automatic Repair couldn't repair your PC: fixes

Short answer

Windows failed to start, ran Startup Repair on its own, and that tool could not find or fix the cause. Your files are usually still there. Select Advanced options > Troubleshoot > Advanced options > Uninstall Updates and remove the latest quality update, especially if the problem started after an update. If that fails, try System Restore, then chkdsk and SFC from Command Prompt.

What this message means

When Windows fails to start (usually after two failed boots in a row), it opens the Windows Recovery Environment (WinRE) and runs Startup Repair on its own. This message means Startup Repair ran its checks and could not fix the problem. It records what it tried in the log file SrtTrail.txt. The message does not mean your data is gone, and it does not name the cause. Typical causes are a bad update or driver, damaged system files, a corrupted boot configuration (BCD), file system errors or a failing drive. The tools under Advanced options work on Windows 10 and Windows 11 and can usually get the PC starting again without reinstalling.

Common causes

Cause	How to tell
A Windows update or driver install that didn't finish or that broke startup	The loop started right after a restart for updates, or after 'Working on updates' or 'Undoing changes' screens. Safe Mode may still work.
Corrupted Windows system files or registry	Windows shows the logo and spinning dots, then restarts or shows a blue screen before reaching the sign-in screen. SrtTrail.txt often mentions a specific file under C:\Windows\System32, or says 'Registry is corrupt'.
Damaged boot configuration (BCD) or boot sector	Windows barely starts. You may get a black screen, 'Boot Configuration Data missing' or 'An operating system wasn't found' before recovery opens. SrtTrail.txt mentions the boot manager or BCD.
File system errors or a failing drive	The PC was shut down during a power cut or forced off. Startup is very slow, the drive clicks, or chkdsk reports bad sectors. The drive may be missing or flagged in the UEFI/BIOS screen.
Third-party security software, disk encryption or a recently added device	The problem started after installing antivirus, disk encryption, a new SSD, RAM or a USB/dock device. Unplugging extra devices sometimes lets the PC start.
BitLocker blocking the repair tools	Advanced options asks for a 48-digit BitLocker recovery key. Or Command Prompt shows the Windows drive as locked or unreadable.

How to fix it

1. Restart once with extra devices unplugged

On the error screen, select Shut down.
Unplug everything except the keyboard, mouse and monitor: USB drives, external disks, docks, printers, SD cards and phones.
Turn the PC on. If Windows starts, plug devices back in one at a time to find the one causing the problem.
If you get the same message again, go on to the next fix.

2. Uninstall the latest update

Windows 10 and Windows 11

On the error screen, select Advanced options > Troubleshoot > Advanced options > Uninstall Updates.
Select Uninstall latest quality update (the monthly update) and follow the prompts. If you use BitLocker, enter your recovery key when asked (you can find it at aka.ms/myrecoverykey from another device).
Restart the PC.
If the error comes back, return to Uninstall Updates and select Uninstall latest feature update, if that option is listed.

3. Roll back with System Restore

Windows 10 and Windows 11. On newer Windows 11 builds the menu may also show Point-in-time restore, which rolls back apps, settings and files to an automatic restore point.

Select Advanced options > Troubleshoot > Advanced options > System Restore (or Point-in-time restore if that is what you see).
Choose your Windows account and enter its password if asked.
Pick a restore point dated before the problem started, then select Next > Finish.
Wait for the restore to finish and the PC to restart. If it says there are no restore points, skip to the next fix.

4. Boot into Safe Mode and remove the recent change

Select Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
When the list appears, press 4 (or F4) for Safe Mode or 5 (or F5) for Safe Mode with Networking.
If Windows starts, uninstall any recently installed antivirus, driver or app from Settings > Apps.
Open Device Manager and roll back or uninstall any driver you recently updated, then restart normally.

5. Check the drive and system files from Command Prompt

Select Advanced options > Troubleshoot > Advanced options > Command Prompt.
Find the Windows drive. In recovery it is not always C:. Type dir C:\Windows and press Enter. If you get 'File Not Found', try D:, E: and so on.
Run chkdsk C: /f /r (replace C: with the drive you found). This can take an hour or more on a large drive.
Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (same drive letter).
Type exit, then select Continue to start Windows.

6. Rebuild the boot configuration

Mainly for the older BIOS/MBR setup. On UEFI PCs, bootrec /fixboot often returns 'Access is denied'. That is common, so continue with the other commands.

Open Command Prompt from Advanced options > Troubleshoot > Advanced options.
Run bootrec /fixmbr, then bootrec /fixboot.
Run bootrec /scanos, then bootrec /rebuildbcd. Type Y if it offers to add a Windows installation to the boot list.
Restart. If you still get the recovery loop, run bcdedit /set {default} recoveryenabled no to stop the loop and see the real error message.
When the problem is fixed, turn recovery back on with bcdedit /set {default} recoveryenabled yes.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

Read the log for the actual cause. In Command Prompt, run notepad and use File > Open to browse to C:\Windows\System32\LogFiles\Srt\SrtTrail.txt (set the file type to All Files). The 'Root cause found' line usually names the file, driver or disk at fault. If chkdsk reports bad sectors or the drive is missing in the UEFI/BIOS, copy your files off using a Linux live USB or by putting the drive in another PC, then replace the drive. If the hardware is fine, use Advanced options > Troubleshoot > Reset this PC > Keep my files, or boot from Windows installation media to reinstall. For a work or school PC, or if you don't have the BitLocker recovery key, contact your IT department or the PC maker's support before you reset anything.

Questions people ask

Will I lose my files if I fix Automatic Repair couldn't repair your PC?

Startup Repair, Uninstall Updates, System Restore, chkdsk, SFC and bootrec do not delete personal files. Only Reset this PC with 'Remove everything', or a clean reinstall, erases them. If the drive itself is failing, back up first.

What is SrtTrail.txt?

It is the log that Startup Repair writes at C:\Windows\System32\LogFiles\Srt\SrtTrail.txt. It lists each test it ran and, when it can tell, the root cause, such as a bad driver file or a corrupt registry.

How do I stop the Automatic Repair loop?

Open Command Prompt from Advanced options and run bcdedit /set {default} recoveryenabled no. This stops Windows from opening recovery at every boot, but it does not fix the cause, so turn recovery back on with recoveryenabled yes once the PC starts properly.

Why does it ask for a BitLocker recovery key?

The drive is encrypted, and recovery tools need the key to unlock it. If you sign in with a Microsoft account, you can find the key at aka.ms/myrecoverykey from another device. Work PCs usually get it from IT.

Can a failing hard drive or SSD cause this error?

Yes. If chkdsk finds bad sectors, if repairs keep failing, or if the drive is missing in the UEFI/BIOS, the drive is probably failing. Copy your data off and replace it before you reinstall Windows.

Sources

Related errors