Trying to install program using Powershell and getting this error

Anonymous
2018-04-05T14:25:20+00:00

PS C:\WINDOWS\system32> Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force

WARNING: MSG:UnableToDownload «https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409» «»

WARNING: Unable to download the list of available providers. Check your internet connection.

WARNING: Unable to download from URI 'https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409' to ''.

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 line:1 char:1

  • Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
  • 
    

    + CategoryInfo          : InvalidArgument: (Microsoft.Power...PackageProvider:InstallPackageProvider) [Install-PackageProvider], Exception

    + FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackageProvider

Any help would be greatly appreciated

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Anonymous
    2018-04-05T14:27:12+00:00

    What is the Powershell script which you were trying to execute?

    Also are you trying to run this through Powershell (Admin) or not?

    15 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-04-05T14:39:10+00:00

    this is the input

    Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force

    and it is being ran as admin

    25 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-04-06T19:48:44+00:00

    Look into below for a possible solution

    https://stackoverflow.com/questions/16657778/in...

    47 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-05-15T23:07:21+00:00

    Well, I had the same problem. Set my Powershell to TLS 1.2 and it worked for me.

    To test this :

    1. Open Powershell (As Admin)
    2. [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
    3. Try it again!

    Niels Weistra

    1,879 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-06-05T14:25:03+00:00

    Well, I had the same problem. Set my Powershell to TLS 1.2 and it worked for me.

    To test this :

    1. Open Powershell (As Admin)
    2. [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
    3. Try it again!

    Niels Weistra

    The solution mentioned above is a workaround, to solve your issue permanently

    1. Open Powershell and check for supported protocols by using[Net.ServicePointManager]::SecurityProtocol

    1. Run the following 2 cmdlets to set .NET Framework strong cryptography registry keys:
    • Set strong cryptography on 64 bit .Net Framework (version 4 and above)

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

    set strong cryptography on 32 bit .Net Framework (version 4 and above)

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

    1. Restart Powershell and check again for supported protocol by using [Net.ServicePointManager]::SecurityProtocol

    Niels Weistra

    527 people found this answer helpful.
    0 comments No comments