Powershell Cheatsheet

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Powershell Cheatsheet

PowerShell Cheatsheet summarizes common cmdlets and scripting patterns for inspecting and automating a system. PowerShell pipelines usually carry objects rather than plain text, making property selection and filtering central to the language. Its quoting, variable expansion, and path behavior differ from Bash and Command Prompt, so examples should be interpreted in the correct shell. A cheatsheet works best as a memory aid while you practice a concrete task. Read the command or syntax together with its arguments, placeholders, and surrounding context. Similar-looking options can have very different meanings, and an example written for one platform or version may need adjustment elsewhere. Keep the reference beside a small test case, use read-only examples first when possible, and check the relevant help output before applying an unfamiliar command to valuable files or a running service.

Guide updated October 13, 2026

How to use this tool

1. Identify the operation you want to perform and find the matching section of the reference. Read the whole example before copying any part of it.
2. Start with a read-only cmdlet and inspect the object's properties before composing a larger pipeline.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Try the adapted example on a small test case, compare the result with the explanation, and save the command with a note about the context in which it works.

SEE IT IN PRACTICE

A worked example

Get-ChildItem -LiteralPath .

Objects representing items in the current directory

The objects expose properties such as Name and Length, allowing structured filtering without parsing a formatted listing.

Pipelines carry structured objects

PowerShell often passes objects with properties rather than formatted text between commands. Select and filter those properties before converting output into a display or file format. A table printed in the console can hide details or truncate values even though the underlying object contains them. Inspect object members when a pipeline behaves unexpectedly, and avoid parsing a formatted listing as if it were the original data. This distinction is central to writing reliable inspection and automation commands.

Quoting and literal paths prevent surprises

PowerShell's expansion rules differ from Bash and Command Prompt, and aliases can hide the actual cmdlet or executable involved. Use explicit command names when clarity matters. LiteralPath is useful when a filename contains characters that could otherwise be treated as wildcards. Before a command changes files or system state, inspect the resolved targets and keep the operation narrowly scoped. A read-only pipeline that identifies the intended objects is a useful precursor to any mutation, especially when working across a large collection.

When this tool is useful

• Review common administrative cmdlets
• Understand object-based pipelines
• Prepare a small inspection script

Tips for a better result

• Check the cmdlet help, current directory, object types, and target paths before using a command that modifies files or system state.
• Replace example paths, identifiers, and names deliberately. Copying a reference command unchanged can target a different file, branch, service, or environment from the one you intended.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions