HELP Command: Get Windows CMD Command Documentation

The HELP command is a Windows Command Prompt utility that displays documentation and usage information for built-in CMD commands. Type HELP alone to see all available commands, or HELP [command-name] to get detailed syntax, parameters, and examples for a specific command. This built-in reference system eliminates the need to search online for basic command documentation.

Whether you're a system administrator troubleshooting server issues, an IT professional writing batch scripts, or a developer automating Windows tasks, the HELP command provides instant access to accurate command syntax and parameters. Instead of memorizing hundreds of command options or searching documentation websites, you can query the help system directly from your terminal for immediate, context-specific guidance.

This comprehensive guide covers HELP command syntax, practical examples for discovering and learning commands, real-world use cases for IT professionals and developers, troubleshooting tips for common issues, and frequently asked questions. By the end, you'll efficiently navigate Windows command documentation and accelerate your command-line workflow.

What Is the HELP Command?

The HELP command is Windows' built-in command-line documentation system, available in Command Prompt (CMD) on all Windows versions from Windows XP through Windows 11. It provides two modes: a general listing of all available commands with brief descriptions, and detailed help for specific commands including syntax, parameters, examples, and related commands.

HELP runs natively in CMD but is not available in PowerShell (which uses Get-Help instead). The command requires no special permissions and works in both standard and administrator Command Prompt sessions. It accesses the same documentation displayed by the /? switch that most commands support.

Syntax

HELP [command]

Parameters

Parameter	Description	Required
`command`	The name of the command to get help for (e.g., DIR, COPY, XCOPY)	No
(none)	When run without parameters, displays a list of all available commands	No

Parameters and Options

HELP (No Parameters)

Running HELP without any arguments displays a complete list of all built-in Windows commands with one-line descriptions. This overview mode helps you discover available commands when you're not sure which tool to use for a specific task. The output is alphabetically sorted and includes commands from file management, networking, system administration, and process control categories.

Example output includes commands like ATTRIB (file attributes), CHKDSK (disk checking), IPCONFIG (network configuration), and TASKLIST (process listing), each with a brief description of its purpose.

HELP [command-name]

Specifying a command name after HELP displays detailed documentation for that specific command, including complete syntax with all parameters, descriptions of each option, usage examples, and notes about command behavior. This detailed mode is equivalent to running command-name /? but provides a consistent interface across all commands.

For example, HELP DIR shows all DIR command switches like /A (attributes), /S (subdirectories), /P (pause), and /O (sort order), along with examples of common usage patterns.

Examples

Example 1: List All Available Commands

Scenario: You need to see what commands are available in Windows CMD.

HELP

Expected Output:

For more information on a specific command, type HELP command-name
ASSOC          Displays or modifies file extension associations.
ATTRIB         Displays or changes file attributes.
CD             Displays the name of or changes the current directory.
CHKDSK         Checks a disk and displays a status report.
CLS            Clears the screen.
COPY           Copies one or more files to another location.
...

Explanation: This displays an alphabetical list of all built-in commands with brief descriptions. Use this when exploring available tools or when you can't remember a command's exact name.

Example 2: Get Detailed Help for a Specific Command

Scenario: You need to learn the syntax and options for the DIR command.

HELP DIR

Expected Output:

DIR [drive:][path][filename] [/A[[:]attributes]] [/B] [/C] [/D] [/L] [/N]
  [/O[[:]sortorder]] [/P] [/Q] [/R] [/S] [/T[[:]timefield]] [/W] [/X] [/4]

  [drive:][path][filename]
              Specifies drive, directory, and/or files to list.

  /A          Displays files with specified attributes.
  /B          Uses bare format (no heading information or summary).
  ...

Explanation: Displays comprehensive documentation for DIR including all parameters, their descriptions, and usage examples. This is faster than searching online documentation.

Example 3: Learn About Network Commands

