How to fix
Windows 11/10 won’t shut down
on windows

Windows 11 or Windows 10 won’t shut down, and it either stays on the shutdown screen or restarts after I click Shut down.

That failure usually appears after choosing Shut down from the Start menu or after a power command that should end the session completely. Instead of powering off, the system may hang, loop back into Windows, or keep closing and reopening the same session state. On some machines the screen goes dark for a moment and then the computer comes back up, while on others Windows appears to begin shutdown but never finishes the process. The behavior has been reported across multiple Windows 10 builds, and the same shutdown logic also exists in Windows 11, so the problem can surface in either version when the power pipeline is disrupted.

The visible symptom is not one single error code but a shutdown path that fails to complete normally. A user clicks the power command, expects the machine to stop, and instead sees a restart, a frozen desktop, or a system that seems to wait indefinitely before giving up. In the source material, the issue is described as Windows refusing to shut down and automatically restarting instead of turning off directly. That pattern matters because it points to a failure in the handoff between user session closure, kernel session termination, and power-state transition. The operating system is responding to the command, but it is not reaching the final off state.

The same complaint can also appear during update activity, after a system change, or when the machine has been using a power feature that changes how shutdown works. Windows is built to close applications, stop services, flush memory, write system state, and then cut power. When any one of those stages stalls, the result looks like a shutdown problem even though the root cause may be buried in a separate component. That is why this issue often feels inconsistent: one restart may end normally, while the next shutdown command loops back into Windows again.

Several mechanisms can create that behavior. Fast Startup, also called Hybrid Shutdown, is one of the most common triggers because it does not perform a full cold shutdown. Instead, it keeps part of the kernel session in a hibernated state so the next boot is faster. That design can interfere with a normal power-off sequence when the saved session data is damaged or when another component expects a clean shutdown rather than a hybrid one. The source text explicitly identifies Fast Startup as a primary reason Windows may not shut down normally, and that aligns with the way the feature shortens shutdown by preserving state.

Corrupted system files are another likely cause because shutdown depends on the integrity of core Windows components. If files that handle service control, power transitions, or session teardown are missing or damaged, Windows may fail partway through the sequence. The source material links system file corruption to shutdown trouble and notes that the System File Checker tool can repair missing or corrupted files. In practical terms, a damaged file does not have to crash the whole operating system to cause trouble; it only needs to interrupt one shutdown dependency for the machine to stay alive longer than it should.

Windows Update problems can also stand in the way. The source text points out that some users cannot shut down Windows 10 during the update process, and recommends the Windows Update troubleshooter along with installing the latest Windows release. Update-related shutdown issues often happen because Windows is trying to finish a pending configuration task, stop a partially installed component, or resolve a reboot requirement before it allows power-off. When the update state is inconsistent, the computer may keep cycling between shutdown and restart behavior as it tries to complete a task that never settles cleanly.

BIOS problems are a fourth cause, and they matter because shutdown is not entirely a Windows-only action. The firmware controls low-level boot and power behavior, and the source text notes that wrong BIOS settings or corruption can prevent proper shutdown. If the boot order, firmware defaults, or related settings are incorrect, the system may return to startup instead of fully ending the power session. The problem can look like Windows refusing to listen, but the underlying conflict may already exist before Windows finishes loading or after it signals the machine to power off.

The source also mentions automatic restart behavior in Safe Mode, which shows that shutdown failures can blend into recovery logic. When Windows encounters a condition that it treats as serious, it may restart rather than stop. That behavior is useful for recovery, but it becomes a problem when the restart policy is masking the original shutdown failure. In those cases, disabling automatic restart can expose the underlying condition so the system does not immediately cycle back into Windows after the shutdown command.

Fast Startup deserves special attention because it changes what shutdown means inside Windows. The feature is designed to reduce boot and shutdown time, and the source text calls it the reason the computer does not fully shut down. By keeping part of the kernel session saved, it trades a complete power transition for speed. That is usually convenient, but when the saved state is unstable, shutdown can fail at the exact point where Windows tries to preserve or restore system context instead of clearing it.

