To get or set the execution policy in PowerShell or CMD, use the Get-ExecutionPolicy and Set-ExecutionPolicy cmdlets. Here’s how to use them:

✅ View Current Execution Policy

In PowerShell, run:

Get-ExecutionPolicy

You may get Restricted in the response.

🔐 Common Execution Policy Levels

• Restricted – No scripts allowed.
• AllSigned – Only signed scripts allowed.
• RemoteSigned – Local scripts run, but remote scripts must be signed.
• Unrestricted – All scripts run; you get a warning for remote scripts.
• Bypass – No restrictions or warnings.

🛠️ Temporarily Bypass Execution Policy (One-liner)

If you just want to run a script without changing the system policy, use:

powershell.exe -ExecutionPolicy Bypass -File "C:\Path\To\Script.ps1"

🔄 Permanently Change Execution Policy

• I personally suggest this command to use, because i found this LocalMachine remote signed is pretty safe

Requires Administrator privileges:

To set to RemoteSigned, Bypass, or AllSigned globally:

Set-ExecutionPolicy RemoteSigned -Scope LocalMachine

Other scopes include:

• Process – Temporary, lasts for current PowerShell session.
• CurrentUser – Applies to the current user.
• LocalMachine – Applies to all users on the computer (admin required).

Example:

Set-ExecutionPolicy Bypass -Scope Process

🧱 Check in CMD Prompt

From Command Prompt (CMD), to get the policy:

powershell -Command "Get-ExecutionPolicy"

To run a script with bypass:

powershell -ExecutionPolicy Bypass -File "C:\Path\To\Script.ps1"

⚠️ Security Note:

Using Bypass disables all execution policy protections — only use it when necessary, and never leave it set system-wide unless you understand the risks.

Would you like help writing a script that sets and restores the policy safely?