Which Windows shell should a beginner learn: PowerShell or CMD?

PowerShell vs CMD, explained for beginners: what each Windows shell is, how to tell which one you are in, why pasted commands fail, and which one to learn first.

The short answer

Learn PowerShell. It ships with Windows, so there is nothing to install. It understands the everyday names that CMD users know, such as dir, cd, copy and del, and it adds its own, more capable commands on top. Microsoft itself recommends PowerShell over the older Windows commands for automating Windows.

Then know that CMD exists. Older guides and some install pages are written for it, and pasting one shell’s command into the other is an easy way to get stuck on day one. Below: what each shell is, why there are two kinds of PowerShell, how to tell which one you are in, and a pretend terminal to try the commands safely.

The older shell: Command Prompt (CMD)

A shell is the program that reads your command and gets the computer to carry it out. Microsoft’s command reference says Windows has two of them: the Command shell and PowerShell. The Command shell is better known as CMD or Command Prompt, and its program file is cmd.exe. Microsoft describes it as the first shell built into Windows for automating routine jobs, using batch files: small scripts whose names end in .bat.

CMD is still part of Windows, and it still does the basics well: listing folders, copying files, running programs. What it cannot do is run PowerShell’s own commands. It also has its own way of writing options, with a forward slash. For example, del /p notes.txt asks for a yes or no before deleting each file.

The newer shell, in two editions

Microsoft says PowerShell can run Windows commands too, plus its own commands, called cmdlets. Cmdlets have long, readable names such as Get-ChildItem, Copy-Item and Remove-Item: a verb, a dash, then the thing it works on. For everyday jobs PowerShell also answers to short nicknames, called aliases, so dir, cd, copy and del work much as they do in CMD.

Here is the part many comparison pages skip. Microsoft makes two products with almost the same name, and they are not the same thing:

• Windows PowerShell 5.1 ships inside Windows. It is the latest version of Windows PowerShell. Microsoft is no longer adding new features to it, and its support follows your version of Windows. Its program is powershell.exe, and it runs only on Windows.
• PowerShell 7, called plain "PowerShell" in Microsoft’s own naming, is a separate, open-source download built on newer versions of .NET. It runs on Windows, macOS and Linux, its program is called pwsh, and it installs side by side with Windows PowerShell, so you can have both.

So "PowerShell is cross-platform" is true of PowerShell 7 (and version 6 before it), not of the copy built into Windows. Even in PowerShell 7, some nicknames exist only on Windows: on a Mac or Linux, ls runs the system’s own ls rather than PowerShell’s. For a beginner on Windows, the built-in Windows PowerShell is plenty. The commands DayOneCode teaches work in both editions, with one difference to know: in Windows PowerShell 5.1, > saves text as UTF-16, which some tools (Git reading a .gitignore, for one) cannot read, while PowerShell 7 saves UTF-8. You can add PowerShell 7 later if you want it.

The window is not the shell

A third name adds to the muddle: Windows Terminal. Microsoft describes it as a modern host application for command-line shells such as Command Prompt, PowerShell and bash. It is the window, with tabs, panes, colours and themes. The shell is the program running inside each tab or pane.

DayOneCode says that using a terminal is like talking to the waiter instead of pointing at the menu. In that picture, CMD and PowerShell are two waiters who speak slightly different dialects, and Windows Terminal is the dining room they work in. It can hold many tables, but it never takes an order itself. One tab can run Windows PowerShell while the next runs Command Prompt, so "I opened Terminal" does not tell you which shell you are talking to. If the whole idea of a terminal is new, start with What is a terminal?.

Same jobs in both shells

For everyday file work the two dialects are close. Microsoft says the nicknames are there so that people used to CMD, or to Unix shells like the ones on Mac and Linux, can keep using names they already know.

The nicknames are only skin-deep. del in PowerShell is really Remove-Item, so CMD’s slash options such as /p do not work with it. PowerShell’s options start with a dash instead. The most useful one for a beginner is -WhatIf: it shows what a command would do, and then does nothing at all.

Get-Alias is the quickest way to learn the real names. Ask it about a nickname such as dir or cp and it answers with the cmdlet behind it, such as dir -> Get-ChildItem.

