This error means PowerShell could not resolve the command you entered. It can refer to a cmdlet, script, function or executable. Check the actual command name and how PowerShell is searching for it.

Check spelling and discovery

Get-Command Get-Process
Get-Command git -ErrorAction SilentlyContinue
Get-Module -ListAvailable

Cmdlet names are case-insensitive: Get-Process, get-process and GET-PROCESS are equivalent. A misspelling such as Get-Proces is different. For a missing module command, confirm that the correct module is installed and compatible with your PowerShell version; Import-Module loads a module. There is no general Add-Module cmdlet.

Run a script using its path

PowerShell does not automatically execute a script from the current directory by its bare name:

.\Report.ps1
& "C:\My Scripts\Report.ps1"

Use the script location guide if you do not know where the file is. For native programs, confirm that the program is installed and either use its full path or the appropriate PATH entry. Open a new terminal after an installer changes PATH.

Read the exact error

A message saying that scripts are disabled or a file is not digitally signed is a different diagnosis. Do not loosen execution policy to fix a misspelled or missing command. Our execution policy guide explains the distinction.

Sources and verification

Command lookup guidance checked against Microsoft documentation. Platform-specific module installation was not performed.

If the error comes from a Linux shell

Inside Ubuntu or Bash, use the Bash command-not-found checklist. A systemctl error also requires checking the Linux service-manager environment; PowerShell execution policy will not fix it.