Scenario: You need to troubleshoot network connectivity and want to see networking command options.

HELP IPCONFIG

Expected Output:

IPCONFIG [/? | /all | /renew [adapter] | /release [adapter] | /flushdns | ...]

This command displays all current TCP/IP network configuration values...

Explanation: Shows detailed IPCONFIG syntax including switches for viewing configuration (/all), renewing DHCP leases (/renew), and flushing DNS cache (/flushdns).

Example 4: Get Help for File Management Commands

Scenario: You need to copy files but can't remember the exact COPY command syntax.

HELP COPY

Expected Output:

COPY [/D] [/V] [/N] [/Y | /-Y] [/Z] [/L] [/A | /B] source [/A | /B]
     [+ source [/A | /B] [+ ...]] [destination [/A | /B]]

  source       Specifies the file or files to be copied.
  /A           Indicates an ASCII text file.
  /B           Indicates a binary file.
  ...

Explanation: Displays COPY command documentation including source/destination syntax, verification options (/V), and overwrite behavior (/Y).

Example 5: Learn About System Administration Commands

Scenario: You need to manage Windows services and want to learn the SC command.

HELP SC

Expected Output:

DESCRIPTION:
        SC is a command line program used for communicating with the
        Service Control Manager and services.
USAGE:
        sc <server> [command] [service name] <option1> <option2>...

Explanation: Shows SC (Service Control) command syntax for querying, starting, stopping, and configuring Windows services.

Example 6: Discover Process Management Commands

Scenario: You need to find and terminate a process but don't know the command.

HELP TASKLIST

Expected Output:

TASKLIST [/S system [/U username [/P [password]]]]
         [/M [module] | /SVC | /V] [/FI filter] [/FO format] [/NH]

DESCRIPTION:
    This tool displays a list of currently running processes...

Explanation: Displays TASKLIST documentation for viewing running processes, including filters (/FI), output formats (/FO), and service information (/SVC).

Example 7: Learn Batch Scripting Commands

Scenario: You're writing a batch script and need to understand the IF command syntax.

HELP IF

Expected Output:

Performs conditional processing in batch programs.

IF [NOT] ERRORLEVEL number command
IF [NOT] string1==string2 command
IF [NOT] EXIST filename command
...

Explanation: Shows IF command syntax for conditional logic in batch files, including error level checking, string comparison, and file existence tests.

Example 8: Get Help for Disk Management Commands

Scenario: You need to check disk integrity and want to learn CHKDSK options.

HELP CHKDSK

Expected Output:

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]]

  volume          Specifies the drive letter (followed by a colon)...
  /F              Fixes errors on the disk.
  /R              Locates bad sectors and recovers readable information.
  ...

Explanation: Displays CHKDSK documentation including repair options (/F), bad sector recovery (/R), and volume dismounting (/X).

Example 9: Understanding Command Redirection

Scenario: You need to learn about command output redirection and piping.

HELP MORE

Expected Output:

Displays output one screen at a time.

MORE [/E [/C] [/P] [/S] [/Tn] [+n]] < [drive:][path]filename
command-name | MORE [/E [/C] [/P] [/S] [/Tn] [+n]]
...

Explanation: Shows MORE command for paginating output, useful when piping long command results like DIR /S | MORE.

Example 10: Learning About File Attributes

Scenario: You need to modify file attributes and want to understand ATTRIB syntax.

HELP ATTRIB

Expected Output:

ATTRIB [+R | -R] [+A | -A] [+S | -S] [+H | -H] [drive:][path][filename] [/S [/D]]

  +   Sets an attribute.
  -   Clears an attribute.
  R   Read-only file attribute.
  A   Archive file attribute.
  ...

Explanation: Displays ATTRIB documentation for setting and clearing file attributes (read-only, archive, system, hidden) with recursive options.

Common Use Cases

1. Quick Command Reference During System Administration

