One-Liner to ByPass when running via "right click + run w/ powershell"

PowerShell.exe -ExecutionPolicy Bypass -File "C:\bypass\prompt\standard.ps1" 2>&1>$null


Get-ExecutionPolicy ; Get-ExecutionPolicy -List | Format-Table -AutoSize


Default: Restricted for Windows clients or RemoteSigned for Windows servers.

#Cannot set execution policy. Execution policies at the MachinePolicy or UserPolicy scopes must
be set through Group Policy.
Set-Executionpolicy -Scope Process -ExecutionPolicy Default -Force
Set-Executionpolicy -Scope CurrentUser -ExecutionPolicy Default -Force
Set-Executionpolicy -Scope LocalMachine -ExecutionPolicy Default -Force
Set-Executionpolicy -Scope CurrentUser -ExecutionPolicy Restricted -Force
Set-Executionpolicy -Scope CurrentUser -ExecutionPolicy UnRestricted -Force


PowerShell.exe -ExecutionPolicy Bypass -File "C:\tmp\runme.ps1"

ExecutionPloicy is configured at 4+1 levels, with priority from High to Low:

MachinePolicy (Group Policy)
   UserPolicy (Group Policy)
      Process (Configured using powershell -ExecutionPolicy flag for new process only)
  CurrentUser (User settings)
 LocalMachine (Computer settings)
MachinePolicy. Set by a Group Policy for all users of the computer.
UserPolicy. Set by a Group Policy for the current user of the computer.
Process. Affects only the current PowerShell session.
CurrentUser. Affects only the current user.
LocalMachine. Default scope that affects all users of the computer.

When you run PowerShell with ByPass flag, you actually set Process-level ExecutionPolicy that overrides CurrentUser and LocalMachine setings, but can be hardened at UserPolicy or MachinePolicy level managed by local or domain Group Policies.