"Scripts Are Disabled On This System" — What To Actually Do

The Error And What It Is Telling You

File C:\scripts\thing.ps1 cannot be loaded because running scripts is disabled on this system.

Windows ships with an execution policy of Restricted, which means no scripts run at all. That is a deliberate default for a clean desktop, and the error is the policy working.

Two things are worth understanding before you change it, because most advice online is a one-liner that fixes the symptom and ignores both.

It is not a security boundary. The execution policy is a safety feature against accidental execution, not a sandbox. Anyone who can run PowerShell can also run powershell -ExecutionPolicy Bypass, which is exactly why every installer does. Microsoft's own documentation says as much. Treat it as a guard rail, not a lock.

The correct fix depends on why it was blocked. A script you wrote is a different problem from a script you downloaded, and they need different answers.

A photorealistic shot of a laptop screen showing a red PowerShell error message in a console window, a hand on the keyboard, home office with a plant, daylight, realistic photography, no legible text.

The Cases, In Order

1. A script you wrote yourself

Set the policy for your own session — nothing persists, nothing changes on the machine:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Or for your user account permanently:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

RemoteSigned allows local scripts to run unsigned, and requires a signature on anything downloaded from the internet. That is the sensible everyday setting, and it is what I would recommend for a workstation.

2. A script you downloaded

This is the case where RemoteSigned still refuses, and where people get stuck — because the file is blocked by something the policy has not told you about.

Files copied from a browser or email carry an alternate data stream called Zone.Identifier marking their origin. RemoteSigned reads that mark and refuses unsigned remote content, regardless of where the file now sits.

Check for it:

Get-Item .\thing.ps1 -Stream Zone.Identifier -ErrorAction SilentlyContinue

If it exists, and you trust the source, remove the mark:

Unblock-File .\thing.ps1

Or for a whole folder:

Get-ChildItem C:\Scripts -Recurse | Unblock-File

This is the actual fix for most "I already set RemoteSigned" cases, and it is the step most guides omit. Note what you are doing: declaring that you trust the file. Which is why the next paragraph matters.

3. Verify before you unblock

Unblocking a file is a statement that you trust it. If you got it from somewhere other than the author, check it first — a signature, or a hash against a known value:

Get-AuthenticodeSignature .\thing.ps1 | Format-List Status, SignerCertificate
Get-FileHash .\thing.ps1 -Algorithm SHA256

Status of Valid with a signer you recognise is meaningful. NotSigned on a file from the internet means you are trusting the delivery channel, which is exactly what the Zone.Identifier was warning you about.

A photorealistic close-up of a PowerShell console showing a hash value and a signature status line, a browser download window behind it, desk with a notebook, realistic photography, no legible text.

What Bypass Actually Does

powershell -ExecutionPolicy Bypass -File thing.ps1 sets the policy for that one process. It does not modify any machine setting, it does not require admin, and it is how almost every legitimate installer invokes PowerShell internally.

It also does not clear the Zone.Identifier mark. A downloaded, unsigned, marked file will still be refused in some contexts even with Bypass — which is why "add -ExecutionPolicy Bypass" sometimes appears not to work and Unblock-File then fixes it immediately.

Useful flags alongside it:

powershell -NoProfile -ExecutionPolicy Bypass -File C:\scripts\thing.ps1

-NoProfile skips the user's profile script, which makes behaviour predictable and slightly faster. Worth having in any scheduled task or launcher.

Should You Set It Machine-Wide?

Set-ExecutionPolicy -Scope LocalMachine -ExecutionPolicy RemoteSigned

You can, as an administrator, and on a managed machine you may have no choice. On a personal workstation, CurrentUser scope achieves the same thing with a smaller blast radius — one account rather than every account on the box.

Do not set Unrestricted or Bypass at LocalMachine scope "so it stops asking". That removes the one guard rail the feature provides and gains you nothing.

A photorealistic shot of a browser download bar with a downloaded PowerShell file visible, a PowerShell window open in front of it, desk lamp light, realistic photography, no legible text.

The Short Version

Local script you wrote: Set-ExecutionPolicy -Scope CurrentUser RemoteSigned.

Downloaded script you have verified: Unblock-File first, then run it.

Untrusted script: do not unblock it. No flag makes an untrusted script safe.

Don't trust the download button. Trust the hash.

If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.


Luke Keam
Spot a bug or want a custom utility built? I'd love to hear from you. Get in touch
Luke Keam | techgeek.biz