System administrators use HELP to quickly check command syntax while troubleshooting servers or configuring systems, eliminating the need to switch to a browser or reference manual. For example, HELP NETSH provides instant access to network shell configuration options.

2. Learning Commands for Batch Script Development

Developers writing batch scripts use HELP to verify command parameters and syntax, ensuring scripts use correct options and avoiding trial-and-error testing. Commands like HELP FOR and HELP IF are essential for scripting logic.

3. Discovering Available Commands for Specific Tasks

IT professionals use HELP without parameters to browse available commands when they know what they want to accomplish but don't know which command to use. The categorized list helps identify the right tool quickly.

4. Verifying Command Options Before Execution

Before running potentially destructive commands like FORMAT or DISKPART, administrators use HELP to verify syntax and understand all available safety options, reducing the risk of data loss or system damage.

5. Training New IT Staff on Command-Line Tools

IT trainers and mentors use HELP to teach new team members about Windows command-line tools, demonstrating how to access documentation and encouraging self-service learning rather than constant supervision.

6. Troubleshooting Network Connectivity Issues

Network administrators use HELP IPCONFIG, HELP PING, and HELP TRACERT to quickly reference diagnostic command options when troubleshooting connectivity problems, DNS issues, or routing failures.

7. Understanding File System Commands for Data Recovery

Data recovery specialists use HELP CHKDSK, HELP DISKPART, and HELP RECOVER to understand disk repair and file recovery options when working with corrupted drives or deleted files.

8. Automating System Maintenance Tasks

IT automation engineers use HELP SCHTASKS, HELP AT, and HELP SC to learn task scheduling and service management syntax when creating automated maintenance scripts for enterprise environments.

9. Configuring Security and Permissions

Security administrators use HELP ICACLS, HELP TAKEOWN, and HELP CACLS to understand file permission management syntax when securing sensitive files or troubleshooting access denied errors.

10. Managing Processes and Services

System administrators use HELP TASKLIST, HELP TASKKILL, and HELP SC to learn process and service management commands when troubleshooting hung applications or configuring Windows services.

11. Creating Documentation for Standard Operating Procedures

Technical writers use HELP to extract accurate command syntax and parameters when creating IT documentation, ensuring SOPs contain correct command examples and complete parameter lists.

12. Remote System Management and Support

Remote support technicians use HELP to quickly reference commands when connected to remote systems via RDP or SSH, especially when working with unfamiliar Windows versions or configurations.

Tips and Best Practices

1. Use HELP to Discover Command Alternatives

When you know what you want to accomplish but not which command to use, run HELP and scan the list for relevant commands. Many tasks have multiple command options (e.g., DEL vs. ERASE, MD vs. MKDIR).

2. Combine HELP with /? for Maximum Information

Some commands provide more detailed help with the /? switch than through HELP. Try both HELP command and command /? to get comprehensive documentation, especially for complex commands like WMIC or NETSH.

3. Pipe HELP Output to MORE for Long Documentation

For commands with extensive documentation, use HELP command | MORE to paginate the output and read it one screen at a time, making it easier to digest complex syntax.

4. Save HELP Output to Files for Reference

Create quick reference files by redirecting HELP output: HELP DIR > dir-help.txt. This is useful for offline reference or creating custom command cheat sheets for your team.

5. Use HELP Before Searching Online

Before searching Google or Stack Overflow, try HELP command first. The built-in documentation is authoritative, version-specific, and often faster than web searches, especially for basic syntax questions.

6. Learn Command Categories from HELP Output

The HELP command list groups related commands together (file management, networking, system info). Understanding these categories helps you find the right tool faster and improves your mental model of Windows command organization.

7. Check HELP for Windows Version Differences

Command syntax and available parameters can vary between Windows versions. Always use HELP on the target system to ensure compatibility, especially when writing scripts for deployment across multiple Windows versions.

8. Use HELP to Verify Deprecated Commands

