To execute an .exe file in CMD, open Command Prompt, navigate to the folder using cd, then type the filename or start [filename.exe].
Running an .exe from Command Prompt is a straightforward skill that avoids clicking through folders and lets you launch programs with precision. The core method takes four steps: open CMD (with admin rights if needed), locate the file path, navigate to that directory, and execute the file. Below we break down each step, cover an alternative for long‑term convenience, and fix the most common mistakes.
Preparing Command Prompt
Press Win + R, type cmd, and press Enter. For programs that need elevated permissions — like system tools or installers — right‑click Command Prompt and select Run as administrator. This avoids silent failures and access‑denied errors.
Finding the File Path
Open File Explorer and browse to the folder containing the .exe file. The folder’s full path appears in the address bar at the top. Right‑click the address bar, choose Copy address (or press Ctrl + C), and you’ll have the path ready for the next step.
Navigating to the Directory
Back in CMD, type cd (with a space after cd) and paste the copied path. For example:
cd C:\Users\YourName\Desktop\MyFolderPress Enter. The command prompt should now show that directory. If it doesn’t change, check for a missing backslash or a space between cd and the path.
Executing the EXE File
Once inside the correct folder, type the file name with or without the .exe extension. For a program named setup.exe, type:
setup.exeor simply:
setupYou can also use the start command: start setup.exe — this opens the program in a new window and lets you continue using the same CMD session. Both methods work identically for most .exe files.
Common Mistakes and How to Fix Them
The table below lists frequent errors and their quick fixes so you can get back to work without frustration.
| Mistake | Consequence | Fix |
|---|---|---|
Using ./filename.exe (UNIX style) |
CMD fails to execute | Use filename.exe or .\filename.exe |
Missing space in cd [path] |
CMD returns an error | Add a space: cd C:\Path |
| Not running CMD as administrator | Protected apps won’t launch | Right‑click CMD → Run as administrator |
| Drag‑and‑drop into CMD (32‑bit issue) | CMD defaults to 32‑bit, may fail | Type the full path manually |
| File blocked by Windows Defender | File won’t run | Right‑click file → Properties → check Unblock |
Changing directory to a different drive without /d |
cd doesn’t change drive |
Use cd /d D:\Folder or type D: first |
Typing start without a file name |
Opens a blank CMD window | Always provide a file name: start app.exe |
Alternative: Run the EXE from Any Directory
If you use a specific .exe often — like a custom tool or a portable app — add its folder to your system’s PATH environment variable. Once added, you can run the program from any CMD location without cd or a full path. Microsoft’s official guidance also recommends this approach for frequently used utilities. To do it:
- Open System Properties (search “Environment Variables” in Start).
- Under System variables, select Path and click Edit.
- Add the folder containing your .exe (e.g.,
C:\Tools\). - Click OK and restart CMD. Now you can run the .exe by typing just its name.
Three Ways to Run an EXE in CMD
Different situations call for different execution methods. The table below summarizes your options.
| Method | Command Example | Best For |
|---|---|---|
Direct name (after cd) |
chrome.exe |
Quick launch when already in the folder |
start command |
start chrome.exe |
Running a program and keeping CMD usable |
Full path (no cd needed) |
"C:\Program Files\App\app.exe" |
One‑off execution without changing directory |
Quick Command Reference
Bookmark this concise rundown for next time you need to run an .exe from the command line:
cmd # Open Command Prompt (Win+R, cmd)
cd C:\Path\To\YourFolder # Navigate to the folder
yourfile.exe # Run the executable
start yourfile.exe # Run and keep CMD activeReferences & Sources
- Microsoft Learn. "Why can I only open some programs with the command prompt?" Covers file blocking, admin rights, and PATH changes.