What is Startup Repair?
Startup Repair is the first repair to try in the Windows Recovery Environment (WinRE) when Windows will not boot. It runs a series of checks on the boot path and the Windows installation, looking for problems such as missing or damaged boot files, a damaged boot configuration data (BCD) store and some disk and registry problems, then fixes what it can. It does not touch personal files, which makes it a low-risk first step.
When Startup Repair runs
- Automatically: after repeated failed boots, the PC shows "Preparing Automatic Repair" and "Diagnosing your PC". It then either restarts normally or reports that Automatic Repair could not repair the PC, with buttons to shut down or open Advanced options.
- On demand: open WinRE (Shift+Restart, Settings > System > Recovery > Advanced startup on Windows 11, or installation media and Repair your computer), then choose Troubleshoot > Advanced options > Startup Repair and select the Windows installation. On a BitLocker-protected drive, have the recovery key ready.
Reading the result
Startup Repair writes a log to C:\Windows\System32\LogFiles\Srt\SrtTrail.txt listing each test, its result and the root cause it found, if any. The failure screen usually shows this path. If every restart lands on the repair screen again, an Automatic Repair loop, Startup Repair cannot fix the underlying cause and you need to move on.
What it cannot fix
- Failed hardware, such as a dead drive or faulty RAM. If the firmware does not detect the drive at all, no Windows tool will help.
- Malware infections.
- Firmware settings: a wrong boot order, or a boot-mode mismatch where Windows was installed in UEFI mode but the firmware is set to Legacy/CSM, or the reverse. Fix these in the BIOS/UEFI setup.
- A badly damaged Windows installation that needs repairing or reinstalling.
If Startup Repair fails
- Uninstall Updates in WinRE if the trouble began right after an update.
- System Restore to a point from before the problem.
- Startup Settings to boot Safe Mode and remove a bad driver or program.
- Command Prompt for manual repairs:
bootrec /fixmbr(MBR disks with legacy BIOS boot),bootrec /fixboot,bootrec /rebuildbcd(scans for Windows installations and rebuilds the BCD), orbcdboot D:\Windowsto recreate boot files on a UEFI system, using whatever letter the Windows partition has in WinRE. Addchkdsk /ffor file-system errors and offlinesfcfor damaged system files. - Back up the user's data, then use a repair installation, Reset this PC or a reimage.
Startup Repair vs. similar tools
Startup Repair fixes the path that loads Windows. System Restore rolls back configuration changes such as drivers, updates and registry settings. sfc and DISM repair Windows system files and the component store. Reset this PC reinstalls Windows. When a boot fails, the usual order is Startup Repair first because it changes the least.
Startup Repair on the CompTIA A+ exam
Startup Repair belongs to the boot-problem scenarios of Core 2 (220-1202) objective 3.1. Know that it runs from WinRE, that Windows starts it automatically after failed boots, and that it is the low-risk step before manual commands. Cues: "BOOTMGR is missing", "Boot Configuration Data is missing" or an operating system not found error after a crash, think Startup Repair first, then bootrec. "No boot device" right after adding a drive or changing firmware settings, check boot order and boot mode first. A repeating Automatic Repair loop means trying Uninstall Updates, System Restore or Safe Mode next.