Startup Repair is the first tool Windows offers when your PC won’t boot — and also the most misunderstood. Many people run it five times hoping for a different result, or give up entirely when it says it couldn’t repair the PC. Used correctly, it’s a fast, safe first attempt that fixes a specific class of boot problems. This guide shows you how to get into it, use it properly, read its log when it fails, and know exactly what to do next.

Think of Startup Repair as triage, not surgery: it handles the common, safe fixes automatically and tells you (via its log) when the problem needs manual work.

Why this happens

  • Corrupt boot configuration data. The BCD store is damaged and Windows can’t find its own startup files.
  • Damaged boot sector or EFI files. The code that hands off from firmware to Windows is broken.
  • Missing critical system files. Files Windows needs during the boot phase are corrupt or absent.
  • Bad driver blocking boot. A driver that crashes during startup prevents Windows from loading.
  • Failed update. An update that didn’t complete can leave the boot environment inconsistent.
  • Disk errors. Bad sectors in the boot area cause failures the automated tool can’t repair on its own.
  • Third-party boot components. Disk encryption or boot-manager tools from other vendors can confuse Startup Repair’s automated checks.

How to fix it

Work through these in order.

Fix 1: Reach Startup Repair correctly

Get into the recovery environment the reliable way.

  1. If Windows attempts to boot: force it off during the logo (hold power), power on, and repeat three times until Automatic Repair appears.
  2. If Windows won’t attempt boot at all: boot from a Windows 11 USB installer and click Repair your computer.
  3. On the Choose an option screen, select Troubleshoot > Advanced options > Startup Repair.
  4. Choose your account, enter your password, and let it run without interrupting it.

Fix 2: Let it run once, properly

One clean run beats five impatient ones.

  1. Start Startup Repair and give it a full 15 minutes — don’t force-quit it early.
  2. The screen may go black or restart the laptop once or twice; that’s normal.
  3. If it succeeds, Windows boots — immediately check Settings > Windows Update and your drivers for the cause.
  4. If it reports failure, don’t run it again right away — move to Fix 3 to read what it found.

Fix 3: Read the Startup Repair log

The log tells you exactly what it tried and where it gave up.

  1. From Advanced options, open Command Prompt.
  2. Open the log with: notepad C:\Windows\System32\LogFiles\Srt\SrtTrail.txt (adjust the drive letter if needed — check with diskpart > list volume).
  3. Scroll to the end for the test results: look for lines like “Boot critical file is corrupt” or “Repair action: System Restore.”
  4. The named failing component tells you what to fix manually — a corrupt boot file means BCD rebuild; a corrupt system file means offline SFC. The Srttrail.txt error guide walks through the most common log findings.
  5. Common log phrases decoded: “Boot critical file is corrupt” points to a BCD rebuild; “a recent driver installation” points to System Restore; “system volume on disk is corrupt” means run chkdsk before anything else.

Fix 4: Follow up with System Restore

Startup Repair often suggests this itself — it’s the natural next step.

  1. From Advanced options, choose System Restore.
  2. Pick the most recent restore point before the boot problem started.
  3. Complete the wizard (10–20 minutes) and let the laptop restart.
  4. System Restore reverts drivers, system files, and registry to the restore point without touching your files.

Fix 5: Rebuild the BCD manually

When the log points at boot configuration, do it by hand.

  1. Open Command Prompt from Advanced options.
  2. Run: bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd
  3. If fixboot gives “Access is denied,” use bcdboot C:\Windows (adjust letter) instead.
  4. Type exit, select Continue, and test the boot.

Fix 6: Run offline SFC and DISM

When the log points at corrupt system files, repair them while Windows is offline.

  1. In the recovery Command Prompt, verify your Windows drive letter with diskpart > list volume.
  2. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows with the correct letter.
  3. Run DISM /Image:C:\ /Cleanup-Image /RestoreHealth (correct letter).
  4. Restart and test. For the full deep-dive on offline repairs, see the startup BSOD troubleshooting guide .

Fix 7: Check the disk, then reset if needed

If every repair fails, suspect the hardware or start over.

  1. Run chkdsk C: /f /r from the recovery Command Prompt and let the full scan finish.
  2. Run your laptop maker’s built-in diagnostics for the storage drive.
  3. If the drive is healthy, use Troubleshoot > Reset this PC > Keep my files > Cloud download for a fresh Windows image from Microsoft.
  4. After the reset, install drivers from your laptop maker’s site first. If the drive is failing, replace it — no repair tool fixes bad hardware.

Closing

Startup Repair is a genuinely useful first step when you use it as intended: run it once, read its log when it fails, and follow the log’s lead into System Restore, BCD rebuild, or offline file repair. The mistake is treating “couldn’t repair your PC” as the end of the road — it’s really just the tool telling you the problem needs hands-on work.

Keep a Windows 11 USB installer somewhere safe; it’s the key that unlocks every fix in this guide when Windows can’t boot itself. Making one takes ten minutes on any working PC via Microsoft’s Media Creation Tool, and it doesn’t expire — a two-year-old installer still boots the recovery environment fine. Pair it with a written-down BitLocker recovery key and you’re prepared for essentially any boot failure short of dead hardware. That’s the whole philosophy here: one good USB stick and one piece of paper turn a crisis into a routine.

Frequently asked questions

What does Startup Repair actually fix?
Startup Repair diagnoses and fixes problems that prevent Windows from booting: missing or corrupt boot configuration data, damaged boot sector code, corrupt system files critical to startup, and faulty driver or registry issues it can safely revert. It runs a series of automated checks and applies targeted repairs, logging everything to a file you can review.
How long should Startup Repair take?
Typically 5 to 15 minutes. If it’s been running over an hour with no progress, it’s likely stuck — force a shutdown and try a different approach like System Restore or the manual boot repairs. Startup Repair that runs long without finishing usually means it’s struggling with disk errors; run chkdsk next.
Will Startup Repair delete my personal files?
No. Startup Repair only touches boot files, system files, and configuration — never your documents, photos, or other personal data. It’s one of the safest recovery tools. Even if it fails, your files remain intact on the drive.
Why does Startup Repair say it couldn't repair my PC?
That message means the automated checks couldn’t identify or safely fix the problem — common with corrupted registry hives, badly damaged BCD stores, failing drives, or third-party boot components it doesn’t understand. It’s not a verdict that your PC is unfixable; it just means you need the manual steps: BCD rebuild, offline SFC/DISM, or System Restore.