This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Command Prompt | |
|---|---|
| Name | Command Prompt |
| Developer | Microsoft |
| Released | 1987 |
| Programming language | C (programming language) |
| Operating system | MS-DOS, Windows NT, Windows 95 |
| Genre | Command-line interpreter |
| License | Proprietary software |
Command Prompt is a command-line interpreter developed by Microsoft for the MS-DOS and Windows NT family of operating systems. It provides a text-based interface to interact with the Windows NT kernel, execute programs, manipulate files, and automate tasks via scripts. Widely used by system administrators, developers, and power users, it bridges historical MS-DOS utilities with modern Windows 10 and Windows 11 system management.
The lineage traces back to MS-DOS command interpreters provided by Microsoft in the early 1980s alongside platforms like the IBM PC. Evolution continued through releases tied to operating system milestones such as Windows 95, Windows 98, and the advent of the Windows NT family. With the release of Windows NT 3.1 and subsequent Windows NT 4.0, the interpreter was integrated into the Windows NT architecture to support administrative tasks and legacy applications. Over years, Microsoft introduced features paralleling developments in contemporaneous systems from vendors such as Apple Inc. and Sun Microsystems, while ecosystem influences included tools like the Unix shell and utilities from projects such as GNU.
The interpreter exposes features for file system navigation, process control, and configuration management tied to Windows Registry operations and service control using Service Control Manager (Windows). It can invoke external utilities provided by Microsoft Sysinternals, interact with network resources via Internet Protocol Suite components, and call scripting hosts like the Windows Script Host. Features evolved to include support for Unicode in later Windows editions and interoperability with subsystem layers such as the Windows Subsystem for Linux. Integration points include authentication frameworks like Kerberos (protocol) and identity providers used across Active Directory domains.
The interpreter implements a command syntax characterized by executable names, options, and arguments, echoing conventions from MS-DOS and other command-line environments. Built-in commands include file and directory manipulation (e.g., copy, del, dir), process and task utilities (e.g., tasklist equivalents), and network-related commands (e.g., net, ipconfig). Commands interact with system APIs exposed by Win32 API and call services registered with Service Control Manager (Windows). Scripting-aware builtins such as echo, set, and for enable control flow and variable handling within batch contexts.
Batch scripting uses plain-text files typically with .bat or .cmd extensions to automate sequences of commands. Batch constructs provide conditional execution, looping, and rudimentary error handling, enabling system administration tasks across Active Directory, file servers, and deployment scenarios tied to platforms like Microsoft System Center. For complex automation, scripts often interoperate with tools such as PowerShell, VBScript, or third-party interpreters, and call APIs from frameworks like .NET Framework. Historical legacy scripts written for MS-DOS frequently required adaptation for differences in Windows NT path and permission semantics.
Users can customize prompt appearance, environment variables, and startup behavior via configuration items stored in user profiles, Windows Registry keys, and shortcut parameters. The PROMPT variable configures the display format, while PATH and PATHEXT control command resolution and executable recognition. Customizations often integrate with developer toolchains from vendors such as Microsoft Visual Studio, build systems like Make (software), and version control clients tied to Git or Subversion. Advanced users leverage console settings exposed by the Windows Console Host and third-party terminal emulators to adjust fonts, colors, and keyboard mappings.
Execution respects the Windows security model with access control lists managed by NTFS and authentication tokens issued by logon services. Administrative tasks typically require elevated privileges granted through mechanisms like User Account Control and membership in groups such as Administrators (Windows). Scripts and commands can impact system integrity, so practices include signing scripts, applying least-privilege principles, and auditing via components like Event Viewer and Windows Defender features. Threat actors exploit misconfigurations affecting command interpreters; mitigation strategies draw on guidance from organizations like CERT Coordination Center and standards such as CIS Controls.
Contemporary alternatives range from Microsoft-developed shells like PowerShell to third-party terminals and Unix-inspired shells such as Bash (Unix shell). Cross-platform variants include implementations in projects like Cygwin and the Windows Subsystem for Linux that provide the Bash (Unix shell) environment on Windows. Terminal emulators and enhanced shells from vendors like ConEmu, Cmder, and integrated development environments such as Visual Studio Code offer extended feature sets. On other platforms, analogous utilities include Terminal (macOS), shells in Linux distributions, and command interpreters embedded in network devices from manufacturers like Cisco Systems.
Category:Command line interfaces