- You are an administrator on your machine.
- Your machine is either:
- In a Windows Domain, and you don't want the domain admins messing with it.
- Not in a Windows Domain, and you just don't want useless services running.
In this case, what you probably want to do is prevent the Group Policy Client Service from running on your machine. Unfortunately, that's not a straightforward task to accomplish, because if you go to "services" and try to stop or disable this service, Windows doesn't let you.
Here is how to do it.
These instructions have worked for me on Windows 7; they might also work on other versions of windows. If there is anything in these instructions that you don't quite understand, what it means is that these instructions are not for you; don't try to follow them, you are going to wreck things. Ignore this post, move on.
Here is how to do it.
These instructions have worked for me on Windows 7; they might also work on other versions of windows. If there is anything in these instructions that you don't quite understand, what it means is that these instructions are not for you; don't try to follow them, you are going to wreck things. Ignore this post, move on.
- Using regedit go to HKLM\SYSTEM\CurrentControlSet\services\gpsvc and:
- Change the owner to yourself.
- Grant Administrators (not just you) full control.
- Change the value of “Start” from “2” to “4”.
- Now go to HKLM\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\GPClient and:
- Change the owner to yourself.
- Grant Administrators (not just you) full control.
- Delete the entire key. (Possibly after exporting it so as to have a backup.)
- Restart your machine.
Great! (win11)
ReplyDeleteThank you! Still functional as of May 2025.
ReplyDeleteSide note: This sent me down the rabbit hole of "Per-User Services". Which if you aren't familiar are services created upon user login (booting windows) and share the same name of their parent service with random alpha-numeric suffixes (ie 'MessagingService' and 'MessagingService_4b77e').
At first glance these are extremely suspect, even more suspect when attempting to disable the service results in an error, and EVEN MORE sus if you notice the service is running under the current user rather than 'Local System Account' that the parent service uses.
I notice you were still on Windows 7 when you published this even though Windows 10 was released in 2015. I'm starting to see why...
Thank you! Still functional as of May 2025.
ReplyDeleteSide note: This sent be down the rabbit hole of "Per-User Services". Which if you aren't familiar are services created upon user login (booting windows) and share the same of their parent service with random alpha-numeric suffixes (ie 'MessagingService' and MessagingService_4b77e).
I see you were still on Windows 7 when you published this even though Windows 11 released 2 years earlier, I'm starting to see why.