Some older commands (like APPEND, GRAPHICS) are deprecated or removed in newer Windows versions. HELP shows only currently available commands, helping you avoid using obsolete tools in new scripts.

9. Combine HELP with WHERE to Find Command Locations

Use WHERE command-name after HELP command to find the executable location. This helps distinguish between built-in CMD commands and external executables, useful for troubleshooting PATH issues.

10. Create Custom Help Scripts for Frequently Used Commands

Write batch scripts that display HELP for your most-used commands: @HELP DIR & HELP COPY & HELP XCOPY. This creates a personalized quick reference for your common workflows.

11. Use HELP in Training Environments

When training new IT staff, encourage them to use HELP instead of immediately asking questions. This builds self-sufficiency and helps them develop command-line research skills.

12. Remember HELP Doesn't Cover PowerShell Cmdlets

HELP only documents CMD commands. For PowerShell cmdlets, use Get-Help instead. Understanding this distinction prevents confusion when working in different shell environments.

Troubleshooting Common Issues

Issue 1: "HELP is not recognized as an internal or external command"

Problem: The HELP command doesn't work in PowerShell or other terminals.

Cause: HELP is a CMD-specific command and not available in PowerShell, which uses Get-Help instead.

Solution: Use Command Prompt (CMD) instead of PowerShell, or use Get-Help in PowerShell for equivalent functionality. To open CMD, press Win+R, type cmd, and press Enter.

Prevention: Remember that CMD and PowerShell have different help systems. Use HELP in CMD and Get-Help in PowerShell.

Issue 2: "No help available for command"

Problem: Running HELP command-name returns "This command is not supported by the help utility."

Cause: The command is either an external executable (not built into CMD), doesn't exist, or is a PowerShell cmdlet.

Solution: Try command-name /? instead, which works for most external commands. For PowerShell cmdlets, use Get-Help command-name. Use WHERE command-name to verify the command exists.

Prevention: Use HELP without parameters first to see the list of supported commands. External tools and PowerShell cmdlets require different help methods.

Issue 3: Help Output is Truncated or Scrolls Too Fast

Problem: Long help output scrolls off the screen before you can read it.

Cause: Commands with extensive documentation exceed the visible console buffer, and the output isn't paginated by default.

Solution: Use HELP command | MORE to paginate output, or redirect to a file: HELP command > help.txt. Alternatively, increase your console buffer size in CMD properties.

Prevention: Always use | MORE for commands you expect to have long documentation, or configure your CMD window with a larger buffer size (right-click title bar → Properties → Layout).

Issue 4: Help Shows Different Syntax Than Online Documentation

Problem: HELP output shows different parameters or syntax than what you find in online tutorials or documentation.

Cause: Command syntax varies between Windows versions. Online documentation may be for a different Windows version than your system.

Solution: Always trust your local HELP output over online sources, as it reflects your actual Windows version. Note your Windows version (VER command) when searching online documentation.

Prevention: Use HELP as your primary reference for syntax, and verify Windows version compatibility when following online tutorials.

Issue 5: Cannot Copy Text from HELP Output

Problem: You can't select and copy command syntax from the HELP output.

Cause: Console selection mode isn't enabled, or you're using an older CMD version with limited selection features.

Solution: Enable QuickEdit mode (right-click CMD title bar → Properties → Options → QuickEdit Mode). Alternatively, redirect output to a file: HELP command > help.txt, then open the file in Notepad.

Prevention: Enable QuickEdit mode permanently in CMD properties, or use Windows Terminal which has better text selection and copy features.

Issue 6: HELP Command Doesn't Show Recently Installed Tools

Problem: A newly installed command-line tool doesn't appear in HELP output.

Cause: HELP only shows built-in CMD commands, not third-party tools or system utilities installed separately.

Solution: Use command-name /? or command-name --help for third-party tools. Check the tool's documentation or website for help information.

