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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. PowerShell.exe can hang if STDIN is redirected

    Votes from Connect: 26

    Original Date Submitted: 7/2/2010 7:56:48 AM

    Description:

    Contact Information
    Handle: Jason Stangroome
    Site Name: PowerShell
    Feedback ID: 572313


    Frequency: Sometimes Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    The Microsoft.PowerShell.ConsoleHost class constructs a M.PS.WrappedDeserializer passing the STDIN TextReader as one of the parameters. By default, the WrappedDeserializer will call ReadLine() on this STDIN TextReader and wait indefinitely, effectively hanging PowerShell and the calling process.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 572313 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=572313).

    Repro Steps:
    1. Create a simple PowerShell script.
    2. Create a…

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  2. PowerShell's base dynamic object needs to implement IDynamicMetaObjectProvider

    Votes from Connect: 21

    Original Date Submitted: 6/28/2010 12:54:06 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 571301


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    Unlike CLR classes, the members of dynamic objects are defined at runtime. DynamicObject is a new abstract class in the .NET Framework 4 that allows developers to easily implement IDynamicMetaObjectProvider.

    This is the standard way that C# and dynamic languages communicate, and it's the core requirement for WPF data-binding to dynamic objects and allowing the use of natural property syntax to access dynamic properties.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add PowerShell_ISE Startup Parameters

    Votes from Connect: 16

    Original Date Submitted: 6/16/2010 11:13:55 PM

    Description:
    Contact Information
    Handle: cmille19
    Site Name: PowerShell
    Feedback ID: 568074


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    The normal PowerShell host supports startup parameters which facilitate building custom shells (i.e. SCOM, Exchange, Admin Tools etc.) callable from the Windows Start Menu. These custom shells either call a startup script that then load modules or import a console files with customizations.

    Unfortunately, PowerShellISE does not support any startup parameters. For the module developer creating solutions which specifically target PowerShellISE.exe and…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  4. Get-Service cmdlets needs a Credential parameter

    Votes from Connect: 29

    Original Date Submitted: 6/13/2010 6:12:31 AM

    Description:
    Contact Information
    Handle: hrottenberg
    Site Name: PowerShell
    Feedback ID: 567007


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    The Get-Service cmdlet has a Computername parameter in v2, but without support for supplying credentials, this is of limited use in non-domain or cross-domain scenarios. Please add a Credentials parameter that works similarly to the one on Get-WMIObject.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 567007 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=567007).

    Repro Steps:
    Expected Results:
    Get-Service should be able to work with…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. PowerShell should have a using statement

    Votes from Connect: 28

    Original Date Submitted: 6/8/2010 10:54:52 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 565815


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    In order to manage disposing of object safely, PowerShell ought to have a using statement like CSharp's (or an equivalent construct).

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 565815 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=565815).

    Repro Steps:
    $site = new-object Microsoft.SharePoint.SPSite($SiteCollectionURL)
    $web = $site.openweb()

    $web.SiteUsers | Where{ Get-QADUser -Domain $myDomain -user $_.LoginName.ToLower().Split('')[1] } | Select -Expand LoginName | out-File "OrphanedUsers.txt" -append

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. ArgumentList parameter to Start-Job Incomplete

    Votes from Connect: 15

    Original Date Submitted: 5/29/2010 12:09:48 AM

    Description:
    Contact Information
    Handle: Clint B.
    Site Name: PowerShell
    Feedback ID: 563695


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    The -ArgumentList parameter is described as passing arguments 'for the script that is specified by the FilePath parameter', which is true. But it also specifies the arguments to a scriptblock specified by the ScriptBlock parameter.

    Additionally the help says that "Because all of the values that follow the ArgumentList parameter name are interpreted as being values of ArgumentList, the ArgumentList parameter should be the…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. v2 bug: test-path returns true for pure whitespace path.

    Votes from Connect: 10

    Original Date Submitted: 5/22/2010 3:29:42 AM

    Description:
    Contact Information
    Handle: x0n
    Site Name: PowerShell
    Feedback ID: 560761


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    Calling test-path " " returns $true. I would expect $false unless a file named " " really did exist.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 560761 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=560761).

    Repro Steps:
    given there is no file or folder named " " in the root of C:\

    ps c:> test-path " "
    True

    Expected Results:
    ps> test-path " " …

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. Get-ChildItem gets FileInfo constructed in different ways depending on parameters

    Votes from Connect: 12

    Original Date Submitted: 4/30/2010 9:13:05 PM

    Description:
    Contact Information
    Handle: Roman Kuzmin
    Site Name: PowerShell
    Feedback ID: 556004


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    The more detailed question and investigation is in here:
    http://stackoverflow.com/questions/2744047/mysterious-different-conversion-to-string-of-seemingly-same-input-data

    Items returned by (Get-ChildItem <path>) and (Get-ChildItem <path> -Include *) are converted to strings differently. Different results of the two commands below, IMHO, do not make any practical sense and only lead to confusion and bugs:

    This command gets just file names

    string[]

    This command gets full file paths

    string[]

    Product Studio item created…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. Problem in Exporting SSRS report to CSV format:

    Votes from Connect: 13

    Original Date Submitted: 4/6/2010 7:37:36 PM

    Description:
    Contact Information
    Handle: vitthalbhovi
    Site Name: PowerShell
    Feedback ID: 549004


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    Description for Problem:

    The CSV export uses the textbox names for the column headings in SSRS 2005/2008 due this column names are not coming properely in CSV file but in SSRS report its coming fine.i need same column names as in SSRS report (bcoz in my report column names are coming from Expressions (Column names are not hardcoded))

    Product Studio item created by Connect Synchronizer…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  10. Change default behavior of module import

    Votes from Connect: 15

    Original Date Submitted: 3/31/2010 2:02:45 PM

    Description:
    Contact Information
    Handle: Martin Zugec
    Site Name: PowerShell
    Feedback ID: 546066


    Frequency: Always Happens
    Regression: Yes, this happens in previous beta versions

    Problem Description:
    Please re-consider default behavior of Import-Module. Current issue is that if you want to use namespaces (module\verb-noun), you still need to pay attention to name of your functions, because last one always wins.

    This forces us to use SCCM\Get-SccmObject always simply because of the fact that we never know which function we will overwrite. SCCM\Get-Object would overwrite Get-Object in this case. This makes modules less…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make PowerShell_ISE More Extensible

    Votes from Connect: 10

    Original Date Submitted: 3/19/2010 8:20:52 PM

    Description:
    Contact Information
    Handle: cmille19
    Site Name: PowerShell
    Feedback ID: 543200


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    In PowerShellISE it is fairly easy to add functionality via menu items that perform some action against PowerShell file types. However, when editing non-PowerShell files it is more difficult to extend. For instance I created a SQL pack for PowerShellIse which provides an IDE for SQL queries. This works OK, however there are a few things that can't be done like implement…

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  12. Auto Refresh Out-GridView

    Votes from Connect: 10

    Original Date Submitted: 3/19/2010 7:19:04 PM

    Description:
    Contact Information
    Handle: cmille19
    Site Name: PowerShell
    Feedback ID: 543192


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    I have use where I need to send output to a grid and have the grid update on a time interval. For instance processes running on a server. It would be nice to add a couple of parameters to Out-GridView cmdlet: a scriptblock and a time interval.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 543192 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=543192).

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. Warning, Verbose and Debug streams do not respect action preferences the way they should

    Votes from Connect: 33

    Original Date Submitted: 3/12/2010 7:45:29 PM

    Description:
    Contact Information
    Handle: Kirk Munro (Quest Software)
    Site Name: PowerShell
    Feedback ID: 541500


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    If you use the preference variables or the -WarningAction common parameter to control how warnings are handled in PowerShell, or if you use the preference variables to control how verbose or debug messages are handled in PowerShell, your control efforts are ignored because the warning, verbose or debug messages are displayed every time anyway.

    This differs from how preference variables and the -ErrorAction…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support converting to/from clixml format without unnecessary file I/O

    Votes from Connect: 15

    Original Date Submitted: 3/2/2010 4:05:15 AM

    Description:
    Contact Information
    Handle: Kirk Munro (Quest Software)
    Site Name: PowerShell
    Feedback ID: 537755


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    Today you can export PowerShell objects using Export-Clixml and then import them deserialized using Import-Clixml. The trouble with this is that you don't always want to use an external file. Sometimes you want an external file, sure, but many other times you want to store the deserialized object data elsewhere or you want to pass it across a remote connection to a client,…

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Get-EventLog should have an EventID parameter

    Votes from Connect: 10

    Original Date Submitted: 12/19/2009 5:04:21 AM

    Description:
    Contact Information
    Handle: hrottenberg
    Site Name: PowerShell
    Feedback ID: 521263


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    This is such an often-used item that it really should be in here. Even the help file admits as much when it says, "Even though Get-EventLog does not have an EventID parameter".

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 521263 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=521263).

    Repro Steps:
    Expected Results:

    Internal BugId: 2307

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  16. switch statement should accept elements from the pipeline.

    Votes from Connect: 17

    Original Date Submitted: 12/9/2009 12:06:32 AM

    Description:
    Contact Information
    Handle: Xaegr
    Site Name: PowerShell
    Feedback ID: 518895


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    When you need to send a array of objects to switch statement, you cannot just pipe it:
    PS > Get-EventLog security -newest 100 | Switch ($.EventId) {672 {$Id672++} 680 {$Id680++} }
    or
    Get-EventLog security -newest 100 | Select -expandProperty eventid | Switch {672 {$Id
    672++} 680 {$Id_680++}}

    You need to specify full expression as "argument" for a switch, like this:
    Switch (Get-EventLog security…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. v2: import-module failing should probably be a terminating error

    Votes from Connect: 12

    Original Date Submitted: 10/31/2009 4:57:26 AM

    Description:
    Contact Information
    Handle: x0n
    Site Name: PowerShell
    Feedback ID: 506808


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    I see that trying to import a module where the module does not exist yields a non-terminating error. I think that really should be a full-blown terminating error; a failure to load a dependency like that really should stop the script. Having to use get-module -list available, or bump $erroractionpreference up to "stop" just to let try/catch work seems like a bit of a hack.

    Product…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. CredSSP should allow delegation of “Default” (current) credentials

    Votes from Connect: 159

    Original Date Submitted: 10/19/2009 3:31:10 AM

    Description:
    Contact Information
    Handle: degustator
    Site Name: PowerShell
    Feedback ID: 498377


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    When I try to use CredSSP I receive the following error message:

    enter-pssession -computername <Remote Server FQDN> -authentication credssp

    Enter-PSSession : The WinRM client cannot process the request. Requests must include user name and password when CredSSP authentication mechanism is used. Add the user name and password or change the authentication mechanism and try the request again.

    This means that Powershell (or WinRM) implementation of…

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add ability to remotely enumerate/query the Local Security Policy within Powershell

    Votes from Connect: 20

    Original Date Submitted: 6/4/2009 3:05:28 AM

    Description:
    Contact Information
    Handle: reballard
    Site Name: PowerShell
    Feedback ID: 463828


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    Add ability to remotely enumerate/query the Local Security Policy within Powershell without having to resort to leverage 3rd party utilities such as DumpSec, etc. output. This ability would be useful when needing to spot check Local Security Policy stuff within a Powershell Script.

    Product Studio item created by Connect Synchronizer due to creation of feedback ID 463828 (http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=99&FeedbackID=463828).

    Repro Steps:
    It doesn't appear possible…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  20. New-WebServiceProxy needs Force parameter to ignore SSL errors

    Votes from Connect: 42

    Original Date Submitted: 2/28/2009 10:20:55 PM

    Description:

    Contact Information
    Handle: hrottenberg
    Site Name: PowerShell
    Feedback ID: 419466


    Frequency: Always Happens
    Regression: Yes, this happens in all previous versions

    Problem Description:
    In a lab environment, or a low-budget situation, SSL certificates come last on the todo list. Currently, the New-WebServiceProxy cmdlet cannot be used with self-signed certificates. When you control the network, self-signed certs present little to no risk and are very commonly used. Please add a Force parameter (or similar) to this cmdlet to allow for ignoring acceptable SSL cert exceptions.

    Product Studio item created by…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base