PowerShell
The PowerShell forum accepts bug reports as well as feedback and suggestions. For more information, check out the PowerShell Homepage
The following is a list of the states we use to track items.
status | meaning |
---|---|
survey | We saw this and we are considering it. Please upvote if it’s important to you. |
needs more information | We don’t understand the issue and need additional details. |
investigating | We are looking at this internally to understand things like: scenario, reproduction of issue, costing, or other technical details. |
in queue | The issue is understood and in our unprioritized backlog. Your votes will be used to drive prioritization of this work. |
-
Pure Pain: Preinstalled PS Modules - Please Rationalize Them with Package Management Installs
I am trying to update Pester on Windows 2016 to 4.x because the preshipped Pester 3.4.0 emits a note about the depreciation of the -quiet switch when I use the quiet switch. This get's scooped into stdout when executing via AWS SSM remote commands. Version 3.x complains it does not understand "-Show None".
I want to update to 4.x - in which I ran into all the problems documented here: https://github.com/OneGet/oneget/issues/215
But ended up with "Install-module pester -force -SkipPublisherCheck.
So far so bad, but when I go to remove the 3.4.0 version (with admin rights) from: 'c:\program files\windowspowershell\modules\pester\3.4.0' I get…
10 votesThe 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…
-
Collapsed region in dark mode is hardly visible
When using the dark theme in ISE, a collapsed region is hardly visible because the font color is black and the background darkblue. There is no way the set the colors for a collapse region in the theme editor.
37 votes -
Add a PowerShell module to manage Windows Updates
Add a PowerShell module to manage Windows Updates like you can now with the GUI. Like checking for updates, installing all updates, or a selection of updates, creating a report of pending updates, etc. The Windows Update options in the Server Configuration Manager (sconfig) are very limited.
47 votesWe don’t own the creation of modules for operating system features. I’ll mark this as Survey so we can provide this information to the WU team, but you might also want to consider filing this in the Windows 10 Feedback Hub. Also, see the community-created PSWindowsUpdate link below :)
-
25 votes
Would be interested in understanding the scenario where you are using the cmdlet & specifying the reason for rebooting. To explain: our previous assumption was that users would EITHER use the server UI that captured this information, OR use the cmdlet (often so they didn’t need to supply that reason text).
So, what would help is to understand in what situations the cmdlet is being used and specifying the reboot explanation is desirable. -
Bring the Azure Automation DSC MOF encryption into the on-premises DSC pull server
In Azure Automation DSC the whole MOF file gets encrypted without the need to manually issue certificates for every node and then to collect the public keys.
From Azure documentation:
"Keeping credentials secure in node configurations (MOF configuration documents) requires encrypting the credentials in the node configuration MOF file. Azure Automation takes this one step further and encrypts the entire MOF file."This extremely useful feature sould also be implemented in the on-premises DSC pull server. Especially because the needed functionality must alread be in the WMF 5 as nothing more than WMF 5 is needed to use the Azure…
16 votes -
Duplicate help files in PSWorkflow module break Get-Help
At some point in the 5.0 time period, Update-Help installed About topic files in the en-US directory for the PSWorkflow module with .txt (not .help.txt) file name extensions.
e.g. about_Foreach-Parallel.txt
Later, this was fixed and Update-Help installed the same help files in the same directory with the (correct) ".help.txt" file name extension.
e.g. about_Foreach-Parallel.help.txt
Now, the PSWorkflow\en-US directory has 9 pairs of files that are identical except for the file name extension.
aboutActivityCommonParameters.help.txt
aboutActivityCommonParameters.txt
aboutCheckpoint-Workflow.help.txt
aboutCheckpoint-Workflow.txt
aboutForeach-Parallel.help.txt
aboutForeach-Parallel.txt
aboutInlineScript.help.txt
aboutInlineScript.txt
aboutParallel.help.txt
aboutParallel.txt
aboutSequence.help.txt
aboutSequence.txt
aboutSuspend-Workflow.help.txt
aboutSuspend-Workflow.txt …17 votes -
Copy headers when copying from Out-GridView
It would be great to copy headers for all the columns when copying data from the Out-GridView table lists.
11 votes -
DSC: Should allow Credentials with Blank Passwords, so you can use GMSA accounts
For some reason DSC errors out with a credential object contains a null password. Unfortunately that is the mechanism use to set group managed service accounts.
Here is a link to a relevant bug in xWebAdministration: https://github.com/PowerShell/xWebAdministration/issues/80#issuecomment-171364644And here is an example of the output your recieve when you attempt to use a managed service account:
"VERBOSE: [COMPUTERNAME]: LCM: [ End Test ] [[xWebAppPool]testpool] in 0.0070 seconds.
The password supplied to the Desired State Configuration resource MSFT_xWebAppPool is not valid. The password cannot be null or empty.
…+ CategoryInfo : InvalidResult: (:) [], CimException
+ FullyQualifiedErrorId : InvalidPassword
+ PSComputerName128 votesThanks for the feedback! I have personally heard this request from a number of customers. IMHO having the ability to use GMS accounts would be a quite useful in DSC configurations. If this is an important feature for you as well, vote it up so that we can appropriately prioritize it as we move forward.
MarkG
-
Out-Gridview should provide a count of the number of objects displayed
It would be very useful if Out-Gridview provided a build in display of the number of objects in the grid. This could be in a status bar at the bottom or at the top along with the Add Criteria button.
This would update as the filters are applied. It would also be nice if the selected items had a count as well.
It would be especially useful with -passthru as you could have an estimate on the number of objects being passed to the next cmdlet in the pipeline.
You can come up with the count by using measure-object, but…
17 votesIt would certainly be cool, but we’re not really investing in Out-GridView at this point in time. I’ll leave this open as a Survey to see if the demand surpasses our bar (though I’d caveat that demand would have to be fairly high).
Thanks,
Joey -
Add support for TLS 1.2 (Invoke-WebRequest, Invoke-RestMethod)
Invoke-WebRequest and Invoke-RestMethod commands only support TLS 1.0 protocol. We need to have a native support for newer TLS (1.2) versions for modern web interfaces.
50 voteschanging to Survey based on Joonas’ comment below – request is to have a flag to force TLS 1.2.
-
Cmdlet version compatibility
We need to define with wich version of Powershel and which operating system cmdlets are compatible.
Could we have this compatibility matrix for each cmdlet in the documentation and also in the help section of each cmdlet?
4 votesWe have a similar item raised as a github issue, crosslinking: https://github.com/PowerShell/PowerShell-Docs/issues/1105
-
Add PowerShell tab and examples to .NET reference pages in MSDN
Votes from Connect: 391
Original Date Submitted: 5/21/2015 12:20:32 AM
Description:
Contact Information
Handle: June Blender
Site Name: PowerShell
Feedback ID: 1351032
Problem Description:
PowerShell users often read .NET reference pages in MSDN. It's all but required, because Get-Help doesn't describe object members. However, in the Examples section of .NET reference pages, there are no PowerShell examples; not even a PowerShell tab.MSDN says they cannot demonstrate a demand for PowerShell examples. I'd like to use this feature request to demonstrate the demand.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 1351032 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1351032).
…
226 voteshttps://github.com/dotnet/docs/issues/3455 The DotNet team is collecting feedback on this item as well.
-
OpenSource the Pull Server
Advances to the current PullServer are, quite frankly, slow and moving in a direction questionable to most MVPs. Microsoft should follow their own lead they took with the DSC modules: opensource it and place it on GitHub so that the community can invest in making a tool that we'd actually like to use.
Example of features still missing that everyone wants:
1. certificate management (use self-signed or pki)
2. web interface for compliance reportingExample of features added that are questionable/actually bad ideas:
1. partial configurations (multiple pull server sources, mofs, and reports all being managed by the node? who…101 votesJustin,
We totally understand that a robust Pull server / central management solution is something that is critical to your success with DSC. We have invested quite heavily in Azure Automation DSC (AA DSC) to fill many of these needs. With that said, I would be very interested to understand if the AA DSC solution does not work for you (and other customers) and why? Vote and comment if this is important to you.
Also interesting feedback on our ‘bad ideas’. Thanks!
MarkG
-
Support basic line wrapping in ISE Script Pane
All IDE's support line wrapping inside the editor, except Powershell ISE (even Notepad has it)! This is useful, for example, when using ISE in a virtual machine console session, where the screen is often smaller than your screens actual resolution.
11 votes -
Returning information from DSC Resource to another
I know this has been discussed, just wanted to make sure to have it in UserVoice. It would be great if it was possible to return information from a resources, so that a later resource could use that information for configuration at runtime.
Example. My configuration apply a new certificate. I would like to write a resource that can get the new certificate thumbprint so that a future resources in the config can use that thumbprint. This is something that Chef allows.
So, something like a global variable that lives during runtime of the config.
Thanks for considering!!
51 votes -
Add A "Start In" Directory for Enter-PSSession
By default, we are placed into Documents (at least I am), then have to change directories. It would be nice to be able to specify a directory we'd like to start in using Enter-PSSession.
19 votes -
ConvertTo-Json doesn't serialize simple objects properly
Given a simple array which has been boxed in a PSObject
[PSObject]$o = @(@(Foo,1),@(Bar,2))
Calling ConvertTo-Json returns a weird pointless wrapper around it:
convertto-json $o
{"value": [
[
"Foo",
1
],
[
"Bar",
2
]
],
"Count": 2}
Which completely breaks round-trip support
ConvertFrom-Json (Convertto-Json $o)
value Count
{Foo 1, Bar 2} 2
16 votes -
Create a SendTo-SysLog cmdlet and include it by default
Please include by default a SendTo-Syslog cmdlet to send log messages to UNIX, Linux and SIEMs.
If you were to add a syslog service role to send or accept syslog messages in a scalable way which integrated with the Windows event logs, that would be great too, but a cmdlet to just send UDP packets is easy enough to include in PoSh 5.1 right now.
Thanks!
26 votesYeah, 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?
-
BUG: new-localuser fails to allow connection to Microsoft account
The New-LocalUser cmdlet available in Windows 10 Anniversary Update cannot perform a function described in the documentation.
Local user accounts may be connected with existing Microsoft accounts. New-LocalUser should support this by accepting a -Name parameter of the form "MicrosoftAccount<user>@outlook.com". This is described in the detailed help.
However this fails because the parameter fails validation as it is over 20 characters in length (already true with "MicrosoftAccount" and "@outlook.com" let alone the "actual" user name). The 20 character limit is valid for a regular local account name, but shouldn't be valid for an MS account name.
There appears no other…
12 votes -
Bug in Show-Command
Scriptblock parameters are interpreted as a [bool] value and is shown as a listbox with values $true or $false
Code to reproduce:
Show-Command -Name Invoke-Command
Scriptblock parameter is shown as a [bool] listbox
Cheers
Tore
15 votes
- Don't see your idea?