Skip to content
WindowsIntermediate

Windows Control Panel Command: How control and control.exe Work

QUICK ANSWER The Windows control command starts control.exe, the built-in program that opens Control Panel. Press Windows key + R, enter control, and press E...

BI
Bison Technical Team Enterprise IT specialists
Updated 20 Sep 2026 12 min read 0 total views

QUICK ANSWER

The Windows control command starts control.exe, the built-in program that opens Control Panel. Press Windows key + R, enter control, and press Enter. The same command works from Command Prompt, Windows PowerShell, Windows Terminal, shortcuts, scripts, and the File Explorer address bar.

Advertisement

You can open a particular Control Panel item with a command such as control appwiz.cpl or, where supported, control.exe /name Microsoft.ProgramsAndFeatures. Microsoft recommends using the modern Settings app whenever it provides the required option because Control Panel functionality continues to migrate to Settings. Microsoft Support

What Is the Windows control Command?

control is the command commonly used to run %SystemRoot%\System32\control.exe, the executable responsible for displaying Control Panel and opening registered Control Panel items.

Control Panel is Windows’ traditional interface for managing system configuration. Its applets cover areas such as:

  • Installed desktop programs
  • Network adapters and sharing
  • User accounts
  • Sound devices
  • Power options
  • Windows Firewall
  • Mouse and keyboard settings
  • Fonts
  • Date and time
  • Administrative tools

Control Panel remains available for compatibility and for settings that have not moved completely to the Settings app. Microsoft nevertheless recommends using Settings when it provides the required function. Microsoft Support

How to Open Control Panel with control

Using the Run Dialog

  1. Press Windows key + R.
  2. Enter:
control
  1. Press Enter or select OK.

Using Command Prompt or Windows Terminal

Run:

control

Using the complete executable name produces the same result:

control.exe

You can also specify its standard system path:

%SystemRoot%\System32\control.exe

The command normally returns immediately after asking Windows Explorer to display Control Panel. A console window does not need to remain open.

Using Windows PowerShell

Run either of these commands:

control
Start-Process control.exe

Start-Process is useful in scripts because it explicitly starts a separate process.

Using File Explorer

Enter the following in File Explorer’s address bar and press Enter:

control

Using Windows Search

Open Start, search for Control Panel, and select the matching result. This method does not require knowledge of a command.

How the Command Works

When Windows receives control as a command, it locates control.exe through the normal executable search process. The standard copy is stored in the Windows system directory.

Depending on the supplied arguments, control.exe can:

  1. Open the main Control Panel window.
  2. Load a traditional .cpl Control Panel module.
  3. Ask the Windows shell to display an item identified by its canonical name.
  4. Pass supported page or tab arguments to an applet.
  5. Redirect to Settings when Windows has migrated that function.

Traditional applets may be implemented as .cpl files, DLL-based shell items, or separate executables. Therefore, not every Control Panel item behaves identically.

Useful Control Panel Commands

The following commands are commonly available in supported Windows desktop installations. Exact behavior can differ by Windows version, edition, installed hardware, and organizational policy.

Purpose Command
Main Control Panel control
Programs and Features control appwiz.cpl
Network Connections control ncpa.cpl
System Properties control sysdm.cpl
Internet Properties control inetcpl.cpl
Mouse Properties control main.cpl
Keyboard Properties control keyboard
Sound control mmsys.cpl
Power Options control powercfg.cpl
Windows Defender Firewall control firewall.cpl
Date and Time control timedate.cpl
Region control intl.cpl
Game Controllers control joy.cpl
Fonts folder control fonts
Printers view control printers
User Accounts control userpasswords
Credential Manager control /name Microsoft.CredentialManager
File Explorer Options control folders

A component may be missing or redirected if it is not installed, does not apply to the device, has been removed from that Windows release, or has moved to Settings.

Commands with Additional Parameters

Some applets accept parameters that select a particular tab or page. For example:

control sysdm.cpl,,3

This traditionally opens the Advanced tab in System Properties.

control inetcpl.cpl,,4

This opens the Connections tab in Internet Properties on systems where that page is available.

These numeric tab indexes are older interfaces and can be less reliable than canonical names or supported Settings URIs. Test them against every Windows version included in an organizational deployment.

Canonical Control Panel Names

Since Windows Vista, many Control Panel items have had non-localized canonical names. Microsoft identifies canonical names as the preferred command-line method for launching compatible Control Panel items because the name can remain stable even if Microsoft changes the underlying module. Microsoft Learn

The syntax is:

control.exe /name CanonicalName

Examples include:

control.exe /name Microsoft.ProgramsAndFeatures
control.exe /name Microsoft.NetworkAndSharingCenter
control.exe /name Microsoft.PowerOptions
control.exe /name Microsoft.Sound
control.exe /name Microsoft.CredentialManager
control.exe /name Microsoft.WindowsFirewall

Canonical names are not guaranteed to remain functional indefinitely. A name documented for an older release may be unavailable or may redirect to Settings in a newer Windows version.

Opening a Specific Canonical Page

