The Run dialog opens any Windows console, Control Panel applet, Settings page or system folder by name. Press Win+R, type devmgmt.msc, press Enter, and Device Manager is on screen without a single menu. If you support Windows machines, a dozen of these names will save you more clicks than anything else.
This Windows Run commands cheat sheet puts the .msc, .cpl, ms-settings: and shell: names into printable tables, then covers the cases where Run rejects a name that looks right. I checked the tables in November 2026 on Windows 11 24H2 (build 26100.9457) and Windows Server 2025 Datacenter (build 26100.33650), and the two systems disagree more often than most lists admit.
Windows Run commands cheat sheet
Type any name from the first column into Run and press Enter. A row marked Windows 11 only was missing from the Server 2025 VM. The last table covers the opposite case, consoles that need Server or the RSAT tools. Every .msc, .cpl, control and shell: row was opened on the lab VMs or confirmed present in System32. The Windows 11 VM ran the Enterprise edition, so expect policy consoles such as gpedit.msc to be missing on Home. Each Settings row was opened in a signed-in session on both VMs, and the table records the page Settings landed on. Microsoft’s ms-settings URI reference lists more pages and warns that some depend on the edition and the hardware.
Management consoles (.msc)
| Command | What it opens |
|---|---|
devmgmt.msc | Device Manager |
compmgmt.msc | Computer Management: disks, services, users and logs in one window |
diskmgmt.msc | Disk Management |
services.msc | Services |
eventvwr.msc | Event Viewer |
taskschd.msc | Task Scheduler |
gpedit.msc | Local Group Policy Editor |
secpol.msc | Local Security Policy |
lusrmgr.msc | Local Users and Groups |
certmgr.msc | Certificates for the current user |
certlm.msc | Certificates for the local computer |
perfmon.msc | Performance Monitor |
fsmgmt.msc | Shared Folders and open files |
wf.msc | Windows Defender Firewall with Advanced Security |
tpm.msc | TPM Management |
printmanagement.msc | Print Management (Windows 11 only by default) |
rsop.msc | Resultant Set of Policy |
comexp.msc | Component Services |
wmimgmt.msc | WMI Control |
Control Panel applets (.cpl)
| Command | What it opens |
|---|---|
ncpa.cpl | Network Connections, the adapter list |
appwiz.cpl | Programs and Features |
sysdm.cpl | System Properties |
firewall.cpl | Windows Defender Firewall |
powercfg.cpl | Power Options |
inetcpl.cpl | Internet Properties (proxy, certificates) |
mmsys.cpl | Sound devices |
main.cpl | Mouse Properties |
timedate.cpl | Date and Time |
intl.cpl | Region and formats |
joy.cpl | Game Controllers |
tabletpc.cpl | Pen and Touch |
telephon.cpl | Location Information (dialing rules) |
wscui.cpl | Security and Maintenance (Windows 11 only) |
hdwwiz.cpl | Lands in Device Manager |
desk.cpl | Redirects to the Settings app |
Control Panel by name or tab
| Command | What it opens |
|---|---|
control /name Microsoft.ProgramsAndFeatures | Programs and Features |
control /name Microsoft.NetworkAndSharingCenter | Network and Sharing Center |
control /name Microsoft.WindowsFirewall | Windows Defender Firewall |
control /name Microsoft.PowerOptions | Power Options |
control /name Microsoft.CredentialManager | Credential Manager |
control /name Microsoft.AdministrativeTools | The Windows Tools folder |
control /name Microsoft.DeviceManager | Device Manager |
control /name Microsoft.System | Redirects to Settings |
control sysdm.cpl,,3 | System Properties on the Advanced tab |
SystemPropertiesAdvanced | The same Advanced tab, no commas |
rundll32 sysdm.cpl,EditEnvironmentVariables | Environment Variables dialog |
Settings pages (ms-settings:)
| Command | Page it opened on Windows 11 | Server 2025 |
|---|---|---|
ms-settings:windowsupdate | Windows Update | Same page |
ms-settings:installed-apps | Apps, Installed apps | Same page |
ms-settings:appsfeatures | Apps, Installed apps | Same page |
ms-settings:about | System, About (device name, specs) | Same page |
ms-settings:display | System, Display | Same page |
ms-settings:sound | System, Sound | Same page, activation banner |
ms-settings:bluetooth | Bluetooth & devices, Devices | Same page |
ms-settings:network-status | Network & internet | Same page |
ms-settings:defaultapps | Apps, Default apps | Same page |
ms-settings:startupapps | Apps, Startup | Same page |
ms-settings:optionalfeatures | System, Optional features | Same page |
ms-settings:storagesense | System, Storage | Same page |
ms-settings:dateandtime | Time & language, Date & time | Same page |
ms-settings:windowsdefender | Privacy & security, Windows Security | Same page |
ms-settings:troubleshoot | System, Troubleshoot | Same page |
ms-settings:recovery | System, Recovery | Same page |
ms-settings:activation | System, Activation | Same page |
ms-settings:remotedesktop | System, Remote Desktop | Same page |
ms-settings:developers | System, Advanced | System, For developers |
Folders (shell:)
| Command | What it opens |
|---|---|
shell:startup | Your Startup folder |
shell:common startup | Startup folder for all users |
shell:sendto | Send to menu entries |
shell:appdata | AppData\Roaming |
shell:local appdata | AppData\Local |
shell:profile | Your user profile folder |
shell:downloads | Downloads |
shell:recent | Recent items |
shell:start menu | Your Start menu folder |
shell:common administrative tools | Administrative Tools shortcuts |
shell:appsfolder | Every installed app, Store apps included |
shell:fonts | C:\Windows\Fonts |
shell:system | C:\Windows\System32 |
shell:recyclebinfolder | Recycle Bin |
shell:printersfolder | Printers |
Tools and utilities
| Command | What it opens |
|---|---|
msinfo32 | System Information |
msconfig | System Configuration (boot options) |
regedit | Registry Editor |
resmon | Resource Monitor |
taskmgr | Task Manager |
winver | Windows version and build |
optionalfeatures | Windows Features on or off |
dxdiag | DirectX Diagnostic Tool |
mstsc | Remote Desktop Connection |
mdsched | Windows Memory Diagnostic |
netplwiz | User Accounts, advanced |
dfrgui | Optimize Drives |
credwiz | Back up or restore saved credentials |
UserAccountControlSettings | UAC slider |
odbcad32 | ODBC Data Source Administrator |
charmap | Character Map |
osk | On-Screen Keyboard |
rstrui | System Restore (Windows 11 only) |
msra | Windows Remote Assistance (Windows 11 only) |
wt | Windows Terminal |
cmd | Command Prompt |
Windows Server and RSAT consoles
| Command | What it opens |
|---|---|
servermanager | Server Manager (Server only) |
dsa.msc | Active Directory Users and Computers |
gpmc.msc | Group Policy Management |
dnsmgmt.msc | DNS Manager |
dhcpmgmt.msc | DHCP |
adsiedit.msc | ADSI Edit |
dssite.msc | Active Directory Sites and Services |
domain.msc | Active Directory Domains and Trusts |
wbadmin.msc | Windows Server Backup (Server only) |
Apart from servermanager and wbadmin.msc, none of the consoles in that last table exist on a fresh install of either system. They arrive with the RSAT features, and until then Run answers with the same error it gives for a typo, which is the first problem covered below.
How do you open the Run dialog as administrator?
Press Win+R, or right-click Start and pick Run. The dialog has a single field, the Open box, and it keeps a history of what you typed, so a console you use every day is usually one arrow key away. Type the name into the Open box (1) and press Enter or click OK (2).

