this post was submitted on 04 Jul 2026
763 points (99.2% liked)

linuxmemes

31991 readers
290 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 3 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] 7rokhym@lemmy.ca 33 points 1 day ago (2 children)

    In corporate environment, add Crowdstrike, Zscaler, windows instrumentation, and then some digital experience management solution to report on why apps are so slow, battery life is still only a few hours while it heats the room while sitting 'idle', or trying to render a file explorer window with 20 cores and 32 GB of RAM. Did I mention there are updates and you MUST REBOOT NOW, forget that you are presenting to a client.

    Almost as offensive as Dell laptop keyboards on their corpo laptops. Ugh.

    My corpo windows laptop has 122 background processes running in task manager

    [–] wizardbeard@lemmy.dbzer0.com 16 points 1 day ago (1 children)

    Sounds like your IT doesn't know how to properly orchestrate updates.

    Best way to do it in a Windows enterprise environment that I've seen so far:

    • 1 Week: Install in the background silently and finish when the machine reboots.
    • After the week, 2 Days: Warn once that the machine will automatically reboot in 48 hours.
    • 12 hours before forced reboot: Pop up a warning in the corner with the countdown before reboot. Options are reboot now or warn me again in X hours. If you dismiss it without selecting, it pops up again in an hour.

    If your Windows machine hasn't rebooted in a week and a half, of course you're going to have performance issues. What, you expect devs to avoid memory leaks?

    That all said, the amount of Windows sysadmins who haven't entirely given up on wrestling Microsoft's update bullshittery is shrinking every day.

    [–] Mio@feddit.nu 4 points 12 hours ago (1 children)

    It is about reasonable defaults. Why would anyone want to stop their presentation for Windows update reboot? It should be much more friendly how it handles this. Like always check what the user is doing and when is a reasonable time to do it? Maybe at the end of the day.

    Personally, I think they need to work on the whole concept. Make it as transparent as possible or less likely need a full reboot - containers or put more things in like wsl? Make the reboot only do reboot and not 20min installing updates... The user cant even chat on teams or browse the web while waiting. Think if it worked like like live cd that Linux can do.

    [–] wizardbeard@lemmy.dbzer0.com 1 points 4 hours ago* (last edited 4 hours ago)

    Oh 100%.

    Microsoft claimed ages ago when they made updates effectively mandatory (you can turn them off entirely or delay them by 27 day chunks forever on non-enterprise installs) that they would dynamically detect the times your computer wasn't actively being used and try to target that, but it never really made a difference besides "aim for when the computer is likely powered off anyway".

    And that still doesn't hit the basic "is the user presenting in PowerPoint, running a full screen video/program?" sort of common freaking sense stuff you're talking about.

    In some nicer news, Microsoft finally started trying to release some updates as "live updates" that don't require a reboot late last year. So maybe in a decade they'll get close to the Linux update experience.