Startup Repair

On this page 7

Startup Repair is the automated diagnostic tool in the Windows Recovery Environment that examines why Windows cannot start and attempts to fix boot-blocking problems without touching personal files. Within Windows updates & recovery, it is the first line of defense when a PC fails to load the operating system after a power loss, a failed update, a driver change or disk corruption.

The tool runs the startrep.exe engine inside WinRE, applies a fixed sequence of diagnostic tests, and records every step in a log file. It repairs startup configuration and boot code, not damaged applications or lost data, which is why administrators treat it as a narrow but valuable instrument rather than a universal cure.

How Startup Repair diagnoses a failed boot

Startup Repair works by running a predefined chain of checks against the boot path, from firmware hand-off to the loading of the kernel. Each test compares the actual state of a component with the expected state and, when it finds a mismatch, applies a scripted remediation before moving to the next test.

Windows launches the tool automatically after two consecutive failed boots, when the boot manager detects that the previous startup did not complete. Administrators can also start it manually from Advanced startup, from a recovery drive or from installation media, under Troubleshoot, Advanced options, Startup Repair.

The following table lists the main diagnostic areas and what the tool does when it detects a fault in each one.

Area checkedTypical faultAutomatic action
Boot Configuration DataMissing or invalid BCD entriesRebuilds or corrects the BCD store
Boot sector and MBRDamaged boot code on BIOS systemsRewrites boot code
EFI system partitionMissing bootmgfw.efi filesRestores boot manager files
Disk metadataFile system inconsistenciesRuns a chkdsk-style check
System filesCorrupted boot-critical driversReplaces files from component store
Pending updatesInterrupted servicing operationReverts pending update actions
Registry hivesCorrupted SYSTEM hiveRestores from RegBack where available
Diagnostic areas checked by Startup Repair

Results are written to SrtTrail.txt in the \Windows\System32\Logfiles\Srt folder. That log lists each test, its result code and the root cause the tool identified, and it is the most useful artifact for deciding what to do next when the repair fails.

Problems Startup Repair can and cannot fix

The tool is effective against configuration and boot-code damage but cannot reconstruct missing data or replace failing hardware. Knowing that boundary saves hours, because repeated runs against an unfixable fault only produce the same message: Startup Repair could not repair your PC.

Fault typeLikely outcomeReason
Corrupted BCD storeUsually fixedBCD can be regenerated from disk layout
Overwritten boot sectorUsually fixedBoot code is standard and replaceable
Failed cumulative updateOften fixedPending actions can be rolled back
Faulty third-party driverSometimes fixedDepends on whether the driver is identified
BitLocker-locked volumeNot fixed without keyThe tool cannot read encrypted data
Failing SSD or HDDNot fixedPhysical damage needs hardware replacement
Malware in boot chainRarely fixedRequires dedicated offline scanning
Fault types and likely outcome

A BitLocker-protected system drive is a frequent source of confusion. WinRE prompts for the 48-digit recovery key before the tool can examine the volume, so organizations should make sure keys are escrowed in Microsoft Entra ID, Active Directory or a Microsoft account before an incident occurs.

Startup Repair compared with other recovery options

Startup Repair is the least invasive recovery option in WinRE because it changes only boot-related components. The other options in the same menu make broader changes, and choosing them in the right order preserves as much of the installation as possible.

OptionWhat it changesData impact
Startup RepairBoot files, BCD, pending actionsNo personal data affected
Uninstall updatesLatest quality or feature updateApps and files kept
System RestoreSystem files, registry, driversPersonal files kept, recent apps removed
Command Prompt repairManual bootrec, bcdboot, DISMDepends on commands used
Reset this PCReinstalls WindowsApps removed, files optionally kept
Recovery drive reinstallFull clean installationAll data on the drive erased
Recovery options ordered from least to most invasive

System Restore depends on a restore point created before the fault and rolls back a much wider set of changes. Reset this PC goes further and reinstalls the operating system. Startup Repair needs neither a restore point nor a reinstall, which is why it is listed first in the troubleshooting sequence.

Running Startup Repair and the manual alternatives

In practice, technicians run the tool two or three times before escalating, because one pass may fix one fault and expose another. When it keeps failing, the manual boot repair commands in the WinRE Command Prompt offer finer control.

  • bootrec /fixmbr and bootrec /fixboot rewrite boot code on legacy BIOS systems.
  • bootrec /rebuildbcd scans disks for Windows installations and adds them to the BCD store.
  • bcdboot C:\Windows /s S: /f UEFI recreates boot files on the EFI system partition.
  • chkdsk C: /f repairs file system errors on the Windows volume.
  • DISM /Image:C:\ /Cleanup-Image /RevertPendingActions cancels a stuck servicing operation.

These commands assume correct drive letter assignments inside WinRE, which often differ from those in the running system. Checking volumes with diskpart and list volume before issuing any repair command prevents writing boot files to the wrong partition.

Limitations and common mistakes

The most common mistake is treating Startup Repair as a general-purpose fix for a slow, unstable or infected system. The tool only addresses failures that occur before or during the loading of Windows; problems that appear after sign-in are outside its scope.

  • Automatic repair loops occur when the underlying fault cannot be fixed; the PC restarts into WinRE repeatedly.
  • Ignoring SrtTrail.txt wastes the diagnostic information the tool has already gathered.
  • Running repairs on a failing disk can accelerate data loss; image the drive first when SMART errors appear.
  • Disabling automatic recovery with bcdedit /set {default} recoveryenabled No hides the tool when it is needed.

In plain words

Startup Repair is like a mechanic who checks only why a car will not start. It looks at the key, the battery and the starter, but it does not repaint the doors or fix the radio.

When Windows refuses to load, this tool checks the small set of files that tell the computer how to begin. If one is missing or broken, it puts it back. Your documents and photos stay untouched, because the tool never works on them. If the real cause is a broken disk or a locked drive, it will say it could not help, and you move to the next recovery option.

A real-world example

An IT technician at a small accounting office receives a laptop that shows a spinning circle and then restarts after a power cut during a cumulative update. After two failed boots, the laptop opens the Windows Recovery Environment and runs Startup Repair automatically.

The first pass reports that it could not repair the PC. The technician opens SrtTrail.txt, which names a pending servicing operation as the root cause. From the Command Prompt, the technician runs the DISM command to revert pending actions, then launches Startup Repair again. The second pass rebuilds the BCD entry and finishes in about four minutes.

The laptop boots normally, the update reinstalls that evening, and the accountant loses no files and no applications. The whole recovery takes under thirty minutes, compared with the two hours a full reset would have required.