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. |
-
$host.ui.prompt default values won't apply
Votes from Connect: 1
Original Date Submitted: 8/28/2015 1:18:57 AM
Description:
Contact Information
Handle: ProveIsso
Site Name: PowerShell
Feedback ID: 1721069
Frequency: PowerShell
Regression: You can use a public example script like this one http://poshcode.org/608
Result being:Key Value
String Field
Secure String System.Security.SecureString
Numeric Value 0Problem Description:
As described by Matt over at StackOverflow - https://stackoverflow.com/questions/26238881/host-ui-prompt-is-ignoring-the-attribute-defaultvalue-in-fielddescription
> $Host.UI.Prompt method accepts a collection of FieldDescription objects. each of those objects can be assigned with a DefaultValue attribute, which is supposed to be returned when no input is given by the user for this specific field.
> I've got everything…2 votes -
limit-eventLog -logname parameter do not accept an array
Votes from Connect: 3
Original Date Submitted: 7/22/2015 3:24:55 PM
Description:
Contact Information
Handle: 响叮咚
Site Name: PowerShell
Feedback ID: 1576035
Frequency: PowerShell
Regression: 【test】
work:
limit-eventLog -logname "SYSTEM" -MaximumSize 204800kbdon't work:
limit-eventLog -logname @("SYSTEM","Application","Security") -MaximumSize 204800kb
limit-eventLog -logname "SYSTEM","Application","Security" -MaximumSize 204800kb
limit-eventLog -logname SYSTEM,Application,Security -MaximumSize 204800kbProblem Description:
limit-eventLog -logname do not accept an array【version】
all version.
from powershell 2.0 to powershell 5.0 in windows 10 preview 10159!【reason】
manual say:
-LogName<String[]>, but after I test, does not support string array,only string!【The reporter】
前进三 (QQ No:120944419)
in
chinese powershell communication salon ---(QQ group No:183173532)Product Studio…
1 vote -
Error when deploying DSC Extension in Azure IaaS VM
Votes from Connect: 6
Original Date Submitted: 6/4/2015 6:00:09 AM
Description:
Contact Information
Handle: AlexWeiss
Site Name: PowerShell
Feedback ID: 1397136
Frequency: PowerShell
Regression: Run a deployment of 10 VMs with a JSON on IaaS V2 using ARM REST API
These 10 VMs must also have a DSC Extension resource deployed.Problem Description:
Hi Team,Wanted to share an error that happens when deploying a VM in Azure using the DSC Extension and Azure Resource Manager.
When the DSC extension try to install, it needs the WMF5 Preview Update but it receive the error below when installing multiple VM at…1 vote -
Auto-generated help for CommonParameters should include InformationAction and InformationVariable
Votes from Connect: 3
Original Date Submitted: 5/27/2015 6:49:42 AM
Description:
Contact Information
Handle: Joel 'Jaykul' Bennett
Site Name: PowerShell
Feedback ID: 1371582
Frequency: PowerShell
Regression: get-help Get-Help -Full | Out-String -stream | select-string "^\s+<CommonParameters>" -Context 0,5Problem Description:
When you call Get-Help on a function right now the InformationAction and InformationVariable common parameters aren't mentioned:PARAMETERS
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (<a rel="nofollow noreferrer" href="http://go.microsoft.com/fwlink/?LinkID=113216)">http://go.microsoft.com/fwlink/?LinkID=113216)</a>.Product Studio item created by Connect Synchronizer due to creation of feedback ID 1371582 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1371582).
…
2 votes -
PowerShell WMF 5 classes lacking
Votes from Connect: 3
Original Date Submitted: 5/6/2015 6:00:56 PM
Description:
Contact Information
Handle: FaustoNascimento
Site Name: PowerShell
Feedback ID: 1307824
Problem Description:
PowerShell are a great introduction to PowerShell, but I feel that they are lacking in a few areas currently:No $PSBoundParameters. With the inability to have fields (rather than properties) in PowerShell classes, and the fact that properties are always public (even with the keyword 'hidden' they can still be accessed externally to the class), it becomes impossible to determine whether a property has a value that is default because of PowerShell's coercion, or if a property…
2 votes -
$PSDefaultParameterValues should be automatically cleared in module scope (for all module types: script, manifest, and binary)
Votes from Connect: 4
Original Date Submitted: 4/6/2015 10:06:18 AM
Description:
Contact Information
Handle: Kirk Munro
Site Name: PowerShell
Feedback ID: 1228413
Problem Description:
While the $PSDefaultParameterValues variable offers many convenient use cases to control how individual or groups of commands behave, it should be automatically cleared in a module scope. Otherwise state configuration that a user sets up in the current runspace may break functionality in modules that are used in that runspace.For example, June sent out a tweet suggesting you should consider forcing Get-Help to always show help in a window, like this:
$PSDefaultParameterValues['Get-Help:ShowWindow'] = $trueThat…
2 votes -
Receive-Job Example 4 is wrong
Votes from Connect: 3
Original Date Submitted: 2/10/2015 9:29:49 AM
Description:
Contact Information
Handle: June Blender
Site Name: PowerShell
Feedback ID: 1122497
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Example 4 of Receive-Job (the one with the $Using scope modifier) fails because the local variable ($j) holds a deserialized job object that Receive-Job can't convert.Please change the example to:
$s = New-PSSession -ComputerName 'MyRemoteServer'
$j = Invoke-Command -Session $s -ScriptBlock {Start-Job -ScriptBlock {Get-Eventlog -LogName System}}
$iid = $j.InstanceID
$results = Invoke-Command -Session $s -ScriptBlock {Receive-Job -InstanceID $Using:iid}Thanks (and sorry about the error), …
2 votes -
-match, -notmatch, -replace, and -split operators have inconsistent case-sensitivity behavior
Votes from Connect: 5
Original Date Submitted: 2/4/2015 1:35:58 PM
Description:
Contact Information
Handle: David Wyatt
Site Name: PowerShell
Feedback ID: 1114651
Frequency: Always Happens
Regression: I do not know if this issue existed previouslyProblem Description:
One would expect -imatch to always be case-insensitive, and -cmatch to always be case sensitive. However, this is only true if you pass something other than a [regex] object on the right of the operator. Under those conditions, PowerShell builds a new regex object with the proper case sensitive setting. If you pass in a [regex] object, it just uses that object regardless…2 votes -
Add support for calculated properties to Measure-Object
Votes from Connect: 4
Original Date Submitted: 11/20/2014 5:43:42 AM
Description:
Contact Information
Handle: Tom Nolan [MSFT]
Site Name: PowerShell
Feedback ID: 1033948
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Most of the *-Object commands support the use of calculated properties, but Measure-Object doesn't. This would be a useful piece of functionality and would also put it in line with the other cmdlets.Product Studio item created by Connect Synchronizer due to creation of feedback ID 1033948 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1033948).
Repro Steps:
The following code is a simple example showing the various *-Object commands
…2 votes -
Add bandwidth switch to invoke-webrequest
Votes from Connect: 3
Original Date Submitted: 11/15/2014 1:29:53 AM
Description:
Contact Information
Handle: Gantcho Radoslavov
Site Name: PowerShell
Feedback ID: 1029839
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
Invoke-webrequest is proving quite helpful. It would be nice however to be able to control the bandwidth used by the cmdlet. Is it possible to add the feature to throttle the bandwidth used by the command?Thank you
Product Studio item created by Connect Synchronizer due to creation of feedback ID 1029839 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1029839).
Repro Steps:
using invoke-webrequest to fetch files from…2 votes -
Caught exceptions still appear in global $Error list
Votes from Connect: 3
Original Date Submitted: 9/16/2014 12:15:09 AM
Description:
Contact Information
Handle: Aaron Jensen
Site Name: PowerShell
Feedback ID: 972566
Frequency: Always Happens
Regression: Yes, this happens in previous released versionsProblem Description:
When you catch exceptions, those exception still appear in the global $Error list. I expect that caught exceptions shouldn't appear there because I'm catching and handling them. We have build pipelines that fail builds if there are any errors in the global $Error variable, and this causes false failures in situations where we are handling the exceptions.$Error.Clear()
try
{throw 'Blarg!'
}
…
catch
{2 votes -
Allow Move-Item/Copy-Item Commands to work Across Compatible Providers
Votes from Connect: 22
Original Date Submitted: 12/27/2013 7:41:19 AM
Description:
Contact Information
Handle: Mark Michaelis
Site Name: PowerShell
Feedback ID: 812361
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Hi,I have created several providers that work for files (e.g. Skydrive, Dropbox, photo sights, etc.). I would like to be able to copy files from the file system up to these providers and vice-versa. Please provide some means so that the provider copy-item and move-item operations will work across providers. Without this feature the following error is returned:
…"Source and destination did not resolve
2 votes -
Mandatory parameter prompts should accept variable input
Votes from Connect: 10
Original Date Submitted: 12/6/2012 12:15:54 AM
Description:
Contact Information
Handle: Trevor Sullivan
Site Name: PowerShell
Feedback ID: 773554
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
When writing a PowerShell function, script, or ScriptBlock that accepts named parameters, it is sometimes desirable to have the end user prompted for input. PowerShell input prompts work great for strings and integers, but fails with other data types (eg. bool, object).Product Studio item created by Connect Synchronizer due to creation of feedback ID 773554 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=773554).
Repro Steps:
function Test-Parameter {
…[CmdletBinding()]
2 votes -
Make it easier for module authors to store user configuration data in the right location
Votes from Connect: 10
Original Date Submitted: 5/9/2012 10:46:55 PM
Description:
Contact Information
Handle: Kirk Munro
Site Name: PowerShell
Feedback ID: 741367
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
This is a request for v.Next (post v3). More and more admins have been asking how they can store modules in a central repository so that they can centrally manage them while making them available to all systems where they use PowerShell. This is easy to do, however they need to be careful because some modules are designed to store configuration/state information in their own…2 votes -
save-help failure - "Unable to connect to help content" error while Connected to internet via corporate proxy server
Votes from Connect: 40
Original Date Submitted: 3/10/2012 1:56:58 PM
Description:
Contact Information
Handle: ramseyg [MVP]
Site Name: PowerShell
Feedback ID: 730195
Frequency: Always Happens
Regression: I don't know if this issue existed previouslyProblem Description:
We have a user-authenticated proxy server on our corporate network. All systems/users must authenticate to access the internet. It is seamless from an internet browser perspective. We have an autoconfiguration script, or we can just enter the proxy information into internet explorer settings, and can browse to the web without any challenge/password.I can even run commands like get-help get-command -online successfully. But I…
2 votes -
Allow the .. Operator to Accept a Step Value and a Keyword to Signify the Array's length
Votes from Connect: 10
Original Date Submitted: 3/8/2012 8:34:09 AM
Description:
Contact Information
Handle: Nektar
Site Name: PowerShell
Feedback ID: 729570
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
In other scripting languages such as Python and MatLab, you can create say a list of all numbers from 0 to 100 stepping by 5 each time by typing something like 0:5:100. Also, you can splice an array from a point to the end by typing 0:end or in Python the last item is -1. In Powershell the .. operator can only accept a starting and…2 votes -
Remote Registry should "just work" (no WinRM dependency)
Votes from Connect: 13
Original Date Submitted: 9/21/2011 11:21:52 AM
Description:
Contact Information
Handle: Matthew Reynolds [MSFT]
Site Name: PowerShell
Feedback ID: 689864
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Remote registry is a core feature of Windows since before I can remember. IT Pros shouldn't have to resort to external exes, WMI, WinRM or .Net methods to use remote regsitry from powershell. They should be able to script naturally against remote registry.Providers/cmdlets which interact with registry (e.g., set-item, get-item, etc) should be updated to use remote registry just like they can use…
1 vote -
Get-ChildItem and 'Filter' parameter misissue
Votes from Connect: 14
Original Date Submitted: 6/14/2011 7:44:51 PM
Description:
Contact Information
Handle: Vadims Podans
Site Name: PowerShell
Feedback ID: 675309
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
'-Filter' parameter tries to bind filter pattern to a both general name and a name in the 8.3 notation (MS-DOS format). This causes that in the 'Get-ChildItem -Filter' output appears unexpected items. For details see repro section.Also this may cause catstrophic results if Get-ChildItem output is passed to Remove-Item cmdlet. Administrator will not expect that Program Files folders will match this pattern. Also PowerShell…
1 vote -
PowerShell Should do Globbing for Cmdlets - at least for FileSystem Paths
Votes from Connect: 15
Original Date Submitted: 10/21/2010 7:25:53 AM
Description:
Contact Information
Handle: rkeithhill
Site Name: PowerShell
Feedback ID: 615447
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
It would be nice if you could decorate an advanced function parameter with an “AcceptsWildcard” attribute like this and have the parameter parsing code actually do the wildcard expansion for you. Of course the doc comment help should use the presence of this attribute to indicate correctly whether or not the parameter accepts wildcards. Perhaps the attribute would take an option to specify simple…2 votes -
get-childitem does not work correctly if -recurse and -literalpath are both specified
Votes from Connect: 4
Original Date Submitted: 8/24/2015 10:15:01 PM
Description:
Contact Information
Handle: herzbube
Site Name: PowerShell
Feedback ID: 1707779
Frequency: PowerShell
Regression: 1. Create a folder C:[foo]
2. Add a file "bar" to the folder
3. Run the following commands in PowerShell:$path = 'C:\[foo]'
get-childitem -literalpath $path -recurseProblem Description:
Let's say I have this file:C:\[foo]\bar
I then run these PowerShell commands:
$path = 'C:\[foo]'
get-childitem -literalpath $pathEverything works fine,
get-childitem
shows me the filebar
, then returns immediately.Now I add the
-recurse
option:$path = 'C:\[foo]'
get-childitem -literalpath $path -recurseget-childitem
no…1 vote
- Don't see your idea?