9 Ways to Fix Windows Hanging on the Shutdown Screen in 2026

Windows is stuck on “Shutting down…” and won’t finish, or it restarts instead of powering off entirely. Modern Windows 10 and 11 have introduced new culprits like Fast Startup and Virtualization-Based Security (VBS) that the old advice doesn’t cover.

Fix #1: Use the shutdown command to bypass the GUI

If Windows is hanging at the shutdown screen right now, this gets you out immediately, and it’s Microsoft’s own documented workaround for the January 2026 VBS-related shutdown regression that affected Windows 10 and 11.

1. Press Windows + S and type cmd.

2. Right-click Command Prompt and select Run as administrator.

3. Type the following and press Enter:

shutdown /s /t 0

Windows should power off within seconds. If this works consistently but the normal shutdown button doesn’t, create a desktop shortcut: right-click the desktop, choose New > Shortcut, and enter shutdown.exe /s /t 0 as the target. Use it until the underlying cause is resolved.

Fix #2: Disable Fast Startup

Fast Startup is enabled by default on most Windows 10 and 11 machines. Instead of a full shutdown, it saves a partial system state to disk, which can cause the shutdown sequence to hang, complete only partially, or make the machine power back on by itself. Disabling it forces a clean, full shutdown every time.

1. Open Control Panel (search for it in the Start menu).

2. Go to Hardware and Sound > Power Options.

3. Click Choose what the power buttons do in the left pane.

4. Click Change settings that are currently unavailable.

5. Under Shutdown settings, uncheck Turn on fast startup (recommended).

6. Click Save changes.

Restart once and then test a normal shutdown. This single change fixes the hanging problem for a large number of users.

Fix #3: Check for a known Windows Update bug

A regression in the January 2026 cumulative updates caused Windows 10 (ESU) and Windows 11 systems, particularly those with VBS or Secure Launch enabled, to hang on “Shutting down…”, restart instead of powering off, or power back on shortly after shutdown. Microsoft acknowledged the issue and released out-of-band hotfixes.

1. Open Settings.

2. – Windows 11: Go to Windows Update > Update history. – Windows 10: Go to Update & Security > Windows Update > View update history.

3. Look for any cumulative update installed immediately before the shutdown problem started.

4. Search that KB number plus the word “shutdown” at learn.microsoft.com/windows/release-health to check for a documented issue.

5. If Microsoft has released an out-of-band fix, install it via Windows Update > Check for updates.

If no fix is available yet, use the shutdown /s /t 0 shortcut from Fix #1 as a temporary workaround while you wait.

Fix #4: Isolate a blocking app with Clean Boot

Cloud sync tools (OneDrive, Dropbox), VPN clients, antivirus software, and RGB lighting controllers are all common shutdown blockers. A clean boot disables all third-party services and startup apps so you can confirm whether one of them is the culprit.

1. Press Windows + R, type msconfig, and press Enter.

2. On the Services tab, check Hide all Microsoft services, then click Disable all.

3. On the Startup tab: – Windows 11: Click Open Task Manager, then disable every non-Microsoft startup item. – Windows 10: Same, click Open Task Manager and disable all startup items.

4. Click OK and restart.

5. After reboot, attempt a normal shutdown.

If shutdown completes normally in clean boot, re-enable your disabled services and startup items in small groups, restart and test after each batch, until the problematic one surfaces. Antivirus, VPN, and cloud backup software are the most frequent offenders.

Fix #5: Update or reinstall network and storage drivers

Windows sends shutdown commands to your network adapter during power-off; a buggy driver can cause the entire sequence to stall waiting for a response that never comes. NVMe SSD drivers and chipset drivers are also common culprits on modern hardware.

1. Press Windows + X and select Device Manager.

2. Expand Network adapters, right-click your adapter, and select Update driver > Search automatically for drivers.

3. Repeat for Disk drives (NVMe or SATA SSD).

