Fixing a Windows PC That Won't Shut Down After an Update

A PC that finishes installing an update and then refuses to power off is one of the more confusing failure modes Windows produces, because the machine looks healthy right up to the moment it should go dark. The screen blanks, the drives spin down, and then the system comes back up instead of staying off. Two distinct causes are documented in the sources here, and they call for different responses.

The first is a bug in the update flow itself. For years, choosing "Update and Shut Down" on a Windows PC did not reliably shut it down: the system installed its updates correctly, then restarted and returned to the login screen rather than powering off. Users who selected the option before going to bed would find the machine had been running all night. According to TechJuice, Microsoft finally acknowledged the behavior and shipped a fix in Windows 11 through the optional KB5067036 update for versions 24H2 and 25H2, appearing first as Build 26200.7019 for 25H2 and Build 26100.7019 for 24H2 ^¹. Anyone who skipped the optional update was due to receive the same fix automatically through the November 11 Patch Tuesday rollout, per the same report.

The second is narrower and tied to a specific patch. After the January 13, 2026 security update KB5073455 for Windows 11 version 23H2, some machines with Secure Launch enabled could not shut down or enter hibernation at all — they restarted instead. Microsoft's own documentation, quoted by Trusted Reviews, limits the problem to 23H2 devices running Secure Launch, the feature that boots the system in a trusted state to block low-level malware ^². An out-of-band update, KB5077797, was released to resolve it, and the same patch also fixed a separate bug that broke sign-in for Remote Desktop connections.

Before working through the steps below, check which situation you are in. If the PC only misbehaves when you pick "Update and Shut Down" and behaves normally on a plain Shut Down, you are almost certainly looking at the update-flow bug, and installing the current cumulative updates is the fix. If the machine restarts on every shutdown attempt regardless of updates, work through the sequence.

1. Note exactly when it fails. Does the screen go black and then the machine reboots, or does Windows sit on a "waiting for a task" style prompt before you intervene? One user in the Microsoft Q&A thread on this problem reported seeing a message that a task was still running, with options to wait or continue, and usually chose to wait ^³. That detail matters: a background process that will not exit is a software hang, not an update bug, and it points the diagnosis in a different direction.

2. Install all pending updates, including optional ones. Both documented bugs were fixed by updates — KB5067036 for the update-flow behavior and KB5077797 for the Secure Launch conflict. If your machine is on 23H2 and you have not yet received KB5077797, check Windows Update manually rather than waiting.

3. Rule out a specific offending patch. In the Microsoft Q&A thread, the original poster traced the hang to KB5017308: uninstalling it restored normal shutdown, Windows Update reinstalled it two days later, the problem returned, and the cycle repeated a third time. If your failures began on a known date, check the update history for that day and consider uninstalling the suspect patch through the update history's uninstall option. Be aware that Windows will try to reinstall it, so this is a diagnostic and a stopgap, not a permanent repair.

4. Disable fast startup and test a full shutdown. Fast startup turns a shutdown into a hybrid hibernation, which means a stuck driver or service can survive into the next boot and keep the machine from completing a clean power-off. Turning it off forces a genuine cold shutdown and often separates a true shutdown fault from a resume fault.

5. Use the command line to see what is blocking. Running a shutdown command with a short timeout from an elevated prompt will report the names of processes holding up the shutdown, which is far more informative than watching the spinning indicator. If a specific application or service appears every time, that is your culprit.

6. Check the Secure Launch angle if you are on 23H2. Confirm whether Secure Launch is enabled on the device. If it is, and the failures began immediately after the January 2026 patch, the KB5077797 fix is the documented remedy rather than a workaround.

7. If nothing above resolves it, treat it as a general shutdown hang. A clean boot, which disables third-party startup items and services, will tell you whether the blocker is something you installed. If the machine shuts down cleanly in a clean boot, re-enable items in batches until the behavior returns.

When a step fails, resist the temptation to escalate straight to reinstalling Windows. The Microsoft Q&A case is instructive precisely because the user's own follow-up shows how persistent these problems can be: after trying a set of PowerShell commands, the machine still failed to shut down that night. That is a signal to gather better evidence — the blocked-process names from step 5, the exact update history, whether Secure Launch is on — rather than to repeat the same fix.

One thing the sources do not establish is how widespread either bug is, or whether every affected configuration has a confirmed resolution beyond the two specific patches described. Microsoft's changelog language, as reported, confirms the update-flow problem existed and was fixed; it does not quantify who was hit. Treat any claim of a universal fix with caution.

The practical order of operations is therefore: identify whether the failure is tied to the update button or to every shutdown, get current on updates including optional and out-of-band ones, and only then start disabling features and services. Most machines in this situation are not broken. They are running software that has not finished the job it was given.

If your machine's problem is the opposite one — it will not stay asleep, or it will not wake — that is a different fault with a different diagnostic path, covered in our guide to a Windows 11 PC waking from sleep by itself.

Sources

1. ¹ Microsoft Fixes Shut Down Bug After Years of Complaints - Get Alerts www.techjuice.pk
2. ² Windows 11 machines can’t shut down after last update – here's how to avoid the bug - Advertisement www.trustedreviews.com
3. ³ Windows 10 Won't Shutdown after Update - Microsoft Q&A - Skip to main content learn.microsoft.com