`Get-Command *` doesn't always retrieve all properties

[iRon7]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

With a PowerShell module installed that contain PowerShell based cmdlets (functions).
E.g. the function Copy-ObjectGraph of the ObjectGraphTools module.
It appears that not all properties load when the commands are retrieved via a wide filter:

Steps to reproduce:

• Open a new PowerShell session and run the following commands:

$CommandName = 'Copy-ObjectGraph'
$Command = Get-Command * | Where-Object Name -eq $CommandName
$Command.ScriptBlock

Expected to return the command's ScriptBlock but returns nothing
Yet, this is works fine:

$Command = Get-Command $CommandName
$Command.ScriptBlock

And now the first command set also appears to work...

Expected behavior

Expected to return the command's ScriptBlock

Actual behavior

Returns nothing

Error details

Environment data

Name                           Value
----                           -----
PSVersion                      7.5.2
PSEdition                      Core
GitCommitId                    7.5.2
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

[mklement0]

Presumably for performance reason, matching commands from not-yet-autoloaded modules via a wildcard expression passed to Get-Command does not trigger autoloading, whereas a literal name match does.

If autoloading isn't triggered, only the properties that can be derived from the module manifest alone are populated.

[iRon7]

@mklement0,

Yes, that is probably the case, also knowing that Import-Module * works around the issue.
Anyways, just wanted to note this pitfall which caused some confusing in our environment.
After a few weeks, I will close this issue myself and ask for a note in the Get-Command documentation if nothing spectacular happens with this issue.

[iRon7]

Closed it the assuming that this won't be fixed.
Besides, the limitation is now documented, see: MicrosoftDocs/PowerShell-Docs#12298

[microsoft-github-policy-service]

📣 Hey @@iRon7, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms