Windows 11 25H2 Fixes Decades-Old “Update and Shut Down” Bug
Microsoft has addressed a long-standing issue with the “Update and shut down” feature in Windows 11 and 10. Beginning with the Windows 11 25H2 Build 26200.7019 and newer versions, the function should finally perform as intended. Users will experience actual shutdowns when they select this option.
Overview of the Update and Shutdown Bug
This problem has been a source of frustration for many users. Often, selecting “Update and shut down” led to unexpected restarts instead of the desired shutdown. This glitch was widely reported and had persisted since the release of Windows 10.
Historical Context
Microsoft’s failure to fix the “Update and shut down” toggle has been noted for years. The issue went largely unacknowledged until the recent developments in Windows 11.
New Fixes and Updates
The October 2025 optional update (KB5067036) has been confirmed to resolve the issues associated with the “Update and shut down” feature. Microsoft indicated that this update addresses the underlying problems preventing proper shutdown after updates.
- Build 26200.7019 and newer addresses shutdown issues.
- October 2025 update (KB5067036) provides a fix.
- November 11 Patch Tuesday will include additional improvements.
Reasons Behind the Bug
The exact reasons for the malfunction have not been fully disclosed. However, it is speculated that the problems could stem from a race condition or an issue within the Windows Servicing Stack.
When a user selects “Update and shut down,” two primary tasks are initiated:
- Installation of pending updates.
- Powering off the computer after installations.
Despite selecting a shutdown, Windows often requires a reboot into an offline servicing phase. This process leads to the frustrating situation where “working on updates” appears, but the system does not shut down as expected.
Conclusion
With the release of newer updates, including KB5067036, users can finally have confidence in the “Update and shut down” choice. The fixes are a welcome change for those who have dealt with issues stemming from this long-standing bug.
