PowerShell errors: find the cause and the fix
Match your error message to one of 15 guides. Each explains what failed, likely causes, diagnostic checks and the next steps to resolve it.
Paste your error message
Not sure which guide fits? Paste the red error text into the error decoder — it names the category and points you at the right guide.
Open the error decoderCommands & modules 3 errors
Command not recognized and module load failures.
PowerShell: command not recognized
Check spelling, command discovery and required modules when PowerShell says a command is not recognized. Trace the cause and verify the fix.
PowerShell: module import failed
Inspect module prerequisites, manifest settings and dependencies when Import-Module cannot load a module. Trace the cause and verify the fix.
PowerShell: module not found
Check module installation, name and PSModulePath when PowerShell cannot find the requested module.
Remoting, network & CIM 3 errors
Remoting transport, web request, and CIM query failures.
PowerShell: CIM query failed
Investigate CIM class names, namespaces, permissions and connectivity when Get-CimInstance fails.
PowerShell: remoting connection failed
Check the remoting transport, target address, authentication and endpoint when a PowerShell remote connection fails. Trace the cause and verify the fix.
PowerShell: web request failed
Separate HTTP status errors from DNS, proxy, TLS and timeout failures when a PowerShell web request fails. Trace the cause and verify the fix.
Data, JSON & parsing 3 errors
JSON parse errors, syntax errors, and null references.
PowerShell: invalid JSON input
Inspect the original response and JSON structure when ConvertFrom-Json cannot parse its input.
PowerShell: null value or missing property
Check lookup results and object properties before accessing a member that may be missing or null.
PowerShell: unexpected token or missing delimiter
Find mismatched quotes, brackets and incomplete expressions when a PowerShell script fails to parse. Trace the cause and verify the fix.
Files & paths 2 errors
IO failures and paths that cannot be found.
PowerShell: file read or write failed
Check file locks, directories, free space and storage connectivity when a PowerShell file operation fails. Trace the cause and verify the fix.
PowerShell: path or item not found
Find incorrect paths, unexpected working directories and wildcard interpretation when PowerShell cannot locate an item. Trace the cause and verify the fix.
Objects & parameters 2 errors
Invalid operations and parameter binding failures.
PowerShell: operation is not valid
Inspect object state, method requirements and collection changes when PowerShell reports an invalid operation. Trace the cause and verify the fix.
PowerShell: cannot bind a parameter
Check argument types, parameter sets and pipeline input when PowerShell cannot bind a parameter.
Security & permissions 2 errors
Execution policy blocks and access denied.
PowerShell: running scripts is disabled
Check execution-policy scopes, script signatures and downloaded-file marks when a PowerShell script is blocked. Trace the cause and verify the fix.
PowerShell: access is denied
Check the calling identity, elevation and resource permissions when a PowerShell operation returns access denied. Trace the cause and verify the fix.
Understand error behavior
Most PowerShell errors don’t stop your script. Learn how $ErrorActionPreference decides what happens next — and how to make errors catchable with -ErrorAction Stop.
Genie guide
Paste the exact error text. Each page names the category, the likely cause, and the first safe check.
Match your error message to one of 15 guides. Each explains what failed, likely causes, diagnostic checks and the next steps to resolve it.
Reading 1 of 8 sections
Error decoder
Paste the red text. The decoder names the kind of error it is and points at the lesson that fixes it. It never runs your code, and decoding happens entirely in your browser — your pasted error is never sent anywhere.