With the release of Windows 11 25H2 Build 26200.7019 (or 26100.7019 for 24H2), users can finally breathe a sigh of relief as the long-standing issue with the “Update and shut down” feature has been addressed. For many, this feature has been a source of frustration, often leading to unexpected restarts instead of the anticipated shutdown.
It’s a familiar scenario: late at night, with an early morning looming, you select “Update and shut down” only to wake up to a login screen, wondering if your device’s battery has succumbed to the night. This glitch, which has plagued both Windows 10 and 11, stems from a faulty toggle that Microsoft introduced years ago without acknowledgment of its flaws until now.
Many users have experienced the confusion that arises from the proximity of the update options. The assumption that one might have inadvertently selected “Update and restart” instead of “Update and shut down” is common. However, it turns out that this was not merely a user error but a genuine bug within the Windows operating system.
While the exact cause of the malfunction remains unclear, Microsoft has confirmed that the optional update released in October 2025 (KB5067036) rectifies the underlying issue that prevented “Update and shut down” from functioning correctly in certain scenarios. According to a support document, Microsoft stated, “Addressed underlying issue which can cause ‘Update and shutdown’ to not actually shut down your PC after updating.”
Why “Update and shut down” was broken in Windows 11 and Windows 10
Though Microsoft has not disclosed the specifics of what led to this problem, speculation suggests it may have been linked to a race condition or complications within the Windows Servicing Stack. When users initiate “Update and shut down,” the operating system is tasked with two critical functions: installing pending updates and powering off the computer once the installation is complete.
The complexity arises because Windows cannot simply bypass a reboot after an update. It must transition into an offline servicing phase, which is indicated by the “working on updates” message. This step is crucial, as Windows needs to finish replacing files while not actively running.
After this phase, the expectation is that the system will power down, yet many users have found themselves greeted by the login screen instead. The root of the issue likely lies within the Servicing Stack, where the command to power off fails to persist through the reboot process, either being cleared or obstructed by a race condition, such as the Fast Startup feature.
