I wonder if there is a real reason why it’s needed, or they just engineered themselves into a bad corner…
Same. They do have some features that sound kinda sane and may play a role here - like the system field are write protected. Programs can request to run a script on start-up to modify them before the write-protection kicks in. Also they might want/think it’s a good idea to run some part of the updates on the new kernel version instead of the old one or maybe do a cleanup on a successful boot or so. Also, maybe they want to force a reboot straight to Windows before the update is finished to prevent problems with dual boot - that could rule out “install and shutdown and only continue with the remainder on the next boot”. Also it might be for convenience, as the next boot is as fast as usual and you do not see 10 mins of “applying updates” when you didn’t calculate with that.
But if you offer “install and shutdown”, it should shutdown in the end and not stay on the lock screen and hopefully go into sleep mode…
Same. They do have some features that sound kinda sane and may play a role here - like the system field are write protected. Programs can request to run a script on start-up to modify them before the write-protection kicks in. Also they might want/think it’s a good idea to run some part of the updates on the new kernel version instead of the old one or maybe do a cleanup on a successful boot or so. Also, maybe they want to force a reboot straight to Windows before the update is finished to prevent problems with dual boot - that could rule out “install and shutdown and only continue with the remainder on the next boot”. Also it might be for convenience, as the next boot is as fast as usual and you do not see 10 mins of “applying updates” when you didn’t calculate with that.
But if you offer “install and shutdown”, it should shutdown in the end and not stay on the lock screen and hopefully go into sleep mode…