Instead, Install-Module recognized that the module was unsigned ( Is this module signed by Microsoft: 'False'), but it still happily installed it without prompting. If you still want to install or update, use -SkipPublisherCheck parameter.īut, i was a bit confused, because I had just updated Pester on my dev machine to 4.0.2 and I didn't encounter this error. Ensure that the version '4.0.2' of the module 'Pester' has the catalog file 'Pester.cat' and signed with the same publisher 'CN=Microsoft Root Certificate Authority 2010, O=Microsoft Corporation, L=Redmond, S=Washington, C=US' as the previously-installed module '4.0.2' with version '3.4.0' under the directory 'C:\Program Files\WindowsPowerShell\Modules\Pester\3.4.0'. PackageManagement\Install-Package : The version '4.0.2' of the module 'Pester' being installed is not catalog signed. PS C:> Install-Module Pester -Force -AllowClobber If you still want to install this unsigned module, use the SkipPublisherCheck parameter. It says that the version of Pester that we're trying to install (4.0.2) in not digitally signed by its author or publisher. While creating a new VM in our office, I tried to install a new version of Pester, but got this somewhat familiar error. Thanks to Mani Bavandla and Matt Graeber for help with this article. This article is based on PowerShellGet 1.1.2.0 on Windows PowerShell 3.953. ![]() In this article, we'll talk about SkipPublisherCheck and signing modules for PowerShell Gallery. But, its effect is actually more persistent and involves some security risk. The SkipPublisherCheck parameter of the Install-Module cmdlet in PowerShellGet technically affects only the current installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |