this post was submitted on 15 Oct 2024
329 points (96.1% liked)
PC Gaming
8576 readers
232 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- 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
view the rest of the comments
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.
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.