- 1Open box
- 2OK
Enter starts the program with your normal token, even when your account is a local administrator. Press Ctrl+Shift+Enter instead and Windows asks for elevation first: on our Windows 11 VM, typing cmd and pressing Ctrl+Shift+Enter brought up the UAC prompt for Windows Command Processor, with Microsoft Windows as the verified publisher.

After clicking Yes, the window title read Administrator: C:\WINDOWS\system32\cmd.exe. A title is only a label, so we also checked the token’s integrity level from inside that prompt:
whoami /groups | findstr /c:"Mandatory Label"
The output names the label in plain words. High is what an elevated process carries:
Mandatory Label\High Mandatory Level Label S-1-16-12288
Anything lower than High means the prompt is not elevated. That difference matters most for cmd and powershell, because neither asks for elevation on its own: open them unelevated and the admin command you paste five minutes later fails with access denied. Make Ctrl+Shift+Enter the habit for shells, and the Windows CMD commands cheat sheet covers what to run once you are in.
Why does Run say Windows cannot find a command?
Run gives one message for several different problems: “Windows cannot find ‘name‘. Make sure you typed the name correctly, and then try again.” On our Windows 11 VM it came from a missing extension, a console that was not installed, and a Control Panel argument that Run does not parse. Before you retype anything, check these:
- The name ends in its extension, so it reads
devmgmt.mscand notdevmgmt. Test-Path C:\Windows\System32\dsa.mscin PowerShell returns True for the console you want.- Any .cpl name followed by commas starts with the word
control.
Each of those failed for us at least once, and the fix differs. The three errors below show the exact message, what caused it and what got the console open.
Windows cannot find ‘devmgmt’
Leaving the extension off a console name fails, even though .MSC is on the PATHEXT list. We typed devmgmt into Run on Windows 11 and got the cannot-find error. The PATHEXT value on the same machine ended in .MSC, as the PATHEXT row in the Environment Variables figure further down shows.
PATHEXT is the list the command shell uses to guess an extension, and the Run box did not apply it to the console here. So type the full file name for every .msc and .cpl entry. Plain programs such as cmd and msinfo32 open fine without one.
Windows cannot find ‘dsa.msc’
On Windows 11, dsa.msc (Active Directory Users and Computers) does not exist until you add the RSAT tools. Our Windows 11 VM had 21 .msc files in System32 and none of the directory consoles: dsa, gpmc, dnsmgmt, dhcpmgmt, adsiedit, dssite and domain were all absent. Run cannot tell you that a console is an optional feature, so the error reads exactly like a typo.

