Install or Update-Module no longer works with 6.10

[iyoumans]

Updating from 6.0.4 to 6.10 breaks Install-Module and Update-Module for me as it cannot connect to PowerShell Gallery.

Steps to reproduce

Tried to run Update-Module in version 6.10.

Expected behavior

Expect it to connect to PowerShell Gallery and update the module

Actual behavior

See errors below. Reverting to version 6.0.4 fixes the issue.

# Update-Module AzureRM.Netcore
Get-PSGalleryApiAvailability : PowerShell Gallery is currently unavailable.  Please try again later.
At C:\program files\powershell\6\Modules\PowerShellGet\PSModule.psm1:12941 char:13
+             Get-PSGalleryApiAvailability -Repository (Get-SourceName  ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (:) [Get-PSGalleryApiAvailability], InvalidOperationException
+ FullyQualifiedErrorId : PowerShellGalleryUnavailable,Get-PSGalleryApiAvailability

WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2/'.
PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'AzureRM.Netcore'. Try Get-PSRepository to see all available registered module repositories.
At C:\program files\powershell\6\Modules\PowerShellGet\PSModule.psm1:12955 char:20
+ ...           $sid = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

Environment data

$PSVersionTable

Name Value

---

PSVersion 6.1.0
PSEdition Core
GitCommitId 6.1.0
OS Microsoft Windows 10.0.14393
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

[mklement0]

PowerShell Gallery is currently unavailable suggests a temporary, server-side issue, so the gallery may simply have been down while you tried.

I just tried, and didn't see the problem.

[iyoumans]

I just retried this: I installed 6.1.0, got the error. I uninstalled it, installed 6.0.4, worked fine. Then I re-installed 6.1.0 and got the problem. So it's repeatable (for me anyway).

[mklement0]

I should have read both error/warning messages :)

The only obvious difference between your setup and mine is the specific Windows 10 version (mine is 10.0.17134).

A few more things to try (just guesses - I'll leave it to someone more knowledgeable in this area to take over from here):

• I found this re Unable to resolve package source 'https://www.powershellgallery.com/api/v2/': https://vanbrenk.blogspot.com/2017/09/install-module-unable-to-resolve.html

• If you open https://www.powershellgallery.com/api/v2/ in a browser, does it work? Does
  Invoke-WebRequest https://www.powershellgallery.com/api/v2/ work? Does Get-PSRepository return what you'd expect?

[edyoung]

What do you see if you run Get-PSRepository? Does Unregister-PSRepository Psgallery ; Register-PSRepository -Default make any difference?

[iyoumans]

The Get looks good. Unregister/Register didn't work either.

PS C:\Users\iyoumans> Get-PSRepository

Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery                 Untrusted            https://www.powershellgallery.com/api/v2

Tried to install Azure module and got this error:

PS C:\Users\iyoumans> Install-Module -Name AzureRM
WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2'.
PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'AzureRM'. Try Get-PSRepository to see all available registered module repositories.
At C:\program files\powershell\6\Modules\PowerShellGet\PSModule.psm1:9491 char:21
+ ...          $null = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

[RichardSiddaway]

I've successfully run install-module azurerm on Windows 10 build 17134 with PowerShell v6.1. As build 14393 is 3 updates back could you consider updating your Windows machine/

[thezim]

@iyoumans You also might look at your TLS setting. Your OS might have some of them disabled by default. Not sure if the default protocol under 6.1 has changed since 6.0.x /cc @markekraus. .Net Core version did change between these versions which PowerShell Core is build against.

You can try each of these so see if all protocols are working.

Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls
Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls1
Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls12

[iyoumans]

See my results below:

PS C:\Users\iyoumans> Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls
Invoke-WebRequest : The requested name is valid, but no data of the requested type was found
At line:1 char:1
+ Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslP ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: GET, Re...rShell/6.1.0
}:HttpRequestMessage) [Invoke-WebRequest], HttpRequestException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
PS C:\Users\iyoumans> Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls1
Invoke-WebRequest : Cannot bind parameter 'SslProtocol'. Cannot convert value "Tls1" to type "Microsoft.PowerShell.Commands.WebSslProtocol". Error: "The identifier name Tls1 cannot be processed because it is either too similar or identical to the following enumerator names: Tls11, Tls12. Use a more specific identifier name."
At line:1 char:78
+ ... quest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls1
+                                                                      ~~~~
+ CategoryInfo          : InvalidArgument: (:) [Invoke-WebRequest], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

PS C:\Users\iyoumans> Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls12
Invoke-WebRequest : The requested name is valid, but no data of the requested type was found
At line:1 char:1
+ Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslP ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: GET, Re...rShell/6.1.0
}:HttpRequestMessage) [Invoke-WebRequest], HttpRequestException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

There must be some machine or enterprise configuration that is messing me up, because it is affecting my co-workers as well. Thanks for your help.

[mklement0]

@iyoumans:

It may be a DNS issue; possibly relevant information in this SO answer

To narrow the problem down, see if you can get a normal response by using the IP address in the URL (40.87.85.101 is what I get for ping www.powershellgallery.com):

Invoke-WebRequest -Uri https://40.87.85.101/api/v2 -SslProtocol Tls -SkipCertificateCheck

[iyoumans]

Here's with the IP. Keep in mind that on my same machine, Windows PowerShell functions just fine, so I don't see how it could be a DNS issue?

PS C:\Users\iyoumans> Invoke-WebRequest -Uri https://40.87.85.101/api/v2 -SslProtocol Tls -SkipCertificateCheck
Invoke-WebRequest : No connection could be made because the target machine actively refused it
At line:1 char:1
+ Invoke-WebRequest -Uri https://40.87.85.101/api/v2 -SslProtocol Tls - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: GET, Re...rShell/6.1.0
}:HttpRequestMessage) [Invoke-WebRequest], HttpRequestException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

[mklement0]

I'm out of my depth here, but my guess is that your / your organization's firewall configuration / DNS configuration / proxy-server configuration may be the problem - all of which are not directly related to PowerShell.

[iyoumans]

Thanks for your suggestions anyway - it's a place to start.

[megamorf]

I'm affected by this as well.

Setup

PS /home/megamorf> $PSVersionTable                                                                          

Name                           Value
----                           -----
PSVersion                      6.1.0
PSEdition                      Core
GitCommitId                    6.1.0
OS                             Linux 4.18.11-93.current #1 SMP PREEMPT Tue Oct 2 00:24:40 UTC 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Installed as snap:

PS /home/megamorf> snap list powershell
Name        Version  Rev  Tracking  Publisher              Notes
powershell  6.1.0    11   stable    microsoft-powershell✓  classic

Troubleshooting

The Gallery is not available and cannot be registered:

PS /home/megamorf> Get-PSRepository
WARNING: Unable to find module repositories.
PS /home/megamorf> Register-PSRepository -Default -Verbose
VERBOSE: Performing the operation "Register Module Repository." on target "Module Repository 'PSGallery' () in provider 'PowerShellGet'.".
PS /home/megamorf> Get-PSRepository
WARNING: Unable to find module repositories.

I tried the PowerShellGet version that ships with PS as well as the latest stable release from Github:

PS /home/megamorf> Get-Module PowerShellGet -ListAvailable


    Directory: /home/megamorf/.local/share/powershell/Modules


ModuleType Version    Name                                PSEdition ExportedCommands
---------- -------    ----                                --------- ----------------
Script     2.0.1      PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-Module, Find-RoleCapability...}


    Directory: /snap/powershell/11/opt/powershell/Modules


ModuleType Version    Name                                PSEdition ExportedCommands
---------- -------    ----                                --------- ----------------
Script     1.6.7      PowerShellGet                       Desk      {Find-Command, Find-DSCResource, Find-Module, Find-RoleCapability...}

Apparently something is wrong with the certificate store/trust. Querying the v2 endpoint of the Gallery by IP works:

PS /home/megamorf> Invoke-WebRequest -Uri https://40.87.85.101/api/v2 -SslProtocol Tls12 -SkipCertificateCheck

StatusCode        : 200                                                                                                                                                  StatusDescription : OK                                                                                                                                                   
Content           : <?xml version="1.0" encoding="utf-8"?><service xml:base="https://40.87.85.101/api/v2" xmlns="http://www.w3.org/2007/app" 
                    xmlns:atom="http://www.w3.org/2005/Atom"><workspace><atom:title type="text">Def...
RawContent        : HTTP/1.1 200 OK
                    Cache-Control: no-cache
                    Pragma: no-cache
                    Server: Microsoft-IIS/10.0
                    X-CorrelationId: 80007c2b-0007-e000-b63f-84710c7967bb
                    DataServiceVersion: 3.0
                    Content-Security-Policy: frame-ancesto...
Headers           : {[Cache-Control, System.String[]], [Pragma, System.String[]], [Server, System.String[]], [X-CorrelationId, System.String[]]...}
Images            : {}
InputFields       : {}
Links             : {}
RawContentLength  : 325
RelationLink      : {}

But with TLS1.2 it does not work:

PS /home/megamorf> Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslProtocol Tls12
Invoke-WebRequest : The remote certificate is invalid according to the validation procedure.
At line:1 char:1
+ Invoke-WebRequest -Uri https://www.powershellgallery.com/api/v2 -SslP ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: GET, Re...rShell/6.1.0
}:HttpRequestMessage) [Invoke-WebRequest], HttpRequestException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

I assume the ca-certificates provided by the snap environment are not up to date/missing certificates to complete the ca chain of trust.