Some Control Panel items expose named pages:

control.exe /name Microsoft.NetworkAndSharingCenter /page Advanced

Page support is specific to the selected item. An unsupported page name might open the item’s main page or produce no useful result.

Using Control Panel Commands in PowerShell

Windows PowerShell provides cmdlets that can discover and open registered Control Panel items.

List available items:

Get-ControlPanelItem

Find items by display name:

Get-ControlPanelItem -Name '*Network*'

Open an item using its display name:

Show-ControlPanelItem -Name 'Programs and Features'

Open an item using its canonical name:

Show-ControlPanelItem -CanonicalName 'Microsoft.PowerOptions'

Wildcards are supported by the -Name and -CanonicalName parameters. Microsoft Learn

Display names can vary with the Windows language, so canonical names are preferable in scripts. Verify cmdlet and item availability on the PowerShell edition and Windows build where the script will run.

Creating a Control Panel Shortcut

To create a shortcut to the main Control Panel:

  1. Right-click an empty area of the desktop.
  2. Select New > Shortcut.
  3. Enter:
control.exe
  1. Select Next.
  2. Name the shortcut Control Panel.
  3. Select Finish.

For a specific item, use a verified command such as:

control.exe /name Microsoft.ProgramsAndFeatures

Shortcuts can also be pinned where the installed Windows version permits it.

Using the Command in Scripts

A batch file can open Control Panel like this:

@echo off
start "" control.exe

To open a specific item:

@echo off
start "" control.exe /name Microsoft.PowerOptions

The empty quoted value after start is the window-title argument. Omitting it can cause incorrect parsing when the executable path is quoted.

A PowerShell equivalent is:

