The script is fine. Windows just refuses to run it — on purpose. A permission gate wearing the costume of a code failure.
You try to run a setup script — the kind a project ships to get you started. Windows stops it cold with a red wall of text about scripts being disabled. Nothing about your code is wrong. It never even ran.
"Big red error, the word 'disabled,' a link to docs I can't parse. My gut said the script was broken or I'd done something dangerous. It looks exactly like a failure — how was I supposed to know it's a setting?"
"The trap I want to avoid here is treating the red text as a code bug and starting to 'fix' a script that's already correct. This message is a Windows permission gate, not an error in your file. I should name that on sight — and reach for the safe, scoped fix, not a blanket 'allow everything.'"
Windows PowerShell has a safety setting called execution policy. By default it can block scripts (.ps1 files) from running at all — so that a random downloaded script can't quietly execute on your machine. The error reads like your code failed. It didn't. A guard at the door simply refused to let it in.
a safety gateA Windows setting that decides whether .ps1 scripts are allowed to run. Default is restrictive.
looks like a crashRed text, "disabled," a docs link. It reads like a code error — but the script never executed.
two different worldsA logic error is in your code. A permission error is a setting. Telling them apart on sight saves an hour.
Why this is the highest-leverage thing to recognize: a beginner who can't tell a permission gate from a logic bug will burn an hour "debugging" a script that was perfect the whole time. The instant you read "running scripts is disabled" and think policy, not code, the fix is a single setting change — and you've learned to spot a whole category of failures that have nothing to do with what you wrote.
You run .\setup.ps1 and get cannot be loaded because running scripts is disabled on this system. What's actually happening?
.ps1 scripts. It's a permission message, not a logic one. The script is fine; you just need to allow scripts to run (safely and scoped). No debugging required.Get-ExecutionPolicy. You'll likely see Restricted.RemoteSigned setting — not a blanket "allow all.".\setup.ps1 again. It executes — because the gate, not the code, was the problem.Same rule as every module: answer it right, or it isn't done.
If the script never ran, the code isn't the bug. "Running scripts is disabled" is a permission gate — change the setting, scoped to you, and move on.
A copy-paste setter that flips the policy the safe, scoped way (your user only, RemoteSigned — never a blanket "allow everything"), with a one-line explanation of each level so you understand exactly what you just allowed. Plus a permission-vs-logic field guide so you can call the next gate on sight.