this post was submitted on 02 Jan 2026
619 points (98.0% liked)

Technology

78393 readers
3471 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 news or articles.
  3. Be excellent to each other!
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ramble81@lemmy.zip 43 points 5 days ago (5 children)

Frankly I’ve never had any issues running Windows 11. It’s just the OS in the background for me. I think the biggest difference is I always run Enterprise versions (not Pro or Home) and most of that crap is either non-existent, disabled by default or easy to disable via GPO.

The big thing for people to realize is that Enterprise is the version most all businesses (especially large ones) run, and Microsoft isn’t going to crap on them as easily. And they know by extension, people will run what their business is, but they can get away with making Pro and Home crappier since it’s just individuals who would switch, not large swaths.

[–] MangoCats@feddit.it 21 points 5 days ago

Pro and Home is where they test-market the worst of the garbage... some of it does make it into Enterprise - a surprising amount has gotten into Office 365 - but, yeah, not enough to make it completely dysfunctional.

[–] Bruncvik@lemmy.world 14 points 5 days ago (3 children)

My company (130,000 employees) sticks to 24H2. IT wouldn't approve the 25H2. Don't know whether the refusal to upgrade hurts Microsoft in any way, but if it does, I think we're big enough to be on their radar, and perhaps they talk to our IT about concerns and complaints we may have.

[–] M0oP0o@mander.xyz 10 points 5 days ago (1 children)

This is the issue I have with people talking about how "you MUST always run the most up to date software". They don't understand that in large enterprise it is common for function and security to not update unless there is a damn good reason. The very idea that the newest version is the best is just marketing brainwashing and does not hold up to the reality of use.

[–] the_crotch@sh.itjust.works 5 points 5 days ago (1 children)

25H2 is a feature update. 24H2, for now, gets all the same security fixes. When people say "always run the latest" they mean stay on a supported OS and always have as many security updates as possible within reason.

[–] M0oP0o@mander.xyz -1 points 5 days ago (2 children)

And they are laughably wrong. Its always the wannabe system admins with 4 end users spouting that nonsense. You get into any big organization and legacy becomes a larger and larger part of the way things are kept running. Hell just for shits and giggles look at the back end of blood banks, government, airports and non blood banks back end infrastructure. I would be shocked if anything was running on less then a decade old software. Hell people think that software hardened over years should just be tossed out the window because the company (who has now made it clear they don't even know what they are doing) released a version with a bigger number.

Just what are they teaching these days? No OS is secure, exploits and vaunrabilitys are in them all. This should not be a hot take but all I see is lazy it departments offloading responsibly left and right. The correct way to handle this has always been from a risk management approach. You need to assume your not ever secure, make backups, develop a plan to recover after an event and if you have sensitive data handle it like it was sensitive. Now a days we have usernames and passwords stored in the same databases, plain text critical data, lack of redundancy at all levels and a slick sales package to justify it all.

[–] the_crotch@sh.itjust.works 3 points 4 days ago (1 children)

You get into any big organization and legacy becomes a larger and larger part of the way things are kept running. Hell just for shits and giggles look at the back end of blood banks, government, airports and non blood banks back end infrastructure. I would be shocked if anything was running on less then a decade old software.

Maybe on the backend or specialized single purpose appliances. Running decade old OS's on workstations is negligence boardering on malpractice.

[–] M0oP0o@mander.xyz 1 points 4 days ago (1 children)

Ha, Welp. I don't think you want to look then.

[–] the_crotch@sh.itjust.works 1 points 4 days ago* (last edited 4 days ago)

I literally work for a government agency lol what you're saying is nonsense. If they worked the way you're describing the compliance guys heads would explode and federal agencies would be brought in to oversee upgrades for the next decade

[–] Valmond@lemmy.dbzer0.com 3 points 4 days ago (1 children)

I worked in hospital payments, they used gcc 4.4 in 2023 (but renamed 4.8 for some reason), no TLS, code is 30+ years old. Only impacts a bunch of millions of people.

But having access to the server? No no IT cannot let you have that :-D

Fascinating and a bit of scary.

[–] M0oP0o@mander.xyz 2 points 4 days ago

Eh, its only scary if you don't see how bad a new roll out normally goes. Software is a tool, and people should remember that.

But yes hospitals are the worst for legacy systems (even outside of the us). I still remember having to relearn how to fix dot matrix printers because the hospital still was using them and had them under contract in 2015.

[–] ramble81@lemmy.zip 8 points 5 days ago

So Microsoft is so diversified, 130K isn’t even a drop to them. We had almost 200K seats of E3 and when I calculated out the revenue from our EA vs their total revenue, it came up to something like 0.012%. Even though it was tens of millions of dollars on our end, we’re still a drop in the bucket to them.

I had a few issues with 25H2 on release, but they're largely fixed now.

24H2 and 25H2 are the same thing, it's just enabling a few different changes. But things like the new obnoxiously ugly start menu have started showing on my 24H2 machines so I don't really know what the difference is.

[–] 11111one11111@lemmy.world 8 points 5 days ago* (last edited 5 days ago)

Lol its amazing how Noone in the real world knows that microsoft makes OS's without all the enshitification shit in them that run decent, dont block features from being disabled, are all around non-infuriating piles of shit like the non-enterprise versions, charge an arm and a leg for it. Then microsoft (or at the same time didnt mean one before the other) releases the functionally identical OS versions but so facefucked full of enshitification shit they constantly break, these versions hold you down with an update pistol in your mouth that tells you inorder to live you will update every fucking shitstorm we tell you to, it rapes yo wife, rapes yo kids, ignores all bugs calling them features, all the while having a bomb strapped to their chest that says you dont accept everything we ruin of yours we blow your whole fucking system sky high. And those versions they call Home and Pro versions.

[–] Limonene@lemmy.world 4 points 4 days ago

How do you get this? My company has the Enterprise version, but when they forced me to switch to a new Windows 11 laptop (same model and specs as my old one which couldn't be upgraded to Windows 11 for some reason), it came with all the crap in the article. Ads in the start menu and everything.