How to Fix Windows Stuck on the Loading Screen

Windows stuck on the loading screen most often comes from corrupted system files that stop the operating system from finishing startup. The spinning dots appear under the Windows logo and never advance to the sign-in screen. The cause sits in damaged system files, a bad driver or update, a failing drive, or too many startup services competing during boot.

This article lists the ranked causes first, then gives step-by-step fixes ordered from forcing the system into recovery through to checking drive health. Each fix states the problem it resolves.

This stage is an operating-system problem that occurs after the Windows logo appears, 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 Safe Mode, Startup Repair, and the system file tools rather than BIOS settings, and they run from the Windows Recovery Environment when the desktop cannot be reached.

Why Does Windows Get Stuck on the Loading Screen?

Windows stuck on the loading screen is caused by a fault in the startup sequence, ranked here from most to least common:

• Corrupted system files — damaged operating-system files stop the boot sequence before the sign-in screen loads.
• A bad driver or update — a recent driver or Windows update introduces a fault that stalls startup.
• A failing drive — bad sectors on the system drive prevent Windows from reading the files it needs to boot.
• Too many startup services — conflicting services loading at boot leave the system hanging on the loading screen.
• A pending update loop — an update that cannot finish restarts and stalls on the loading screen repeatedly.

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.

Force Restart Into the Recovery Environment

Forcing the system into the Windows Recovery Environment opens the repair tools when the desktop cannot be reached. The Recovery Environment is the entry point for every fix that follows.

1. Hold the power button until the computer powers off.
2. Power it on, then force it off again as soon as the Windows logo appears.
3. Repeat the interrupted start three times.
4. On the next start, Windows opens Automatic Repair and then the Recovery Environment.
5. Select Advanced options to reach the repair tools.

Run Startup Repair

Running Startup Repair fixes the boot configuration and missing system files that prevent Windows from loading. The tool scans the boot files automatically and rebuilds the entries it finds broken.

1. From the Recovery Environment, select Troubleshoot.
2. Select Advanced options, then Startup Repair.
3. Choose the Windows installation when prompted.
4. Let the tool diagnose and repair the startup files.
5. Restart and check whether Windows reaches the sign-in screen.

Boot Into Safe Mode

Booting into Safe Mode loads Windows with a minimal driver set so a conflicting driver or service can be removed. A system that loads in Safe Mode but not normally has a startup conflict.

1. From Advanced options, select Startup Settings, then Restart.
2. Press the key for Safe Mode with Networking.
3. Once at the desktop, open Device Manager.
4. Disable or uninstall the most recently added driver.
5. Restart normally to test the change.

Reaching the desktop only in Safe Mode confirms a third-party driver or service, not the core operating system, is the cause.

Run SFC and DISM

Running System File Checker and DISM repairs the corrupted system files that most often cause the loading screen to hang. SFC restores damaged files and DISM repairs the underlying component store that SFC draws from.

1. From the Recovery Environment, open Advanced options and select Command Prompt.
2. Type sfc /scannow and press Enter, then wait for the scan to finish.
3. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
4. If running from offline recovery, point DISM at the Windows drive with the /Image switch.
5. Restart the computer and check whether Windows loads.

Run SFC again after DISM completes, because DISM repairs the component store that SFC needs to replace any remaining damaged files.

Uninstall the Last Update or Driver

Removing the most recent update or driver reverses a change that introduced the startup fault. A hang that began right after an update points to that update as the cause.

1. From Advanced options, select Uninstall Updates.
2. Choose Uninstall latest quality update, or the feature update if that matches the timing.
3. Confirm and let the removal complete.
4. Restart and test startup.
5. If a driver was the trigger, remove it from Safe Mode using Device Manager instead.

A pending update that loops can also be cleared with System Restore from Advanced options, which rolls the system back to a point before the update was applied.

Disable Startup Items With a Clean Boot

Performing a clean boot stops non-essential services and startup items that overload the loading sequence. Disabling them identifies whether a third-party item is stalling startup.

1. Boot into Safe Mode and open System Configuration by running msconfig.
2. On the Services tab, check Hide all Microsoft services, then disable the rest.
3. On the Startup tab, open Task Manager and disable each startup item.
4. Restart into a normal boot.
5. Re-enable items in groups to find the one responsible.

Use System Restore to Roll Back a Recent Change

Running System Restore reverses a recent change that started the loading-screen hang without removing personal files. A restore point captured before a bad update or driver returns the system to a working state in one step.

1. From the Recovery Environment, select Troubleshoot, then Advanced options.
2. Select System Restore and choose the Windows installation.
3. Pick a restore point dated before the hang began.
4. Confirm and let the restore complete, then restart.
5. Check whether Windows now reaches the sign-in screen.

System Restore depends on protection being enabled beforehand, so a system with no restore points available must rely on update removal and the system file tools instead. A restore that fails partway can be run again from the same point, since the operation is non-destructive to documents.

Check Drive Health

Checking the system drive confirms whether bad sectors are stopping Windows from reading its boot files. A failing drive produces long delays and repeated loading-screen hangs.

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 the blue screen of death once Windows does load.

Rebuild the Boot Configuration Data

Rebuilding the Boot Configuration Data repairs a damaged boot record that Startup Repair could not fix automatically. A corrupted boot store leaves Windows unable to locate the system files it needs, holding the system on the loading screen.

1. Open Command Prompt from the Recovery Environment.
2. Run bootrec /scanos to detect installed Windows entries.
3. Run bootrec /rebuildbcd and add the detected installation.
4. Run bootrec /fixmbr and bootrec /fixboot to repair the master boot record and boot sector.
5. Restart and check whether Windows reaches the sign-in screen.

An access-denied result on the fixboot command on a UEFI system means the EFI partition must be assigned a letter and repaired with the bcdboot command, which copies the boot files back to the EFI partition.

Free Up Drive Space and Reset the Update Components

Clearing drive space and resetting the update components breaks a pending update loop that stalls on the loading screen. An update that cannot finish for lack of space or a corrupted download restarts and hangs on each boot.

1. From the Recovery Environment Command Prompt, check free space on the Windows drive with the dir command.
2. Delete the contents of the SoftwareDistribution Download folder to clear failed update files.
3. Rename the SoftwareDistribution folder so Windows rebuilds it on the next start.
4. Remove large temporary files if the drive is near full.
5. Restart and let Windows attempt the update with a clean download.

A system drive that repeatedly fills points to oversized temporary files or a shadow-copy backlog, and clearing that space prevents the update loop from returning on the next cycle.

Key Takeaways

• 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.
• Use Safe Mode to remove a bad driver or service that loads normally but not minimally.
• Run SFC and DISM together to repair corrupted system files and the component store.
• Check drive health with chkdsk when delays and clicking suggest a failing disk.

Last Thoughts on Windows Stuck on the Loading Screen

Windows stuck on the loading screen is an operating-system fault that appears after the Windows logo, separating it from a power-on self test hang at the motherboard logo. Starting in the Recovery Environment with Startup Repair, then moving through Safe Mode, SFC and DISM, update removal, and a clean boot, resolves the software causes in order.

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 faults sits in the common PC problems hub.