Open JustinGrote opened 9 months ago
Thanks @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
Today I hit the same problem in one Windows 11 VM:
gmo Microsoft.PowerShell.PSResourceGet; $PSVersionTable | Format-Table
ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Binary 1.0.1 Microsoft.PowerShell.PSResourceGet {Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository, Get-PSScriptFileInfo…}
Name Value
---- -----
PSVersion 7.4.1
PSEdition Core
GitCommitId 7.4.1
OS Microsoft Windows 10.0.22631
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
As suggested by SydneyhSmith the workaround is to add "-SkipPublisherCheck" as parameter during Install-Module.
Prerequisites
Steps to reproduce
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
Actual behavior
Error details
Environment data