I'm curious if there is any technical or user experience design reason for this phenomenon I'm experiencing:
Whenever I select "Update and shut down", the machine will update for a while and then shut down, but when I start it up again, it will still spend time on updating. As far as I know, an "Update and restart" will fully complete the update. So why is that not the case with "Update and shut down"?
I clicked update and shut down last night, expecting Windows to be done with whatever it needs to do, and turned on the machine this morning to be greeted with an hour-long update process I did not expect.
I see no technical reason for this behavior, as Windows is perfectly capable of rebooting any number of times during an update (as it indeed did this morning).
As for user experience, consider this:
What is the use case for shutting down versus turning on the PC?
- Why do I want to turn off my computer? Because I'm not planning on using
it for a good while. It now has all the time in the world to install
updates and reboot as necessary along the way, then shut down.
- Why do I want to turn on my computer? It is very likely that I want to turn it on because I actually want to use it, perhaps for work.
I'm sorry if this sounds a bit more like a rant than a question, but I'm genuinely curious about the reasons behind this behavior. Is there a technical reason? Does Microsoft simply think that this is the best way to go about updates? Is my preferred use case so unexpected / out of norm?
Is there a way to tell Windows to really install everything and then shut down?