You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attemping to install module jmg.files from the PowerShell Gallery repository. It failed to install saying it was NotSigned. Module is not signed but also has no indicators that it should be (that I can tell).
The module does have Microsoft.Graph dependencies which may be related?
Expected behavior
Installs the module
Actual behavior
❯ install-module jmg.filesInstall-PSResource: The signature for 'JMg.Files' is 'NotSigned.Install-PSResource: Package(s) 'jmg.files' could not be installed from repository 'PSGallery'.``
Error details
❯ install-module jmg.filesInstall-PSResource: The signature for 'JMg.Files' is 'NotSigned.Install-PSResource: Package(s) 'jmg.files' could not be installed from repository 'PSGallery'.``
Environment data
❯ gmo Microsoft.PowerShell.PSResourceGet; $PSVersionTable|Format-Table
ModuleType Version PreRelease Name ExportedCommands
-----------------------------------------------
Binary 0.9.0 rc1 Microsoft.PowerShell.PSResourceGet {Find-PSResource,Get-InstalledPSResource,Get-PS…
Name Value
---------
PSVersion 7.3.6
PSEdition Core
GitCommitId 7.3.6
OS Microsoft Windows 10.0.23545
Platform Win32NT
PSCompatibleVersions {1.0,2.0,3.0,4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Thanks Justin Grote (@JustinGrote) this looks like an issue with the Compat module translating a change in behavior of PSResourceGet, we should turn off publisher checks in compat as this doesn't translate well
Activity
SydneyhSmith commentedon Sep 25, 2023
Thanks Justin Grote (@JustinGrote) this looks like an issue with the Compat module translating a change in behavior of PSResourceGet, we should turn off publisher checks in compat as this doesn't translate well
wrbst commentedon Jan 19, 2024
Today I hit the same problem in one Windows 11 VM:
As suggested by SydneyhSmith the workaround is to add "-SkipPublisherCheck" as parameter during Install-Module.