Windows Stuck in Restart Loop? Fix It Now

If your Windows PC is stuck in a restart loop—turning on, showing the logo, then restarting again before you can sign in—the cause is usually a failed update, a corrupted driver, or a hardware conflict, and you can break the cycle by booting into the Windows Recovery Environment and using the built-in startup repair or safe mode tools. This guide walks you through the most effective fixes, from automatic repair to command-line solutions, and explains why the loop happens so you can prevent it from coming back.

Why Windows Gets Stuck in a Restart Loop

A restart loop (sometimes called a boot loop) occurs when Windows encounters a critical error during startup, attempts to recover, and then hits the same error again. The system may show a blue screen with a stop code, flash the manufacturer logo, or simply reboot without warning. Common triggers include:

Failed Windows updates – A partially installed update can leave system files in an inconsistent state.
Driver conflicts – A newly installed or updated driver (especially graphics or storage drivers) may be incompatible.
Corrupted system files – Power outages, disk errors, or malware can damage critical boot files.
Hardware issues – Faulty RAM, a failing hard drive, or overheating components can cause repeated crashes.
Overclocking or BIOS settings – Unstable overclocks or incorrect boot order can prevent Windows from loading.

In most cases, the loop is software-related and can be fixed without reinstalling Windows. The key is to interrupt the boot cycle and access the recovery tools before Windows tries to load again.

How to Break the Loop and Access Recovery

If Windows restarts too quickly to reach the login screen, you need to force it into the Windows Recovery Environment (WinRE). Here’s how:

Turn the PC off completely (hold the power button for 10 seconds if needed).
Turn it on, and as soon as the Windows logo appears, hold the power button again to force a shutdown.
Repeat this three times. On the third attempt, Windows should display “Preparing Automatic Repair” and then load the recovery screen.

If that doesn’t work, you can use a Windows installation USB drive. Insert it, boot from it (you may need to press a key like F12 or Del to choose the boot device), and select “Repair your computer” instead of “Install now.” Once you’re in the recovery environment, you can try the fixes below.

Fix 1: Run Startup Repair

Startup Repair is Windows’ built-in tool for fixing boot problems. It scans for common issues—like missing boot files or corrupted registry hives—and attempts to repair them automatically.

In the recovery screen, go to Troubleshoot → Advanced options → Startup Repair.
Select your user account and enter your password if prompted.
Wait for the tool to finish. It may take several minutes.
If it says it couldn’t repair your PC, don’t give up—move on to the next fix.

Startup Repair is safe and non-destructive; it won’t delete your personal files. However, it doesn’t always work, especially if the underlying issue is a driver or update conflict.

Fix 2: Boot into Safe Mode and Uninstall Recent Changes

Safe Mode loads Windows with only the essential drivers and services. If you can get into Safe Mode, you can uninstall the problematic update or driver that’s causing the loop.

In the recovery screen, go to Troubleshoot → Advanced options → Startup Settings.
Click Restart. After the PC reboots, you’ll see a list of options.
Press 4 or F4 to start in Safe Mode (or 5/F5 for Safe Mode with Networking, if you need internet access).

Once in Safe Mode, do the following:

Uninstall recent updates: Go to Settings → Update & Security → Windows Update → View update history → Uninstall updates. Remove the most recent quality or driver update, then restart normally.
Roll back a driver: Open Device Manager, right-click the device you suspect (e.g., display adapter), select Properties → Driver → Roll Back Driver.
Disable automatic restart: To stop the loop from happening while you work, go to Control Panel → System → Advanced system settings → Startup and Recovery → Settings, and uncheck “Automatically restart.” This lets you see the blue screen error code instead of rebooting.

If Safe Mode itself crashes or you can’t get in, try the next fix.

Fix 3: Use Command Prompt to Repair Boot Files

If Startup Repair and Safe Mode fail, you can manually rebuild the boot configuration and check system file integrity using Command Prompt from the recovery environment.

In the recovery screen, go to Troubleshoot → Advanced options → Command Prompt.
Run the following commands one by one, pressing Enter after each:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

If bootrec /fixboot gives an “access denied” error, you may need to run bootsect /nt60 sys first. After these commands, type exit and restart your PC.

You can also check for corrupted system files with:

sfc /scannow

Note that SFC can take a long time and may not work offline. If it fails, you can try DISM /Online /Cleanup-Image /RestoreHealth (requires internet) from an elevated Command Prompt in Safe Mode.

Fix 4: Disable Automatic Restart and Check the Blue Screen Error

Sometimes the loop is caused by a specific stop code (like CRITICAL_PROCESS_DIED or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). If you can see the blue screen, write down the error code—it will point you to the exact driver or component.

To disable automatic restart (if you can get to the login screen):

Press Win + R, type sysdm.cpl, and press Enter.
Under Startup and Recovery, click Settings.
Uncheck Automatically restart under “System failure.”
Click OK and restart. Now the blue screen will stay visible so you can note the error.

If you can’t get to the desktop, use the recovery Command Prompt to run wmic minidump or check the C:\Windows\Minidump folder for .dmp files after you boot into Safe Mode. You can analyze these with a tool like WinDbg, but even a quick web search of the stop code will often reveal the culprit.

Fix 5: Check Hardware and Reset BIOS

If all software fixes fail, the loop may be hardware-related. Here’s what to check:

RAM: Try reseating the memory sticks or testing them one at a time. You can also run Windows Memory Diagnostic from the recovery screen.
Hard drive: Listen for clicking sounds. In the recovery Command Prompt, run chkdsk /r C: to check for bad sectors (this can take hours).
Overheating: If the PC shuts down after a few minutes, check that fans are spinning and vents are clear.
BIOS: Reset the BIOS to default settings (look for “Load Optimized Defaults” or remove the CMOS battery for a minute). This can fix unstable overclocks or incorrect boot order.

If you recently installed new hardware, remove it and see if the loop stops. If you have a spare power supply or GPU, swapping parts can isolate the issue.

When to Reinstall Windows

If you’ve tried all the above and the loop persists, a clean reinstall is the last resort. You can do this from the recovery screen by choosing Troubleshoot → Reset this PC. You’ll have the option to keep your files (but not your apps) or remove everything. If the PC won’t even reach recovery, you’ll need a Windows installation USB to reinstall from scratch.

Before reinstalling, make sure you back up your data if possible—you can often copy files to an external drive from the recovery Command Prompt if you know the drive letter (e.g., copy D:\Users\YourName\Documents E:\backup).

Frequently Asked Questions

Why does my PC keep restarting before Windows loads?

This usually means the boot files are corrupted or a critical driver is failing at startup. It can also be caused by a failing hard drive or RAM. Try the recovery tools first; if the loop happens before the Windows logo, check BIOS boot order and hardware connections.

Can a Windows update cause a restart loop?

Yes, a failed or incompatible update is one of the most common causes. If you can boot into Safe Mode, uninstall the most recent update from Settings → Windows Update → View update history. Microsoft often releases a fix within days, so you can also wait and try updating again later.

How do I get into Safe Mode if I can’t boot normally?

Force a shutdown three times as described earlier, or use a Windows installation USB and select “Repair your computer.” From the recovery screen, go to Troubleshoot → Advanced options → Startup Settings → Restart, then press F4 for Safe Mode.

Will I lose my files if I run Startup Repair or use Command Prompt?

No, Startup Repair and the bootrec commands do not delete personal files. They only repair system files and boot configuration. However, if you choose “Reset this PC” and select “Remove everything,” your files will be erased—so always back up if you can.

What does the blue screen error code mean?

The stop code (e.g., INACCESSIBLE_BOOT_DEVICE or KERNEL_DATA_INPAGE_ERROR) indicates the type of failure. Search the exact code online along with your Windows version to find specific driver or hardware fixes. Disable automatic restart to see the code if it flashes too quickly.

Is a restart loop always fixable?

Most software-related loops are fixable with the steps above. Hardware failures (like a dead SSD or faulty RAM) may require replacing parts. If the loop persists after a clean install, it’s almost certainly a hardware issue.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →