Type help to print the built-in Command Prompt command list, or type help plus one command name to read that command’s own help text. Type doskey /history to view commands from the current session. If you guess the wrong switch, you lose time and can run the command the wrong way. This guide shows the quickest path to the built-in CMD list, command-specific help, and command history.
What you need before starting
- Windows with Command Prompt available as
cmd.exe. - Access to the Run dialog or Start search.
- A regular Windows account is fine for listing help and history; admin rights matter only for commands that change protected settings.
Command Prompt is the Windows command-line shell for administrative and troubleshooting tasks. It is also called cmd.exe, CMD, Command Line, Command Line Interface, or CLI. One common way to open it is through Run, and Windows 8.1 and later may place it in the Power User Menu. Some Windows versions put PowerShell there instead.
- Press Win + R to open Run.
- Type
cmdand press Enter. - In the Command Prompt window, use
helpto list built-in commands. - If a command needs more detail, use
helpwith that command name orcommand /?. - If you need recent entries, use
doskey /historyin the same window.
If you open Run, type cmd, and need the syntax for cd right away, use help cd or cd /?. Both point to the command’s usage text. doskey /history only shows commands already entered in that session.
How do you see all commands in cmd?
Type help at the Command Prompt to display the built-in command list. That is the fastest way to see commands that CMD knows internally, rather than every program installed on the PC. If you want a short summary of one command, add its name after help.
The difference is straightforward: help lists built-in CMD commands, while external executables and scripts may not appear there. That is why dir is useful for files and folders, but it is not a catalog of everything Command Prompt can run.
Use the help command first
- Open Command Prompt with
cmdfrom Run or Start search. - Type
help. - Press Enter.
- Scan the list for the command you need, such as
cdordir.
Use help for one command
- At the prompt, type
help cdor another command name. - Press Enter.
- Read the short description and available switches.
A common first-time mistake is typing dir and expecting a complete command inventory. dir lists files and directories in the current folder. It does not report every CMD command.
What does help show in CMD?
help shows commands built into Command Prompt and gives a quick description of each one. It helps when you know a command exists but do not remember the exact name or switch order. It does not list every file on the system, and it does not replace a full command history view.
For many common tasks, the help output is enough to keep you from guessing. If you are checking syntax for a built-in command like cd, copy, or mkdir, help is the first place to look.
Use help with a command name
- Type
helpfollowed by the command name. - Press Enter.
- Use the output to confirm the basic purpose and supported options.
Use the /? switch for command-specific usage
- Type the command name, then a space, then
/?. - Press Enter.
- Read the syntax block and option list for that command.
For example, cd /? returns usage details for the built-in change-directory command. That differs from help, which shows the broader built-in command list first and then a short description for the command you name.
How do you see previous commands in Command Prompt?
Use doskey /history to display previously entered commands from the current Command Prompt session. This is the right command when the real question is “What did you just run?” rather than “What commands exist?” The Up Arrow key moves through recent entries one by one.
doskey /history does not pull every command from every past session. It typically shows the history for the current window. If you closed Command Prompt, that session history is gone unless you saved it elsewhere.
View the current session history
- Click into the active Command Prompt window.
- Type
doskey /history. - Press Enter.
- Scroll through the list of prior commands in that session.
Recall one recent command quickly
- Press the Up Arrow key.
- Keep pressing it until the command you want appears.
- Edit the line if needed, then press Enter.
Say your last command was ipconfig /all and you now want to repeat it with a different switch. The Up Arrow gets you back to that entry quickly; doskey /history shows the full current-session list so you can confirm the exact text.
CMD command cheat sheet
| task | exact command | what it returns |
|---|---|---|
| List built-in commands | help |
The built-in CMD command list with short descriptions |
| Get brief help for one command | help <command> |
A short summary and basic use for that command |
| Get detailed syntax for one command | <command> /? |
Command-specific usage, switches, and syntax notes |
| See recent commands | doskey /history |
Previously entered commands from the current session |
| List files in the current folder | dir |
Files and directories in the current location, not a command catalog |
This table separates the three tasks people often mix up: listing built-in commands, getting help for one command, and reviewing command history. dir belongs here only as a contrast point. It shows folder contents, not the CMD command set.
Command Prompt vs PowerShell
Command Prompt and Windows PowerShell are related, but they are not the same. Some Windows menus open PowerShell where older versions showed Command Prompt, and the Power User Menu can change by version. If a shortcut lands you in PowerShell, that does not mean CMD is missing; it may just be placed elsewhere.
Use Command Prompt when you want classic cmd.exe commands, built-in help with help, and session history with doskey /history. Use PowerShell when the menu shortcut opens there and you are working in that shell’s command set instead.
Check which shell you opened
- Look at the window title and prompt style.
- If needed, open Run with Win + R, type
cmd, and press Enter for Command Prompt directly. - Use
helpinside CMD to confirm you are in the right shell.
Use the menu path that gives you CMD
- Open the Start search and type
Command Prompt. - Or right-click the Windows icon to open the Power User Menu.
- If the menu shows PowerShell instead, use Run and type
cmd.
Common mistakes
- Confusing
dirwith a command list. It only lists files and folders in the current directory. - Using
doskey /historyand expecting every past session. It only shows the current window’s history. - Opening PowerShell and expecting the same output or the same built-in help behavior as CMD.
- Skipping
/?when a command needs syntax details, then guessing at switches.
If you only need to check a few troubleshooting steps, stay with help, help <command>, and doskey /history. Those three commands cover most fast lookups without forcing you to learn every CMD command at once.
Frequently asked questions
How do I see all commands in Command Prompt?
Type help inside Command Prompt and press Enter. That prints the built-in CMD command list. If you only need one command’s syntax, follow it with the command name, such as help cd.
What does the help command show in CMD?
help shows built-in Command Prompt commands and a short description for each one. It is the quickest way to find what CMD can run internally. For one command’s full usage, use help <command> or <command> /?.
How do I get details for one command in Command Prompt?
Type help plus the command name, or type the command followed by /?. For example, help cd gives a short summary, while cd /? shows command-specific syntax and options.
What is the difference between Command Prompt and PowerShell?
Command Prompt is cmd.exe, while PowerShell is a different Windows shell. Some Windows menus may open PowerShell instead of CMD. If you need classic CMD help, open Run with Win + R, type cmd, and use help or doskey /history there.