Windows Terminal is a terminal application. PowerShell is a shell and scripting environment that can run inside it. A Terminal profile selects a shell, starting directory, appearance, and related settings. Keeping these roles separate makes errors easier to understand.
Read the window before typing
Open Windows Terminal from a standard user account. The tab title and profile menu identify the active profile. Microsoft documents that Terminal can generate profiles for installed PowerShell and WSL shells in its dynamic-profile guidance. Available profiles depend on installed software and organization policy.
Do not run as administrator for ordinary practice. An elevated terminal can change protected system state and may be blocked on institution-managed devices.
Understand the prompt
A PowerShell prompt commonly shows the current location:
PS C:\Users\Student>
PS identifies PowerShell, the path is the current directory, and > marks
where input begins. Do not copy prompt characters from examples.
Inspect without changing:
Get-Location
Get-ChildItem
PowerShell commands called cmdlets often use a Verb-Noun name:
Get-Process
Get-Content
Copy-Item
The naming pattern helps discovery but does not make every operation safe.
Parameters specify behavior
Parameters begin with a hyphen:
Get-ChildItem -Path . -File
Here, -Path identifies the location and -File limits results to files.
Before using an unfamiliar parameter, inspect help:
Get-Help Get-ChildItem
Get-Help Get-ChildItem -Examples
Get-Help Get-ChildItem -Parameter Path
Microsoft’s current
Get-Help documentation
explains basic, example, parameter, and online help. Local help may be limited
until help files are updated, and updates may require network access or policy
permission.
Practice with a safe folder
Create a PowerShell-Practice folder through File Explorer. Open it in Terminal
or navigate to it:
Set-Location -Path "$HOME\PowerShell-Practice"
Get-Location
Get-ChildItem
Create no system-wide profile changes yet. Record which shell and PowerShell version you actually have:
$PSVersionTable
Windows PowerShell 5.1 and modern PowerShell 7 are related but distinct. Module, command, and behavior availability can differ. Follow the course’s required version. If the location syntax is unfamiliar, review Windows paths, file extensions, and hidden items before practicing; that article explains the file and path concepts this section assumes.
Use completion and history carefully
Tab completion can reduce typing mistakes; command history can recall prior commands. Always reread the complete command before pressing Enter. A recalled command may target the wrong current directory or contain private information.
Never paste a command from a website or AI tool without identifying its command, parameters, paths, permissions, and rollback.
Common mistakes
- Calling Terminal and PowerShell the same program.
- Copying
PS C:\...>as part of a command. - Practicing as administrator.
- Assuming examples target the installed PowerShell edition.
- Running a command because its name sounds harmless.
- Sharing screenshots containing usernames, paths, or tokens.
Do this now
Open a standard Terminal tab, identify its profile, print the current directory,
list the safe practice folder, inspect help for Get-ChildItem, and record the
PowerShell version. Change no administrative setting.
Log what you learned
Record only:
- Result: What did the action produce?
- Evidence: What observation, test, or source supports that result?
- Next action or unresolved question: What should happen next?
Next, use WinGet to inspect and install one explicitly approved developer tool.