On Windows 11 the fix is the RSAT optional features, which our guide to install RSAT on Windows 11 walks through. On Windows Server it takes one Install-WindowsFeature command, shown in the Server section below. Either way, confirm the file is in System32 before you blame the spelling, because the console name is the same on both systems once the tools are in.
Windows cannot find ‘sysdm.cpl,,3’
The comma suffix opens a Control Panel applet on a chosen tab, but only when control runs it. Typed on its own, Run treats sysdm.cpl,,3 as a file name and shows the cannot-find error. With the prefix, control sysdm.cpl,,3 opened System Properties straight on the Advanced tab, where Performance, User Profiles and Startup and Recovery live.

For this particular tab, SystemPropertiesAdvanced lands in the same place without the commas and is easier to remember. Keep the control form for applets that have no shortcut of their own, and for the control /name canonical names in the table, which open the same windows by a readable name.
Which ms-settings pages can you open from Run?
Any page on Microsoft’s ms-settings list that your edition and hardware support opens from Run. We opened all 19 names in the table on both VMs from a non-elevated user session, and every one landed on a named page, not on the Settings home screen. Only ms-settings:developers differed. It opened System, Advanced on Windows 11 and the older System, For developers page on Server 2025. Server’s Sound page also carried a “You need to activate Windows” banner, since our evaluation install was not activated. ms-settings:windowsupdate went straight to Windows Update, the fastest route to Check for updates on a machine you are setting up.

