This guide covers common issues you might encounter when using Pxp. Each issue has its own detailed documentation page.
- PowerShell Execution Policy Error - "File cannot be loaded. The file is not digitally signed"
- Permission Denied When Installing - Access denied errors during installation
- Download Fails - Issues downloading PHP versions
- Git Bash / MINGW64 Compatibility - "command not found" in bash terminals
- Apache Won't Start After Switching - Apache fails to start after changing PHP versions
- PHP Version Not Found - Version not detected even though it's installed
Symptoms:
pxp : File C:\Program Files (x86)\Pxp\pxp.ps1 cannot be loaded. The file is not digitally signed.
Quick Fix:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Unblock-File "C:\Program Files (x86)\Pxp\pxp.ps1"Symptoms:
$ pxp
bash: pxp: command not foundQuick Fix: Use PowerShell or CMD instead, or add bash alias:
pxp() {
powershell.exe -ExecutionPolicy Bypass -File "C:/Program Files (x86)/Pxp/pxp.ps1" "$@"
}Symptoms: Access denied errors during pxp install
Quick Fix: Run PowerShell as Administrator
If you're still experiencing issues after checking the guides above:
- Check the README.md for usage instructions
- Verify your XAMPP installation is at
C:\xampp - Run
pxp whereamito verify installation paths - Open an issue on GitHub with:
- The exact error message
- Output of
pxp whereami - Output of
Get-ExecutionPolicy -List(if PowerShell issue) - Your Windows version
Run these commands to gather diagnostic information:
# Check Pxp installation
pxp whereami
# Check PHP versions
pxp list
# Check PowerShell execution policy
Get-ExecutionPolicy -List
# Check if running as administrator
([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)