Unexpected Token at 'WARNING: MSG:UnableToDownload...'

[cgrycki]

The following error is encountered when using this module on a system that is isolated from the internet.

Debug: Prefetching windowspowershell resources for psrepository
Debug: Executing: 'C:/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.EXE -noprofile -executionpolicy bypass -command
     @(Get-PSRepository).foreach({
      [ordered]@{
        'name' = $_.Name
        'source_location' = $_.SourceLocation
        'installation_policy' = $_.InstallationPolicy.ToLower()
      } | ConvertTo-Json -Depth 99 -Compress
    })
'
Debug: Storing state
Debug: Pruned old state cache entries in 0.00 seconds
Debug: Stored state in 0.06 seconds
Error: Failed to apply catalog: 751: unexpected token at 'WARNING: MSG:UnableToDownload https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409'

OS: Windows Server 2019
PSVersion: 5.1.17763.1
Get-PackageProvider -Name NuGet returns NuGet 2.8.5.208

[hbuckle]

Hi @cgrycki - please could you post the puppet manifest you are using along with the version of PowerShellGet?

Import-Module PowerShellGet, PackageManagement
Get-Module PowerShellGet, PackageManagement

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     1.2.2      PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package, Get-Pack...
Script     2.0.1      PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Find-RoleCap...

Thanks

[jrdbarnes]

Hi @hbuckle, @cgrycki,

I was seeing a similar issue on a system isolated from the internet. I was importing Microsoft.PackageManagement.NuGetProvider.dll from an internal web server so the packageprovider worked, but got the same error as above. Once I added a checksum to the download and restarted the command prompt i was running in, I no longer got the error above.

Now I have the below error:

Debug: Executing: 'C:/Windows/System32/WindowsPowerShell/v1.0/powershell.EXE -noprofile -executionpolicy bypass -command     @(Get-PSRepository).foreach({
      [ordered]@{
        'name' = $_.Name
        'source_location' = $_.SourceLocation
        'installation_policy' = $_.InstallationPolicy.ToLower()
      } | ConvertTo-Json -Depth 99 -Compress
    })
'
Debug: Storing state
Debug: Pruned old state cache entries in 0.00 seconds
Debug: Stored state in 0.03 seconds
Error: Failed to apply catalog: 751: unexpected token at 'WARNING: Unable to find module repositories.'

Which I think is because the code doesn't expect no repositories at all and errors?

Versions:

PS C:\Windows\system32> Get-Module PowerShellGet, PackageManagement
ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     1.0.0.1    PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package, Get-Pack...
Script     1.0.0.1    PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Find-RoleCap...

PS C:\Windows\system32> Get-PackageProvider -Name NuGet
Name                     Version          DynamicOptions
----                     -------          --------------
NuGet                    2.8.5.208        Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag...

OS:Server 2019
PSVersion: 5.1.14393.2828

Manifest:

class profile::powershellbase {

  file{'C:/Program Files/PackageManagement/ProviderAssemblies/nuget/':
    ensure => 'directory',
  } ->
  file{'C:/Program Files/PackageManagement/ProviderAssemblies/nuget/2.8.5.208/':
    ensure => 'directory',
  } ->
  file{'C:/Program Files/PackageManagement/ProviderAssemblies/nuget/2.8.5.208/Microsoft.PackageManagement.NuGetProvider.dll':
    ensure         => 'file',
    source         => 'https://proget.internal.fqdn/endpoints/Binaries/content/nuget/2.8.5.208/Microsoft.PackageManagement.NuGetProvider.dll',
    checksum       => 'md5',
    checksum_value => '628da2d060916bba4e8623eb3e53cdc8',
  } ->
  psrepository { 'ps-repo':
    ensure              => present,
    source_location     => 'https://proget.internal.fqdn/nuget/PowershellGallery/',
    installation_policy => 'trusted',
    provider            => 'windowspowershell',
  }
}

[amirgr-tr]

Hi,
Recently Microsoft changed their CDN that serves the nuget package provider dll, they disabled security protocols under TLS 1.2 (aka TLS 1.1 and TLS 1.0 no longer work).
And since PowerShell 5.1 doesn't support by default TLS 1.2, pspackageprovider resource fails with the same warning.

I changed my configuration to serve this dll from an internal source instead but the psrepository resource fails with the same warning (this issue). Fixing it and publishing new version would help a lot thanks :)

Details:
PowerShell version 5.1 that comes preinstalled with Windows (2016, 2019) needs to be bootstrapped with PackageManagement Nuget Provider dll file that is downloaded from Microsoft CDN page:
(https://onegetcdn.azureedge.net/providers/providers.masterList.feed.swidtag).
This CDN page ^ redirects to this CDN page:
(https://onegetcdn.azureedge.net/providers/nuget-2.8.5.208.package.swidtag)
which no longer support tls 1.0 and tls 1.1 (only 1.2 and above).
As you can see by testing the URLs here: (https://www.cdn77.com/tls-test).

[wmaniek123]

Hi.
Regarding previous reply.
Yes this requires to switch the registry for powershell to allow tls tls 1.1 1.2: (it will disable sslv3 as well for powershell).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319.

SchUseStrongCrypto

1

Regerding the issue : As well this is required for the nodes without internet access to use package resource for offline installations. Without fixing it I would need to drop of using that module in our implementations.

[amirgr-tr]

@wmaniek123 you are correct regarding the registry.
But since this change affects the entire system and not only PowerShell, I don't want to perform it.

I also don't think this module should make the registry change, instead it could just run this to affect the current session:
[Net.ServicePointManager]::SecurityProtocol += [Net.SecurityProtocolType]::Tls12
before running the Get-PackageProvider Nuget -Bootstrap