One bit of confusion I'd like to clear up: The primary version of PowerShell you are running (5.1.15063.786) is not something that can be disabled using the "Windows Feature" UI. You can only activate/de-activate the legacy version of PowerShell (version 2) in control panel.

The issues you have encountered can be frustrating, sorry that is the case for you.

Moving this to Survey to try to gauge the scope of the problem for users generally.

We are somewhat limited by security requirements: what ships with Windows will always be tagged so that nothing can replace it easily unless it is signed by Microsoft. While Pester is part of Windows, it is not owned or developed by Microsoft, so updates delivered via the Gallery cannot be Microsoft signed.

Once the Gallery version is installed on a system, -SkipPublisherCheck is no longer required for future updates. That first experience, however, is bad.

This leaves us with a dilemma: do we stop shipping Pester in with PowerShell in the future, or do we continue to provide the feature set knowing users who update from the Gallery will encounter these issues?

Looking for feedback from as many users as are willing to respond.
Thanks

The issues you have encountered can be frustrating, sorry that is the case for you.

Moving this to Survey to try to gauge the scope of the problem for users generally.

We are somewhat limited by security requirements: what ships with Windows will always be tagged so that nothing can replace it easily unless it is signed by Microsoft. While Pester is part of Windows, it is not owned or developed by Microsoft, so updates delivered via the Gallery cannot be Microsoft signed.

Once the Gallery version is installed on a system, -SkipPublisherCheck is no longer required for future updates. That first experience, however, is bad.

This leaves us with a dilemma: do we stop shipping Pester in with PowerShell in the future, or do we continue to provide the feature set knowing users who update from the Gallery will encounter these issues?

Thanks for the feedback, we are listening.
It's both an unfortunate and required limitation that things installed using Trusted Installer are extremely difficult to change by anything else. The approach Trusted Installer uses is built into Windows. There are changes that are happening to how Windows setup works, albeit slowly.

We did discuss not including Pester in the product, but the reported value of having it be present currently outweighs the number of issues that are being reported.

The only way to acquire content from the Gallery is using PowerShellGet module, which does require PS3 or above, and then internet access to get to the Gallery. PowerShellGet does more than copy, it also performs certain validation actions, and ensures all dependencies are also downloaded.
If you can get to a system that meets those requirements, use Save-Module to put the module you want, and all of its dependencies, into a folder on that system. That folder can then be zipped up, or xcopied, to a folder listed in the PSModulePath of the system where the code will be used.

This report is a bit confusing, so need some information.
On the system where you received this error, please try running any of the commands from Microsoft.PowerShell.Utility, such as get-member, or get-date. The error message and the information you provided seems to indicate that the module is already loaded, so we are looking for other indications that it is not.

Either I’m unable to repro this, or I am missing the issue. I get consistent output between the ISE and standard PS shell.

Can you provide the following, please, so I can understand it better:
> Copy & paste the output of the standard shell & the ISE for this command. Don’t worry that it doesn’t look right in this editor, I’ll convert it to a non-proportional font to understand it.
> In one of the windows, run $psversiontable, and include that in the output.

One last request – can you try replacing Get-WMIObject with Get-CimInstance & see if it does the same thing? The -WMI cmdlets have been replaced with the largely equivalent -Cim cmdlets for a while, and you should really be using the newer cmdlets.

Hi Fred - turns out this is harder to understand using the text output this way. Please contact me using keithb@microsoft.com, if you are willing.
The one thing I can see - the elipsis in the output from ISE indicates that the screen width for the ISE window prevented you from displaying the same output. Can you confirm that the command add-on window is closed, and that the width of the 2 output display areas (the standard PS prompt and the output window in the ISE) match? Alternatively, it may be easier to set the font temporarily to a smaller size in both views, so that the same number of columns can be displayed.
If you can, do a screen capture & send me the jpgs using the email address above. I'll respond to you offline. Thank you.

As an FYI (not disagreeing with the feedback, just providing information) what this command does today is to always place all the required modules in the same path you save the script to. It won't install the modules, but does do a save, as per Save-Module.
Awaiting feedback from others on this item.

Yeah, that’d be cool. Probably wouldn’t be too complex, but it also is probably outside the scope of the PowerShell core cmdlets. Maybe someone would be willing to publish something like this to the Gallery?

Balancing what is in Windows and what is in the Gallery is hard. It would help us to understand why having this in the OS is so much better than having it in the Gallery.

What would help is to understand why installing the Posh-SYSLOG module from the Gallery is not meeting the need. Merging things into the Windows OS has some big implications, so we are trying to strike the balance. Additional information will help.