One of the reasons I choose a PC over a Mac is because I want to decide things for myself. Microsoft's updates seem very Appleish to me.
All they need is large text that says something like, "You are more likely to get viruses, malware, randomware, etc if you uncheck this setting." Heck, make them confirm the choice two or three times. Some people want to risk it, some people need to risk it. Let them, it's their machine and their data.
Implementations actually matter. Hordes of us would jump ship if we could, but convincing vendors to port flagship software, or even do something as seemingly straightforward as a license migration is never easy.
Sorry, I have no sympathy. Look for alternatives, or roll your own. Or find a new line of business altogether. Whining about your OS vendor abusing you is getting really, really old now. Like an abusive boyfriend, they're not going to change, so it's up to you to make a change.
There is.
In my configuration this is still working. I went to services.msc and searched for "Windows Update". I stopped the service, went to its preferences and selected "Disabled" as startup type.
It works fine.
ChromeOS updates the system once every 6 weeks and still has a far more secure system.
This can be rather dangerous if your laptop is stuck in a backpack with no airflow on a hot day.
The laptop would be hot enough to toast bread when I pull it out.
If I'm out of town for 2 weeks, I cannot have my Windows 10 machine reboot, it runs the software for my security cameras and that can't start until I log back in. Thankfully, I set up Windows Update to not install updates automatically(Win10 Pro) way back when it came out and it has continued to stick. Major updates are a constant worry that they will finally break this forever when it shouldn't even be a concern in the first place.
^_^
shutdown /r /t 0
AFAIK, this has always avoided updates.
Is it not still like that? MacOS seems worse to me, since restarting when an update exists isn't sufficient: you have to remember to go back to the update and click 'update & restart'...
Linux handles this best though, by a long shot.
IME OSX is way better, the shutdown update process is much shorter than on Windows (where it is frustratingly long) and not all updates require rebooting.
Then one day windows realizes, holy smokes, we have to install those updates now! And proceeds to restart your computer regardless of your update preferences, typically right in the middle of your business day.
Changing the updates to install on shutdown is slightly more challenging than disabling updates (it is hidden in an option about power settings on boot). So guess what people do?
Their current solution is scheduling updates to periods when the computer is not in use. I think recently they added an option for you to define a set of hours where updates take place.
But the problem with this is that people don't treat Windows PCs like always-on devices like they treat mobile phones and tablets. So in those night hours the computer is off forcing daytime updates.
In fact, if you can't afford the restart even when you schedule it, there's ksplice and a variety of similar solutions that can switch to a new kernel without a restart.
I did have firefox behave weirdly once after an upgrade until I restarted it, around v15 or so -- but I believe even that is no longer an issue; at the very least, I haven't had any issue with upgrading firefox while using it, and restarting it a week later.
But whatever windows does is way worse, I dread seeing the "please wait while Windows is configuring your updates" screen. I have an SSD, rebooting Windows takes less than 30 seconds, it's a non issue. But those update installs can take a long time and your computer is completely unusable while that happens.
It's also frustrating when that happens while shutting down because I normally turn off my computer's power outlet when I'm done (it switches off the rest of my equipment) so I have to wait patiently for Windows to allow my computer to shutdown before I can do that.
Well, how do Linux and other unices do that?
If you never restart a Linux desktop (or at least log out), you will be running outdated libraries, even if you run updates in the background.
(The best solution would be what Android does, where every program is supposed to know how to checkpoint itself, and they are forcefully restarted on a upgrade, transparently to the user. But even there, updates to system libraries still require a full reboot.)
services: they are specifically designed to be updated and restarted
I write plenty of daemons (you call them "services"). What exactly do I write specifically for them to be able to continue to run when a library is upgraded?
I don't think systemd supports what you are asking but it shouldn't be too hard to write a service that restarts other services if their shared libraries change?
From what I know, Windows doesn't allow a library to be replaced until it's not used by anything, which is more intrusive and is IMO the root cause (though indirect) why people hate updating Windows.
I ended up having to delay my working day by about 45 minutes while Windows decided to do a mandatory update without any granularity of choice on when is convenient for me. That's what is frustrating. I ended up being unproductive for a whole hour because Windows forced an update on me.
Windows definitely have to make it better as Troy suggests. The frequency is also costly.