Prevention: Understand that HELP is limited to CMD built-in commands. External tools require their own help systems (usually /?, --help, or -h).

Frequently Asked Questions

What is the difference between HELP and /?

HELP is a CMD command that displays documentation for built-in commands, while /? is a parameter that most commands (both built-in and external) accept to display their own help. HELP DIR and DIR /? show similar information, but /? works for more commands including external executables.

Does HELP work in PowerShell?

No, HELP is a CMD-specific command and doesn't work in PowerShell. PowerShell uses Get-Help instead. If you type HELP in PowerShell, it actually runs Get-Help (HELP is an alias for Get-Help in PowerShell), which has different syntax and output format.

Can I get help for third-party commands with HELP?

No, HELP only displays documentation for built-in Windows CMD commands. For third-party tools, use command-name /?, command-name --help, or command-name -h, depending on the tool's convention. Check the tool's documentation for its specific help syntax.

How do I save HELP output to a file?

Use output redirection: HELP command > filename.txt. For example, HELP DIR > dir-help.txt saves DIR help to a text file. To append to an existing file, use >> instead of >. This is useful for creating command reference documents.

Why does HELP show different commands on different Windows versions?

Windows versions include different sets of built-in commands. Newer versions add commands (like WHERE in Windows 7+) and remove deprecated ones (like APPEND). HELP reflects only the commands available on your specific Windows version, ensuring accurate documentation.

Can I search HELP output for specific keywords?

Yes, pipe HELP output to FIND or FINDSTR: HELP | FINDSTR "file" shows all commands with "file" in their description. For detailed help, use HELP command | FINDSTR "keyword" to search within a specific command's documentation.

How do I get help for batch file commands like IF and FOR?

Use HELP IF, HELP FOR, HELP GOTO, etc. Batch scripting commands are documented through HELP just like other CMD commands. These help pages include syntax for conditional logic, loops, and flow control.

Is there a way to get more detailed examples than HELP provides?

HELP provides basic examples, but for more detailed scenarios, use command /? (which sometimes has more examples), check Microsoft's official documentation online, or use Windows Terminal's built-in documentation features. Some commands like ROBOCOPY have extensive documentation files in C:\Windows\System32.

Why does HELP not work for some commands like WMIC or NETSH?

Complex commands like WMIC and NETSH have their own hierarchical help systems. Use WMIC /? or NETSH /? to access their help, which often includes sub-commands with their own help pages (e.g., NETSH interface ip /?). HELP may show basic info, but the command's own help is more comprehensive.

Can I customize or extend the HELP command?

No, HELP is a built-in CMD function and cannot be customized or extended. However, you can create batch scripts that display custom help information or combine multiple HELP outputs. For example, create myhelp.bat that runs HELP DIR & HELP COPY & HELP MOVE for your frequently used commands.

How do I get help when working on remote systems?

When connected to a remote system via RDP or SSH, run HELP in the remote CMD session to get documentation specific to that system's Windows version. For remote PowerShell sessions, use Invoke-Command -ComputerName server -ScriptBlock { Get-Help command }.

Does HELP work in Windows Terminal?

Yes, HELP works in Windows Terminal when you're using a CMD profile. Windows Terminal is just a modern terminal emulator; the underlying shell (CMD, PowerShell, etc.) determines which help system is available. Use HELP in CMD profiles and Get-Help in PowerShell profiles.

Related Commands

Get-Help (PowerShell)

PowerShell's equivalent to CMD's HELP command, providing documentation for PowerShell cmdlets, functions, and scripts. Use Get-Help in PowerShell instead of HELP for PowerShell-specific commands. Supports detailed help (-Detailed), examples (-Examples), and online documentation (-Online).

When to use: Use Get-Help in PowerShell sessions for PowerShell cmdlets. Use HELP in CMD for CMD commands. They are not interchangeable.

Command /? (Universal Help Switch)