Microsoft’s list is not complete. ms-settings:installed-apps does not appear on it, yet on Windows 11 it opened Apps, Installed apps and counted 36 apps on the VM. Microsoft documents ms-settings:appsfeatures for that page, and it opened the same Installed apps list on both VMs, so use the documented name in scripts you hand to other people and the short one when you are typing it yourself.
More of Control Panel now sends you to Settings than most cheat sheets admit. These classic names still work on Windows 11, but they no longer open the window you might remember:
desk.cplopens the Settings app.control /name Microsoft.Systemopens the Settings app.control /name Microsoft.WindowsUpdateopens the Settings app.hdwwiz.cplopens Device Manager.
Microsoft says Control Panel settings “are in the process of being migrated to the Settings app” and that Control Panel stays for compatibility. So the old names keep working, they just land somewhere new. Applets such as ncpa.cpl still open their classic windows, and that one is still the quickest route to adapter properties when you open a port in Windows Server Firewall or set a static address.

Network Connections shows every adapter with its driver name, which on the lab VM was the emulated Intel PRO/1000. Right-click an adapter and choose Properties to reach the IPv4 settings, the one dialog Settings still hides several clicks deep.
Which shell: folders are worth remembering?
A shell: name opens a special folder wherever Windows keeps it for the current user. You don’t need the real path, and hidden files can stay hidden. Windows 11 registers 134 of these names, and we resolved 36 of them on the lab VM to keep the ones people actually reach for. shell:startup is the one you will use most, because anything you drop in it starts when you sign in.

Explorer showed it as Start Menu, Programs, Startup, and the real path behind it was C:\Users\harrison\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. Three details from the lab are worth keeping in mind:
shell:common startupresolves toC:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startupand runs its items for every user.shell:screenshotsresolved to nothing on a fresh profile, because the Pictures\Screenshots folder did not exist yet.shell:appsfolderis a virtual folder, so it lists Store apps that have no .exe you could browse to.
If a shell: name opens nothing, the folder probably has not been created yet; save one file there through the app that owns it and try again. For anything a whole team should start at sign-in, use the common folder or a scheduled task rather than each person’s own Startup folder.
What changes on Windows Server 2025?
Server 2025 runs almost the same Run commands as Windows 11, with a few gaps either way. We inventoried both VMs as SYSTEM, then repeated the alias check in the signed-in user’s session, because Store app aliases only exist per user. These are the differences that change what you type:
| Command | Windows 11 | Server 2025, fresh install |
|---|---|---|
servermanager | Missing | Present |
wbadmin.msc | Missing | Present |
printmanagement.msc | Present | Needs RSAT-Print-Services |
dsa.msc, gpmc.msc, dnsmgmt.msc | Needs RSAT | Needs RSAT features |
wscui.cpl | Present | Missing |
rstrui, msra | Present | Missing |
sudo | Present, off by default | Missing |
wt, winget | Per-user alias | Per-user alias |
wmic | Missing | Missing |
The aliases explain a common surprise: an admin script that runs wt or winget as SYSTEM fails even though both work when you type them. We checked in each user session with Get-Command:
Get-Command wt, winget, mspaint, SnippingTool, sudo -ErrorAction SilentlyContinue | Format-Table Name, Source -AutoSize
On Server 2025, wt and winget resolve to the user’s WindowsApps folder, Paint and Snipping Tool are ordinary System32 programs, and sudo is simply not there:
Name Source
---- ------
wt.exe C:\Users\harrison\AppData\Local\Microsoft\WindowsApps\wt.exe
winget.exe C:\Users\harrison\AppData\Local\Microsoft\WindowsApps\winget.exe
mspaint.exe C:\WINDOWS\system32\mspaint.exe
SnippingTool.exe C:\WINDOWS\system32\SnippingTool.exe
On Windows 11 the same command also listed C:\WINDOWS\system32\sudo.exe. Running sudo config on the fresh VM answered “Sudo is disabled on this machine”, which matches Microsoft’s Sudo for Windows page: you switch it on under System, Advanced (ms-settings:developers). Paint and Snipping Tool came back as WindowsApps aliases rather than System32 files. Treat anything under WindowsApps as belonging to one user, and call the full System32 path in scripts that run as a service.
Add the directory consoles with Install-WindowsFeature
The consoles in the RSAT table come from Windows features on Server, and one elevated PowerShell line adds all of them. Drop any feature name you don’t need. This is the set we installed on the Server 2025 VM:
Install-WindowsFeature RSAT-ADDS,RSAT-DNS-Server,RSAT-DHCP,GPMC,RSAT-Print-Services
It took about six minutes on a 4 vCPU VM and needed no installation media. Watch the RestartNeeded line, which came back No:
Success : True
RestartNeeded : No
FeatureResult : {Group Policy Management, Remote Server Administration Tools, Active Directory Administrative Center,
Active Directory module for Windows PowerShell...}
ExitCode : Success
Every console in the RSAT table landed in System32 in that one run. Before you close the elevated window, check the result the same way we did:
- Get-WindowsFeature shows GPMC, RSAT-ADDS, RSAT-DHCP, RSAT-DNS-Server and RSAT-Print-Services as Installed.
Test-Path C:\Windows\System32\dsa.mscreturns True, and so does the same check forgpmc.msc.dsa.msctyped into Run opens a console, with no sign-out needed first.
All three passed on our VM. If you are building Group Policy next, our walkthrough on Group Policy on Windows Server 2025 picks up from gpmc.msc, and the same console is where you set up Windows LAPS for local admin passwords. On a server outside a domain, though, expect the warning in the next section.
dsa.msc warns to use Local Users and Groups
On a server that has not joined a domain, dsa.msc opens with a warning instead of your directory. The VM was a workgroup machine, so Active Directory Users and Computers had nothing to connect to. This is the message it showed:

