Windows 11 stuck in a restart loop: use recovery options in the least disruptive order
Move from Windows Recovery Environment and startup checks toward restore or reinstall only when the loop persists.
- Disconnect newly added external hardware that is not required to boot.
- If Windows Recovery Environment appears, use it rather than repeatedly forcing power cycles.
- Note whether the loop began after an update, driver or app change.
- Back up important files from a recovery route if possible before high-impact repair.
What this problem usually means
A restart loop can be caused by a failed update, driver, boot problem or broader system damage. Microsoft’s recovery guidance is useful because it orders options by scenario and disruption rather than jumping directly to Reset this PC.
Work from the narrowest fix to the broader one.
Enter Windows Recovery Environment
Low riskWhy this belongs here: Windows RE is the central supported environment for startup repair and recovery when normal Windows cannot stay running.
- Use the automatically offered recovery screen when it appears.
- Choose Troubleshoot > Advanced options.
- Start with Startup Repair when the failure is clearly a startup problem.
Use the recovery option that matches the trigger
Medium riskWhy this belongs here: A recent update, restore point or startup failure has a more targeted recovery option than a full reset.
- If the problem followed an update, review the update-uninstall recovery option.
- If a restore point exists from before the problem, consider System Restore.
- Use Startup Settings/Safe Mode when you need to remove a problematic driver or app.
Escalate to reinstall/reset only after preserving data
High riskWhy this belongs here: Reset and reinstall can remove apps, settings or data depending on the option, so they belong after lower-impact recovery paths.
- Read exactly what the selected recovery option keeps and removes.
- Back up important files first when possible.
- Use the least destructive option that still addresses the failure.
When this guide stops being the right path
If the machine fails before Windows recovery can load, firmware cannot see the boot drive, or hardware diagnostics fail, move out of software-only troubleshooting.
If the problem is still not fixed
Once Windows can remain running, inspect the update/driver history and the exact failure that started the loop so the root cause can be addressed instead of only recovering from it.
Sources reviewed for this page
Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.