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.

Please feel free to provide feedback or file bugs here.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Make all cmdlet parameters accept scriptblocks

    Votes from Connect: 14

    Original Date Submitted: 7/23/2008 3:57:45 AM

    Description:

    ********Contact Information********
    Handle: Dmitry Sotnikov
    Site Name: PowerShell
    Feedback ID: 357352
    ***************************************

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

    Problem Description:
    Some cmdlets accept scriptblocks for some parameters, while others don't. This is very inconsistent and confusing.

    On the one hand you can use this syntax for these examples: http://blogs.msdn.com/powershell/archive/2008/04/21/mindwarpingpower-cmdlets-scriptblock-parameters.aspx

    On the other, something like this would fail for no apparent reason:
    Get-DistributionGroup | Set-DistributionGroup -DisplayName {$_.name}

    This is actually (IMHO) a design flaw of PowerShell (unfortunately still present in v2 ) – you (if…

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    • Make module availability network-discoverable

      Votes from Connect: 10

      Original Date Submitted: 4/21/2012 9:43:26 PM

      Description:
      ********Contact Information********
      Handle: PowerShellDon
      Site Name: PowerShell
      Feedback ID: 738071
      ***************************************

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

      Problem Description:
      I suggest a Register-Module cmdlet, which can be used to register a given module, on a given machine, optionally within a given AD site, as being publicly available. Registration would be in DNS, likely as SRV records (much like an AD domain controller).

      "Get-Module -List" would then list local modules as well as modules advertised in DNS *for the user's current site* (or…

      1 vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
      • AutoHelp with Get-Help and Advanced Functions - needs improving

        Votes from Connect: 13

        Original Date Submitted: 12/27/2008 11:39:54 PM

        Description:

        ********Contact Information********
        Handle: tfl
        Site Name: PowerShell
        Feedback ID: 389767
        ***************************************

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

        Problem Description:
        I think the new auto-help stuff is fantastic. But it's a tad buggy and inconsistent.

        To demonstrate this, I've created a simle advanced function file (get-autohelp.ps1) attached. You will need to save this file then run get-help against it to see the errors I note.

        Here are the issues:

        1. You can not specify a .NAME section in auto-help. If you do, then…

        1 vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
        • PowerShell ISE Intellisense should display .NET object constructor signatures

          Votes from Connect: 28

          Original Date Submitted: 6/26/2012 10:32:58 PM

          Description:
          ********Contact Information********
          Handle: Trevor Sullivan
          Site Name: PowerShell
          Feedback ID: 750939
          ***************************************

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

          Problem Description:
          The Windows PowerShell ISE does not currently display .NET object constructor signatures. When instantiating .NET objects using the New-Object cmdlet, along with its -TypeName and -ArgumentList parameters, it would be a great workflow enhancement to have the ISE's Intellisense display the object constructor signatures, such that a developer does not have to resort to pulling up the MSDN documentation online much less frequently. Memorizing…

          1 vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
          • PowerShell ISE v3 Release Preview: Intellisense does not show parameter name for parameter with existing value

            Votes from Connect: 18

            Original Date Submitted: 6/28/2012 2:16:48 AM

            Description:

            ********Contact Information********
            Handle: Trevor Sullivan
            Site Name: PowerShell
            Feedback ID: 751184
            ***************************************

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

            Problem Description:
            The PowerShell ISE v3 Release Preview does not show the parameter name in the Intellisense window, for a parameter that already has a value define (based on its position).

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

            Repro Steps:
            1. Open ISE v3 Release Preview
            2. In a new script window, type a cmdlet…

            1 vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
            • 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.

              1 vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
              • 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 {$Id_672++} 680 {$Id_680++} }
                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 -newest 100 |…

                1 vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                • PowerShell 3.0 ISE needs '-version 2.0' option

                  Votes from Connect: 10

                  Original Date Submitted: 7/12/2012 9:58:36 PM

                  Description:
                  ********Contact Information********
                  Handle: sba
                  Site Name: PowerShell
                  Feedback ID: 753454
                  ***************************************

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

                  Problem Description:
                  Given that PS3 will not be available for legacy operating systems, and that PS3 will not be deployed everywhere overnight, it is currently required to write scripts that are backwards-compatible with PS2.

                  This can be achieved by:
                  - using 'Set-StrictMode-version 2.0'
                  - testing in a host created by running 'powershell -version 2.0'

                  But it's not possible to develop using the ISE in PS2 mode.

                  IMVHO…

                  1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                  • 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

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                    • powershell v3-RC: specific comment line causes all scripts to fail

                      Votes from Connect: 11

                      Original Date Submitted: 7/13/2012 3:45:58 AM

                      Description:
                      ********Contact Information********
                      Handle: RichardMcKenzie
                      Site Name: PowerShell
                      Feedback ID: 753494
                      ***************************************

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

                      Problem Description:
                      A new bug has been introduced in powershell v3.0 - RC that does not exist in v3.0 CTP2.

                      It appears that .ps1 scripts fail to execute and throw the runtime error "Executable script code found in signature block" if the following line appears in the script:

                      # organizational unit filter

                      Product Studio item created by Connect Synchronizer due to creation of feedback ID…

                      1 vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                      • Get-HotFix Id parameter should accept wildcard characters

                        Votes from Connect: 15

                        Original Date Submitted: 7/15/2012 7:48:53 PM

                        Description:
                        ********Contact Information********
                        Handle: Shay Levi
                        Site Name: PowerShell
                        Feedback ID: 753770
                        ***************************************

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

                        Problem Description:
                        When you issue the Get-HotFix you can see that not all HotFixId's follow a naming convention. For example, on my system some starts with KBxxxxxx and some with numbers only (in some cases 5 digits and in others 6 digits).

                        That makes it very hard to search for specific hot fixes when all you know is a part of the Id.
                        That's why the…

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                        • 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…

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                          • 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…

                            1 vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                            • 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[]](Get-ChildItem C:\TEMP\Test)

                              # This command gets full file paths
                              [string[]](Get-ChildItem…

                              1 vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                              • 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
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                • 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…

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Help for Polish is missing.

                                    Votes from Connect: 23

                                    Original Date Submitted: 9/18/2012 3:37:35 AM

                                    Description:
                                    ********Contact Information********
                                    Handle: Bartek Bielawski
                                    Site Name: PowerShell
                                    Feedback ID: 763122
                                    ***************************************

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

                                    Problem Description:
                                    There is no help available in Polish both in previous versions and in current version of PowerShell. Actually - nothing is really localized to Polish (including menus in ISE, most of error messages). But I would consider missing help as top priority here: it's not big issue for people who are fluent in English, but reading documentation in foreign language can be challenging.

                                    Product…

                                    1 vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Please add documentation in German language for PowerShell 3.0

                                      Votes from Connect: 78

                                      Original Date Submitted: 9/18/2012 6:29:36 PM

                                      Description:
                                      ********Contact Information********
                                      Handle: Peter Kriegel
                                      Site Name: PowerShell
                                      Feedback ID: 763246
                                      ***************************************

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

                                      Problem Description:
                                      In PowerShell 3.0 there are no help files available in German language. But I would consider missing help as top priority here. Most of the the east German peoples are never learned English (they learned Russia). Even for Peoples who can read English, there is a big danger to misunderstood something. Reading documentation in a foreign language can be very challenging.

                                      Calling…

                                      1 vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Accidental code execution in ISE by pressing F1

                                        Votes from Connect: 12

                                        Original Date Submitted: 9/19/2012 5:52:24 AM

                                        Description:
                                        ********Contact Information********
                                        Handle: TobiasWeltner
                                        Site Name: PowerShell
                                        Feedback ID: 763406
                                        ***************************************

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

                                        Problem Description:
                                        when you press F1 in ISE 3.0, the word the cursor is in is used as a keyword, and ISE executes this code:

                                        Get-Help "keyword" -ShowWindow

                                        The problem here are the double-quotes. The keyword should be placed into single quotes. With double quotes, unexpected behavior and accidental code execution is possible.

                                        See details section below for steps to repro.

                                        Product Studio item created…

                                        1 vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                        • 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…

                                          1 vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

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

                                          Feedback and Knowledge Base