How to Fix 'Unable to Install NuGet Provider for PowerShell' Error

Start by launching PowerShell with elevated privileges. This is crucial because installing NuGet providers and updating system modules requires administrator access.

Right-click on the Windows Start button and select "Windows PowerShell (Admin)" or "Terminal (Admin)" on Windows 11. If you're using PowerShell 7, search for "PowerShell" in the Start menu, right-click it, and select "Run as administrator".

The most common cause of NuGet provider installation failures is PowerShell using outdated TLS protocols. PowerShell Gallery requires TLS 1.2, but older systems default to TLS 1.0 or 1.1.

Run this command to enable TLS 1.2 for the current session:

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

[Net.ServicePointManager]::SecurityProtocol

You should see "Tls12" in the output. If you see "SystemDefault" or older protocols, the command worked and upgraded your connection security.

This step is particularly important on Windows Server 2016, where TLS 1.2 isn't enabled by default.

Before attempting fixes, identify which versions of PackageManagement and PowerShellGet you're running. Outdated versions are the root cause of most NuGet provider issues.

Check your current module versions:

Get-Module PackageManagement -ListAvailable | Select-Object Name, Version
Get-Module PowerShellGet -ListAvailable | Select-Object Name, Version

Look for multiple versions installed. The problematic combinations are:

• PackageManagement 1.0.0.1 with PowerShellGet 1.0.0.1
• Any version with NuGet provider 2.8.5.208 (bootstrap version)
• Missing or corrupted PackageManagement modules

Also check the NuGet provider status:

Get-PackageProvider -Name NuGet -ErrorAction SilentlyContinue

If this returns an error or shows version 2.8.5.208, you need to update your modules.

The most effective solution is updating PowerShellGet, which automatically installs the latest NuGet provider. This approach is preferred over manually installing the NuGet provider.

Force install the latest PowerShellGet module:

Install-Module PowerShellGet -Force -AllowClobber

When prompted about installing NuGet provider, type Y and press Enter. The -AllowClobber parameter allows overwriting existing commands, which is necessary when updating core modules.

If you encounter trust issues with the PowerShell Gallery, temporarily set it as trusted:

Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
Install-Module PowerShellGet -Force -AllowClobber
Set-PSRepository -Name PSGallery -InstallationPolicy Untrusted

Get-Module PowerShellGet -ListAvailable | Sort-Object Version -Descending | Select-Object -First 1

You should see version 2.x or newer.

If the PowerShellGet update fails, manually update PackageManagement. This method works when network issues or module conflicts prevent the standard update process.

First, try the direct installation approach:

Install-Module PackageManagement -Force -AllowClobber

If this fails, use the manual download method:

1. Open a web browser and navigate to: https://www.powershellgallery.com/packages/PackageManagement
2. Click "Manual Download" tab and download the latest .nupkg file
3. Rename the .nupkg file to .zip and extract it
4. Copy the contents to: C:\Program Files\WindowsPowerShell\Modules\PackageManagement\1.1.0.0

Create the directory structure if it doesn't exist:

$ModulePath = "$env:ProgramFiles\WindowsPowerShell\Modules\PackageManagement\1.1.0.0"
New-Item -Path $ModulePath -ItemType Directory -Force

After manual installation, restart PowerShell as Administrator and verify:

Import-Module PackageManagement -Force
Get-Module PackageManagement

Install-Module PowerShellGet -Force

Multiple versions of PackageManagement and PowerShellGet can cause conflicts. Clean up old versions while preserving the base system modules.

First, identify all installed versions:

Get-Module PackageManagement -ListAvailable | Format-Table Name, Version, ModuleBase
Get-Module PowerShellGet -ListAvailable | Format-Table Name, Version, ModuleBase

Remove problematic versions, but keep version 1.0.0.1 (base system module). Look for versions in these locations:

• C:\Program Files\WindowsPowerShell\Modules
• C:\Users\[Username]\Documents\WindowsPowerShell\Modules

Remove conflicting versions manually:

# Remove user-installed old versions (example paths)
Remove-Item "$env:USERPROFILE\Documents\WindowsPowerShell\Modules\PackageManagement\1.0.0.1" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item "$env:USERPROFILE\Documents\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1" -Recurse -Force -ErrorAction SilentlyContinue

Check your module path for any custom locations:

$env:PSModulePath -split ';'

Get-Module PackageManagement, PowerShellGet -ListAvailable | Sort-Object Name, Version

Now test if the NuGet provider works correctly by attempting to install a common module. This verifies that all components are functioning properly.

Test with a lightweight module first:

Install-Module PSReadLine -Force -AllowClobber

If successful, test with a more complex module like Exchange Online Management:

Install-Module ExchangeOnlineManagement -Force

Check the NuGet provider status:

Get-PackageProvider -Name NuGet

You should see version 2.8.5.201 or newer. The provider should show as "Installed" with no errors.

Get-PackageProvider -ListAvailable

You should see NuGet, PowerShellGet, and other providers listed without errors.

If you need to install modules for the current user only (without admin privileges), configure the NuGet provider for user scope installations.

For non-admin scenarios, use the CurrentUser scope:

Install-PackageProvider -Name NuGet -Force -Scope CurrentUser
Install-Module PowerShellGet -Force -Scope CurrentUser -AllowClobber

Set PowerShell Gallery as trusted for the current user:

Set-PSRepository -Name PSGallery -InstallationPolicy Trusted

Test user-scoped module installation:

Install-Module Az.Accounts -Scope CurrentUser -Force

Get-Module Az.Accounts -ListAvailable | Select-Object ModuleBase

The path should show Documents\WindowsPowerShell\Modules or Documents\PowerShell\Modules for user-scoped installations.

Check the user-specific module path:

$env:PSModulePath -split ';' | Where-Object { $_ -like "*$env:USERNAME*" }

If you're still experiencing connection problems after updating modules, address network-level issues that can prevent NuGet provider downloads.

Test connectivity to PowerShell Gallery:

Test-NetConnection -ComputerName www.powershellgallery.com -Port 443

If behind a corporate firewall or proxy, configure PowerShell to use your proxy settings:

# Set proxy for current session
$proxy = [System.Net.WebRequest]::GetSystemWebProxy()
$proxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials
[System.Net.WebRequest]::DefaultWebProxy = $proxy

For persistent proxy issues, configure WinHTTP proxy settings:

netsh winhttp set proxy proxy-server:port

Test DNS resolution for PowerShell Gallery:

Resolve-DnsName www.powershellgallery.com

If using Windows Server 2016, ensure TLS 1.2 is enabled system-wide via registry:

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value 1 -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value 1 -Type DWord

[Net.ServicePointManager]::SecurityProtocol

You should see Tls12 available in the protocol list.