Managing Packages Using Windows PowerShell

Windows hasn't had a package manager in the style of the Advanced Packaging Tool (APT) of Linux distributions. Apt-get is a great way of installing packages and other software. We have Chocolatey, of course which has a growing library of software and even allows you to automatically update software. Now PowerShell has an 'official' way of using any system, such as NuGet, Chocolatey, GitHub or PSget. It is definitely useful and likely to mature into an indispensable tool for Windows users. Nicolas explains why

PowerShell gives you a fine control over the management of Windows machines that is easy to achieve. However, until recently the process of installing, updating and uninstalling packages was always described vaguely as “writing some custom PowerShell scripts to obtain the desired result”. Since WMF 5.0, however, a package manager called “PackageManagement” has become available, and which gives us the facilities we’d expect, and allows you to use a wide range of package sources.

Why a package manager?

For those of you who have already used Linux, you will have seen how simple it is to install software on a Linux machine via the “apt-get” or “yum install” or “rpm –ivh” commands. A package manager keeps track of what software is installed on your computer, and allows you to easily install new software or remove software that you previously installed. This feature was not available on Microsoft platforms except using 3rd party tools such as Chocolatey that were not officially supported by Microsoft. Since WMF 5, Microsoft has filled the gap in Windows by integrating a package manager called “PackageManagement“.

Note: For those who have already started using this feature, you probably know it as “OneGet“. Since WMF 5.0 RTM, it was renamed to “PackageManagement“; but Microsoft does not systematically rename all of their components, so you will still encounter this term.

PackageManagement” is a unified package management component that allows you to perform software discovery, installation and inventory for any type of software package that it supports through its extensible provider interface. But it goes beyond that, as there exists a PowerShell module to interact with packages and which will allow you to automate packages management not only locally, but also remotely! This is a real breakthrough in the management of Windows packages.


To facilitate the understanding of this new concept, this article will be based on a diagram available on the TechNet website in order to analyse in detail the architecture of this new feature. “PackageManagement” is a Package Management Aggregator which is divided into four sections:

Figure 1 – PackageManagement Architecture

  • EndUser: As a user or sysadmin, you are in the “EndUser” section: This gives you access to several PowerShell cmdlets that we will use in the next section of this article.
  • PackageManagementCore: This corresponds to the actions that can be performed on your machine. Available actions are: discovery, install / uninstall and inventory.
  • PackageManagementProviders: This section regroups the providers that can interconnect to PackageManagementCore. It can be an officially-supported “Microsoft” provider or a 3rd party provider to expand the possibilities.
  • Package Sources: Also called “Repositories”. This is the place where the software packages are stored. These sources are managed by the providers themselves. Their location can be an online URL, a local folder or a network shared folder.

Basically, a normal user can install a package from a provider.

In practice, what happens?

We will use Windows PowerShell to manage our packages. We will begin by listing the cmdlets of the “PackageManagement” module using the following command:

PS > get-command -module packagemanagement | sort noun,verb

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          Find-Package                                 PackageManagement
Cmdlet          Get-Package                                  PackageManagement
Cmdlet          Install-Package                              PackageManagement
Cmdlet          Save-Package                                 PackageManagement
Cmdlet          Uninstall-Package                            PackageManagement
Cmdlet          Find-PackageProvider                         PackageManagement
Cmdlet          Get-PackageProvider                          PackageManagement
Cmdlet          Import-PackageProvider                       PackageManagement
Cmdlet          Install-PackageProvider                      PackageManagement
Cmdlet          Get-PackageSource                            PackageManagement
Cmdlet          Register-PackageSource                       PackageManagement
Cmdlet          Set-PackageSource                            PackageManagement
Cmdlet          Unregister-PackageSource                     PackageManagement

It is not the number of available cmdlets that is important to analyse in this result, but rather the usefulness of each cmdlet. We can group this result into three categories:

  • Package (yellow)
  • Provider (green)
  • Package source (blue)

The first thing we want is the list of available providers on our machine. Let us relook at the initial diagram, we are in the following section:

Let us use the Get-PackageProvider cmdlet (In my example, I use Windows 10 anniversary update):

