Windows Startup Repair Is a Write. Don't Run It on a Dying Drive.

Written and maintained by the Desert Data Recovery lab team. · Updated September 25, 2026

We already wrote about CHKDSK /f, about Windows Initialize Disk, and about Device Encryption that turns itself on. This page is the blue screen that appears before Windows loads. Automatic Repair and Startup Repair are the same tool. One starts by itself after a failed boot. The other is the button in the recovery menu. Neither one is a spectator pass over a dying HDD or SSD.

What the screen actually shows

The wording changes with the Windows version. The path does not.

• Preparing Automatic Repair. Windows has given up on a normal start and is loading the recovery environment from the patient disk.
• Diagnosing your PC. A spinner. It is reading the install it could not boot. It is not a SMART report, and it does not stop because the drive is already failing.
• Attempting repairs. This is the write. Boot files, the BCD, filesystem metadata, sometimes a restore. You are not shown a list of changes and asked to confirm them.
• Automatic Repair couldn't repair your PC. Restart, or Advanced options. The line under it is often a log path on C:. Restart frequently drops you back into Preparing Automatic Repair.
• Choose an option, then Troubleshoot. People call this Fix issues. Advanced options on the next screen still offers Startup Repair, System Restore, Uninstall Updates, and Command Prompt.
• Startup Settings, including Safe Mode. You reach it by restarting out of that same menu. On a machine that already failed to boot, Automatic Repair has usually run before the menu exists. If Safe Mode fails, the next start is the repair loop again.

A stop code or a black screen may have come first. The repair screen is what Windows does after that, on its own, often on the second failed boot. Nobody typed chkdsk. The write can still happen.

The public case log has no Automatic Repair or Startup Repair intake. We will not invent a case ID or an outcome. This post is what the screen does.

What a repair pass writes

Startup Repair is built to change a Windows install that will not start. A given pass can do one of the following or several. The spinner does not preview them.

• Boot configuration and the BCD. The boot configuration data store is a registry hive on the EFI system partition, or on the older System Reserved partition. Repairing it writes that hive. Replacing or updating bootmgr — the Windows Boot Manager — writes that partition too. A rebuild that points Windows at the wrong volume is a new failure, not a test.
• Registry hives on the Windows volume, when the session rolls them back or applies a restore point. A restore point is a volume shadow copy. Applying it writes files and registry onto the patient. We will not claim every pass rewrites every hive. Windows 10 and 11 do not keep a full RegBack set the way Windows 7 did. You are still not offered a read-only diff.
• Filesystem metadata. The session can run a CHKDSK-class repair — corrections to NTFS — without putting a chkdsk window on the screen. That is the write in CHKDSK /f is a write, started from the recovery environment.
• System files an integrity check decides are wrong. Those replacements land in the Windows directory on the same disk.

Couldn't repair your PC does not mean nothing was written. The session can repair the BCD, run a disk check, write its log at C:\Windows\System32\LogFiles\Srt\SrtTrail.txt, and then fail a later test. The blue screen is the end of the pass. It is not a receipt that says read-only.

Why it is a trap on a failing drive

Startup Repair assumes the disk can take a repair: a bad shutdown, a boot file that did not flush, an update that left the BCD wrong. A clicking, grinding, rapidly retrying, RAW, or intermittently dropping drive is often not that disk.

Heads that are already weak. Diagnosing and Attempting repairs keep the platters spinning and the heads seeking. Couldn't repair, then Restart, is another cycle of the same thing. Overnight "let it keep trying" is how a head-stack job picks up media damage. Power it off. See clicking and grinding.

The map a lab still needed. File contents often sit further in. The boot sector, the BCD, the registry, and the NTFS indexes are what we read first from an image. A repair that "almost boots" overwrites that map with Windows's reconstruction. The log file is not a backup of the old tree.

A drive that drops mid-write. SATA or USB that disappears, then comes back on the next spin-up, can tear a metadata update in half. The next Automatic Repair then "fixes" the torn copy. Power off. Do not reseat it so the loop can continue.

SMART was already failing. Automatic Repair does not read SMART and stop. Reallocated sectors, pending sectors, or a BIOS warning are a media problem. The blue screen will still offer a repair. That repair writes.

SSDs do not give you a long undo window. A metadata write on NAND is a write. TRIM and garbage collection can drop the old blocks faster than people expect from a hard drive. Do not let Attempting repairs "make it boot again" on a stick that is already throwing errors or vanishing. See SSD failure signs.

RAW is a host-side status: Windows will not mount a filesystem it trusts. It is not a lab report that the files left. A repair pass that then runs a disk check, or a later Initialize Disk prompt once the drive shows up in Disk Management, is another write on that status. See drive not recognized.

What not to do

Let Attempting repairs finish on a drive that is clicking, freezing, or dropping. You did not choose a target. Windows chose one and wrote it.

Run Startup Repair from WinRE — the Windows disk, a recovery drive, or a Windows installer USB whose first offer is Repair your computer. That menu item is this tool again.

Click Troubleshoot, or any Fix issues path that ends in Startup Repair, System Restore, or Uninstall Updates. Uninstalling an update writes the install. System Restore applies a shadow copy. Both feel like undos. Both write the patient.

