There is insufficient information to respond to this item.
The only suggestion we can make at this time is to repeat the command with -Verbose specified.
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.
Updating status - The information you added was appreciated, do not have an answer, but we are investigating this.
4 votesAdminJ. Keith Bankston [MSFT] (Admin, Windows Server) supported this idea ·
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 email@example.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.
I would like to re-name this item to focus on the request for a way to determine if servicing is underway. This seems like it could be achievable, & I would mark it as a Survey item to gauge interest.
The recommendation to block WinRM during servicing would result in some very bad behaviors, particularly during a rollback. That particular request would have to be declined.
If this is OK, pls reply or simply modify the title.
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.
Moving under the PowerShell area
Thanks for filing this. It seems related to this item: https://windowsserver.uservoice.com/admin/forums/301869-powershell/suggestions/11678499-register-psrepository-fails-against-authenticated, which we are also taking a look at.