VpasModule
PowerShell module for CyberArk APIs

Install VpasModule

Two quick ways to get started. Pick one.

Automatic (PSGallery) Manual (GitHub)

Manual • GitHub ZIP

Useful for offline installs or testing specific commits.

  1. Download the repo as ZIP 
    https://github.com/vmelamed5/VpasModule
    Open GitHub Manual install step 1

  2. Extract the ZIP and locate the VpasModule folder. Manual install step 2

  3. Move the folder into a PowerShell module path 
    $env:PSModulePath -split ';'
    Manual install step 3

  4. Restart PowerShell, then import and verify 
    Import-Module VpasModule -Verbose
    Get-Module -ListAvailable -Name VpasModule
    Manual install step 4

Troubleshooting

If you hit an error, please view some common FAQs below. If none apply and this is an error with the module itself, please open an issue via GitHub or contact me

GitHub Issues Contact Me

FAQs

*Please note: The FAQs below are suggestions and should be carefully reviewed before running any commands. If you are on a corporate or managed machine, always confirm with your organization’s security policies before making changes.

Why can’t I download from PSGallery?
Common culprits:
- No internet or blocked by firewall/proxy
- PSGallery repo missing or untrusted (`Get-PSRepository`)
- TLS too old (force TLS 1.2)
- NuGet provider missing/outdated
- Insufficient permissions for AllUsers install
- Temporary PSGallery outage/throttling
How do I check if PSGallery is registered and trusted?
Get-PSRepository
Unregister-PSRepository -Name PSGallery -ErrorAction SilentlyContinue
Register-PSRepository -Default
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
How to enable TLS 1.2?
PSGallery enforces TLS 1.2+.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
NuGet provider errors—what should I do?
PowerShellGet relies on NuGet to fetch packages.
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
`Install-Module` fails but `Find-Module` works—why?
Often permissions.
Install-Module -Name VpasModule -Scope CurrentUser -Force -AllowClobber -Verbose
Module installed but not found on import
Check your module paths and installed copies.
$env:PSModulePath -split ';'
Get-Module -Name VpasModule -ListAvailable | Select Name,Version,ModuleBase
Files are 'blocked' and import fails
Unblock downloaded files.
$mod = (Get-Module -ListAvailable VpasModule | Sort Version -Descending | Select -First 1).ModuleBase
Get-ChildItem -Path $mod -Recurse | Unblock-File
Could execution policy be blocking it?
Check and temporarily bypass (current process only):
Get-ExecutionPolicy -List
Set-ExecutionPolicy -Scope Process Bypass -Force
Version / architecture compatibility
Some modules target specific editions/bitness.
$PSVersionTable.PSEdition   # Desktop (5.1) vs Core (7+)
[Environment]::Is64BitProcess

Try the matching PowerShell (x64 vs x86) or version.
Multiple copies or conflicting module names
PowerShell loads the first match in PSModulePath. Import a specific path:
Get-Module -Name VpasModule -ListAvailable
Import-Module 'C:\Path\To\Module\VpasModule.psm1' -Force -Verbose
Fixing a corrupted or partial install
Remove and reinstall:
Uninstall-Module -Name VpasModule -AllVersions -Force
Install-Module -Name VpasModule -Scope CurrentUser -Force
Manual install when `Install-Module` fails
Save + import directly:
Save-Module -Name VpasModule -Repository PSGallery -Path "$env:TEMP\PSModules" -Force
Import-Module "$env:TEMP\PSModules\VpasModule\<Version>\VpasModule.psm1" -Force -Verbose
Corporate proxy issues
Check/configure proxy:
netsh winhttp show proxy
$proxy=[System.Net.WebRequest]::DefaultWebProxy
$proxy.Credentials=[System.Net.CredentialCache]::DefaultNetworkCredentials