Windows 11 Automatic Repair Loop? What to Try Next

Before another repair attempt

Photograph the error, including any stop code or repair-log path. Leave the laptop on reliable power and disconnect nonessential USB devices after a safe shutdown. Do not interrupt a screen that is actively installing firmware or making update progress. A repair failure is a symptom; it does not prove Windows must be erased.

Protect files first. If Safe Mode or Windows works even once, back up important files to a separate drive. Locate your BitLocker recovery key before using recovery tools. For a work or school PC, ask IT for recovery access. Do not reset the PC or alter partitions to bypass a missing key.

1. Open recovery without starting a reinstall

On the repair screen choose Advanced options, then Troubleshoot > Advanced options. If you can reach sign-in, hold Shift while choosing Power > Restart. When neither is available, use the PC manufacturer's recovery entry method or official Windows installation media and select its repair option.

Creating installation media on another computer erases the selected USB drive; use an empty drive. Booting that media for recovery does not require installing Windows. Avoid repeated forced shutdowns just to return to a menu you can already open.

2. Decide whether Startup Repair has already had its chance

If you have not run it yet, choose Startup Repair once. It addresses startup configuration and related faults. If it reports that it could not repair your PC and returns to the same loop, record the result and move on. Running it again without a changed condition rarely adds useful information.

Menu availability varies by Windows version and device configuration. A missing option is not a reason to use an unrelated destructive one. See Microsoft's Startup Repair guide for the tool's scope.

3. Match rollback to the change that preceded the loop

If the loop began immediately after a Windows update, look in Advanced options > Uninstall Updates. Removal of the latest quality update is separate from reverting a feature version; use the option matching the recent change if available. Some updates cannot be removed. Record what you removed and try a normal boot before doing anything else.

If you changed a device driver, choose Startup Settings > Restart and select 4/F4 for Safe Mode if offered. PIN sign-in may be unavailable, so have your account password. If Safe Mode works, back up files and use Device Manager to roll back only the identified driver when its rollback button is available. Do not uninstall a storage controller blindly.

4. Try a restore point when the timing fits

From Advanced options, System Restore may let you select a point before the failure. Review the affected programs before confirming. It is intended to preserve personal files while reversing system changes, but apps, drivers and settings installed later can be removed or changed. A restore point is not a backup and may not exist.

After any successful recovery, confirm Windows can restart normally, verify your files and update your backup. Investigate the failed driver or update before reinstalling it; do not permanently disable security updates as a workaround.

5. Stop for storage symptoms; reserve reset for a recovery decision

A drive missing from firmware, repeated read errors, clicking, or freezing inside recovery raises concern about hardware. A single repair failure alone does not. If files are irreplaceable, stop write-heavy repair attempts and seek qualified data-recovery help before diagnostics that might stress a failing drive.

Reset, reinstall and partition work come last. Even Reset this PC with Keep my files removes apps and settings and is not a backup guarantee. Remove everything, formatting and partition deletion can erase data. Confirm backups and recovery-key access before proceeding with any of these. This workflow does not require command-line boot-record or partition edits.

A repair log or an offline Windows installation also needs correct drive identification. Do not paste generic online DISM, SFC or boot commands into recovery and assume C: is the Windows volume. Get model-specific help when rollback and restore fail.