this post was submitted on 15 Oct 2024
330 points (96.3% liked)

PC Gaming

8505 readers
419 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] jlh@lemmy.jlh.name 28 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

The amount of times that windows "features" come back after I disable them via GPO on Windows 10 Entrerprise tells me that this isn't true.

The irony that setting up Windows now requires more command line use than Linux in 2024.

[–] wizardbeard@lemmy.dbzer0.com -2 points 3 weeks ago (1 children)

If you're using Enterprise on a personal machine, you've messed something up. There are other ways beyond Group Policy in that environment that are probably causing what you're seeing. SCCM, Intune, Policies over the network vs local... that significantly raises the chances of something else stepping on your local Group Policies.

I've not had that problem on either of my Win 10 Pro machines when using Group Policy to disable things, over the last four years.

[–] jlh@lemmy.jlh.name 1 points 3 weeks ago

It's been a year since I've uninstalled Windows, but I believe Windows 10 Pro does not have access to the stronger GPO policies that enterprise has. Enterprise was the ad-free version for a while there, but I think it's just as bad as Pro now.