4. For the most reliable drivers, visit your PC manufacturer’s support site (Dell, HP, Lenovo, etc.) or your motherboard manufacturer’s site and download chipset, network, and storage drivers directly.

5. If updating doesn’t help, right-click the network adapter in Device Manager and choose Uninstall device, then restart, Windows will reinstall a clean copy automatically.

Also test with any external devices (USB docks, Thunderbolt peripherals, external drives) disconnected. If shutdown completes normally without them, the driver for that specific device is the problem.

Fix #6: Check Event Viewer for services blocking shutdown

Windows logs exactly which services fail to stop cleanly. Event Viewer can point you straight to the culprit without guessing.

1. Press Windows + X and select Event Viewer.

2. In the left pane, expand Windows Logs and click System.

3. Click Filter Current Log in the right pane.

4. In the Event sources dropdown, check Service Control Manager, then click OK.

5. Look for errors or warnings timestamped around your last shutdown attempt. Note the service names mentioned.

6. Also look for Event ID 41 (unexpected power loss) and Event ID 1074 (planned shutdown/restart).

Once you identify a problematic service, update, disable, or uninstall the software associated with it.

Fix #7: Repair system files with SFC and DISM

Corrupted Windows system files can break the shutdown sequence. Running SFC followed by DISM repairs both individual files and the underlying component store they’re pulled from.

1. Press Windows + S, type cmd, right-click Command Prompt, and select Run as administrator.

2. Run the following command and wait for it to finish (it can take 10–15 minutes):

sfc /scannow

3. After SFC completes, run:

DISM /Online /Cleanup-Image /RestoreHealth

4. Restart when DISM finishes, then test shutdown.

If SFC reports it found and repaired corrupt files, that was likely contributing to the hang.

Fix #8: Disable the “Clear virtual memory pagefile” policy

A Group Policy setting called Shutdown: Clear virtual memory pagefile forces Windows to wipe the paging file on every shutdown. Security software sometimes enables this silently, and on large paging files it can add many minutes to shutdown time.

1. Press Windows + R, type gpedit.msc, and press Enter. (This is only available on Windows 10/11 Pro, Enterprise, and Education, not Home.)

2. Navigate to: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.

3. Find Shutdown: Clear virtual memory pagefile and double-click it.

4. Set it to Disabled and click OK.

Restart once to apply the policy, then test shutdown speed.

Fix #9: Temporarily disable Memory Integrity (VBS regression workaround)

If your shutdown hang started immediately after a Windows update and nothing else has worked, the January 2026 VBS/Secure Launch regression may be the cause. Temporarily disabling Memory Integrity removes the trigger while you wait for or install the corrective update. This reduces your system’s protection against kernel-level attacks, re-enable it as soon as you’ve installed the relevant fix.

1. Search for Windows Security in the Start menu and open it.

2. Click Device security.

3. Click Core isolation details.

4. Toggle Memory integrity to Off.

5. Restart and test shutdown.

6. Return to this setting and re-enable it after installing the latest cumulative update from Windows Update.

Check Windows Release Health for the specific KB number that addresses the regression on your Windows version, and install it promptly.

When none of the fixes work

If shutdown hangs persist after all of the above, a Windows repair install (in-place upgrade) is the next step. Download the latest Windows ISO using the Media Creation Tool, run setup.exe from within Windows, and choose Keep personal files and apps. This refreshes all Windows system components without wiping your data. If even that doesn’t resolve it, a hardware fault, most commonly a failing storage drive, may be the root cause; run a full drive health check with your manufacturer’s diagnostic tool before reinstalling Windows from scratch.

Conclusion

Disabling Fast Startup (Fix #2) solves this for the majority of users, it’s the first thing to try on any Windows 10 or 11 machine that hangs at shutdown. If your problem started right after a Windows update in early 2026, Fix #3 and Fix #9 are the most relevant. A shutdown that takes forever and started out of nowhere, with no recent updates or hardware changes, almost always points to a third-party service caught by the clean boot in Fix #4.