Start-Process -FilePath "$env:SystemRoot\System32\control.exe" `
    -ArgumentList '/name', 'Microsoft.PowerOptions'

Opening an applet does not automatically modify a setting. Automating an actual configuration usually requires a supported PowerShell cmdlet, Windows API, Group Policy, configuration service provider, or management product. UI automation of Control Panel is fragile and unsuitable for reliable enterprise configuration.

Permissions and Security

Opening Control Panel normally does not require administrator privileges. Individual changes may require elevation and produce a User Account Control prompt.

Examples of actions that can require administrative authorization include:

  • Changing system-wide network configuration
  • Removing software installed for all users
  • Changing firewall rules
  • Modifying system-level power or hardware settings
  • Changing another user’s account
  • Accessing protected administrative tools

Important safety practices include:

  • Do not disable UAC merely to avoid elevation prompts.
  • Do not run unknown command files with administrator rights.
  • Confirm the source and purpose of any .cpl file before opening it.
  • Do not download replacement Control Panel files from unofficial websites.
  • Use organizational management policies for repeatable fleet configuration.
  • Test scripts and policy changes on a non-production device first.

control.exe is only a launcher. It does not bypass Windows permissions, Group Policy, MDM restrictions, or security controls.

Benefits of the control Command

Fast Access

The command provides quick access without navigating through several menus. This is especially useful for support technicians working across many computers.

Consistent Entry Point

control works from Run, Command Prompt, PowerShell, Windows Terminal, File Explorer, scripts, and shortcuts.

Direct Access to Legacy Features

Some advanced settings and desktop-program management functions remain easier to reach through Control Panel.

Script and Shortcut Integration

Canonical names can be included in support scripts, remote-assistance instructions, application launchers, and desktop shortcuts.

Language Independence

Canonical names such as Microsoft.PowerOptions do not depend on the displayed language, making them more suitable than localized item names for administrative scripts.

Troubleshooting Efficiency

Commands such as ncpa.cpl, sysdm.cpl, and appwiz.cpl let technicians reach commonly used diagnostic interfaces quickly.

Limitations

The control command has several important limitations:

  • It opens graphical interfaces; it is not a complete command-line configuration system.
  • Applet availability varies by Windows release, edition, hardware, installed software, and enabled features.
  • Some Control Panel links now redirect to Settings.
  • Older .cpl or numeric-tab commands may change or stop working.
  • Graphical Control Panel is unsuitable for unattended server automation.
  • Policies can hide or block individual items.
  • A 32-bit process and a 64-bit process may encounter different component behavior in specialized legacy environments.
  • Commands that work interactively may fail in non-interactive sessions.
  • Opening an applet does not confirm that a requested configuration was successfully changed.

Microsoft is migrating many functions to Settings, so new scripts should use supported Settings URIs or management interfaces when appropriate.

Control Panel Versus Windows Settings

Requirement Recommended interface
Ordinary modern Windows configuration Settings
Legacy applet not fully represented in Settings Control Panel
Open a modern page from Run or an application ms-settings: URI
Repeatable enterprise configuration Group Policy, MDM, PowerShell, or supported management API
One-time interactive troubleshooting Control Panel, Settings, or an appropriate administrative console
Unattended automation Supported command-line, API, policy, or management interface

Press Windows key + I to open Settings. From Run, you can enter:

ms-settings:

Specific pages can be opened with supported URIs, for example:

ms-settings:appsfeatures
ms-settings:network
ms-settings:windowsupdate

Settings-page availability can vary by Windows version and edition. Microsoft maintains a documented ms-settings: URI reference for application and administrative integration. Microsoft Learn

How to Verify a Command Before Deployment

IT professionals should test each command on every supported Windows release:

  1. Run the command as a standard user.
  2. Confirm that the intended item or page opens.
  3. Check whether Windows redirects it to Settings.
  4. Repeat the test with the organization’s policies applied.
  5. Verify behavior on each required architecture, edition, and display language.
  6. Test elevation separately if the subsequent action changes protected settings.
  7. Replace legacy commands when a supported modern interface is available.

PowerShell can help identify registered items:

Get-ControlPanelItem |
    Sort-Object Category, Name |
    Format-Table Name, CanonicalName, Category -AutoSize

The results reflect items discoverable in the current environment rather than every item that has existed in Windows.

Troubleshooting the control Command

Nothing Happens

Try the explicit path:

%SystemRoot%\System32\control.exe

If the main Control Panel opens but a particular item does not, that item may be unavailable, removed, redirected, or blocked.

Windows Cannot Find control

Verify that the executable exists:

where control.exe

The normal result should point to the Windows system directory. Do not obtain a replacement executable from a third-party download site.

If Windows components appear damaged, an administrator can use Microsoft’s supported servicing tools:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart Windows after repairs if instructed. These scans can take time and should not be interrupted unnecessarily.

A Specific .cpl Command Fails

Possible causes include:

  • The applet was removed or moved to Settings.
  • Its optional Windows component is not installed.
  • The device does not have the relevant hardware.
  • Group Policy or MDM blocks the item.
  • A third-party applet was uninstalled or corrupted.
  • The command applies only to an older Windows release.

Try the main Control Panel and search for the item. Also check Settings for an equivalent page.

The Wrong Page Opens

A numeric tab index or legacy argument may have changed. Prefer a documented canonical name or ms-settings: URI, then validate it on the target Windows build.

The Item Is Missing

Change View by from Category to Large icons or Small icons. If it remains absent, use:

Get-ControlPanelItem

On managed devices, contact the administrator because policy may intentionally hide the item.

Access Is Denied or Options Are Unavailable

Sign in with an authorized account and approve UAC only when the requested change is expected. On organizational devices, policy can prevent changes even for local administrators.

FAQ

Frequently Asked Questions

Is control the same as control.exe?

Yes. When entered as a command, control normally resolves to the control.exe executable in the Windows system directory.

Does control require administrator rights?

Opening Control Panel generally does not. A particular system-level change may require administrative credentials or UAC approval.

Does the command work in Windows 10 and Windows 11?

Yes, the main control command is available in both. Individual applets and arguments can differ or redirect to Settings as Windows evolves.

What is a .cpl file?

A .cpl file is a traditional Control Panel module. Examples include appwiz.cpl, ncpa.cpl, and sysdm.cpl. Not every modern Control Panel item is implemented as a .cpl file.

What is the safest way to open a particular applet?

Use an officially documented canonical name where available, such as:

control.exe /name Microsoft.PowerOptions

For modern Windows pages, prefer an applicable, documented ms-settings: URI.

Can control.exe change settings silently?

Normally, no. It primarily opens a graphical Control Panel interface. Silent, repeatable changes should use supported policies, PowerShell cmdlets, management APIs, or configuration tools.

Why does a Control Panel command open Settings?

Microsoft is transferring many configuration experiences from Control Panel to Settings. Windows may redirect an older entry point to its modern replacement.

Can Group Policy restrict Control Panel?

Yes. Administrators can hide specified items, show only approved items, or prohibit access to Control Panel and Settings. Canonical item names can be used by applicable policies. Microsoft Learn

Can I use Control Panel commands on Windows Server?

Some commands work on Windows Server, but availability depends on the release, installed roles, features, and whether the graphical interface is installed. Use PowerShell and supported server-management tools for repeatable administration.

FINAL RECOMMENDATION / CONCLUSION

Use control for quick, interactive access to Control Panel and use verified canonical names when a specific legacy item is required. Prefer Windows Settings for ordinary modern configuration and supported PowerShell, Group Policy, MDM, or management APIs for automation.

Before deploying a Control Panel command across an organization, test it on every supported Windows version and with the applicable security policies. Never assume that an older .cpl, canonical name, or tab number will behave identically on future Windows builds.

 

#Windows #ControlPanel #ControlCommand #ControlExe #Windows11 #Windows10 #CommandPrompt #PowerShell #WindowsTerminal #RunCommands #CPL #SystemAdministration #ITSupport #WindowsSettings #Troubleshooting #SystemConfiguration #CanonicalNames #GroupPolicy #WindowsSecurity #ITProfessionals

SOURCES

 

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.

THE BISON BRIEF

Practical IT knowledge, once a week.

New troubleshooting guides, scripts and infrastructure notes. No noise.

By subscribing, you agree to our privacy policy.