this post was submitted on 15 Jan 2026
983 points (97.3% liked)

linuxmemes

28992 readers
775 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 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Gladaed@feddit.org 6 points 6 days ago (2 children)
    [–] SpikesOtherDog@ani.social 3 points 5 days ago (1 children)

    Honestly, Windows MMC tools are one of the oldest and most dependable ways to:

    Manage printers

    View logs

    Manage devices and drivers

    Manage group policy

    Manage MDT

    The interface is almost 30 years old and it is prone to crash. Microsoft cannot seem to rewrite tools that replace the snap-ins.

    There are some alternatives, such as diskpart to replace diskmanagement, but nobody is talking about replacing devmgmt with PowerShell or regedit with PowerShell for reg commands for the one off or the lay user.

    Also, attempting to duplicate printmanagement with devices and printers has resulted in a loss of functionality for managing printer ports and drivers. Attempting to manage printers through just PowerShell is pure madness as you can't properly parse the vendor options.

    If you have made it this far, thank you for hearing me out. I'm not sure I actually made a point, but I do feel better.

    [–] MotoAsh@piefed.social 1 points 5 days ago* (last edited 5 days ago) (2 children)

    There are already PowerShell commands for reading searching and updating registry entries. I don't think anyone is replacing one with the other, though.

    Devices and Printers in Windows can go to hell where it belongs.

    [–] SpikesOtherDog@ani.social 2 points 5 days ago

    I guess I wasn't clear. The average Windows user isn't aware of PowerShell and would hardly be able to use reg itself. I agree that it is a great tool for managing registry in an environment, but I have seen professional technicians darn near cry over using cd to traverse directories.

    [–] jj4211@lemmy.world 0 points 5 days ago (1 children)

    Hey, and PowerShell commands aren't GUI, bringing us back to the point of this post...

    [–] MotoAsh@piefed.social 1 points 5 days ago* (last edited 5 days ago)

    Yes, and I've ran in to several guides that have used the powershell regedit commands instead of the GUI. Not only do the commands already exist, but they're absolutely something some prefer over the GUI, even on Windows.

    [–] jj4211@lemmy.world 1 points 5 days ago

    It's relevant. From about 1995 to 2006, Microsoft was pretty much hard set on 'cli is dumb, do nothing cli wise, cmd is a concession, but a crappy one'. As an artifact of that, you got regedit, a godawful 'GUI' that took a messy datastore model and just kept it ugly, in a way that would have been pretty much better as a CLI interface.

    Microsoft started getting the idea again, but in true Microsoft fashion, had to reinvent the wheel and did PowerShell to try to create a CLI ecosystem from scratch rather than trying to build anything vaguely familiar. To their credit, for first party stuff they did a fine job enabling it, though third party applications remain a mess to this day. It does highlight that even Microsoft figured out that CLI actually does make sense a lot of the time.