要解決Windows 10中PowerShell無法運(yùn)行腳本的問題，需調(diào)整執(zhí)行策略；1. 推薦將執(zhí)行策略設(shè)為RemoteSigned，允許本地腳本運(yùn)行且要求遠(yuǎn)程腳本簽名，通過以管理員身份運(yùn)行Set-ExecutionPolicy RemoteSigned命令實(shí)現(xiàn)；2. 若僅臨時(shí)測(cè)試腳本，可使用PowerShell -ExecutionPolicy Bypass -File .\your-script.ps1命令臨時(shí)繞過限制；3. 為更安全，可僅為當(dāng)前用戶設(shè)置策略，運(yùn)行Set-ExecutionPolicy -Scope CurrentUser RemoteSigned，避免管理員權(quán)限需求；注意不要隨意設(shè)置為Unrestricted，企業(yè)環(huán)境中組策略可能覆蓋設(shè)置，且修改系統(tǒng)策略時(shí)需以管理員身份運(yùn)行。

You're hitting a common issue in Windows 10: PowerShell won't run scripts because of the execution policy . This is a security feature, not a bug — but it can be frustrating when you're trying to run your own scripts.

Here's how to fix it, safely and effectively.

? Understanding the Execution Policy

By default, Windows 10 sets the PowerShell execution policy to Restricted , which means:

• You can run individual commands
• But .ps1 script files cannot run at all

To check your current policy, run this in PowerShell as Administrator :

 Get-ExecutionPolicy

? How to Allow Scripts to Run

You need to change the execution policy. Here are the most practical options:

1. Set Execution Policy to RemoteSigned (Recommended)

This allows:

• Local scripts to run without signing
• Downloaded scripts must be signed by a trusted publisher

Run this command in PowerShell as Administrator :

 Set-ExecutionPolicy RemoteSigned

Then confirm with "Yes" or "Yes to All".

? This is the sweet spot between security and usability for most users.

2. Use Bypass for Temporary Script Testing

If you just want to run a script once without changing system settings:

 PowerShell -ExecutionPolicy Bypass -File .\your-script.ps1

This temporarily bypasses restrictions only for that command — safe and clean.

3. Set Policy for Current User Only (Safer)

Instead of changing the system-wide policy, limit it to your user:

 Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

This avoids needing admin rights every time and keeps things contained.

?? Important Notes

• Never set Unrestricted unless you fully understand the risks — it's not needed in most cases.
• Group Policy (in corporate environments) can override your settings. If changes don't stick, your IT admin may be enforcing policies.
• Always run PowerShell as Administrator when changing system-wide policies (except CurrentUser scope).

? Example: Run Your Script Safely

Let's say you have a script called deploy.ps1 in your Documents folder.

? Option 1 – Change policy permanently (recommended):

 # Run as Admin
Set-ExecutionPolicy RemoteSigned

Then run:

 .\deploy.ps1

? Option 2 – One-time bypass:

 PowerShell -ExecutionPolicy Bypass -File "$env:USERPROFILE\Documents\deploy.ps1"

Basically, you don't need to disable security — just configure it properly. RemoteSigned or CurrentUser policies are safe and solve 95% of script-blocking issues.

以上是Win 10 PowerShell執(zhí)行策略是防止腳本運(yùn)行的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！