this post was submitted on 12 Oct 2024
403 points (98.1% liked)

Technology

58635 readers
3562 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. 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
[–] Kongar@lemmy.dbzer0.com 121 points 20 hours ago (7 children)

This is the third update in like six months that is horribly broken. There was a windows 10 update that wouldn’t install because the recovery partition that Microsoft’s installer created was too small. The prior win 11 update just won’t install for lots of people and there’s no real rhyme or reason. Now this crap.

They just don’t give a shit anymore. Microsoft had a great run folks, time to move on.

[–] match@pawb.social 4 points 4 hours ago

That's not even counting the ones that make your user experience worse on purpose

[–] EddoWagt@feddit.nl 20 points 15 hours ago (1 children)

Remember the dozens of times a Windows 10 update could potentially wipe your personal data?

[–] Archer@lemmy.world 3 points 4 hours ago

Your files are EXACTLY WHERE YOU LEFT THEM

[–] LaunchesKayaks@lemmy.world 19 points 15 hours ago

Part of my job is keeping all of the endpoints my work manages up to date with patch compliance. I've had to create exceptions for the past two windows 11 updates because they won't run on most machines for no reason. It's been a pain in the ass. I can't just add the machines to the exception list without doing basic troubleshooting because "procedure" and I've spent so much time doing absolutely unnecessary shit.

[–] Toes@ani.social 26 points 16 hours ago (1 children)

They also released an update that broke dual boot Linux installations. Still feeling that one

[–] Kongar@lemmy.dbzer0.com 16 points 15 hours ago (1 children)

Oh right! Forgot about that one! FOUR major screw ups.

[–] Teils13@lemmy.eco.br 9 points 12 hours ago

i think that one is not a screw up...

[–] dan1101@lemm.ee 16 points 16 hours ago

I have avoided Win 11 by disabling TPM in BIOS. Because I expect MS would eventually figure out some way to install 11 otherwise.

[–] kautau@lemmy.world 38 points 20 hours ago (1 children)

I’m honestly waiting for a crowdstrike level BSOD from one of their updates at some point. At that level, corporations would recover in the same way they did from crowdstrike, but consumers who didn’t understand how to roll back, or restore from backup, restore windows, etc would be livid and hopefully it would create some awareness on better understanding and control of the products you buy and use

[–] Toes@ani.social 17 points 16 hours ago

Microsoft has largely mitigated this concern by pushing all their fresh updates to the consumers for testing before pushing them to their sensitive business customers.

[–] SynopsisTantilize@lemm.ee 12 points 20 hours ago (2 children)

I'd say they started the misstepping after they "fixed" Vista with windows 7. After that, they tried to hard instead of slow rolling. Windows 10 was good but 11 is just....windows 8 again.

[–] Itdidnttrickledown@lemmy.world 9 points 17 hours ago (2 children)

Windows ME was the original mistake edition. It was terrible.

[–] GreyEyedGhost@lemmy.ca 5 points 9 hours ago

Lol look who forgot about Win 98, the version so bad they made an SE version with a free upgrade.

MS has been alternating good releases and bad releases for most of my life.

[–] SynopsisTantilize@lemm.ee 2 points 13 hours ago (1 children)

Well yes. But in more recent times for the examples I was giving

[–] Itdidnttrickledown@lemmy.world 1 points 6 hours ago (1 children)

The 17th anniversary of vistas release is coming up in January of next year.

[–] SynopsisTantilize@lemm.ee 1 points 4 hours ago

Wonder what's next for Microsoft to fuck up. I was the equivalent of Linux minimal but for windows 11.... I guess I want server core.

[–] chaogomu@lemmy.world 3 points 18 hours ago (2 children)

Windows has always had broken versions. The old advice was to always skip every other version.

NT, Millennium, Vista, 8... 10... 11... More misses than hits really. And the bad updates are turning hits into misses.

[–] Blue_Morpho@lemmy.world 9 points 12 hours ago (2 children)

That list mixes NT kernel OS's with Win95 OS's to support a bad hypothesis.

The NT line is:

NT 3.1, NT 3.51, NT 4, Windows 2000, Windows XP, Vista, 7,8, 10.

NT 4, 2000, and XP were all great. Vista was good on good hardware. 7 was good. 8 was bad, 10 good, 11 bad.

If you take the 95 path it's 95 good, 98 good, Me bad.

The only pattern is 7 good, 8 bad, 10 good, 11 bad.

[–] QuarterSwede@lemmy.world 5 points 10 hours ago (1 children)

Anyone who says NT was ever bad is out of their mind. That was the thing that saved Windows since 95’s kernel wasn’t modern. Anything that crashed took the entire system down. Yeah, that was fun times kiddos.

[–] Blue_Morpho@lemmy.world 1 points 3 hours ago

Well 11 is NT as was 8. Although it's only problem was the UI.

[–] SpaceCowboy@lemmy.ca 3 points 10 hours ago (1 children)

Windows 98 sucked. Windows 98SE was... well I won't say good, but it was ok.

Vista was good on good hardware

That's a hell of a caveat for an OS meant to be run on consumer hardware. You might get away with that kind of caveat if MS only offered in on good hardware and people went and put it on non-recommended hardware on their own accord. But that's not the case, Vista sucked when running on hardware that met MS's specs, so it sucked.

So the real pattern is Win 3.0 sucked, 3.1 ok, 95 sucked, 95B ok, 98 sucked, 98SE ok. Windows Me? OMG let's just move everyone over to NT and never talk about this again!

2000 was good. XP wasn't great but improved after awhile. Vista sucked. Windows 7 was peak windows, it was downhill from here. 8 sucked, 10 was ok, and 11 is shaping up to be complete dogshit.

So it's not precisely every other release is bad, but close enough to see a pattern. I guess you could say 2000-> XP doesn't follow the pattern, but Me->XP does. And since 2000 and previous NT versions were meant for servers, not home PCs, while XP was meant for home PCs. It would make more sense to look at the pattern of releases for PC releases rather than mixing in server releases.

When MS has an OS that works decently they tend to try to cram in a bunch of shit into the next release which causes problems. Then they either remove the shit (or at least make it work better) for the release after that so they have something that works ok again. Then it's back to adding a bunch of shit into the next one.

[–] Blue_Morpho@lemmy.world 2 points 3 hours ago (2 children)

Win95 did not suck. 3.1 was trash compared to 95. 95 has a real desktop UI, tcpip built in and a 32 bit preemptive kernel.

98 was great. It wasn't any more buggy than 95.

You ignored NT 4.

[–] SpaceCowboy@lemmy.ca 1 points 50 minutes ago

I'm speaking from experience in using theses OSes, not from a list of features they had. I didn't use NT 4 personally (and that's way outside the scope of personal computer OSes), so I didn't talk about it.

[–] Asidonhopo@lemmy.world 1 points 1 hour ago* (last edited 1 hour ago)

People used 3.1 and 3.1.1 for years even though it was running on top of MSDOS but show me someone who used 3.0? Or 1.x, 2.x? Unheard of. Version 3 started off with some problems that needed a more or less immediate large update.

[–] SynopsisTantilize@lemm.ee 1 points 13 hours ago

Yea I still follow that advice.