Let us dwell a moment on the providers displayed for your machine:

  • Msi: Allows you to manage .MSI files.
  • Msu: Allows you to manage .MSU files (Microsoft Update Files).
  • PowerShellGet: Allows you to manage PowerShell modules stored in an online gallery. The default package repository is
  • Programs: Allows the inventory of available programs via “Add and Remove Programs and Features

After identifying the provider that you want to query, we can use the following command to get the list of available packages in the repositories (source):

Windows immediately searches for a provider named “Nuget”. When this provider is not installed, it offers to add it automatically for you. So you can press “Y” to continue. What is this provider?

  • NuGet: It is a package provider to manage NuGet packages. NuGet is a free and open-source package manager designed for the Microsoft platform.

After installing this provider, the list of packages is displayed.

In this result, we see that there are several versions of the package and they are available from the same source, namely the “PSGallery” repository. To install this package, nothing more simple, just use the “Install-Package” cmdlet:

What did we actually do? Let us take the previous diagram to identify the steps:

  • Step 1 and step 2: Using the “Install-Package” cmdlet to install the PSReadline module.
  • Step 3: Using the provider and making this module available. In our case it is the “PowerShellGet” module.
  • Step 4: Install the package from the “PowerShell Gallery” repository which hosts this package.

The number of packages is constantly increasing. To prove this, we can use PowerShell:

I recommend using the Out-GridView cmdlet to view the list of these packages:

If you analyze the result, you will find that it only contains PowerShell modules. This is normal because we only have a single repository installed. Let’s see all the available registered package sources by using the “Get-PackageSource” cmdlet:

You will soon find this rather too limited, so let’s immediately install a new provider that will allow us to use new repositories. But how to know which providers can be installed? Well it is simple, the “Find-PackageProvider” cmdlet displays them for you:

Currently “Package Management” looks for the providers in the and in Azure blob store. So I install the “Chocolatey” provider, specifying the provider release.

Note: The RequiredVersion parameter is not mandatory, because by default, the latest version will be installed.

For those who want to do the installation manually, the following command will do what you want.

The number of package available for installation is now 5001!

And we can now deploy as much software as we want. I will let you imagine the possibilities of automation that is available to you through this new feature.

I previously installed the “7Zip” package on my machine, and now I validate that the installation was successful:

The cmdlets of the “PackageManagement” module are simple enough to understand, so I do not need to detail all of them. For more details on their use, I recommend the Microsoft documentation:

If you are wondering how to update an installed package on your machine? Well, there is no way to perform this task. You must uninstall your package and reinstall it to get the latest version. It’s very frustrating but I did not find any official solution. You can create a custom function which will uninstall and then reinstall the package. Missing a cmdlet like “Update-Package”. If you have another option, please let me know in the comments section.

Note: You can come up with another provider named “APPX” which will be used with Windows Nano Server to deploy your packages on a “Nano Server” machine:

Several cmdlets are provided with this provider. For more information on using this provider, please refer to this TechNet article:

To go further

As a sysadmin, you would probably want to use a trusted repository so as to deploy packages on your machines. Well, it is possible to create one’s own repository.

Not being an expert with the Visual Studio tool that you will need for this step, I suggest you to begin with this official guide:

You will subsequently record a repository and associate it with your provider. For this, the following command should be used:

For those of you who wish to continue to use the “public” repositories, I suggest that you mark them as “Trusted”. By default, the repositories are marked as “untrusted”, so the following command will trust them and you will have no warning message:

If you no longer want to use a repository, do not worry, you can remove it very simply:


We have seen in this article a new way of managing packages on Windows Clients and Servers machines. This feature, called “PackageManagement“, provides a very adaptable way of administration for sysadmins. This feature allows you to automate the deployment of your applications on your workstations and servers. Users can also use this feature to independently install packages.

From purely a personal point of view, I prefer to use Desired State Configuration (DSC) to deploy packages via the DSC resource named “package”. This allows me to control exactly the versions used on my machines and also their origin. These repositories are certainly controlled but in a production environment, it is difficult to deploy software without being sure of their compliance and integrity. For more information about this, I refer you to the series on PowerShell DSC.

PackageManagement is a breakthrough in the automation process for deploying your packages on Windows platforms because it not only gives you a feature that has existed on Linux for a long time, but also allows you to use a wide range of existing galleries and repositories.