Case Study: Fixing a Windows Computer Stuck in Automatic Repair

A Windows computer that repeatedly displays “Preparing Automatic Repair” or “Diagnosing your PC” can be difficult to interpret. The message does not identify one specific failed part. It only means that Windows detected a startup problem and entered its recovery environment.

This case study describes a representative repair pattern rather than claiming a particular customer outcome. The same symptom can result from damaged system files, a failed update, a corrupted boot configuration, file-system errors, a failing drive, or occasionally a memory or motherboard problem. The safest approach is to separate those possibilities before making changes.

What the Automatic Repair loop usually looks like

In this pattern, the computer powers on normally, shows the Windows logo, and then displays one of these screens:

Preparing Automatic Repair
Diagnosing your PC
Automatic Repair could not repair your PC
A recovery menu containing “Advanced options” and “Turn off your PC”

Some computers restart and return to the same screen without showing a menu. Others reach the Windows Recovery Environment, often called WinRE, but every attempted startup returns to recovery.

The first diagnostic question is whether the computer can consistently reach Advanced options. If it can, software and boot-recovery checks may be possible without immediately reinstalling Windows. If it cannot, the cause may include a damaged boot drive, an interrupted update, a power problem, or hardware that is not reliably completing startup.

Protect data before using repair tools

Warning: Do not use Reset this PC, format a partition, delete partitions, or reinstall Windows until important files have been backed up or otherwise assessed. Some repair actions are intended to preserve personal files, but no recovery procedure should be treated as risk-free.

If the drive is making repeated clicking, grinding, or unusual mechanical noises, or if the computer becomes extremely slow while trying to read it, stop repeated startup attempts. A failing drive can deteriorate further, and repeated scans can complicate data recovery.

BitLocker or device encryption may also require a recovery key. Recovery environments and drive changes can trigger an encryption recovery prompt. Before proceeding with advanced work, locate the correct recovery key through the Microsoft account or the organization that manages the computer. Do not attempt to bypass encryption or an account sign-in.

When files are important and Windows will not start, the safest next step may be copying data from a properly prepared recovery environment or removing the drive for a read-only assessment. If the drive shows signs of failure, professional data recovery may be more appropriate than additional repair commands.

Step 1: Check simple causes without forcing a repair

Disconnect nonessential USB devices, external drives, memory cards, docks, and printers. Leave the keyboard, mouse, display, and power connected. A damaged removable drive or a device that changes the boot order can occasionally interfere with startup.

Then choose Continue if it is offered. If Windows starts, back up important files before investigating further. If it returns to Automatic Repair, return to Troubleshoot > Advanced options.

Avoid repeatedly holding the power button to interrupt startup unless Windows is completely unresponsive and there is no other way to reach recovery. Forced shutdowns can add file-system damage, especially if Windows is writing an update or recovering from an earlier failure.

Step 2: Try the least destructive recovery options

In Advanced options, the available tools vary by Windows version and computer configuration. A sensible order is:

Startup Repair: This checks common boot configuration and startup problems. It may report that it could not repair the computer; that result does not identify the root cause by itself.
Uninstall Updates: If the loop began immediately after a Windows quality or feature update, try removing the most recent applicable update. This may not be available if recovery information is missing.
System Restore: If restore points exist, restoring to an earlier point can reverse some driver, registry, or software changes. It is not a substitute for a file backup and does not undo every type of problem.
Startup Settings: Use this to attempt Safe Mode. Safe Mode loads a reduced set of drivers and services, which can help identify a recently installed driver or startup program.

System Restore should not be selected casually on a business computer without considering recently installed applications, line-of-business software, and encryption or management policies. If the computer is managed by an employer, involve the responsible administrator before making changes.

Step 3: Check whether Windows sees the correct drive

If the easier options fail, open Command Prompt from Advanced options. The recovery environment may assign Windows a different drive letter than it uses during normal operation. Do not assume that C: is the Windows partition.

One non-destructive way to inspect available volumes is:

diskpart
list volume
exit

Look for a volume containing the Windows folder. In a recovery environment it might be D:, E:, or another letter. You can check a candidate volume with:

dir D:Windows

Replace D: with the letter that appears appropriate. If the folder is missing, stop and reassess. The Windows partition may be encrypted, inaccessible, assigned another letter, or affected by a storage problem.

Step 4: Repair system files carefully

After identifying the Windows volume, System File Checker can sometimes replace damaged protected files. An offline example is:

sfc /scannow /offbootdir=D: /offwindir=D:Windows

Use the correct volume letter. The command may report that it found and repaired files, found corruption it could not repair, or found no integrity violations. Those messages are clues, not proof that the entire startup problem has been solved.

DISM can sometimes repair the Windows component store, but offline DISM work is more sensitive to the Windows version, recovery image, and available source files. It is better to stop than to guess at a source path or apply commands intended for a different installation. A mismatched repair source can create additional confusion.

Step 5: Consider boot configuration and disk health

A damaged boot configuration can prevent Windows from loading even when the personal files and operating system files are still present. On supported systems, rebuilding the boot files with bcdboot may help, but the command requires correctly identifying both the Windows partition and the small EFI system partition. Choosing the wrong volume can make the system less bootable.

For that reason, do not blindly run boot-record commands copied from an unrelated guide. BIOS mode, UEFI mode, partition layout, and encryption status all matter.

File-system checking also requires caution. chkdsk can correct logical errors, but it does not repair a physically failing drive. On a drive that is unstable, unusually slow, or producing read errors, a full scan may place additional stress on the device. Data protection and drive-health assessment should come first.

Observation	What it may suggest	Safer next step
Windows starts in Safe Mode	Driver, update, or startup software issue	Back up files, then review recent changes
Recovery tools cannot see the Windows volume	Encryption, partition, controller, or drive problem	Verify encryption status and assess the drive
Drive is extremely slow or reports read errors	Possible storage failure	Stop unnecessary scans and prioritize data
Repair began after an update	Update or driver conflict is possible	Consider Uninstall Updates or System Restore

When Reset or reinstalling Windows is appropriate

Reset this PC or a clean installation may be reasonable when the drive is healthy, important files are backed up, recovery options have been exhausted, and the owner understands what will be removed. A reset may remove applications, settings, and sometimes personal files depending on the selected option. A clean installation removes the existing Windows installation and requires reinstalling drivers and software.

Neither option is a good first response to a drive that may be failing. Reinstalling Windows also does not solve a defective SSD, faulty memory, overheating problem, or intermittent motherboard fault.

Safe stopping points

Stop troubleshooting and seek qualified help when files are irreplaceable, BitLocker recovery is requested and the key is unavailable, the drive shows physical warning signs, the recovery environment cannot see the expected disk, or the computer has begun restarting unpredictably. Small businesses should also stop before changing a managed or encrypted computer without confirming backup, administrative, and compliance requirements.

Automatic Repair is a symptom, not a diagnosis. A careful repair process protects data first, identifies whether the drive is readable, and only then tests Windows recovery options. That approach may take longer than applying a single command, but it reduces the chance of turning a startup problem into data loss or an unnecessary reinstall.

When to call a professional

If the problem continues, the data is important, or the repair requires work beyond your comfort level, AME Computers can provide professional diagnosis and repair or call 402-505-6600.