Corruption in system files affects shutdown more directly than many users expect because shutdown is not a single action. Windows has to notify processes, close open handles, stop background services, write cached data, and finalize registry and kernel state before power is removed. If SFC finds damaged files, the system may already be missing one of the components that handles that chain correctly. The result can be a machine that boots and runs well enough during everyday use but cannot complete the end of the session cleanly.

Update trouble creates a different kind of failure because it often introduces a pending state. Windows may be waiting on a configuration change, a repair action, or an updated component that has not fully settled. The source text links shutdown trouble to update errors and recommends the troubleshooter for those cases. That makes sense because the shutdown command can be blocked when Windows believes there is unfinished maintenance work that should happen before the next power transition.

BIOS settings sit below Windows, but they still shape how the computer behaves when the operating system asks for shutdown. The source text recommends entering BIOS and restoring default or HDD boot settings if shutdown problems continue. That approach addresses the possibility that the machine is not following a clean boot and power order. Since firmware governs the handoff between hardware state and Windows startup, a wrong setting can surface as a Windows shutdown failure even when the operating system itself is functioning normally.

Windows uses the power stack to coordinate user actions with kernel behavior, device state, and firmware control. In normal use, a shutdown command should close the user session, stop active work, and place the computer into a powered-off state. Fast Startup modifies that chain by preserving kernel data, which is why it shortens boot time but can also create shutdown confusion. The feature is helpful when it works, yet it changes the shutdown path enough that a machine can behave as if it is refusing to power off.

That is why the issue affects more than just a single menu command. The Start menu, the command line, Windows Update, Safe Mode recovery, system file integrity, and BIOS all feed into the same end result. If the shutdown sequence breaks anywhere along that path, the user sees the same symptom even though the cause is different. A direct power-off problem can therefore be a Windows feature problem, a file integrity problem, a pending update problem, or a firmware problem depending on where the interruption occurs.

Here are 6 solutions to fix Windows 11/10 won’t shut down.

Fix 1. Disable Fast Startup

Turning off Fast Startup removes the hybrid shutdown behavior that most often keeps Windows from powering off completely.

Open Settings from the Start menu.

Go to System and open Power & sleep.

Select Additional power settings.

Choose Choose what the power buttons do.

Select Change settings that are currently available.

Clear Turn on fast startup (recommended).

Click Save changes.

Fix 2. Run a Full Shutdown

A full shutdown bypasses the hybrid state and forces Windows to end the session instead of preserving it.

Open the Start menu.

Click the Power button.

Hold down Shift while selecting Shut down.

Or open Command Prompt as administrator.

Type shutdown /s /f /t 0.

Press Enter.

Fix 3. Run the Windows Update Troubleshooter

This method addresses shutdown failures that are tied to unfinished update work or update-related system errors.

Open Search from the taskbar.

Type troubleshoot.

Open Troubleshoot.

Select Windows Update under Get up and running.

Click Run the troubleshooter.

Apply any fixes that Windows reports.

Restart the computer after the troubleshooter finishes.

Fix 4. Disable Automatic Restart in Safe Mode

Stopping automatic restart helps prevent Windows from looping back into startup when the shutdown process is failing.

Restart the computer and enter Safe Mode.

Open Search after Windows loads.

Type sysdm.cpl and open it.

Go to the Advanced tab.

Under Startup and Recovery, click Settings.

Clear Automatically restart.

Click OK and reboot the computer.

Fix 5. Repair Corrupted System Files

Running SFC checks the Windows file set for damaged components that can interrupt shutdown handling.

Open Search.

Type cmd.

Right-click Command Prompt.

Select Run as administrator.

Type sfc /scannow.

Press Enter.

Wait until the scan completes, then shut down again.

Fix 6. Reset BIOS Boot Settings

Restoring BIOS settings can correct firmware-level boot behavior that keeps the machine from ending the power session properly.

Force the computer off with the power button.

Turn it back on and press F2, F11, or Del to enter BIOS.

Open the Boot section.

Select The Default or HDD at the top of the boot order.

Press F10 or click Save.

Exit BIOS.

Restart the computer and test shutdown again.

Šaltinis: easeus.com