How to Fix Windows Stuck on the Loading Screen

This stage is an operating-system problem that appears after the Windows logo, which separates it from a power-on self test hang at the motherboard logo. Because the firmware has already handed control to Windows, the fixes use a wait, a peripheral check, Safe Mode, Startup Repair, and the system file tools rather than BIOS settings, and the recovery steps run from the Windows Recovery Environment when the desktop cannot be reached.

What Causes Windows to Get Stuck on the Loading Screen?

Windows stuck on the loading screen comes from a fault in the startup sequence, and four causes account for almost every case.

The table below maps each symptom to its most likely cause.

Because this stage runs after the firmware finishes, knowing what an operating system is clarifies why these fixes target Windows components rather than hardware initialization.

How Do You Fix Windows Stuck on Loading?

Work through these steps in order, because each one is faster and safer than the next and rules out the most common causes first.

• Wait it out. Leave the spinning dots for at least fifteen minutes, or longer if a percentage or a Working on updates message is showing, since a large update can take an hour or more. A blinking drive-activity light means the system is still working.
• Unplug all peripherals. Shut down by holding the power button, disconnect every USB drive, external disk, printer, and dock, leave only the monitor and internal disk, then power on and watch for the sign-in screen.
• Open the Recovery Environment. If it still hangs, force the start and power off as the Windows logo appears, three times. The next start opens Automatic Repair and then the Recovery Environment, where the rest of the fixes live.
• Run Startup Repair. From Troubleshoot, Advanced options, choose Startup Repair and let it scan and rebuild the boot files automatically. This is the single highest-yield fix for a boot configuration fault.
• Boot into Safe Mode. From Advanced options, Startup Settings, Restart, press 4 or 5. Safe Mode loads a minimal driver set; if Windows reaches the desktop here, a third-party driver or service is the cause, and you remove it in Device Manager.
• Uninstall the recent update or driver. From Advanced options, choose Uninstall Updates and remove the latest quality or feature update, or remove the driver from Safe Mode. Use this when the hang began right after an update, including the 2026 24H2 and 25H2 update failures.
• Run System Restore. From Advanced options, choose System Restore and pick a restore point dated before the hang. It reverses a bad update or driver in one step without touching personal files.
• Run SFC and DISM. From Advanced options, Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow to repair the component store and replace corrupted system files. Run SFC again after DISM finishes.
• Check the disk. Still in Command Prompt, run chkdsk C: /f /r to scan and repair the system drive. Long delays and clicking point to bad sectors; back up and replace the drive if unrecoverable sectors appear.

Startup Repair is the first tool to reach for because it fixes the boot configuration and missing system files without any commands. If it cannot repair the boot record, rebuilding the Boot Configuration Data from Command Prompt with bootrec /scanos, bootrec /rebuildbcd, bootrec /fixmbr, and bootrec /fixboot is the manual fallback. An access-denied result on fixboot on a UEFI system means the EFI partition needs a letter and a bcdboot repair.

How Do You Repair Corrupted System Files From Recovery?

System File Checker and DISM repair the damaged system files that most often hold the loading screen, and they run from the Recovery Environment Command Prompt when the desktop is out of reach. SFC restores individual protected files, while DISM repairs the underlying component store that SFC draws its healthy copies from.

1. From the Recovery Environment, open Advanced options and select Command Prompt.
2. Run DISM /Online /Cleanup-Image /RestoreHealth first to repair the component store.
3. If running fully offline, point DISM at the Windows drive with the /Image switch instead of /Online.
4. Run sfc /scannow to replace any corrupted protected files.
5. Restart and check whether Windows reaches the sign-in screen, then run SFC once more to confirm.

Run SFC again after DISM completes, because DISM repairs the component store that SFC needs to replace any remaining damaged files. The same tools and the wider repair routine are covered in how to fix corrupt system files.

How Do You Clear a Stuck or Looping Update?

A pending update that cannot finish restarts and stalls on each boot, and clearing the failed download breaks the loop. Removing the update or resetting the update components returns Windows to a clean state so the install can be retried.

1. From Advanced options, select Uninstall Updates and remove the latest quality update, or the feature update if that matches the timing.
2. If the update keeps returning, open Command Prompt and clear the SoftwareDistribution Download folder to remove failed update files.
3. Rename the SoftwareDistribution folder so Windows rebuilds it on the next start.
4. Free drive space if the disk is near full, since an update needs room to stage and apply.
5. Restart and let Windows attempt the update with a clean download, or use System Restore to roll back the change.

In 2026, some Windows 11 24H2 and 25H2 updates caused boot failures on affected PCs, and Microsoft shipped a fixed update and an automatic Known Issue Rollback to mitigate them. After removing a bad update, check Microsoft release health for the corrected build before reinstalling, and see how to fix Windows update errors for the full update-repair routine.

How Do You Check Whether the Drive Is Failing?

Checking the system drive confirms whether bad sectors are stopping Windows from reading its boot files. A failing drive produces long delays, clicking noises, and loading-screen hangs that worsen over time.

1. Open Command Prompt from the Recovery Environment.
2. Run chkdsk C: /f /r to scan and repair the system drive.
3. Let the scan complete, which can take a long time on a large drive.
4. Review the result for bad sectors that could not be repaired.
5. Back up data and replace the drive if unrecoverable sectors are found.

Repeated hangs alongside disk strain can also surface as 100 percent disk usage, and a drive on the edge of failure may produce a blue screen of death once Windows does load.

Last Thoughts on Windows Stuck on the Loading Screen

Windows stuck on the loading screen is a software fault that appears after the Windows logo, which separates it from a power-on self test hang at the motherboard logo. The fastest path is to wait the spinning dots out for fifteen minutes, force a restart with every USB device unplugged, and only then open the Recovery Environment. From there, Startup Repair, Safe Mode, update removal, System Restore, and the SFC and DISM tools resolve the software causes in order, with a chkdsk scan reserved for a drive that shows signs of failing.

A hang that began at the motherboard logo instead belongs to a computer stuck on the boot screen, and persistent delays with disk strain point toward 100 percent disk usage. The wider catalogue of startup and performance faults sits in the common PC problems hub.

Key Takeaways:

• Wait the spinning dots out for at least fifteen minutes before forcing a restart, longer if a percentage is showing.
• Unplug every USB and external device next, since a faulty peripheral can stall the boot on its own.
• Force three interrupted starts to open the Recovery Environment when the desktop cannot be reached.
• Run Startup Repair first, because it fixes the boot configuration automatically with no commands.
• Use Safe Mode to isolate a bad driver or service, and Uninstall Updates or System Restore to reverse a bad update.
• Run DISM then SFC to repair system files, and chkdsk when delays and clicking suggest a failing drive.

Frequently Asked Questions (FAQs)