PROVIDER Β· the legacy built-in Windows command scripting
Windows Batch (CMD/BAT)
Windows batch is the MS-DOS-era built-in command scripting that runs on every Windows version for installs, startup entries, and restricted environments, with primitive syntax and encoding pitfalls pushing new work to PowerShell.
Pros
Cons
Product Information
Detailed Notes
Overview
Windows batch scripting descends from MS-DOS: .bat or .cmd files store CMD command sequences run by double-click, built into every Windows version from Windows 7 to Windows Server 2022.
For Programming Languages & Frameworks work the value is running on any Windows machine, since installs, startup entries, environment variables, and scheduled tasks through schtasks take a few lines, restricted environments where PowerShell is unavailable or policy-blocked leave it as the only option, and legacy systems plus industrial equipment maintenance depend on it.
Recognise the limits, because syntax is primitive without functions, error handling, or data structures so complex logic becomes unmaintainable goto spaghetti, encoding issues across GBK, UTF-8, and chcp cause garbled Chinese text, and weak string handling makes modern alternatives like PowerShell advisable almost everywhere.
Core Strengths
- Built into every Windows version with no runtime to install
- Suits simple automation such as installs, startup entries, and environment variables
- Still runs in restricted environments where PowerShell is blocked
- The only practical scripting for legacy systems and industrial equipment
Product Ecosystem
Commands and flow
echo, set, if, for, goto, and call with percent variable expansion.
System integration
schtasks for scheduled tasks, reg for the registry, sc for services, and start launching programs.
Encoding
chcp 65001 switches to UTF-8 with files saved as ANSI or UTF-8 without BOM.
Drawbacks
- Primitive syntax without functions, exceptions, or data structures
- Complex logic degrades into unmaintainable goto jumps
- Encoding issues across GBK, UTF-8, and chcp garble Chinese text
- Weak string and numeric handling unfit for modern automation
Use Cases
- Legacy Windows maintenance (β β β β ) - Often the only option
- Simple install and startup scripts (β β β β ) - Built in with no dependencies
- Restricted environment automation (β β β ) - When PowerShell is unavailable
- Modern complex automation (β ) - Use PowerShell instead
Pricing
| Plan | Price | Scope |
|---|---|---|
| Batch and CMD | $0 | Included with Windows at no extra cost |
| Scheduled tasks through schtasks | $0 | Built into the system |
| Migrating to PowerShell | $0 | PowerShell 7 is free and open source |
Zero cost since Windows includes it, where the real cost is maintenance, as debugging complex batch scripts often exceeds rewriting in PowerShell, so new needs should target PowerShell directly.
FAQ
-
Is batch still usable? Yes, every Windows version supports it, though new work should use PowerShell with batch reserved for simple tasks and legacy environments.
-
How is garbled Chinese fixed? Add chcp 65001 as the first line and save as UTF-8 without BOM, or keep files in ANSI encoding for cmd.
-
Can it do functions? Labels with call simulate them fragilely, so anything beyond a few dozen lines belongs in PowerShell or Python.
Code Examples
Directory mirror backup
@echo off
setlocal enabledelayedexpansion
set BACKUP=D:\backup\%DATE:~0,4%-%DATE:~5,2%-%DATE:~8,2%
if not exist "%BACKUP%" mkdir "%BACKUP%"
robocopy "D:\www" "%BACKUP%" /MIR /R:1 /W:1 /NFL /NDL
echo Backup finished: %BACKUP%
endlocal
/MIR mirrors including deletions while /R:1 /W:1 prevents retries from hanging a scheduled task.
Multi-site status check
@echo off
for /f "usebackq tokens=*" %%u in ("sites.txt") do (
curl -s -o nul -w "%%u %%{http_code}
" --max-time 5 "%%u"
)
Windows 10 ships curl, matching Linux habits for many PowerShell-style checks.
Community & Resources
Communities and official channels
- Windows Commands β Microsoft's official command reference
- SS64 Batch Reference β Command and syntax lookup
- Stack Overflow #batch-file β The main batch scripting Q&A pool
Learning resources and tools
- SS64 Syntax β Variables, loops, and delayed expansion
- Task Scheduler β The official way to schedule scripts
- cmd vs PowerShell β When to move to PowerShell