Windows Apps & tools

PowerShell execution policy explained

Run PowerShell scripts without opening the door to unsigned malware — scopes and signing explained.

10 min read Intermediate Updated 9 Jun 2026

Step-by-step guide

Work through each section in order. Stop when your issue is resolved — you do not need every step for every situation.

Warning

Use an administrator account for these steps, and keep a recent backup before making repair or security changes.

What you will achieve

Run PowerShell scripts without opening the door to unsigned malware — scopes and signing explained.

1) Check current policy by scope

Get-ExecutionPolicy -List

2) Use least-permissive option needed

For most admin/dev usage, set current user to RemoteSigned rather than Bypass:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

3) Run one-off scripts safely

For a single trusted script, prefer temporary bypass in that process only.

Related guides

powershell scripting security