I had often reboots followed by more update installation and then a shutdown, so I assumed this was working as intended (i.e. finish installing the updates, which might require a reboot, and then power off).
That was a bug? I always thought it was because of my dual boot configuration.
Looking at the rest of their recent update history, this likely just broke...
Task failed successfully.
For a long time, windows had two options:
1. Update and restart and prompt for bitlocker password and update and restart and prompt for bitlocker password and restart
2. Update and restart and prompt for bitlocker password and update and restart and prompt for bitlocker password and shut down (and restart)
Finally, they fixed the last bit of option 2
I can't believe I'm alive to witness this.
My laptop did something like it last night but not exactly : it booted from HIBERNATION to apply updates and reboot. Auto updates have been turned off for a while and yet this happens. You can't trust micro$oft for even the smallest thing. Edit: And I'm fairly sure this is a wanted malicious behavior. The thing was hibernating for quite a time before doing it, like it would wait for me to leave the office/for the computer to be in a bag on the way back home and I wouldn't notice what happened.
I noticed Windows's start menu only updates certain tracked files (e.g., remove deleted files) on a normal shutdown + start, and not on a restart.
Which is odd because I was under the impression a restart is the only "true" shutdown due to fastboot behavior.
I didn't look too much into it and chalked it up to a quirk of Windows start menu behavior in tracking recent files.
Oh so it wasn't a business decision for such horrible behavior,it was an actual bug.
I wonder if they'll backport this fix to Windows 10 (Very much doubt).
I also wonder if they'll ever fix the menu entry delay bug. At the moment neither of the "Update and ..." options is in the menu when you first open it. Opening the shutdown menu then checks if there are updates available to install and will then add those options, shifting the existing menu entries. Which makes it incredibly easy to quickly click on an option you didn't want.
This happened to me last night! I was going to bed and I clicked Update and Shut Down, then I went in to the other room.
After a few minutes I could see the blue glow of my Windows background shining on the wall.
Glad it is fixed!
I’ve always assumed it’s either just something my corporate laptops like to do (my older HP would often switch itself back on even when you told it to shut down, forgetting about any updates), or that I had just clicked the wrong button.
Well, guess that’s my mentally stability so slightly restored!
Microsoft denied a bug for a decade that harmed 100% of users every month in an obvious way.
It is the denial that is so very Microsoft.
I have always blamed my Dell desktop for this.
Incredible.
About time... I guess
Oh. My God.
Finally.
For me 25H2 was the first update that didn't update and shut down. All the previous ones did (on multiple computers).
it'd be nice if Microsoft paid just a bit of attention to the immutable/atomic Linux ecosystem a bit and if they could finally ship an OS that wasn't always a dearly loved "pet".
pity to those who have to work on/with this jank.
How dare you shut down such a great operating system?
Seriously, on a Linux system, I update everything except the kernel without a reboot. Why can’t Windows do this?
What a joke of an OS and company.
"Microsoft shipped a broken “Update and shut down” toggle with Windows 10, and it never acknowledged it until now."
I guess they know what's best for the user base, and this was obviously deemed not important. But boy did they get Copilot integrated in everything post haste.
Typical Microsoft hubris.