Restart from "couldn't repair your PC" to see if the next boot is kinder. On a failing drive the next boot is the same repair, plus another spin-up.

Use Safe Mode as the gentle option after the repair environment has already started, or keep rebooting when Safe Mode falls back into Automatic Repair.

Open Command Prompt in WinRE and run chkdsk, bootrec, bcdboot, or an offline system-file check because a thread listed them. Same writes, fewer warnings. chkdsk /f from that prompt is the CHKDSK post with a recovery wallpaper.

Reset this PC from the Troubleshoot menu. That is a reinstall, not a milder Startup Repair. It writes a new Windows over the volume.

Enter the BitLocker recovery key so the repair can continue. The key unlocks ciphertext. The repair still writes. The published note on encryption Windows can enable by itself is Device Encryption.

This is the boot path, not the other Windows dialogs

The CHKDSK /f post is a volume you can already see: Error Checking, Scan and repair, chkdsk /f, or autochk scheduled for the next reboot. Startup Repair can launch that class of filesystem write without showing you the check. Do not treat this page as a substitute for that one, and do not run both.

Initialize Disk is Disk Management, after a disk is visible and looks Unknown or Not Initialized. It writes a partition table. Different dialog. People reach it when the repair fails and the drive shows up empty. It is not the undo for a boot repair.

Device Encryption is the 48-digit key prompt on a machine where BitLocker came on with a Microsoft account. This page is what not to do with that prompt when the disk is failing and WinRE wants to repair. A data-only external that Explorer wants to scan is the CHKDSK page, not this one. If the screen in front of you is Preparing Automatic Repair, you are here.

What to do right now

Do not let it attempt repairs. Do not run Startup Repair. Do not click Restart into the loop. Do not run chkdsk from the recovery environment. Do not reset the PC.

1. If the drive is clicking, grinding, or the repair is grinding, power it off. Hold the power button. A clean shutdown is not on that screen. Waiting for Couldn't repair so Advanced options will appear is more time on a failing disk. If Windows is still up and only offering recovery on the next reboot, do not take that reboot while the disk is noisy or the machine freezes when the volume is touched.
2. Photograph the screen before anything else changes. The exact words — Preparing Automatic Repair, Diagnosing, Attempting repairs, couldn't repair — any stop code from the boot before it, and the log path if it is already shown. Screenshots help. They are not a diagnosis.
3. Write down the symptoms: click, grind, freeze, the drive disappearing, a power cut, how many times it already looped, whether you entered a BitLocker key, whether anyone already opened Command Prompt.
4. Stop the reboot cycle. The next start is not a second opinion. Unplug an external boot disk instead of letting the dock retry it. See external not recognized if the failing disk is a USB drive the PC is trying to boot or repair.
5. Copy from other media only when the disk still looks healthy. Quiet, stays online, the volume mounts, you only need files off it: boot something that is not this Windows install — another computer, or a live environment that is not WinRE — and copy onto different media. Do not choose Repair your computer on a Windows installer USB. That is this menu. Do not install Windows onto the patient disk. If it clicks, drops, freezes, or the volume is RAW, stop. That is an evaluation, not a copy.

A laptop whose drive is not a simple pull can come in as a whole machine. Do not open it on a table to look. Pack it the way you would any failed drive — how to ship a failed drive safely. Then talk to a lab before anyone boots it into repair again.

How a lab handles it

We do not boot the patient into Automatic Repair to see if Windows comes back. We do not run Startup Repair, bootrec, System Restore, or chkdsk from WinRE on your disk. We do not enter a BitLocker key so the repair environment can keep going.

The drive is imaged write-blocked first — as much of it as the heads or the controller will still give us, including a disk that only reads in pieces. Work happens on the copy. Imaging uses the lab tools already named on this site, including the ACE Lab PC-3000 and DeepSpar Disk Imager. Boot files, the BCD, registry hives, and NTFS are read from that image. They are not repaired in place so the original will boot. If the problem is mechanical, firmware, or a controller that drops, Startup Repair would not have fixed it, and the retries can make the image worse.

What imaging cannot do: put back a BCD store, a registry hive, or an NTFS index the repair already replaced, or files a later Reset or format wrote over. We will tell you if the data is not there. There is no Startup Repair case in the public case log, and we will not invent one.

The closest published cousins are laptop drives that had stopped giving access, where the work was imaging and a filesystem rebuild. DDR-2026-0013: a 1 TB Seagate ST1000LM035, failing heads, an SMR drive with a firmware reallocation fault. Full image, file system rebuilt from the image, full recovery on that drive. DDR-2026-0012: a 320 GB Toshiba MK3259GSX, failed heads and a damaged translator. Cleanroom head swap, translator rebuild, then an image and an NTFS rebuild. The client's critical folders and files came off that image. Neither write-up mentions Automatic Repair, Startup Repair, or WinRE. Those results belong to those drives. They are not a rate, and they are not a prediction about the PC looping on your desk. We don't advertise a success rate.

If the screen is Scan and repair on a letter that still opens, start with CHKDSK /f. If Disk Management wants to initialize, that is Initialize Disk. If it is clicking, start with power it off. For the hardware paths, see laptop, hard drive, or SSD data recovery.