Windows 11 Stuck in a Boot Loop Before Reaching the Desktop

Windows 11 Stuck in a Boot Loop Before Reaching the Desktop

You turn the PC on, the Windows logo appears, maybe the spinning dots run for a while — and then, before the sign-in screen ever shows up, the machine restarts and does the exact same thing again. And again. It never gets far enough to reach the desktop, log in, or even show an error message most of the time. It just keeps starting the boot process over from the beginning.

A genuine boot loop like this is different from a PC that fails to boot once and stays off, and different from one that restarts unexpectedly during normal use after already reaching the desktop. This is specifically about something breaking early in the startup sequence itself, badly enough that Windows can’t get past it and restarts rather than either finishing the boot or stopping with a visible error. The good news is that Windows has a dedicated recovery environment built exactly for this situation, and it activates automatically after a couple of failed boot attempts.

Quick explanation: this guide covers what a true boot loop looks like versus a single failed boot, letting the Windows Recovery Environment take over once it detects the repeated failures, running Startup Repair and reading what it finds, rolling back a driver or update from Safe Mode when Startup Repair alone doesn’t fix it, using System Restore to go back to a point before the loop started, and repairing system files once the PC is bootable again so the loop doesn’t come back.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

A Windows 11 PC that restarts repeatedly before ever reaching the sign-in screen almost always triggers the Windows Recovery Environment automatically after two or three failed attempts — if it doesn’t appear on its own, forcing a hard shutdown during the boot process three times in a row usually brings it up. From there, Startup Repair resolves a large share of boot loops on its own, and when it doesn’t, rolling back a recent driver or update, or using System Restore to return to a point before the loop began, resolves most of what’s left. Once the PC boots normally again, checking system files for damage helps make sure the loop doesn’t return.

What a True Boot Loop Looks Like, and What It Doesn’t

It’s worth being precise about the symptom before troubleshooting it. A boot loop means the restart happens during the boot sequence itself — while the Windows logo, spinning dots, or a black screen with a cursor is showing — and the PC never reaches the sign-in screen or desktop at all before it cycles back to the beginning. If it does reach the desktop and only then restarts, that’s a different problem with a different set of causes.
It’s also worth distinguishing a loop from a single failed boot. One bad startup attempt that then sits on a black screen or an error message, without repeating, is often recoverable with a simple retry or a wait for a pending update to finish installing. A genuine loop — the same failure, repeating three, four, five times in a row without ever progressing further — is what the rest of this guide addresses.
If the loop started right after installing a specific driver or update, keep that detail in mind going in — it narrows down which repair path below is most likely to work first. Checking Reliability Monitor for anything installed shortly before the loop began is worth doing right after the PC becomes bootable again, even if it can’t be checked while the loop is actively happening.

Let the Windows Recovery Environment Take Over

Windows is built to detect exactly this failure pattern on its own. After two or three consecutive boot attempts that don’t complete successfully, Windows automatically launches the Windows Recovery Environment, commonly called WinRE, instead of trying to boot normally a fourth time. This usually happens without any action needed — the loop itself is often what triggers the switch.
If WinRE doesn’t appear on its own after several cycles, it can be forced: as soon as the Windows logo appears during a boot attempt, hold the power button to force a hard shutdown, then power on again. Repeating that three times in a row — interrupting the boot at the same early point each time — reliably triggers WinRE even when the automatic detection doesn’t kick in.
Once WinRE loads, it presents a menu with several repair options, covered next. Reaching this menu is the actual turning point in a boot loop — everything from here is about choosing the right repair path rather than continuing to wait on Windows to fix itself.

Run Startup Repair and Read What It Finds

From the WinRE menu, Troubleshoot leads to Advanced Options, where Startup Repair is usually the first thing worth trying. It’s an automated tool built specifically for boot loops and boot failures, and it scans for the most common causes — a corrupted boot configuration, a missing boot file, an inconsistency between the boot loader and the installed Windows version — before attempting to fix whatever it finds.
Startup Repair can take anywhere from a few minutes to over half an hour depending on what it finds, and it’s worth letting it run to completion without interrupting it. If it reports that it couldn’t fix the problem, WinRE’s command prompt can pull up more detail on exactly what stage of the boot process is failing, which helps decide between the driver-rollback and System Restore paths covered next.
reagentc /info
Run from the WinRE command prompt, that command reports the current state of the recovery agent and confirms whether the recovery partition itself is intact and correctly configured — useful context if Startup Repair keeps failing, since a damaged recovery partition needs a different fix than a damaged boot configuration.

