Set of commands to install PowerShell modules from local file or from the web. Inspired by NuGet
Switch branches/tags
Nothing to show
Pull request Compare This branch is 391 commits behind psget:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

PsGet Utils

Set of commands to install PowerShell modules from contral directory, local file or from the web.


  1. Install modules from central directory
  2. Install modules from web or local file
  3. Install modules to user profile or for all users ( elevated access required )
  4. Install multifile modules from ZIP
  5. Import module after install
  6. Alter you profle to load module every time that PowerShell starts
  7. Execute Install.ps1 if found in module folder


To install something from central directory just type:

install-module PsUrl

This command will query central directory to find required information about PsUrl module and install it if found.

Another example is how to install PsUrl module located at , to install it just execute

install-module -ModuleUrl

or zipped modules like posh-git. Zip package is located at , to install it just execute


Also this command will execute Install.ps1 that is install scrtipt for posh-git. (pls note posh-git is in the directory so install-module posh-git is enough).

And of course it supports local files. Both ZIP and PSM1

install-module -ModulePath \TestModules\

install-module -ModulePath \TestModules\HelloWorld.psm1

Command also can make given module to start with your profile

install-module PsUrl -Startup   


While this tool streamlines installation of the modules, it should be installed manually for now.

  1. Copy PsGet.psm1 to your modules folder (e.g. $Env:PsGet\PsGet\ )
  2. Execute Import-Module PsGet (or add this command to your profile)
  3. Enjoy!

Experimental Installation

(new-object Net.WebClient).DownloadString("") | iex

Or long version:

(new-object Net.WebClient).DownloadString("") | invoke-expression


Q: Error "File xxx cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details." A: By default, PowerShell restricts execution of all scripts. This is all about security. To "fix" this run PowerShell as Administrator and call

Set-ExecutionPolicy RemoteSigned

For mode details run get-help about_signing or git-help [about_Execution_Policies](visit


Roadmap is not sorted in any order. This is just list what is think should be done.

  1. Support for other than PSM1 types of modules
  2. Support for modules with more than one file with NuGet packages
  3. Support for NuGet repositories
  4. Support for versions of the modules
  5. Git/Hg/Svn sources


  1. Blog about PsGet -
  2. Another module management for PowerShell , nice point is that it supports GIT as source for modules
  3. PowerShell wrapper for NuGet (yes also has name PsGet)
  4. Instruction how pack PowerShell module to NuGet package -


Module based on Install-Module by Joel Bennett