I legitimately haven’t had a windows update take more than 5 minutes during the reboot phase for years. Most of the time it’s about 30 seconds.
Same here. I don’t know what people that have all these issues are doing, but none of my systems or those of my friends and family have these issues.
We also aren’t fucking around with the various random guides to “debloat”, mess with telemetry, eetc. however, so I can only assume that it’s things in those guides and programs that cause issues. For the people with enough technical knowledge to look for the guides but not enough knowledge to know what they do, or care enough to find out.
The longest update I’ve had took about 15 minutes. My system never restarts in the middle of use to install updates, with the only exception when I was actively hitting the delay button for several days to see if I could force it to. And it finally did, after several days of it asking and me telling it no, and it still gave me a countdown to save my work. It did not randomly restart while in use without warning.
Programs like candy crush, that had install links that were preinstalled (it’s not the full game, just a link to install it) I uninstalled like any regular app and they never returned. I use my system like a regular user, not mucking about blindly in the registry, and never run into these weird issues people complain about. I block telemetry I don’t want at the network level. The OS never knows and I don’t have to blindly trust random guides telling me to mess with things that aren’t intended to be messed with. The OS seems to work just fine with telemetry connections working but failing to connect, as would be expected and tested by MS. People messing with those things manually is not something they’d likely spend much, if any, time on testing.
From my experience, many so-called “power user” complaints are caused by the user doing things they don’t understand, outside of what would be expected and tested.
It’s people who had a single bad experience 15-20 years ago, or heard second hand of such issues. Or if they’ve experienced it recently then they were probably running a very slow hard drive rather than an ssd.
My friend needed to reinstall Windows because it broke after the update, and he is using a ~5-year old PC with an SSD. Windows can sometimes break, even if you are not messing with debloating scripts and etc. It was and it will always be the case. But Linux can unexpectedly break itself too. I suppose it can be the case with MacOS too.
The more important thing for me is the possible options for troubleshooting and, if the situation is really bad, how fast can you reinstall the system to have a fully operational PC again. And in that case, Linux wins, because even if it is harder to troubleshoot, it’s very often possible to just insert some commands, where on Windows, most of the time, the best solution is to reinstall the whole OS. And even reinstallation is faster on Linux. It’s even faster if you have /home on a separate partition.
The problem with windows is it’s one time it’s installing ads that you have to disable for apps, a different time it’s installing ads by re-enabling Cortana and forcing local searches over the web, a different time it’s adding ads by installing a bullshit weather app, a different time it’s adding ads with a bullshit news app, a different time it’s reverting all your settings limiting spyware telemetry, a different time…
It’s not one thing repeatedly. But it’s constantly whack a mole to figure out how to disable the newest hostile anti-feature it installed without your consent.
Yeah, I have never had Windows 11 undo anything I’ve changed or reinstall anything I have uninstalled.
You all are doing something that is causing these issues.
The longest update I’ve had took about 15 minutes.
Asking someone to take 15 minutes out of their work time to do updates is exactly why people DON’T want to update. Even 15 minutes is insane. That’s a whole standup meeting, that’s a whole presentation, that’s work disruption for a bunch of people.
Linux updates in a minute. That’s the kind of performance we SHOULD be expecting in the modern age and that Microsoft refuses to deliver.
So don’t update in the middle of your work day. It literally pops up in the corner saying it needs a restart after installing what it can while the system is running, and you can delay it. It only forces a restart when you’ve delayed it several times already over multiple days.
Most updates on my system are handled overnight, outside the active hours I’ve set in the settings. So it doesn’t affect my usage at all. I get on in the morning with a freshly updated system, and if I left apps open overnight, they are reopened where I left off. I only see updates when I tell it to update manually.
I’m sorry but as much as I hate Windows, the only updates that take this long are feature updates that happen twice a year. The vast majority of windows updates take less than a minute for me and don’t require a restart. Even the ones that do finish in under 5 mins
I legitimately haven’t had a windows update take more than 5 minutes during the reboot phase for years.
I wasn’t just talking about the reboot phase…
Downloading gigabytes worth of updates, waiting for them to install, rebooting, see more updates, reboot again takes WAY more than 5 minutes.
But why are you paying attention to a process that a) doesn’t need supervision and b) is done automatically in the background? It’s such a weird thing to complain about.
Not to mention, the vast majority of windows updates are tiny. The only large updates are the yearly major updates. If you’ve got multi gig downloads happening even weekly, you might want to look into what’s wrong with your system.
I am guessing you run your computer all the time instead of putting it to sleep, because it’s never a process that completes transparently in the background for me. It will always build up and then I have to go in and manually trigger it. Or I have to restart because I installed a new application that requires it and then it decides to do them all at once and takes forever.
