Problems with installing modules from the PowerShell Gallery

Lately, on several Windows Server 2016 servers, I wanted to install a PowerShell module such as VMware PowerCLI.  When trying to install the module  I’ve got the following error:

NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘’ or newer to interact with NuGet-based repositories. The NuGet provider must be available in ‘C:\Program Files\PackageManagement\ProviderAssemblies’ or
‘C:\Users\Administrator\AppData\Local\PackageManagement\ProviderAssemblies’. You can also install the NuGet provider by running ‘Install-PackageProvider -Name NuGet -MinimumVersion -Force’. Do you want PowerShellGet to install
and import the NuGet provider now?
[Y] Yes [N] No [S] Suspend [?] Help (default is “Y”): Y
WARNING: Unable to download from URI ‘′ to ”.
WARNING: Unable to download the list of available providers. Check your internet connection.

PackageManagement\Install-PackageProvider : No match was found for the specified search criteria for the provider
NuGet’. The package provider requires ‘PackageManagement’ and ‘Provider’ tags. Please check if the specified package has the tags.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\\PSModule.psm1:7405 char:21
+ … $null = PackageManagement\Install-PackageProvider -Name $script:N …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Microsoft.Power…PackageProvider:InstallPackageProvider) [Install-Pac
kageProvider], Exception
+ FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackagePro

The required modules come from the PowerShell Gallery. Windows Server 2016 has PowerShell version 5.1 installed and supports TLS 1.0 and TLS 1.1. by default. The PowerShell Gallery has deprecated and discontinuing support for TLS 1.0 and 1.1  as of April 2020! TLS 1.2 is set as default for the PowerShell Gallery.

A temporary fix (that won’t persist) is to add the following line before installing the PowerCLI module:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Another way is to add this line to your PowerShell profile. More information about the PowerShell TLS change can be found here, link.

5 thoughts on “Problems with installing modules from the PowerShell Gallery”

  1. This worked for me on my Windows 2016 VM. What a time saver this is. Please promote this page as I did spend a hours attempting to resolve this simple TLS issue. Just like Microsoft to not give accurate details in their logging on why something failed.

  2. 2 Lines solved my problem:
    Install-PackageProvider -Name PowerShellGet -Force -ErrorAction SilentlyContinue;
    Install-PackageProvider -Name NuGet -Force -ErrorAction SilentlyContinue;

Leave a Comment