Replies: 1 comment 1 reply
-
Seems to work fine? Have you tried to open a new shell?
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Even after install 'PnP.PowerShell' by running the following command
'Get-Module -ListAvailable PnP.PowerShell' doesn't show 'PnP.PowerShell' whereas
'Get-InstalledModule' shows 'PnP.PowerShell'
It appears to be a bug.
Expected Result:
'Get-Module -ListAvailable PnP.PowerShell' show the information about 'PnP.PowerShell'
Based on my research with Copilot, it appears that 'Get-Module -ListAvailable PnP.PowerShell' doesn't show 'PnP.PowerShell' because
🧠 Why Get-Module -ListAvailable Fails
PowerShell expects either:
A .psm1 file (script module), or
A .dll file (binary module), or
A manifest (.psd1) that explicitly defines the root module
If the .psd1 file doesn't correctly point to the actual module entry point (like a .psm1 or .dll), PowerShell won't recognize it as a valid module.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions