Windows 11 Stuck on Restarting
How to tell whether your PC is really frozen on the Restarting screen, power it off without corrupting anything, and repair it from the Windows recovery menu.
If Windows 11 has been sitting on “Restarting” with the spinning dots and nothing is changing, the order that works is: disconnect external devices, hold the power button until the screen goes black, then let the machine open its own recovery environment and run Startup Repair. If the hang started after an update, uninstalling that update from the recovery menu is the first repair worth trying. One exception outranks every step below: if the screen says “Working on updates” with a percentage, leave it alone.
First, check whether it is actually stuck
Microsoft’s boot-troubleshooting guidance starts with signs of life rather than fixes. Look at the hard-disk activity light, and press NumLock to see whether its indicator toggles. Either one responding means Windows is still working behind an unchanged screen; nothing moving on either usually means it is wedged. There is no official waiting time here, and Microsoft publishes no figure for it, so treat any “wait two hours, per Microsoft” advice as invented. As a judgment call, a few minutes is a fair pause for a plain restart, longer if the machine was mid-update.
Then clear the desk. Microsoft’s documented first step for boot problems is blunt: “If there are any external peripherals connected to the computer, disconnect them.” Docks, external drives, USB hubs, card readers and game controllers all take part in shutdown and startup. Leave the keyboard and mouse; unplug the rest.
What the screen is telling you
The word on screen changes what you should do, and merging these states is how people lose data.
| What is on screen | What Windows is doing | What to do |
|---|---|---|
| “Restarting” with spinning dots, no percentage | Waiting for an app, service or driver to close | Give it a few minutes, unplug peripherals, then force the power off |
| “Working on updates X% complete. Don’t turn off your computer.” | Installing an update; the time “depends on connection speed, network settings, and the size of the update” | Leave it running. This is the screen you least want to interrupt |
| Black screen after the logo, or a stuck spinning wheel | A kernel-phase symptom in Microsoft’s boot-troubleshooting list | Force into recovery, try Safe Mode, then a clean boot |
| It restarts, hangs, restarts again | Repeated boot failure | Recovery opens by itself after two failed starts; run Startup Repair, then Uninstall Updates |
| A blue screen flashing past too fast to read | Automatic restart on system failure is on | Use Startup Settings option 9 to hold the stop code on screen |
Force the power off once, and do it properly
Press and hold the power button until the screen goes black, wait a few seconds, then press it again. Ignore any article that gives one universal hold time. Microsoft’s Event ID 41 article calls the gesture “pressing and holding the power button for at least four seconds,” while its own Surface instructions say about 20 seconds on recent models, or volume-up plus power for about 15 seconds on older ones. Hold until the screen goes black; that is the only version true on every machine.
Microsoft’s caution is worth repeating: use this method “only if you’ve no alternative,” because “a dirty shutdown can cause data loss or corruption and can also lead to boot-up problems.” Do it once, deliberately, after the PC has clearly stopped moving.
One program can hold up the whole restart. When a shutdown begins, Windows sends a WM_QUERYENDSESSION message to every running app that has a user interface and waits for each one to agree. After five seconds it displays the applications that are preventing shutdown so you can end them. If your PC gets that far, that screen names the culprit, so write the name down before you cut the power.
Get into the recovery environment
The Windows Recovery Environment is where the real repairs live. It starts on its own after two consecutive failed startup attempts, or two unexpected shutdowns or reboots within two minutes of the boot completing. Two, not three. Windows sets a flag when startup begins and clears it before the sign-in screen; if it is still set next time, the loader assumes a failure and opens recovery. Microsoft notes this can misfire, since losing power during startup looks identical to a crash.
To force it on a machine that will not boot, Microsoft’s consumer instruction is to start the device, press and hold the power button when the Windows logo appears to shut it down, repeat that interruption a second time, then turn the device on a third time. Windows should display the Automatic Repair screen, where you select Advanced options.
If the PC still boots and you want to get there on purpose, use Settings > System > Recovery > Advanced startup > Restart now, or select the power icon on the sign-in screen and hold Shift while you click Restart, or run shutdown /r /o from a command prompt. The /o switch goes to the advanced boot options menu and must be used with /r; adding /t 0 skips the default 30-second delay.
On Windows 11 you can run most recovery tools without selecting an administrator account and entering a password, but encrypted volumes still ask for the BitLocker recovery key. Look in your Microsoft account under your devices, in a work or school account’s device list, on the printout made when BitLocker was turned on, or on a USB drive. Microsoft states in writing that its support staff cannot retrieve or recreate a lost key.
On Windows 11 version 24H2 build 26100.4700 or later, unmanaged Home and Pro PCs also have quick machine recovery: after repeated boot failures it connects recovery to Windows Update and looks for a published fix. It needs a wired connection or password-based WPA/WPA2 Wi-Fi, and Microsoft calls it “a best-effort feature.”
Work through the recovery menu in order
| Tool | Path from the recovery screen | What it costs you |
|---|---|---|
| Startup Repair | Troubleshoot > Advanced options > Startup Repair | Nothing; it repairs system files, boot configuration data, the master boot record, drivers and registry errors |
| Uninstall Updates | Troubleshoot > Advanced options > Uninstall Updates | The latest quality or feature update. Some updates cannot be uninstalled |
| Startup Settings | Troubleshoot > Advanced options > Startup Settings > Restart | Nothing; it gets you Safe Mode or a readable stop code |
| Point-in-time restore | Troubleshoot > Point-in-time restore, if your menu lists it | Rolls the whole PC back, personal files included |
| Reset this PC | Troubleshoot > Reset this PC | Every installed app and setting, even when you keep your files |
Run Startup Repair first. Microsoft describes it as a tool “that can fix certain system problems that might prevent Windows from starting,” and it is the safest thing in the menu. When it finishes, Microsoft’s instruction is to select Shutdown and then turn the PC on, rather than restarting from inside recovery. Its log sits at %windir%\System32\LogFiles\Srt\Srttrail.txt.
If the hang started right after patch day, Uninstall Updates is the one to try next. Choose the latest quality update (a monthly patch) or the latest feature update (the annual version), and note Microsoft’s plain warning that some updates cannot be uninstalled. Our piece on whether to install Windows updates right away covers the trade-off for next time.
Startup Settings gets you the numbered boot list: 4 or F4 for Safe Mode, 5 or F5 for Safe Mode with Networking, and 9 for “Disable automatic restart on system failure,” which holds a blue screen up long enough to copy the stop code. If restarts behave normally in Safe Mode on Windows 11, a third-party driver or service is the cause. Microsoft’s next step is a clean boot: search msconfig, on the Services tab select Hide all Microsoft services then Disable all, and on the Startup tab open Task Manager and disable each enabled item. Re-enable in batches until the culprit reappears. A driver that will not install cleanly is a common one.
After several forced power-offs, a disk check is reasonable from the recovery command prompt. Confirm the Windows drive letter first, because in recovery it is often not C:, then run chkdsk C: /f /r with the letter you confirmed in place of C:. On a large hard drive Microsoft warns that “high-hour runtimes aren’t uncommon.”
Rollbacks are the last tier. If your menu shows Point-in-time restore (Windows 11 version 24H2 or later; Microsoft describes starting it from recovery as in preview), it restores an automatic restore point kept up to three days, personal files included, so anything newer is gone. System Restore rolls back system files and settings but not personal files. If the hang began right after a version upgrade, “Go back” is available for 10 days, not 30. Resetting Windows 11 is genuinely last: keeping your files still removes every app and setting.
Once Windows boots again, fix the cause
Open Event Viewer and read the System log. Event ID 1074 shows what actually asked for the restart, 41 means the system rebooted without shutting down cleanly, 6008 flags an improper shutdown, and 6006 is a clean one. That is usually enough to tell a hung app from a crash.
Then repair the system files, in Microsoft’s order. In an elevated Command Prompt (type cmd in Search, right-click Command Prompt, choose Run as administrator), run DISM.exe /Online /Cleanup-image /Restorehealth and then sfc /scannow. DISM supplies the files System File Checker needs, so running it second defeats the point. Neither is documented as a cure for a restart hang; both are sensible hygiene once you are back in Windows.
Finish with the update path. Run the Windows Update troubleshooter at Settings > System > Troubleshoot > Other troubleshooters > Windows Update, and check free space, since Microsoft wants at least 20 GB free to upgrade a 64-bit system; our guide to freeing up space on Windows 11 is the quickest route there. If the PC boots but keeps misbehaving and your Recovery page lists Fix problems using Windows Update, Reinstall now reinstalls the current version and “preserves your apps, files, and settings.” It needs a reasonably current Windows 11, is hidden on work- or school-managed PCs, and only runs from inside a working Windows, so it is the follow-up repair, not the emergency one.
Popular fixes that do not apply here
Turning off fast startup is the most common wrong answer to this exact problem. Microsoft’s documentation on fast startup states that “the Fast Startup setting doesn’t apply to Restart,” that restart “continues to perform a full boot cycle,” and separately that “disabling Fast Startup is not recommended.” Fast startup can interfere with a shutdown or a hibernate; it has no role in a restart.
Copying registry hives out of the RegBack folder is equally dead. Since Windows 10 version 1803 Windows no longer backs the registry up there by design, so the folder is normally empty; Microsoft’s recommendation for a corrupt hive is a system restore point. Pressing F8 during boot does not open Safe Mode either, because the legacy boot menu is off by default. And the registry timeout tweaks suggested for hung shutdowns are not documented by Microsoft as a fix for this.
The recovery environment covers this whole job with what already ships on the PC, so there is no third-party boot-repair tool to buy. If you do only two things, force the power off cleanly once, then let Startup Repair and Uninstall Updates run. Write down the stop code or blocking app name you saw, because that is what turns a repeat into a five-minute fix.