IT TOOK A DECADE, BUT WINDOWS' „UPDATE AND SHUT DOWN" FINALLY WORKS AS IT SHOULD

Phone callbackI call you at the time you choose
← Back to the blog
Blog

IT TOOK A DECADE, BUT WINDOWS' „UPDATE AND SHUT DOWN" FINALLY WORKS AS IT SHOULD

Author: Lakatos Szilárd | Published:

Windows 11 received an interesting optional update in October that fixed a long-standing bug causing several problems. The essence of the bug was that, starting with Windows 10, choosing „Update and shut down" often didn't shut the system down at the end of the update, as users expected, but simply restarted it.

According to Windows Latest, the bug has been fixed in build 26200.7019 of Windows 11 25H2 and build 26100.7019 of version 24H2. It had existed for at least a decade without Microsoft's developers responding, so the fix was a very long time coming. Because of the faulty feature, users shutting down at the end of the working day or before bed with „Update and shut down", believing Windows would complete the process properly, often found their computer the next morning not switched off but on, waiting for them at the sign-in screen.

With desktop setups, this just means some extra power use, since the PC ticks over idle for hours; but with laptops and tablets it can mean the system shut down in the evening no longer responds in the morning, because the update was followed by a restart rather than a shutdown, and the idle machine drained its battery completely. That can be very annoying in the morning when you need to leave or start your day

The faulty behaviour was ended by update package KB5067036, which can be downloaded optionally and is already available for both Windows 11 25H2 and Windows 11 24H2-based editions. Microsoft's announcement unfortunately doesn't explain what may have caused the bug, but most likely the routine that installs updates, the Servicing Stack, simply didn't receive or register the request to shut down rather than restart at the end of the update process. Installing updates normally requires a restart so the process can run, because some files are locked while the system is running and can't be updated by that routine. The complex process was probably mishandled, or timing errors occurred because of features such as Fast Startup.

Either way, tests so far show that the decade-old problem has finally been solved: the system now carries out the requested process flawlessly and doesn't restart after applying updates if we originally asked it to shut down when finished. A small step for Microsoft, but many users will be glad that Windows finally does what it was asked to.

25h2updatebugrepairAIwindowswindows 11

More IT news and tips on the blog

More articles

See all articles →