I think that was because Windows 10 Home edition was designed to do updates on its own. That’s why you have to set up a time Windows where you are productive. However, as often the PC got shut down or suspended before that time window was over, Windows took a fallback and restarted the PC at the next possible moment.
The worst thing was: you could not influence that behaviour unless you picked the business edition, as some GPOs were locked behind that.
Windows updates. Me: “how dare you”.
CachyOS, also me: “It’s been 15 min, I wonder if there are any updates, oh good there are”.
CachyOS be like:
- boot computer
- check for updates
- there are updates
- there are always updates
- apply updates
- reboot
- check for updates
- there’s more updates
- Because. There. Are. Always. Updates.
“Please read these 27 makefiles, with a 40 second delay between each one, or you’ll find yourself at the center of the next malicious AUR upload”
A single line of code was added while you were updating, would you like to update?
That’s because Linux updates usually* make it better, while Windows updates just make it more abusive.
*___ Things like SystemD and Snaps may be exceptions, but even then they’re still much more “YMMV” than the shit Microsoft pulls.
If you use Windows, you chose not to be in control of your own computer.
Fool me once…
If you use Windows you’ve been fooled over and over again. So the shame is 100% on you!!! 🤡
I do agree that it’s an issue, but part of “you have the freedom to update when you want” is “you have the responsibility to update”.
I think that a lot of folks running Linux distros, which normally give a user control over updates, are more techie types. Yeah, you’re going to update because you don’t want your system exposed to compromise.
But Windows is kinda the default in offices, and you have people out there who are going to just see updates as a pointless nuisance and given the opportunity, won’t ever update.
An added wrinkle is that Unix file semantics normally permit an open file to be replaced. Windows file semantics normally do not. This means that on Linux, update systems can often update running software underfoot, and it will just start working next time it’s launched. On Windows, the update syatem normally forces a reboot or restart of software so that the files can be modified with the software not running That interruption is also disruptive.
The flip side is that some software, like Firefox, does not deal well with being updated while running and may malfunction if done so until restarted (these days, I think that Firefox detects and update and forces the user to restsrt it itself). I suspect that thst misbehavior could be confusing to some users.
I agree based on the principle: “The most popular OS in the world should update automatically.” Granted, the most popular OS should not be Windows, and the workflow should be better. But many people obstinately want to never update windows and never give it periods to update on its own.
There IS genuinely a user fault to the issue, even if MS isn’t handling it great. They deal with a lot of stupid customers.
I set my grandpa’s Mint to update automatically with backup on boot, one could probably set it in offices. No idea hpw hard it’d be for multiple computers, though.
Shoot… that reminds me that Win10 would do it automatically on my old machine, and it seems like Win11 on this new machine doesn’t seem to be set up that way.
I wonder what landslide of updates I need to manually install at this point. 😑