Running scripts is disabled: what to check first
Read the policy without changing it, and involve IT.
Applies to: Windows execution-policy checks. These commands only read settings and do not make a script safe.
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 |
|---|---|---|
| Running scripts is disabled on this system | Execution policy limits which scripts load, and Group Policy can control it. This is not an instruction to bypass it. | Read the policy without changing it, and involve IT. |
| 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.
Confirm the script source
- Do this
- Check the script is authorised and from an approved source. Do not run an unfamiliar download.
- What you should see
- Trust and ownership are established or remain uncertain.
- Then what?
- If this explains what you see, record it and continue only if the next check still applies.
Read the effective policy
- Do this
- If permitted, run Get-ExecutionPolicy. It only reads the setting.
- What you should see
- The effective policy is shown.
- Then what?
- Record the result without changing settings. Stop if work, data or security could be affected.
Read policy by scope
- Do this
- If permitted, run Get-ExecutionPolicy -List and note the output. It only reads.
- What you should see
- The value at each scope is shown.
- Then what?
- Use only the approved action described here. If it does not match your screen, stop and ask IT.
Ask IT
- Do this
- Give IT the script owner and your read-only findings. Do not use Bypass, Unrestricted or change policy under this guide.
- What you should see
- IT can assess an authorised route.
- 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.