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. |
-
$_ should be accessible without curly brackets with Where-Object
Votes from Connect: 5
Original Date Submitted: 10/30/2014 6:04:29 AM
Description:
Contact Information
Handle: Peter M10
Site Name: PowerShell
Feedback ID: 1014939
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
I would like to access the pipeline object with Where-Object without curly brackets like so:1..10 | Where-Object $_ % 2 -eq 1
to get only uneven numbers.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 1014939 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1014939).
Repro Steps:
1..10 | Where-Object $_ % 2 -eq 1Expected Results:
Gives an "Cannot validate argument on parameter 'Property'."…3 votes -
Write-Error allows both Message and Exception parameters without an error saying the parameters are mutually exclusive
Votes from Connect: 3
Original Date Submitted: 8/22/2014 2:01:53 AM
Description:
Contact Information
Handle: Aaron Jensen
Site Name: PowerShell
Feedback ID: 951925
Frequency: Always Happens
Regression: I do not know if this issue existed previouslyProblem Description:
Write-Error isn't supposed to take both a message and an exception (seehelp Write-Error
), but you can pass both without getting the "Parameter set cannot be resolved using the specified named parameters." error message.Also, when you use Write-Error in a catch block, and use both parameters, the original exception bubbles up instead of what gets written with Write-Error.
Product Studio item…
3 votes -
New Get-Content parameter for XML content support
Votes from Connect: 19
Original Date Submitted: 12/19/2010 9:54:31 PM
Description:
Contact Information
Handle: Shay Levi
Site Name: PowerShell
Feedback ID: 632433
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
To load an XML file we usually do the following:$xml = xml
To make it easier and type less I suggest to add a new parameter:
$xml = Get-Content -Path .\file.xml -AsXml
Product Studio item created by Connect Synchronizer due to creation of feedback ID 632433 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=632433).
Repro Steps:
Expected Results:Internal BugId: 2772
3 votes -
Set-Acl cannot change filesystem/registry ACL if current user or one of his group hasn't TakeOwnership permission
Votes from Connect: 20
Original Date Submitted: 2/27/2009 5:16:35 PM
Description:
Contact Information
Handle: Itanium2
Site Name: PowerShell
Feedback ID: 418906
Frequency: Always Happens
Regression: Yes, this happens in previous released versionsProblem Description:
For example, we have a folder and Administrator or Administrators group is object owner and doesn't have explicit (or inherited from parent) ACE with TakeOwnership right. Running code (see reprodiction steps) we get an error.Product Studio item created by Connect Synchronizer due to creation of feedback ID 418906 (http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=99&FeedbackID=418906).
Repro Steps:
here is code that adds Everyone group to existing ACL:
$acl =…3 votes -
Export-Csv - not quite right error message
This command
1 | Export-Csv
gets an error
> Export-Csv : You must specify either the -Path or -LiteralPath parameters, but not both.
The command specifies none of the -Path or -LiteralPath, not both, as the message claims.
PowerShell 5.0
0 votes -
ConvertFrom-StringData needs an -Ordered switch (to create an ordered hash table).
Votes from Connect: 15
Original Date Submitted: 10/21/2012 9:05:32 PM
Description:
Contact Information
Handle: mjolinor
Site Name: PowerShell
Feedback ID: 768183
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
ConvertFrom-StringData should have an -Ordered switch, to specify that you want to create an ordered hash table (to maintain the same order of elements as the string you're converting).Product Studio item created by Connect Synchronizer due to creation of feedback ID 768183 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=768183).
Repro Steps:
Expected Results:Internal BugId: 3895
2 votes -
`Get-ChildItem <wildcard-path>` may fail in a directory with backticks
The script shows the issue:
# make directory with backticks and cd to it
$null = mkdir '``test``'
Set-Location -LiteralPath '``test``'# it fails "Cannot find path '...\`test`'
Get-ChildItem *1 vote
- Don't see your idea?