Which shell am I in?

Two quick checks answer it. The first tells PowerShell from CMD; the second tells the two editions of PowerShell apart.

1. Look at the prompt, the text just before the blinking line. PowerShell starts it with PS, as in PS C:\Users\you>. CMD shows only the folder, as in C:\Users\you>.
2. In PowerShell, run $PSVersionTable. It answers with a small table. A PSVersion that starts with 5.1 and a PSEdition of Desktop mean Windows PowerShell, the one built into Windows. A PSVersion that starts with 7 and a PSEdition of Core mean PowerShell 7. If you are in CMD by mistake, it simply says the command is not recognised.

PS C:\Users\you> $PSVersionTable.PSEdition
Desktop

The practice terminal on this page always shows PS, because it pretends to be Windows PowerShell, the shell DayOneCode teaches. It does not know $PSVersionTable, so try that one on your own computer.

Why a pasted command fails

Some install pages for coding tools give a separate line for each shell, and pasting the wrong one is the classic first-day error. The install page for Claude Code, an AI coding tool, is a good example: it gives a PowerShell line that starts with irm, a different CMD line that joins its steps with &&, and the two error messages you see if you mix them up. Red text is a clue, not a disaster:

• The token '&&' is not a valid statement separator means a CMD line landed in Windows PowerShell 5.1. The && sign, which runs the next step only if the last one worked, arrived in PowerShell 7, so 5.1 rejects it. Open Command Prompt and paste the line there, where it was written to run.
• 'irm' is not recognized as an internal or external command means a PowerShell line landed in CMD. CMD cannot run PowerShell commands, so open PowerShell and paste it again.
• The same "not recognized" message appears if you try ls or pwd in CMD. Those are PowerShell (and Mac and Linux) names, not CMD ones; in CMD, dir lists a folder.

When you write your own two-step line in Windows PowerShell 5.1, Microsoft documents the long way round for &&: a semicolon, then a check of $?, which holds True when the last command worked.

git add .; if ($?) { git commit -m "First save" }

Which one should a beginner learn?

PowerShell, for four reasons:

1. It is already there. Windows PowerShell ships with Windows, so there is nothing to download and no account to make.
2. It covers CMD’s everyday jobs. The nicknames mean dir, cd, copy and del still work, and Microsoft says it runs Windows commands as well as its own.
3. It goes further. Cmdlets, -WhatIf and Get-Alias exist only in PowerShell, and Microsoft recommends it for automating Windows.
4. AI coding agents can use it. Claude Code’s docs say that on Windows without Git for Windows installed, it uses PowerShell to run its commands. Read What is an AI coding agent? before you set one up.

Keep CMD in your back pocket. When a guide says "open Command Prompt", or a line full of && fails in Windows PowerShell 5.1, open CMD for that one job and come back. You do not need its slash options until a guide asks for them.

That is the path DayOneCode follows, with no account and no install. Meet the terminal starts you in a practice PowerShell, and Dialects: PowerShell, CMD, Mac matches the names across all three. Then race the names in Command Racer, keep the PowerShell cheat sheet beside your real terminal, and read PowerShell for beginners next.

Try it on DayOneCode

• Dialects: PowerShell, CMD, Mac

  Lesson 19 of the free course: ls or dir, cp or copy, and how to ask PowerShell what a nickname really runs.

• Meet the terminal

  Lesson 5: your first dir and cd in a practice PowerShell that cannot touch your real files.

• Delete carefully

  Lesson 17: look with dir, then delete with rm, on a pretend disk where a slip costs nothing.

• PowerShell cheat sheet

  Every terminal command the course teaches, on one page, with what it does and an example.

More from the blog

• What is a terminal? The plain answer, and your first three commands

  A terminal is the window where you give your computer commands in words. Learn terminal vs shell vs command line, how to open one, and try three safe commands.

• What is a file path? Every file’s home address, explained

  A file path is the address of a file on your computer. See Windows and Mac paths side by side, absolute vs relative paths, how to copy a path, and try it safely.

• What is an AI coding agent? What it does, and how to stay the boss

  An AI coding agent reads your project, edits files and runs commands. See how it differs from a chatbot, how to stay safe, and who is old enough to use one.