Windows stuck in an Automatic Repair loop
Distinguish a pending repair from a failed attempt. Use the result and Safe Mode access to choose the next step while protecting your files.
Try this first
1 quick checks · ~5 min
Find your situation
See all the clues. Choose the one that matches what you observe.
Startup Repair has not run yet
Use the supported recovery attempt and observe its result.
Repair displays a specific error
Keep the message before choosing another tool.
Repair finishes but returns to the same loop
Repeating the same attempt does not provide a different test.
Safe Mode starts successfully
Investigate recent changes while the system runs with a reduced configuration.
No non-destructive startup route works
Protect data before considering recovery that could replace it.
A tool requests the BitLocker recovery key
This is a security barrier, not an error to bypass.
Diagnostic signals
- ObservationIt returns to exactly the same state
- Without changes between attempts, repetition does not distinguish a new cause.
Step-by-step solutions
Identify which repair has already run
The current screen and last result prevent repeating an attempt without new information.
Record the exact text and whether Windows reported that Startup Repair could not repair the computer. If you are only at recovery options and have never run it, use the first branch; if it finished and returned to the loop, keep that result.
If Windows starts and then goes black, use the black-screen guide. If there is never an image from power-on, use the no-display guide. An update code such as 0xC1900101 adds a different context worth preserving.
Run Startup Repair if it has not been attempted
The tool attempts to resolve startup problems but cannot recover every failure.
From Windows Recovery Environment, choose Troubleshoot > Advanced options > Startup Repair. Use the available recovery screen; do not repeatedly force shutdowns to reach it. If BitLocker is requested, follow the key branch before continuing.
Let the attempt finish. If Windows starts normally, stop and protect your files. If an error appears, record it; if the same loop returns, compare Safe Mode rather than running repair repeatedly.
Use the message as a clue, not a complete diagnosis
A file or log name can help support without proving a damaged component.
Photograph or note the diagnosis and log location if shown, without exposing private information. Microsoft covers several startup causes, including files, boot configuration, and drivers; the general failure message does not distinguish yours.
If the message identifies another tool or requires the key, address that condition. Do not translate every error into a bootrec, bcdedit, or diskpart sequence copied from the internet.
Compare a Safe Mode startup
A reduced set of services and drivers helps separate some normal-startup causes.
If WinRE offers Startup Settings, use Advanced options > Startup Settings > Restart and select Safe Mode as shown. If it already produced the same result and nothing changed, do not repeat it as a ritual.
If it starts, continue with recent changes. If it does not start or returns to the loop, record the result alongside Startup Repair and move to data protection; do not conclude that the SSD is dead.
Investigate the recent change from the reduced startup
Working Safe Mode narrows the scope but does not automatically identify the culprit.
First protect accessible files. Relate the loop’s onset to a recently installed app or driver and use its supported update or rollback procedure, one change at a time. Do not uninstall all drivers.
After a justified change, test normal startup. If it works, stop. If there is no specific change or rollback does not alter the result, keep that evidence for support rather than chaining repairs.
Resolve legitimate access to the recovery key
Recovery tools may need to unlock the encrypted volume.
Find the key saved for that computer in your records or ask the administrator on a managed device. Check that it matches the identifier shown on screen. Do not publish the key or give it to unknown services.
Without the required key, stop operations needing disk access. Do not format or disable BitLocker in an attempt to recover encrypted files.
Advanced checks
Continue if the earlier steps did not help. Read each procedure’s precautions first.
Stop before destructive recovery
When no non-destructive path changes the state, preserving data becomes the next objective.
If important files are unbacked up and you cannot start, request help preserving them before resetting or reinstalling. Keep messages, preceding changes, and results; avoid further commands without a specific hypothesis.
Only with data protected and authorized access to the computer should you review Microsoft-supported recovery options and what each preserves with support. This guide does not prescribe formatting or deleting partitions as a test.
Still not working?
The same result after non-destructive options, with unbacked-up data, is a stop condition. Protect information with appropriate help before destructive recovery; further repetition does not turn a hypothesis into a diagnosis.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
- Microsoft SupportOfficialStartup Repair
- Microsoft SupportOfficialWindows recovery environment
- Microsoft SupportOfficialWindows startup settings
Source review: . A documentation review, not a physical hardware test.
Related problems
Black screen after Windows starts
The display goes black when entering Windows or after sign-in. If there was never a boot image or any sign of Windows, start with PC turns on but no display.
View solutionPC turns on but no display
The PC shows signs of power, but the monitor has no usable picture. Check the monitor, selected input, cable and video output before moving on to internal components.
View solutionWindows upgrade error 0xC1900101
The Windows upgrade failed with a driver-related problem. Check peripherals and devices before trying the upgrade again.
View solution