Most updates on my system are handled overnight, outside the active hours I’ve set in the settings.
Not everyone leaves their computer on draining power. I always put it to sleep when I am not using it. If your argument is that, yeah updates aren’t a problem, you just let your computer run and chew on it for a long time, that’s still a problem…
There is nothing it is “chewing” on for an extended period. I know the updates take at most 15 minutes (on an NvME drive, a SATA M.2 or HDD of course will take longer), because I manually update my systems most of the time. I can see it perform the update right in front of me, most of the time in less than 5 minutes. IF I instead leave it on overnight and it updates and restarts automatically, it is ready to go in the morning where I left off.
Never updating your system manually and never leaving it online outside of your set active hours to perform maintenance when you aren’t actively using it (like installing updates automatically), then getting angry at the system despite you never giving it any downtime to do so, is a YOU problem. Same for the users that delay the restart for multiple days after the updates are installed, and then get surprised when it finally needs to restart like it’s been requesting for 2+ days and being ignored.
is a YOU problem.
Wtf is this crap? How is it MY problem when other OSes do a much better job with the update process? You talk about 15 minutes or leaving updates running overnight as if that’s decent. I can do a Linux update within 2 minutes and get my system back up by minute 3. That’s the kind of performance I am expecting and I don’t even need a super fast NVMe drive to do it.
The fact that you’re okay with putting up with Window’s comparatively slow update speed and then have to make excuses for it by saying that the USER needs to constantly baby it or waste power by leaving it overnight is honestly hilarious. To be quite frank, you just don’t know how updates could be better because you’re just used to what Windows has always offered you.
Don’t put the blame on users for a problem that Microsoft can definitely solve but never does.
