Windows
Installation on Windows (Powershell)
1. Prerequisites
Windows 10/11, 64-bit (Requires Administrator rights for system-wide installs and changes to execution policy)
PowerShell 7+ (install/update via GitHub releases)
2. Install Node.js (v22+) & npm
To install using the official installer:
Download the Windows x64 MSI for Node.js v22.x.x (LTS) https://nodejs.org/en/download/
Right-click → Run as Administrator.
Accept defaults on each screen (ensures
node
&npm
are added to your PATH).
After installing, you can verify the version by running the following command in your powershell:
node --version # should be v22.x.x or higher
npm --version
3. (Optional) nvm-for-Windows
If you need multiple Node versions side by side:
Download nvm-setup.zip from https://github.com/coreybutler/nvm-windows/releases
Unzip & run
nvm-setup.exe
as Administrator.Open a new PowerShell session, then:
nvm install 22.24.0 nvm use 22.24.0 node --version # now v22.24.0
4. Handling PowerShell Execution Policy & Blocked Remote Files
Issue: scripts cannot be loaded because running scripts is disabled on this system
Allow local & signed scripts only:
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
Issue: Powershell flagging
.ps1
or.msi
as “blocked",
Unblock remote files:
Get-ChildItem .\path\to\downloads\* -Recurse | Unblock-File
5. Install the P0 CLI
npm install -g @p0security/cli
If you see permissions errors, run powershell as an administrator and run the command again.
Alternatively, to use a per-user install, run the following command:
npm install --location=global @p0security/cli
You can verify P0 installation in your system by running the following command:
p0 --version
p0 help
6. AWS CLI & Session Manager Plugin (for p0 aws
& p0 ssh
)
p0 aws
& p0 ssh
)AWS CLI v2
To install AWS CLI v2:
Download the MSI: https://awscli.amazonaws.com/AWSCLIV2.msi
Run installer as administrator.
You can verify the installation by running the following command:
```powershell
aws --version # e.g. aws-cli/2.x.x Python/3.x Windows/10 exe/AMD64
```
Session Manager Plugin
Run the MSI.
You can verify the installation by running the following command:
```powershell
session-manager-plugin --version
```
7. Handling Proxy & Corporate Firewall Issues
Issue:
npm install
times out, orp0 login
can’t reach your org.
Set npm proxy:
npm config set proxy http://proxy.company.com:8080 npm config set https-proxy http://proxy.company.com:8080
Set Environment vars:
[Environment]::SetEnvironmentVariable('HTTP_PROXY','http://proxy.company.com:8080','User') [Environment]::SetEnvironmentVariable('HTTPS_PROXY','http://proxy.company.com:8080','User')
8. Troubleshooting & Tips
p0: command not found
- Restart PowerShell (to pick up new PATH).- Check %USERPROFILE%\AppData\Roaming\npm
.
Error: EACCES permissions denied
- Run PowerShell as Administrator.- Try --location=global
for npm.
Set-ExecutionPolicy
still blocked on corporate PC
- Check with IT: some shops lock policy via Group Policy (GPO).
session-manager-plugin
not recognized
- Ensure AWS CLI folder is on PATH.- Reopen PowerShell.
p0 login
never opens browser
- Set $env:AZURE_AUTH_METHOD = 'browser'
for certain orgs that disable embedded webviews.
You’re all set! Next up: Configuration → p0 login <YOUR_ORG_ID>
and start requesting access.
Last updated