Solutions

Solution 1: Set Execution Policy (Recommended)

This is the recommended approach that balances security and functionality.

Step 1: Open PowerShell as Administrator

• Press Win + X and select "Windows PowerShell (Admin)" or "Terminal (Admin)"

Step 2: Set the execution policy

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

When prompted, type Y and press Enter.

Step 3: Unblock the script file

Unblock-File "C:\Program Files (x86)\Phat\phat.ps1"

Step 4: Test the installation

phat --version

Solution 2: Unblock File Only

If your execution policy is already set but the script is still blocked:

Unblock-File "C:\Program Files (x86)\Phat\phat.ps1"

Solution 3: Bypass for Current Session

If you only need to run Phat temporarily:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

This only affects the current PowerShell session and doesn't make permanent changes.

Understanding Execution Policies

Check Current Policy

To see your current execution policy settings:

Get-ExecutionPolicy -List

Why RemoteSigned is Recommended

• Security: Downloaded scripts still require a digital signature
• Functionality: Your own local scripts (like Phat) can run without issues
• Balance: Provides protection against malicious downloaded scripts while allowing legitimate local development

Related Resources

• PowerShell Execution Policies Documentation
• Back to Troubleshooting Index