The term is not recognized
Do not install random modules or run as administrator by default.
Applies to: Windows PowerShell and PowerShell 7.
Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

What does the message mean?
Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.
| What you see | What it may indicate | What to check |
|---|---|---|
| The term ... is not recognized | The session cannot resolve that command. A typo, a missing module or a different shell may be the reason. | Do not install random modules or run as administrator by default. |
| No message at all | Problems can happen without any message. A blank screen or a missing control is still useful evidence. | Record the visible behaviour, the time and who is affected. Do not guess a code. |

Step-by-step checks
Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.
Check the spelling
- Do this
- Compare the exact command with the approved documentation.
- What you should see
- The name matches or has a typo.
- Then what?
- If this explains what you see, record it and continue only if the next check still applies.
Check the shell
- Do this
- Note Windows PowerShell versus PowerShell 7, and where it worked before.
- What you should see
- You know whether the same environment is used.
- Then what?
- Record the result without changing settings. Stop if work, data or security could be affected.
Check documented dependencies
- Do this
- Read the prerequisites without installing anything.
- What you should see
- The needed module is identified or unclear.
- Then what?
- Use only the approved action described here. If it does not match your screen, stop and ask IT.
Ask the script owner
- Do this
- Give the exact message and host details and ask for the approved install route.
- What you should see
- No untrusted package or elevation is used.
- Then what?
- If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.
When to stop and contact IT or the owner
- Work could be lost, or you cannot tell which version is current.
- The problem repeats, or a managed setting blocks you.
- A step would change production data, shared connections, permissions or security.
What to put in your support request
The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.
Microsoft reference
Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.
Related guides
Was this guide helpful? Leave feedback
Tell us what worked, what was unclear, or what is missing. Feedback is private and goes to The Workflow Lab for review. It is not shown publicly and is not an IT support request.
The Workflow Lab is independent of Microsoft and is not your employer’s service desk.