Most Windows commands support the /? parameter to display help information. This works for both built-in CMD commands and external executables, making it more universal than HELP.

When to use: Use command /? for external tools, third-party utilities, or when HELP doesn't provide information. Use HELP for browsing available commands.

WHERE (Command Locator)

Displays the location of executable files. Use after HELP to find where a command's executable is located, useful for distinguishing built-in commands from external programs.

When to use: Use WHERE command-name after HELP to verify a command exists and find its location. Helpful for troubleshooting PATH issues.

MORE (Output Paginator)

Displays output one screen at a time. Pipe HELP output to MORE for easier reading of long documentation: HELP command | MORE.

When to use: Use HELP command | MORE when help output is longer than your screen. Essential for commands with extensive documentation like ROBOCOPY or NETSH.

FIND / FINDSTR (Text Search)

Searches for text in command output. Use with HELP to find commands by keyword: HELP | FINDSTR "network" shows all commands with "network" in their description.

When to use: Use HELP | FINDSTR "keyword" to search for commands related to a specific topic when you don't know the exact command name.

CLS (Clear Screen)

Clears the Command Prompt screen. Use after viewing HELP output to clean up your terminal before continuing work.

When to use: Run CLS after reading HELP documentation to clear the screen and start fresh with a clean workspace.

Quick Reference Card

Command	Purpose	Example
`HELP`	List all available commands	Browse command categories
`HELP DIR`	Get help for DIR command	Learn DIR syntax and options
`HELP command \| MORE`	Paginate long help output	Read extensive documentation
`HELP \| FINDSTR "file"`	Search for file-related commands	Find relevant commands by keyword
`HELP command > file.txt`	Save help to text file	Create offline reference
`command /?`	Alternative help syntax	Works for external commands too
`HELP COPY`	Learn file copy syntax	Quick reference for COPY parameters
`HELP NETSH`	Network shell help	Network configuration commands
`HELP FOR`	Batch scripting loops	Learn loop syntax for scripts
`HELP IF`	Conditional logic help	Batch file conditional statements

Try It Yourself

Ready to master Windows command documentation? Practice using the HELP command in our interactive Windows Command Simulator. Experiment with different commands, explore help output, and build your command-line expertise in a safe, risk-free environment.

Launch the Windows Command Simulator to start practicing HELP commands now.

Want to explore more Windows commands? Check out our Complete Windows Commands Reference for detailed guides on over 200 CMD commands, including networking, file management, system administration, and process control tools.

Related Guides:

DIR Command Guide - Learn directory listing with detailed help examples
ECHO Command Guide - Master text output and batch scripting basics
CD Command Guide - Navigate directories efficiently with complete syntax

Summary

The HELP command is an essential tool for Windows command-line users, providing instant access to accurate, version-specific documentation for all built-in CMD commands. Whether you're listing all available commands with HELP or getting detailed syntax for a specific command with HELP command-name, this built-in reference system eliminates the need for external documentation and accelerates your workflow.

We covered HELP command syntax, including both general listing mode and specific command help mode, along with ten practical examples demonstrating how to discover commands, learn syntax, and troubleshoot issues. The command works in all Windows versions and requires no special permissions, making it accessible for both standard users and administrators.

Key use cases include quick command reference during system administration, learning commands for batch script development, training new IT staff, and verifying syntax before executing potentially destructive commands. The HELP system is particularly valuable for IT professionals working on remote systems or in environments without internet access.

Remember to use HELP in CMD (not PowerShell, which uses Get-Help), combine it with MORE for long output, and try both HELP command and command /? for comprehensive documentation. For external tools and third-party utilities, use the /? or --help switches instead.

Practice using HELP regularly to build your command-line knowledge and reduce dependence on online searches. The more familiar you become with the built-in documentation system, the faster and more confident you'll be when working in Windows Command Prompt. Start with HELP to explore available commands, then dive deeper into specific commands as you encounter new tasks and challenges.