How to Fix Windows 11 Stuck on Restarting Screen — The Process That Refuses to Close

You clicked Restart. The screen went black, the Windows logo appeared, and the familiar spinning dots animation started. Everything looks normal. The restart should take 30 seconds to a minute.

Five minutes pass. The dots are still spinning. Ten minutes. Still spinning. You go make coffee, come back, and the dots are still going. It has been 25 minutes and your computer is stuck on the exact same screen — “Restarting” with dots spinning in an infinite loop.

Your computer is not frozen. The dots are animating smoothly, which means the CPU is running. But the restart process itself is stuck. Something inside Windows is preventing the restart from completing — a process that will not close, a service that will not stop, or an update that is waiting for something that will never happen.

Why Windows Gets Stuck on Restarting

The restart process follows a specific sequence:

1. Windows sends a close signal to all running applications
2. Applications save their state and close
3. Windows sends a stop signal to all running services
4. Services complete their current operations and stop
5. Windows unmounts file systems and flushes disk caches
6. Windows signals the hardware to perform a warm reboot
7. The BIOS/UEFI reinitializes and boots Windows fresh

When the restart gets stuck, it is almost always at step 2 or 3 — an application or service received the close/stop signal but has not responded. Windows waits for a response before proceeding to the next step, and depending on configuration, it can wait forever.

Common culprits:

Windows Update services. The TrustedInstaller service, Windows Update service, and Windows Modules Installer often hang during restart because they are in the middle of staging or applying update files. The update process holds locks on system files and cannot release them if something goes wrong during the staging phase.

Antivirus software. Real-time protection services sometimes hang during shutdown because they are still scanning a file or writing log data and do not respond to the stop signal promptly.

Print spooler. The Print Spooler service is notorious for hanging during shutdown, especially when it has stuck print jobs in its queue.

VPN clients. VPN services that manage network tunnels and virtual adapters sometimes fail to disconnect cleanly during restart, holding the network stack in a partially torn-down state.

Cloud sync services. OneDrive, Google Drive, Dropbox — if they are in the middle of syncing a large file during restart, they may hang while trying to complete or abort the sync operation.

The Wait-Then-Force Approach

Step 1: Wait 15 minutes first.

This sounds like a long time, but there are legitimate reasons the restart might take a while:

• Windows Update is installing updates during the restart phase (you may have clicked “Update and restart”)
• A large disk cache is being flushed to storage
• System file operations from a recent update are completing

Look at the hard drive/SSD activity indicator on your laptop. If it is blinking, Windows is still working — the disk is being written to. Be patient.

If the activity light has been solid dark (no blinking) for more than 5 minutes while the spinning dots continue, the system is stuck.

Step 2: Force restart.

Press and hold the power button for 10 seconds. The computer shuts off completely. Wait 10 seconds, then press the power button to turn it back on.

On the next boot, Windows may:

• Show “Preparing automatic repair” briefly, then boot normally
• Boot directly to the desktop with no issues
• Enter the Windows Recovery Environment if it detects abnormal shutdown

In most cases, the computer boots normally after the forced restart. The stuck process was terminated by the hard shutdown, and on the fresh boot, everything initializes cleanly.

Is this safe? Yes. Modern file systems (NTFS) use journaling — every file write operation is logged before it is executed. If a write is interrupted by a power loss, the journal allows the file system to roll back or complete the partial write on the next boot. Data corruption from a hard shutdown on NTFS is extremely rare.

The one exception: if you can hear the hard drive actively grinding (constant activity light, audible disk noise) at the moment you press the power button, you are interrupting an active write. Wait for the activity to stop before forcing the shutdown. On SSDs, there is no audible noise, but the activity light tells you the same information.

Preventing Future Restart Hangs

Disable Fast Startup

Fast Startup creates a hybrid shutdown state that can carry over problematic process states between sessions:

1. Control Panel → Power Options → Choose what the power buttons do
2. Click “Change settings that are currently unavailable”
3. Uncheck “Turn on fast startup”
4. Click Save changes

Set Aggressive Shutdown Timeouts

By default, Windows waits several seconds for each application and service to close during shutdown. If an application is hung, this wait can stack up — 10 hung processes at 5 seconds each is nearly a minute of waiting before Windows even starts force-closing them.

You can reduce these timeouts:

Open Registry Editor (regedit) and navigate to:

HKEY_CURRENT_USER\Control Panel\Desktop

Find or create these values:

• WaitToKillAppTimeout (String value): set to 2000 (2 seconds instead of the default 5000). This is how long Windows waits for applications to respond to the close signal.
• AutoEndTasks (String value): set to 1. This tells Windows to automatically close hung applications during shutdown without waiting for user intervention.

Also navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

Find or create:

• WaitToKillServiceTimeout (String value): set to 2000 (2 seconds). This controls how long Windows waits for services to stop.

These changes make the shutdown and restart process more aggressive — Windows gives processes 2 seconds to close cleanly, then force-terminates them. The trade-off is that applications with slow save operations (like a large document in an unsaved state) have less time to save before being killed. But for the vast majority of users, 2 seconds is more than enough, and the benefit of a restart that actually completes outweighs the minor risk.

Check for Stuck Windows Updates

Partially installed updates are a common cause of recurring restart hangs:

1. Settings → Windows Update → check for pending updates
2. Install any available updates and let them complete
3. If updates appear stuck, run the Windows Update Troubleshooter: Settings → System → Troubleshoot → Other troubleshooters → Windows Update

To manually reset a stuck update state, open Command Prompt as Administrator and run:

net stop wuauserv
net stop bits
del /f /s /q C:\Windows\SoftwareDistribution\*
net start wuauserv
net start bits

This stops the update services, clears the update cache (which may contain corrupted update files), and restarts the services. On the next update check, Windows downloads fresh copies of any needed updates.

Identify the Hanging Process

If restarts hang regularly, identify the specific process that causes the hang:

1. Before restarting, open Event Viewer → Windows Logs → System
2. After the next restart (forced or successful), check for events around the restart timestamp
3. Look for events from User32 with Event ID 1074 (clean shutdown) or 6008 (unexpected shutdown)
4. Check for warnings from services that took too long to stop

You can also enable verbose shutdown status messages to see exactly what Windows is doing during restart:

Registry Editor → HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System → create DWORD VerboseStatus → set to 1

With this enabled, instead of seeing just “Restarting…” with spinning dots, the screen shows specific status messages: “Stopping service: Print Spooler,” “Waiting for application: Zoom,” etc. When the restart hangs, the last message displayed tells you exactly which process is the problem.

A restart that hangs is Windows being too polite — it waits patiently for processes that will never respond instead of just killing them and moving on. The registry timeout changes make Windows less patient and more decisive. Combined with identifying and fixing the specific service or application that causes the hang, you get a computer that restarts in 30 seconds instead of sitting on the Restarting screen until you lose patience and hold the power button.