Install-packageprovider -name Nuget -force Site

PackageManagement\Install-PackageProvider : No match was found for the specified search criteria for the provider 'NuGet'. Or worse:

The Windows operating system ships with (the meta-package manager), but it does not ship with all package providers pre-installed. The default installation includes only the provider for MSI and (sometimes) the legacy PowerShellGet v1.0. The NuGet provider—which is required to query repositories like https://www.powershellgallery.com/api/v2 —must be bootstrapped on demand or manually installed. install-packageprovider -name nuget -force

if (-not ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator')) $params.Scope = 'CurrentUser' The NuGet provider—which is required to query repositories

NuGet provider is required to continue PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. But beneath those four parameters lies a critical

The command Install-PackageProvider -Name NuGet -Force is deceptively simple. But beneath those four parameters lies a critical process that every Windows automation engineer, DevOps professional, and system administrator should understand.