Roll Back a Recent Driver or Update From Safe Mode

If the loop started shortly after installing a driver, especially a graphics or storage driver, that driver is a strong candidate even if Startup Repair didn’t flag anything specific — some driver problems prevent Windows from finishing its startup sequence without technically corrupting any boot file, which is exactly the kind of issue Startup Repair isn’t built to catch.
From the WinRE Advanced Options menu, Startup Settings allows booting into Safe Mode, which loads Windows with only its essential built-in drivers active. If the PC boots successfully into Safe Mode without looping, that’s strong confirmation a third-party driver is involved, and it can be rolled back or uninstalled from within Safe Mode before attempting a normal boot again.
This is also the point to check whether a Windows update was installed right before the loop began — Advanced Options includes an option to uninstall the most recent quality update directly, which resolves the loop in cases where an update itself was the trigger rather than a separately installed driver.
NordVPN
One Thing Worth Knowing

Researching a Boot Loop When the Looping PC Can't Get Online

A PC stuck in a boot loop can't reach the internet at all, so every search for a fix, every downloaded recovery tool, and every driver you look up has to happen on a phone or a second computer instead — often over public or unfamiliar Wi-Fi if you're away from home when it happens. NordVPN keeps that research and any files you download encrypted regardless of which device or network ends up being the one you're stuck relying on.

Protect This Session

Use System Restore to Go Back to Before the Loop Started

When Startup Repair doesn’t fix it and there’s no obvious recent driver or update to point at, System Restore — also available from the WinRE Advanced Options menu — rolls the system back to an earlier restore point, undoing whatever changed around the time the loop began without touching personal files.
This depends on a restore point actually existing from before the problem started, which is why it’s listed after the more targeted options above rather than first — it’s a broader fix that undoes everything since that point, not just the one thing that broke, so it’s worth trying the more specific repairs first when there’s a clear lead to follow.
If no restore point exists, or the available ones are from before the PC was even set up the way it currently is, this path isn’t available, and the driver-rollback or a full reset from WinRE becomes the more realistic next step.

Once the PC Boots Again, Repair What Might Cause It to Loop Again

Getting past the loop with Startup Repair, a driver rollback, or System Restore fixes the immediate problem, but it doesn’t always address whatever underlying damage led to it in the first place. A boot loop caused by corrupted system files, for instance, can return the next time those same files get touched by an update or a driver install.
Once Windows boots normally again, it’s worth running a full system file check while everything is working, rather than waiting for the next loop to force the issue. This is one of the few points in this whole process where a tool running inside Windows itself can actually help — everything before this point required WinRE, since Windows couldn’t boot far enough for anything else to run.
Fixyfier’s Fix & Repair section includes both Repair System Files and Repair the Windows Image as one-click actions, which is worth running as soon as the desktop is reachable again to repair any underlying file damage before it has a chance to cause another loop.

Frequently Asked Questions

How many restarts count as a real boot loop rather than bad luck?

Windows itself uses roughly two to three consecutive failed boot attempts as its own threshold before automatically launching the Recovery Environment, which is a reasonable line to use. A single failed boot that then sits on an error screen without repeating usually isn’t a true loop and can often be resolved with a simple retry.

Will I lose my files if I use System Restore or Startup Repair?

Both are designed to leave personal files untouched. Startup Repair only targets boot configuration and system files, and System Restore reverts system settings, drivers, and installed software changes to an earlier point without deleting documents, photos, or other personal data created since then.

What if WinRE itself won’t load or fails to fix anything?

If the automated repair options in WinRE don’t resolve the loop, the next steps involve either a more advanced manual repair from the WinRE command prompt or, as a last resort, a reset or reinstall of Windows using installation media — at that point it’s usually worth backing up any accessible files from the recovery environment first, since a full reinstall does remove installed programs even when personal files are preserved.

Let Fixyfier Help Once Windows Boots Again

Once a boot loop is broken and the desktop is reachable again, Fixyfier’s Fix & Repair section runs Repair System Files and Repair the Windows Image together to repair the system files a loop like this can leave damaged, and its Windows Tools section’s Reliability Monitor helps confirm what changed right before it happened — so the fix holds instead of just getting you back to the desktop once.
Get Fixyfier from the Microsoft Store