The Scriptage field guide

Run a PowerShell recipe

Prepare a Windows automation workspace and inspect the command.

Use the listed PowerShell version

These recipes target PowerShell 7 unless their guide says otherwise. Windows PowerShell 5.1 is a separate older application. Check $PSVersionTable.PSVersion and see Microsoft’s installation guidance.

Inspect and extract the recipe

Extract the ZIP. Read the .ps1 file in a text editor and review its parameters. Use the sample path first. The page describes whether the command produces a report, reads system information, or changes anything.

Run from the project folder

Open PowerShell in the extracted folder. Use the exact command on the recipe, often beginning with pwsh -File or .\. Parameter names such as -Path are part of the script’s own interface and vary by recipe.

If Windows blocks a downloaded script

Check your organization’s rules before changing execution policy. Inspect the file first. Microsoft documents Unblock-File for removing a downloaded-file block on an individually trusted file. This library does not require changing machine-wide execution settings.

Match permissions to the task

Begin in a normal user session. Some system queries depend on Windows services, modules, or permissions. Follow the recipe prerequisites. If a query is unavailable on your edition of Windows, keep that result in mind when interpreting a report.

Put it into practice

Choose one small task from the library, run its example, and change one thing you understand.

Find a beginner script ↗