A boot loop is when your computer starts, gets partway through loading Windows, then restarts — over and over, never reaching the desktop. You see the manufacturer logo or the Windows loading animation, then the screen goes black, and the process starts again. Sometimes it loops silently. Sometimes you catch a brief blue screen before the restart. Either way, the computer is unusable until you break the cycle.
The first goal is to stop the loop and get to a screen where you can make changes. Windows has a built-in recovery environment (WinRE) that loads from a separate partition on the drive, so it can work even when Windows itself cannot start.
If Windows fails to boot three times in a row, it should automatically enter the recovery environment on the fourth attempt. You will see a blue screen that says "Automatic Repair" or "Recovery" with options. If the computer is looping but never reaches this screen, it may be crashing too early in the boot process for Windows to count it as a failed boot — in that case, use the manual method below.
If the recovery environment still does not appear after multiple attempts, you may need a Windows installation USB. You can create one on another working computer using the Windows Media Creation Tool from Microsoft's website. Boot from the USB (usually by pressing F12, F2, or Del during startup to reach the boot menu) and select Repair your computer instead of Install.
Windows updates are the most common cause of boot loops. An update installs partially, the computer restarts to complete it, the installation fails, it restarts to try again, and the loop begins. If the blue recovery screen mentions anything about updates, this is almost certainly the cause.
Fix from the recovery environment:
Once Windows boots successfully after removing the update, go to Settings, Windows Update, and check for updates again. Microsoft often releases a fixed version of the problematic update within a few days. If the same update causes another boot loop, you can pause updates temporarily while Microsoft resolves the issue.
A newly installed or updated driver — especially a graphics driver — can cause a boot loop if it crashes during the Windows loading process. The crash happens so early that Windows restarts before you see anything useful.
Fix:
System files can become corrupted from a sudden power loss during an update, a failing storage drive, or malware. When a critical boot file is damaged, Windows starts loading, hits the corrupted file, crashes, and restarts.
Fix from the recovery environment:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows. This scans Windows system files and replaces corrupted ones from a cached copy. If SFC reports that it found and repaired files, close the command prompt and try restarting normallyDISM /Image:C:\ /Cleanup-Image /RestoreHealth. DISM repairs the component store that SFC uses as its source, so running DISM and then SFC again can fix issues that SFC alone cannotThe BCD store tells the computer where Windows is located on the drive and how to start it. If this data is corrupted, the computer may loop because it cannot find or start Windows properly.
Fix from the recovery environment command prompt:
bootrec /fixmbr — rewrites the master boot record (MBR systems only)bootrec /fixboot — writes a new boot sector. If this returns "Access is denied," run bootsect /nt60 sys first, then retrybootrec /rebuildbcd — scans for Windows installations and adds them to the BCD. When prompted, type Y to add the detected installationIf you cannot identify the specific cause, System Restore rolls back Windows to a previous point in time — before whatever change triggered the boot loop. This does not affect your personal files (documents, photos, downloads) but it will uninstall programs and drivers installed after the restore point date.
System Restore only works if restore points exist. Windows creates them automatically before major updates and software installations, but only if System Protection is enabled for the system drive. If no restore points are available, this option will not help.
A boot loop can also be caused by failing hardware, though this is less common than software causes. Signs that point to hardware:
Hardware-related boot loop diagnosis:
wmic diskdrive get status should return OK. For a more thorough check, boot from a USB and run the drive manufacturer's diagnostic tool. If the drive is failing, replace it — an SSD is the recommended replacement for a mechanical driveIf none of the above fixes resolve the boot loop, resetting Windows reinstalls the operating system while giving you the option to keep your personal files.
A reset removes all installed programs and drivers and returns Windows settings to their defaults. You will need to reinstall your applications afterward. But your personal files in the user folders (Desktop, Documents, Downloads, Pictures) are preserved if you chose Keep my files.
If your computer is stuck in a boot loop and you are not comfortable working in the recovery environment, or if you have tried these steps and the loop continues, LuxuriousComputers Repair in Marion can diagnose whether the cause is software or hardware and get it booting again.