Script execution is blocked
Documentation: Microsoft Learn
Work the problem
A local policy change has no effect
Fictional case: CurrentUser is RemoteSigned, but MachinePolicy is AllSigned. An unsigned script is blocked.
Reasoning notebook
Record the evidence that supports your answer and the check you would run next. Your notes stay in this browser — nothing is uploaded.
Why it happens
Execution policy is a per-scope setting and the effective value is the first one set in a fixed precedence order that puts machine policy above anything a user chooses. That is why Set-ExecutionPolicy can report success and change nothing. A value delivered by Group Policy occupies the highest scope and cannot be overridden locally at all.
Check this first
What to look for
MachinePolicy takes precedence. Use an approved signed artifact or resolve the policy requirement with its owner.
Working through it
Read the error and effective policy before changing settings. MachinePolicy and UserPolicy take precedence over local scopes. When a downloaded-file marker is the cause under RemoteSigned, review the script before unblocking it.
If the environment requires a trusted signature or enforces application control, use the approved artifact and policy workflow. Changing execution policy cannot resolve every form of script blocking.
Avoiding it next time
Verify the repair: Confirm the effective policy and validate the approved script signature before retrying in the intended context.