Clicking OK opens the console with a red X on the root node. Nothing is broken: the tools are installed, they just need a domain. Sign in with a domain account, or use lusrmgr.msc for the local accounts the message points to.
File system error (-2147219196) on ms-settings:about
About three minutes after the first sign-in on the Server 2025 VM, ms-settings:about failed instead of opening Settings. The dialog gives a number and nothing else:

We ran the same command about 40 seconds later and System, About opened normally, so on our VM the error came from first sign-in setup that was still running. If you hit it on a new profile, wait a minute and retry before you start repairing the Settings app. If it keeps happening on a profile that has been in use for days, that is a different problem from the one we saw.
How do you open Environment Variables from Run?
Type rundll32 sysdm.cpl,EditEnvironmentVariables in Run and the Environment Variables dialog opens directly, skipping System Properties. The PATHEXT row (1) is where we read the extension list from the devmgmt test. In the System variables pane, New, Edit and Delete were greyed out (2), because a dialog launched with plain Enter only edits your own user variables.

- 1PATHEXT
- 2greyed out
To change a system variable such as Path for every user, open it from an elevated place instead: SystemPropertiesAdvanced started with Ctrl+Shift+Enter, then the Environment Variables button. User variables are the safer default anyway, since a bad edit there breaks one account rather than every service on the machine.
Where did wmic go?
It’s gone from both systems we tested. Microsoft’s removed features list says WMIC has been removed from current Windows 11 releases, and it is no longer offered as a Feature on Demand either. wmic.exe was missing from System32 on our Windows 11 and Server 2025 VMs alike. Old Run lists that still include wmic now produce the cannot-find error.
The WMI data itself is still there. wmimgmt.msc opens the WMI Control console, and PowerShell’s Get-CimInstance replaces the queries people used wmic for; our PowerShell cheat sheet has the common ones side by side.
Which Run commands should you try on a new machine?
Five commands tell you in about two minutes whether a machine is ready for the rest of this sheet. Run them in this order on any new Windows 11 or Server box, because each one assumes the one before it passed:
winvershows the build you expect, so you know which rows above apply.ms-settings:windowsupdatereports no pending updates.devmgmt.mscshows no device with a yellow warning icon.cmdopened with Ctrl+Shift+Enter reports High Mandatory Level from the whoami check.dsa.mscopens a console instead of the cannot-find error, if you manage a domain from this machine.
If all five pass, the machine is ready and the tables above will behave as described. If one fails, the matching section above has the cause we hit and the fix. For the rest of a fresh Windows 11 build, our things to do after installing Windows 11 checklist and the Windows 11 keyboard shortcuts sheet pair well with this one, and every printable sheet is on the cheat sheets hub.