Enable running Powershell scripts on Windows 10

If PowerShell says a script cannot be loaded because running scripts is disabled, first inspect the active policies:

Get-ExecutionPolicy -List

For a trusted local script, a temporary change for the current PowerShell process is usually enough:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned

This ends when that process closes. If you need a persistent setting for your own account, use -Scope CurrentUser instead. These scopes normally do not require an administrator shell. A policy imposed through Group Policy can take precedence.

RemoteSigned permits local scripts but generally requires downloaded scripts to be signed. After reviewing a trusted downloaded file, Unblock-File .\yourScript.ps1 removes its downloaded-file marker; do not use that as a substitute for checking the script.

The original article recommended unscoped Unrestricted, which changes the machine policy by default. That was broader than this task requires. Execution policy is a safeguard against accidental execution, not a security boundary or a sandbox.

A one-process bypass also exists, but it bypasses that safeguard for the child process and should be reserved for a script you have already reviewed:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\yourScript.ps1

Source: Microsoft’s execution policy documentation (checked 15 October 2026).

Originally published on blog.yavuz.support: https://blog.yavuz.support/enable-running-powershell-scripts-on-windows-10.