New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catalog signature in 'PSScriptAnalyzer.cat' does not match the hash generated from the module #681

Closed
megamorf opened this Issue Dec 7, 2016 · 4 comments

Comments

Projects
None yet
5 participants
@megamorf

megamorf commented Dec 7, 2016

Hey guys, I wanted to check out the latest version of PSSA but ran into this issue with Win10 x64 AU.

Find-Module PSScriptAnalyzer  | Install-Module -Verbose
...
VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/PSScriptAnalyzer/1.9.0'.
VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/PSScriptAnalyzer/1.9.0'.
VERBOSE: Completed downloading 'PSScriptAnalyzer'.
VERBOSE: InstallPackageLocal' - name='PSScriptAnalyzer', version='1.9.0',destination='C:\Users\Administrator\AppData\Local\Temp\1433055360'
VERBOSE: Found the catalog file 'PSScriptAnalyzer.cat' in the module 'PSScriptAnalyzer' contents.
VERBOSE: Valid authenticode signature found in the catalog file 'PSScriptAnalyzer.cat' for the module 'PSScriptAnalyzer'.
VERBOSE: Validating the 'PSScriptAnalyzer' module files for catalog signing using the catalog file 'PSScriptAnalyzer.cat'.
PackageManagement\Install-Package : The module 'PSScriptAnalyzer' cannot be installed because the catalog signature in 'PSScriptAnalyzer.cat' does not match the hash generated from the module.
In C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1764 Zeichen:34
+ ...          $null = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
    + FullyQualifiedErrorId : InvalidCatalogSignature,ValidateAndGet-AuthenticodeSignature,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

Adding -SkipPublisherCheck which helped me with updating the Pester version that ships with Win10 also helped in this case.

Here's my PS version information.

PS > $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14393.206
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.206
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@tysonjhayes

This comment has been minimized.

Show comment
Hide comment
@tysonjhayes

tysonjhayes Dec 7, 2016

I'm seeing the same thing on my machine. Same PSVersionTable as above.

tysonjhayes commented Dec 7, 2016

I'm seeing the same thing on my machine. Same PSVersionTable as above.

@bmanikm

This comment has been minimized.

Show comment
Hide comment
@bmanikm

bmanikm Dec 7, 2016

It looks like the latest version of NuGet provider is not installed.

Please try again after installing the latest version of NuGet provider.

Install-PackageProvider Nuget –force
exit

More details can be found at https://github.com/PowerShell/PowerShellGet#get-the-latest-version-from-powershell-gallery .

bmanikm commented Dec 7, 2016

It looks like the latest version of NuGet provider is not installed.

Please try again after installing the latest version of NuGet provider.

Install-PackageProvider Nuget –force
exit

More details can be found at https://github.com/PowerShell/PowerShellGet#get-the-latest-version-from-powershell-gallery .

@kapilmb

This comment has been minimized.

Show comment
Hide comment
@kapilmb

kapilmb Dec 14, 2016

Member

Closing this issue - updated the readme to reflect the instructions.

Member

kapilmb commented Dec 14, 2016

Closing this issue - updated the readme to reflect the instructions.

@kapilmb kapilmb closed this Dec 14, 2016

@bergmeister

This comment has been minimized.

Show comment
Hide comment
@bergmeister

bergmeister Jun 2, 2018

Collaborator

For anyone reading this again, the new 1.17.0 release suffers from the same issue but cannot be resolved by updating the nuget provider. Using the -SkipPublisherCheck switch on Install-Module is currently the only known workaround.

Collaborator

bergmeister commented Jun 2, 2018

For anyone reading this again, the new 1.17.0 release suffers from the same issue but cannot be resolved by updating the nuget provider. Using the -SkipPublisherCheck switch on Install-Module is currently the only known workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment