Complete Guide to Running PowerShell Scripts from Batch Files

Problem Background and Common Errors

In Windows environments, many developers and system administrators need to execute PowerShell scripts from batch files. A typical scenario involves users attempting to run PowerShell scripts containing WMI event registration but encountering execution policy-related errors.

Analysis of Original Error Code

The user's initial batch file code was:

@echo off
Powershell.exe set-executionpolicy remotesigned -File C:\Users\SE\Desktop\ps.ps1
pause

This code produces errors because PowerShell interprets set-executionpolicy remotesigned as a command to execute rather than parameters. Since the Set-ExecutionPolicy cmdlet doesn't have a -File parameter, execution fails.

Correct Solution

The correct approach is to use the -ExecutionPolicy parameter:

Powershell.exe -executionpolicy remotesigned -File C:\Users\SE\Desktop\ps.ps1

This method directly sets the execution policy and runs the specified file, avoiding command parsing errors.

Enhanced Execution Method

For a more robust solution, the following code is recommended:

PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& 'C:\Users\SE\Desktop\ps.ps1'"

This approach offers several advantages:

• -NoProfile: Avoids loading user profiles, ensuring consistent script execution environment
• -ExecutionPolicy Bypass: Bypasses execution policy restrictions, suitable for various environment configurations
• -Command: Explicitly specifies command execution mode

Administrator Privilege Execution

When scripts require administrator privileges, use this method:

PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Start-Process PowerShell -ArgumentList '-NoProfile -ExecutionPolicy Bypass -File \""C:\Users\SE\Desktop\ps.ps1\""' -Verb RunAs}"

This approach uses the Start-Process cmdlet with the -Verb RunAs parameter to launch a new PowerShell process and request administrator privileges.

Path Handling Best Practices

To avoid hard-coded path issues, place batch files and PowerShell scripts in the same directory:

@ECHO OFF
SET ThisScriptsDirectory=%~dp0
SET PowerShellScriptPath=%ThisScriptsDirectory%ps.ps1
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '%PowerShellScriptPath%'"

This method uses %~dp0 to get the batch file directory, ensuring path correctness.

Parameter Passing Techniques

To pass parameters to PowerShell scripts, use these methods:

Passing ordered parameters:

PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '%PowerShellScriptPath%' 'Parameter1' 'Parameter2'"

Passing named parameters:

PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '%PowerShellScriptPath%' -Param1Name 'Value1' -Param2Name 'Value2'"

In-Depth Execution Policy Analysis

PowerShell execution policies are security mechanisms that prevent accidental script execution. Common policies include:

• Restricted: Default policy, prevents all scripts from running
• RemoteSigned: Local scripts can run, remote scripts require digital signatures
• Bypass: Doesn't block anything, only shows warnings
• Unrestricted: Allows all scripts to run

Error Handling and Debugging

For better user experience, add pause code at the end of PowerShell scripts:

if ($Host.Name -eq "ConsoleHost") {
    Write-Host "Press any key to continue..."
    $Host.UI.RawUI.FlushInputBuffer()
    $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyUp") > $null
}

This allows users to view script output and error messages, preventing immediate window closure.

Practical Application Scenarios

The techniques discussed in this article apply to:

• Providing simple execution methods for users unfamiliar with PowerShell
• Automated deployment scripts
• System administration task automation
• Development environment configuration scripts

Conclusion

By correctly using PowerShell parameters and batch file techniques, you can create user-friendly script execution solutions. The key is understanding execution policy mechanisms, path handling, and privilege management. Adopting the best practices introduced in this article ensures reliable PowerShell script execution across various environments.