Update-Module fails with ModuleAuthenticodeSignature error for modules with signed PSD1

[bmanikm]

PowerShell/PSScriptAnalyzer#628

update-module PSScriptAnalyzer

PackageManagement\Install-Package : The version '1.8.0' of the module 'PSScriptAnalyzer' being installed is not
catalog signed. Ensure that the version '1.8.0' of the module 'PSScriptAnalyzer' has the catalog file
'PSScriptAnalyzer.cat' and signed with the same publisher 'CN=Microsoft Root Certificate Authority, DC=microsoft,
DC=com' as the previously-installed module '1.8.0' with version '1.7.0' under the directory 'C:\Program
Files\WindowsPowerShell\Modules\PSScriptAnalyzer\1.7.0'. If you still want to install or update, use
-SkipPublisherCheck parameter.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.1.0.0\PSModule.psm1:2080 char:20
+ ...           $sid = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package],
   Exception
    + FullyQualifiedErrorId : ModuleIsNotCatalogSigned,Validate-ModuleAuthenticodeSignature,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

[kilasuit]

@bmanikm - There was a massive thread on this previously with @Jaykul @JamesWTruher in the PSMVP D/L

Work around currently is to run Install-module with the SkipPublisherCheck Parameter not update-module

[bmanikm]

@kilasuit Yes, I am aware of the thread on catalog signing verification feature in the PSMVP D/L.
This is related to the psgallery modules whose previous versions are having the authenticode signed module manifest file, for example, PSScriptAnalyzer.