|
|
|
|
|
by wongarsu
822 days ago
|
|
Windows has gotten pretty good at staying out of your way with updates if you have typical usage patterns. That is: either you turn it on at the beginning of the business day, it downloads updates in the background and installs them when you shut the machine down at the end of the day; Or you leave the machine on 24/7, get a couple prompts over multiple days about a scheduled restart with the option to schedule it, and if you don't react it just restarts in the dead of night (or rather, a reasonable prediction of when you won't be using the computer). The rub is that this doesn't work as well in atypical setups like a lab. The machines are probably only on while students are using it, preventing the "install at night" strategy, and if your normal workflow includes restarts Windows will take that as a cue to finally install the update. Of course all of this is avoidable by configuration, or by the user (restarting explicitly without updates). But the Home version hasn't always given you as much agency in this as the more expensive Windows versions. |
|
I know I could probably suspend or something, but I never do that because it used to be a lottery on Windows whether your machine would actually unsuspend or you would need to fight it pressing the power button until it rebooted (did they ever fix that?)