Never seen this clip?
Ah, right, there is a solution:
Just turn it off, and it won't reboot while it's turned off.
I Think that some people at Microsoft doesn't see the issue here:
Ok, installing updates make the computer lag for a while. But at least it doesn't throw off users.
The problem is the rebooting.
There wasn't long ago there was an "important" patch that required a reboot.
What it did? It changed something with the time zones at the city of Novosibirsk. So, well, in a way I understand Microsoft doesn't want to really shout out what the patches that require a reboot do. I mean, as I'm not even living in Russia (also as set in regional options from where time zone is picked), it's obvious I need the new Novosibirsk timezone *now*. It's very important and not something that can wait until the next patch tuesday or something. Telling me "This patch sets the Clock right if you live in the Novosibirsk region" might make users want to install this patch later, and perferably in the monthly batch of other patches like the dotnet ones, would make me Think "ok I don't need this patch *now* I can wait until some rollup update" and that wouldn't be good for the patchmakers if people want to install them later. (
https://support.microsoft.com/sv-se/help/3182203/september-2016-time-zone-change-for-novosibirsk )
Again, my setting is that I automatically fetch and install updates after a Schedule.
The thing I decide when it happens is the rebooting. I can make a setting so I can run the script to update my computer and then reboot it immediately afterwards (so it's ready to go when I come back for lunch). Or I can install all updates, those that can be installed live gets installed within minutes and the ones that require a reboot will have to wait until I don't have anything serious running, *then* I can reboot, or get those patches installed when I shutdown the computer normally.