How to Fix Windows 11 Stuck on Restarting Screen Forever

You clicked restart, the screen went to that circular dots animation, and now it’s been twenty minutes with nothing happening. No progress percentage, no disk activity light, just dots spinning in place like the computer forgot what it was doing mid-sentence. This windows 11 stuck on restarting screen forever situation is scarier than it needs to be, mostly because Windows gives you zero information about whether it’s actually doing something or just frozen.

Let’s figure out which one it is and get you unstuck.

Why It Fails

A “restarting” hang isn’t one bug, it’s Windows failing at one of several different stages, and the stage matters for how you fix it:

A pending update is applying during restart, not just the shutdown/boot cycle. This is the most common cause by a wide margin. When Windows Update needs to install something, it often does the real work during a restart rather than before it, and large cumulative updates can genuinely take 20-40 minutes on slower drives. Annoying, but not actually broken.

A driver failing to unload cleanly during shutdown. Some drivers — GPU drivers especially — don’t release control properly when Windows tries to shut down, which stalls the whole restart sequence indefinitely instead of timing out.

Fast Startup interfering with a proper restart cycle. This feature hibernates the kernel session instead of doing a full shutdown, and it occasionally gets into a state where restart doesn’t fully break that hibernation, leaving you stuck between two half-finished states.

A failing or dying storage drive. I hate to say it, but it’s true — an aging SSD or HDD with bad sectors can cause exactly this symptom, especially if the restart coincides with heavy disk writes from an update.

Peripheral conflicts during POST re-initialization. Occasionally a USB device, external drive, or docking station causes the restart to hang before Windows even fully loads back up, not during Windows shutdown at all.

Quick Answer

• Wait at least 30-45 minutes if you just installed an update before doing anything else — this fixes it more often than people expect
• Do a hard shutdown by holding the power button 10 seconds if it’s truly frozen
• Disconnect all non-essential USB devices and try restarting again
• Boot into Safe Mode to check if a driver is causing the hang
• Check Windows Update history after recovery to confirm whether an update was actually the cause

The waiting step feels unsatisfying, I know. But it’s genuinely the right first move most of the time.

Common Scenarios

• Stuck after a major feature update (23H2, 24H2-style releases) — usually just a slow update applying, especially on HDDs
• Stuck after a routine restart with no update pending — more likely a driver or Fast Startup issue
• Stuck specifically after connecting a new peripheral or dock — points to a hardware conflict during POST
• Stuck repeatedly, every single restart — suggests a deeper driver or disk health issue, not a one-off

Technical Comparison

Honestly the update-related hangs are the ones I get the most messages about, and they’re also the ones that need the least actual troubleshooting — just patience.

Step-by-Step Fixes

Step 1: Rule Out a Legitimate Update Install

If you know an update was pending, or you saw “Working on updates” before you restarted, give it real time. Thirty minutes minimum, and up to an hour on an older HDD isn’t unheard of. Check for disk activity — if your drive light is flickering, something’s happening even if the screen looks static.

Step 2: Force a Hard Shutdown If Truly Frozen

If there’s been zero disk activity for 45+ minutes and nothing’s changed:

1. Hold the power button for 10 seconds until it powers off completely
2. Wait 10 seconds
3. Power back on
4. Let it boot fully — this might trigger an automatic repair sequence, which is fine, let it run

And yeah, this feels like the nuclear option, but at this point continuing to wait isn’t accomplishing anything either.

Step 3: Boot Into Safe Mode to Isolate a Driver Issue

If the hang happens on every restart, not just once:

1. Force shutdown twice in a row during boot to trigger Automatic Repair
2. Choose Advanced options → Troubleshoot → Advanced options → Startup Settings → Restart
3. Select Safe Mode
4. If restart works fine from Safe Mode, a driver (usually GPU or a recently installed peripheral driver) is the likely cause

Step 4: Disable Fast Startup

1. Boot into Windows normally (or Safe Mode if that’s all that’s working)
2. Control Panel → Power Options → Choose what the power buttons do
3. Click “Change settings that are currently unavailable”
4. Uncheck “Turn on fast startup”
5. Restart and see if the behavior changes

Fast Startup is one of those features that’s genuinely useful most of the time but causes a disproportionate number of restart and shutdown headaches when it goes wrong.

Step 5: Check Disk Health

From Safe Mode or a recovered session, open an elevated Command Prompt and run:

chkdsk C: /f /r

This requires a restart to run fully, so schedule it for when you can leave the PC alone for a while — on a large or aging drive, it can take hours.

What Actually Worked For Me

Most of the time when I’ve hit this, it really was just a big update taking forever on an older laptop, and walking away for coffee solved it more often than any actual troubleshooting did. Not the most exciting answer, but true.

The one time it wasn’t that simple, though, was genuinely frustrating. Forced shutdown, restarted, hung again at the exact same point. Did that twice more before trying Safe Mode, which worked fine — so I figured driver issue, probably GPU. Updated the GPU driver, still hung on normal restart. Disabled Fast Startup, still hung.

What actually fixed it, somewhat annoyingly, was unplugging a USB dock that had been connected the whole time. Never would’ve suspected it since it wasn’t new hardware — I’d been using that same dock for months. Not 100% sure why it suddenly started causing a problem, but once it was disconnected during restart, everything went back to normal. Plugged it back in afterward with zero issues, which honestly bugs me more than if it had just stopped working outright.

Advanced Fixes and Edge Cases

Check Event Viewer after a forced recovery. Windows Logs → System, look around the timestamp of the hang for Kernel-Power or Disk warnings. A Kernel-Power Event ID 41 often indicates an unclean shutdown was recorded, which can point toward power delivery or driver issues rather than pure software.

Use Reliability Monitor to spot a pattern. If the hang correlates with a specific driver update or software install, Reliability Monitor will often show that install right before the pattern started.

Check BIOS/UEFI power settings if the issue happens at the hardware level, not within Windows. Some motherboards have their own “fast boot” equivalent at the firmware level that can conflict with Windows’ own restart handling, especially with Secure Boot enabled alongside certain third-party disk encryption tools.

Consider a corrupted Windows Update cache. From an elevated Command Prompt, stopping the Windows Update service and clearing the SoftwareDistribution folder can resolve hangs tied specifically to a stuck update install rather than a general restart bug.

Prevention Tips

• Don’t force shutdown during an update unless you’ve genuinely waited long enough — interrupting an update mid-install can cause worse problems than the hang itself
• Keep GPU and chipset drivers reasonably current, but don’t feel obligated to update the moment every new version drops
• Periodically disconnect and reconnect peripherals, especially docks and hubs, just to rule them out as a habit rather than a crisis response
• Run disk health checks occasionally on older drives before they start causing restart or boot problems

FAQ

How long should I actually wait before assuming it’s frozen, not updating? Give it at least 30 minutes if you know an update was pending, longer on older hardware. If there’s zero disk activity the whole time, that’s a stronger sign of an actual freeze.

Can I lose files if I force shutdown during a restart? It’s possible, especially if an update is mid-install, which is exactly why waiting first matters so much.

Does this happen more on laptops or desktops? Both, but laptops with slower eMMC or older SSD storage tend to hit update-related hangs more often just due to write speed.

Is this the same issue as a black screen after restart? Related but not identical — a black screen with no dots animation at all often points more toward a GPU driver or display connection issue specifically, not a general restart hang.

Editor’s Opinion

the annoying part of this one is that half the time the fix is just “wait longer” which feels wrong when your staring at a frozen screen for 40 minutes. but its true more often then not. if your on the third or forth restart with the same hang tho, thats when i’d start actually troubleshooting instead of just waiting again — that pattern usually means somethings actually wrong, not just a slow update