Finally! Microsoft has squashed one of the most frustrating Windows 11 bugs, and it's a game-changer for anyone who's ever clicked 'Update and shut down' and found their PC wide awake the next morning.
I've been there, haven't you? You're ready for a good night's sleep, click the button, and assume your computer will be off. Instead, it restarts, updates, and keeps running all night. This has happened to me more times than I can count. This issue has been a persistent annoyance, dating back to Windows 10, and it's a relief to see Microsoft finally address it in Windows 11.
According to Windows Latest, Microsoft has fixed the 'Update and shut down' function so that it actually shuts down your PC after updating, rather than restarting it. This fix is included in the October 2025 optional Windows 11 update (KB5067036).
In their patch notes, Microsoft stated that they have 'addressed the underlying issue which can cause 'Update and shutdown' to not actually shut down your PC after updating.'
So, how do you get this fix?
To resolve this issue, you'll need to download the Windows 11 25H2 update if you haven't already. You can find this in Settings > Windows Update on your PC. Then, go to Settings > Windows Update > Advanced Options > Optional Updates and download and install the optional KB5067036 update.
But here's where it gets interesting: Microsoft has confirmed that this fix will also be included in the monthly Patch Tuesday update, which is released to all Windows 11 users. Patch Tuesday happens on the second Tuesday of each month, so mark your calendars for November 11th for this update.
Microsoft didn't specify what exactly caused the 'Update and shut down' issue or how they fixed it. My guess is that when Windows entered its offline servicing phase (that black screen that says 'Windows is working on updates'), it was failing to execute the shutdown command after a reboot. The update process would reboot the system to apply changes, but the shutdown command was getting lost. This patch appears to ensure that the shutdown command is executed correctly.
This is a long-overdue fix, and I'm thrilled Microsoft has finally implemented it. This bug affected power bills and laptop batteries, so this fix is a welcome change.
What are your thoughts? Did this bug ever drive you crazy? Do you have any theories about what caused the issue? Share your experiences and opinions in the comments below!
