this post was submitted on 12 Mar 2024
403 points (96.8% liked)
Technology
58895 readers
3649 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.