Imported PowerShell module shows no ExportedCommands

Question

I have a batch of 150-200 Windows 2016 servers that were upgraded to 2019. Following the upgrade about a dozen of them can no longer run commands from an AWS supplied module, while the others can. Upon further investigation we found that importing the module gives no errors, and get-module will list the module name. But the issue is the ExportedCommands property is blank/null. When you attempt to call any of the commands within the module it of course fails.

The issue spans across a few isolated/untrusted domains. Both the "good" and "bad" servers all have the same policies applied to them. In fact many of the servers were probably cloned from one another.

Any suggestions on how to troubleshoot? I've tried to research the issue but most hits suggest a problem with the module itself, in which case it does not work anywhere.

Answer 1

You might try Remove-Module (and use the -Force switch) followed by Import-Module (and use the -Force switch here, too).

If that doesn't fix things, try Test-ModuleManifest to verify that something isn't wrong on those machines where you don't see any exported commands.

Are there any dependencies on .Net versions for the module? Are all machines running the same .Net versions? Powershell versions the same (release and bitness)?