Microsoft released a new version of PowershellGet (2.2.4) in April 2020 that supports TLS 1.2. The issue is that Powershell 5.1 doesn’t support this configuration out of the box and the PowershellGet module (1.0.0.1) didn’t support TLS 1.2 at all.
In April 2020, Microsoft disabled support for TLS 1.0 on the Powershell Gallery and now requires TLS 1.2. That leaves TLS 1.2 as the de facto standard, with TLS 1.3 adoption rising but not as widespread yet. This was largely adopted across the internet by 2020. Starting in 2018, there was a groundswell of (good) advice that TLS 1.0 and 1.1 should be deprecated on websites and in browsers. Transport Layer Security (TLS) is the successor to SSL. By default, Powershell uses TLS 1.0 and that’s been widely deprecated. The root cause is that Powershell is trying to connect to a site and there’s no agreement on the encryption protocol to use. InstallPackageĪ similar issue arises with using the Invoke-WebRequest cmdlet. : String ), Exception + FullyQualifiedErrorId : PackageFailedInstallOrDownload, Microsoft. At C: \ Program Files \ WindowsPowerShell \ Modules \ PowerShellGet \ 1.
PackageManagement\Install-Package : Package ‘PSWindowsUpdate' failed to download. WARNING : Source Location ‘ https : // com / api / v2 / package / PSWindowsUpdate / 2.
0 kommentar(er)
