How to Run a PS1 File in PowerShell (And Why It Sometimes Fails)

Running a .ps1 file — PowerShell's script format — sounds straightforward. Double-click, run, done. In practice, Windows often blocks the attempt entirely, throws a cryptic error, or opens the file in Notepad instead. Here's what's actually happening and how to handle it properly.

What a PS1 File Is

A .ps1 file is a plain text file containing PowerShell commands, saved with the .ps1 extension. PowerShell reads the file line by line and executes each command, just as if you'd typed them manually into the console. Scripts can automate backups, configure system settings, install software, manage files, or do virtually anything PowerShell commands support.

The catch: Windows deliberately restricts PS1 execution by default for security reasons. A double-clicked .ps1 file won't run automatically — it opens in a text editor instead. This is intentional.

The Execution Policy: The First Thing to Understand 🔒

Before a PS1 file will run, PowerShell checks the execution policy — a setting that controls which scripts are allowed to execute. There are four common policy levels:

To check your current policy, open PowerShell and run: