This guide walks through restricting domain users from opening the Windows Control Panel on their managed computers. This is a common policy for locked-down workstations, kiosks, or shared machines where you want to prevent users from changing system settings. The process uses Group Policy Management on a Windows Server, and the changes apply to any computer in the selected Organizational Unit (OU) after the policy refreshes.
What You’ll Need
- A Windows Server with the Group Policy Management Console installed (available by default on Domain Controllers, or via RSAT on member servers).
- Domain Administrator or equivalent permissions to create and link Group Policy Objects (GPOs).
- The target computers must be joined to the domain and located in an Organizational Unit (OU) you can link the policy to.
- Knowledge of which users or computers should be affected—this determines whether you filter by security group or by OU.
Step-by-Step
- Open Group Policy Management. On your Windows Server, press Win + R, type
gpmc.msc, and press Enter. This opens the Group Policy Management Console. - Create a new GPO. In the left pane, expand your forest and domain. Right-click on Group Policy Objects and select New. Give it a descriptive name like “Restrict Control Panel for Domain Users” and click OK.
- Edit the GPO. Right-click the newly created GPO and select Edit. This opens the Group Policy Management Editor.
- Navigate to the Control Panel policy. In the editor, go to:
User Configuration → Policies → Administrative Templates → Control Panel - Enable the restriction. In the right pane, find the policy named Prohibit access to Control Panel and PC settings. Double-click it, select Enabled, then click OK. This setting does two things: it removes the Control Panel icon from the Start menu and File Explorer, and it prevents running
control.exefrom any command line or Run dialog. - Close the editor. Click OK or close the Group Policy Management Editor window to save the changes.
- Link the GPO to the target OU. Back in the main GPMC window, find the OU containing the computers or users you want to restrict (for example,
Domain → Computers → Workstations). Right-click the OU and select Link an Existing GPO. Choose the GPO you just created and click OK. - Verify the link order (optional). If you have other GPOs that might conflict, ensure this one is processed last or has higher precedence. In GPMC, click the linked OU, and in the right pane under Linked Group Policy Objects, use the up/down arrows to adjust order. Higher in the list means higher precedence.
- Force a refresh (optional but helpful). To apply the policy immediately on a test machine, open Command Prompt as administrator on that machine and run
gpupdate /force. Otherwise, the policy applies automatically within 90 minutes (plus a random offset of up to 30 minutes). - Test the restriction. Log in as a domain user on a computer in the affected OU. Try opening Control Panel from the Start menu, typing
controlin the Run dialog, or runningcontrol.exefrom Command Prompt. All should be blocked with an error message.
Common Mistakes
- Linking to the wrong OU. If you link the GPO to an OU that contains only users, but the computers are elsewhere, the policy won’t apply because the setting is under User Configuration. Make sure the OU contains either the user accounts or the computer accounts that should be affected—but remember that User Configuration policies apply to users, so linking to an OU with the user accounts is the typical approach.
- Forgetting that this blocks PC Settings too. The policy also blocks the modern “Settings” app (PC Settings) on Windows 8 and later. If you only wanted to block the legacy Control Panel, this is not the right policy—you’d need a different approach, but this is the standard way to block both.
- Not considering loopback processing. If you linked the GPO to a computers OU, the User Configuration portion won’t apply unless you enable loopback processing mode on the computer. For most setups, link to the users OU instead.
- Overlooking other access paths. Users can still open some individual Control Panel applets via right-click on the desktop (e.g., Display settings) or via context menus in File Explorer (e.g., “Personalize”). This policy does not block those. To fully lock down, you may need additional policies, but this one is the primary gate.
- Testing as an administrator. If you test while logged in as a domain admin, the policy may not apply because administrators are often excluded by security filtering. Always test with a standard domain user account.
Tips
- Use security filtering to target specific users. By default, a GPO applies to “Authenticated Users.” To limit it to a specific group, go to the Scope tab of the GPO, remove “Authenticated Users” from the Security Filtering list, and add your domain group (e.g., “Restricted Users”). This gives you more control than OU placement alone.
- Combine with other restrictions. This policy works well alongside “Prevent access to registry editing tools” (under System) and “Remove Run from Start Menu” (under Start Menu and Taskbar) for a more locked-down experience.
- Document your GPOs. Add a comment to the GPO (right-click → Edit → Comment) explaining what it does and why. This helps other admins later.
- Test on a pilot group first. Create a test OU with a few computers, link the GPO there, and verify behavior before rolling out to the whole domain.
- Know the refresh interval. If you need changes to apply faster, you can run
gpupdate /forceon the client, or adjust the Group Policy refresh interval in the policy itself (Computer Configuration → Policies → Administrative Templates → System → Group Policy).
Troubleshooting
- Policy not applying. Run
gpresult /ron the client machine to see which GPOs are applied and whether yours appears. If it’s missing, check the security filtering, the OU link, and that the user has “Apply Group Policy” permission (usually inherited from “Authenticated Users”). - Control Panel still accessible. First, confirm you’re testing with a standard user, not an admin. Then check if the policy is actually applied by running
gpresult /h report.htmland looking for the setting. If it’s applied but still accessible, the user might be using a different path—for example, right-clicking the desktop and choosing “Personalize” still works. That’s expected with this policy. - Policy applies but also blocks Settings app. That’s by design. If you need the Settings app for certain tasks, you’ll need to either remove this policy or use a more granular approach (like AppLocker) which is beyond this guide’s scope.
- Changes not appearing after gpupdate. Make sure the client can reach the domain controller and that the time is synchronized. Also, check that the GPO is not blocked at a higher level (e.g., a parent OU has “Block Inheritance” enabled).
- Users can still run applets via command line. Some older applets (like
sysdm.cpl) may still run directly. If you need to block those, you’d need to use software restriction policies or AppLocker to block specific .cpl files, which is a more advanced setup.
Frequently Asked Questions
Q: Does this policy affect Windows 10 and Windows 11?
A: Yes. The policy applies to Windows 10 and 11, blocking both the classic Control Panel and the Settings app. On Windows 8, it also blocks the PC Settings app.
Q: Can users still open Control Panel by typing its full path?
A: No. The policy intercepts the execution of control.exe and displays a message like “This operation has been cancelled due to restrictions in effect on this computer.” This applies to Run, Command Prompt, and File Explorer.
Q: Will this policy affect administrators?
A: By default, yes, unless you filter them out. If you want admins to retain access, add a security filter that excludes the Domain Admins group, or use a WMI filter to target only non-admin users. However, the simplest approach is to test with a regular user and leave admins unaffected by placing the GPO on an OU that doesn’t contain admin accounts.
Q: How long does it take for the policy to apply?
A: By default, Group Policy refreshes every 90 minutes with a random offset of up to 30 minutes. You can force it with gpupdate /force on the client, or restart the computer.
Q: Can I allow access to just one specific Control Panel applet?
A: Not with this policy. It’s all-or-nothing. If you need selective access, you’d have to use a different approach, such as deploying shortcuts to specific .cpl files or using AppLocker rules—both are significantly more complex.
Q: Does this policy work on Windows Server operating systems?
A: Yes, it applies to Windows Server desktops as well, though it’s more commonly used on client workstations. The same GPO can be linked to an OU containing Windows Server computers if needed.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Hard Drive Very Slow Suddenly? Fixes That Work
- Windows Insider: Check New Windows 10 Features
- Restore Pitted Chrome Sink Drain Surrounds
- Error Performing Query Error Facebook: Fixes
- WiFi Not Working on HTC 10? Solved
- Fix Windows 100% CPU Usage: 7 Real Fixes