The "Restarting" screen with spinning dots can legitimately take a while, especially after installing updates — but there's a real difference between "slow" and "actually stuck," and it's worth knowing how to tell them apart before assuming the worst.
How long is actually normal
- A regular restart with no updates pending: usually well under a minute or two.
- A restart that's installing updates ("Working on updates, don't turn off your computer" or similar): can reasonably take 10-20 minutes, sometimes longer for major feature updates. This is normal and expected — Windows is actually doing meaningful work during this time, not stuck.
- The very first restart after a large feature update: can occasionally take 30+ minutes as the system completes post-update configuration. Frustrating, but not necessarily a sign of a problem.
Signs it's likely actually stuck, not just slow
- No disk activity light blinking at all for an extended period (if your PC has a visible activity light) — genuine ongoing work usually shows at least intermittent disk activity
- It's been over 30-45 minutes with no progress indication of any kind, especially without an update-related message
- The screen looks frozen rather than showing the normal subtle animation of the spinning dots
What to do if you've waited a reasonable amount of time
If you're confident it's actually stuck rather than legitimately working:
- Press and hold the power button for about 10 seconds to force a shutdown
- Wait a few seconds, then power back on
- In most cases, Windows will resume the interrupted process and either complete it or detect the failure and attempt automatic repair
Risk to be aware of: force-restarting during an actual in-progress update installation carries some risk of leaving the system in a partially-updated, unstable state. This is exactly why patience genuinely matters here — if there's any reasonable chance it's still legitimately working (especially if you saw an "installing updates" message before this started), it's worth waiting longer than feels comfortable before forcing a restart.
If forcing a restart leads to a boot loop or repeated failure
If after force-restarting, the system repeatedly fails to complete startup, it should automatically enter the Windows Recovery Environment after a few failed attempts (or you can force this with 2-3 manual force-shutdowns during boot). From there, Troubleshoot → Advanced options → Startup Repair can often resolve issues from an interrupted update or boot process.
Going forward: avoid interrupting updates
To reduce the chance of hitting this in the future, avoid manually triggering restarts or shutting down abruptly when you know Windows Update is actively installing something — letting updates complete naturally, even if it takes a while, is generally safer than interrupting partway through.