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. Windows Update Provider for Powershell Package Manager

    Votes from Connect: 3

    Original Date Submitted: 6/1/2015 12:20:47 AM

    Description:
    ********Contact Information********
    Handle: Matt McNabb
    Site Name: PowerShell
    Feedback ID: 1386686
    ***************************************

    Problem Description:
    Please distribute Windows Updates via a package provider. This will allow browsing and installing updates via existing cmdlets such as Find-Package and Install-Package.

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

    Repro Steps:

    Internal BugId: 14531

    56 votes
    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

      2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    • Allow Register-PSRepository to persist credentials

      NuGet feeds allow security around both listing/retrieving packages as well as pushing packages. NuGet.exe and other clients further allow you to persist credentials for listing/retrieving packages using the "nuget sources" command. (https://docs.nuget.org/consume/command-line-reference#sources-command)

      This persistence is important for two reasons:

      1) When you push a package to a secured NuGet feed, NuGet clients generally do a list/read operation first. That list/read operation doesn't contain any API key that you pass along in the push operation. In order for a push to succeed with an API key, you also need to have credentials set for the read operation. You can…

      4 votes
      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

        1 comment  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
      • Powershell (self) update

        It would be very helpful if we could update PowerShell to newest version through PS package manager or OS included script - with all dependencies and prerequisites checks.

        6 votes
        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

          1 comment  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

          This is definitely something we’re thinking about and working towards. The question becomes whether it’s “good enough” to update all the built-in modules (like MS.PS.Utility or MS.PS.Management) via PowerShellGet or if we need to actually update PowerShell itself.

          As we work on PowerShell Core on GitHub (https://github.com/powershell/powershell) we’re beginning to think about how more engine work might be abstracted into individual modules (which, again, could be updated async from the Gallery).

          That being said, there also is probably some value in installing PowerShell Core all up via “Install-Package” or “Update-Package”. Given that PS Core is fully side-by-side enabled, you could slap down a new version of PowerShell Core next to the one from which you’re actually running PowerShell Core.

          At the same time, updating Windows PowerShell (the Windows-only edition of PowerShell that sits on top of the full, .NET Framework) from within Windows PowerShell is significantly trickier…

        • No StdOut output on console until second object

          Let me explain. I have a script that is collecting data, and I send it to StdOut by simply piping it into Select (but problem also happens if I add a ForEach loop and simply make [PSCustomObject] objects). Then my script loops to the next server. That output is not displaying on the screen. All is not lost though, when the script loops to the second server and displays both the first and second will now display. When the third server finishes it displays OK, as does the 4th.

          So it looks like it's just the first one. Normally I…

          4 votes
          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

            3 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
          • ISE should provide an option to restore previously opened files at startup

            When ISE starts up, it should by default (make that configurable: always, prompt, never) restore all files that were open in the previous session.

            49 votes
            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

              3 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
            • ISE hangs after using a Windows Forms dialog

              Votes from Connect: 12

              Original Date Submitted: 4/4/2015 8:50:49 AM

              Description:
              ********Contact Information********
              Handle: Arnoud Jansveld
              Site Name: PowerShell
              Feedback ID: 1224213
              ***************************************

              Frequency: PowerShell ISE
              Regression: function Show-Form
              {
              [reflection.assembly]::LoadWithPartialName("System.Windows.Forms") >$null
              $form = New-Object System.Windows.Forms.Form
              $label = New-Object System.Windows.Forms.Label
              $label.Text = "Please close this form"
              $label.AutoSize = $true
              $form.Controls.Add($label)
              $form.ShowDialog()
              }

              $result = Show-Form

              # Workaround (slow):
              # $result = Start-Job ${function:Show-Form} | Receive-Job -Wait -AutoRemoveJob

              "Form result: " + $result.ToString()

              Write-Warning "The following step may hang PowerShell ISE, save your work!"
              Read-Host -Prompt "Hit Enter or Ctrl-C to abort"

              # This generates a WM_SETTINGCHANGE broadcast message
              [Environment]::SetEnvironmentVariable("foo", "bar",…

              22 votes
              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

                3 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
              • Add maintenance window awareness to DSC / LCM

                Votes from Connect: 17

                Original Date Submitted: 8/13/2015 12:17:49 AM

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

                Problem Description:
                Suggestion one:

                Add maintenance window awareness to the Local Configuration Manager. Edited via metaconfig, it specifies times when configuration changes are acceptable, when automated reboots are acceptable. Further automates configuration maintenance especially when you're implementing changes vs. correcting drift.

                Suggestion two:

                Add universal "DoNotImplementBefore" and "ImplementBy" settings to DSC resources. Just as "Present=" specifies to add/remove something, these would indicate a date/time for the setting to become valid (e.g., "we want to implement a bunch of…

                91 votes
                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

                  2 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                • Option to disable scroll-to-prompt on left mouse click in ISE console window.

                  In PowerShell v3 there was a "feature" added, that moved cursor/ scrolled down to prompt whenever console window gets focus. It makes selecting text in output from previous commands a real nightmare.

                  I would love to get rid off this "feature", or if not possible - at least have an option to turn it off. If possible, make it a default behavior.

                  34 votes
                  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

                    4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                  • Double click highlight occurrences

                    Double clicked strings and integers should be clearly highlighted (like in Notepad++ or in VSCode) if there are multiple occurrences of the same word or number.

                    35 votes
                    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

                      6 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                    • PowerShell ISE VariableExplorer

                      Votes from Connect: 6

                      Original Date Submitted: 10/16/2015 2:00:41 PM

                      Description:
                      ********Contact Information********
                      Handle: Gimli92
                      Site Name: PowerShell
                      Feedback ID: 1907258
                      ***************************************

                      Problem Description:
                      It would be nice to have a built in VariableExplorer in order to see and browse through all variables of the current PowerShell session.

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

                      Repro Steps:

                      Internal BugId: 15901

                      50 votes
                      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

                        2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                      • INPUTS and OUTPUTS section of get-help not displaying properly

                        Problem description
                        --------------------------
                        INPUTS and OUTPUTS section of get-help -Full content shows some unwanted tab and new line characters for almost all cmdlets.

                        For e.g.,

                        get-help content with INPUTS and OUTPUTS section highlighted where extra new line and tab comes for every cmdlet help content.


                        INPUTS
                        PSObject OR array of PSObject OR String OR array of String


                        You can pipe one IP address or a list of IP addresses as Strings, or one PSObject or list of PSObjects having
                        the iLO details such as IP Address, Hostname, Username and Password to access the iLO.


                        OUTPUTS



                        PSObject[] is returned. Use Get-Member…

                        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

                          1 comment  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
                        • workflow common parameters

                          The WorkflowCommonParameters entry is missing from help for workflows.

                          PowerShell workflows have both common parameters and workflow common parameters.

                          Get-Help help for workflows has an entry in the Parameters section for CommonParameters, but not for WorkflowCommonParameters. It needs both.

                          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

                            1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                          • Would be better if the exit command in PowerShell ISE only closed the current tab

                            In PowerShell ISE, if you invoke the exit command, it closes the entire application regardless of how many tabs you have open. It would be better if the exit command simply closed the current tab (if you have multiple tabs open) or the entire application if you only have one runspace open. This would prevent accidentally closing runspaces that you wanted to go back to just because you used the all-too-familiar exit command.

                            Also, making this change would address this issue within PowerShell ISE: when you invoke exit, the Runspace.StateChanged event is only fired for the current/active runspace (tab), even…

                            19 votes
                            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

                              2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                            • WMF 5 Update

                              I am trying to install "Win8.1AndW2K12R2-KB3134758-x64.msu" onto a Windows 8.1 x64 Enterprise, WMF 4.0 .Net4.5 and latest security patches. from March 2016.

                              Each time I run the update I get an error saying 'Update is not applicable to this computer'

                              Any help would be much appreciated.

                              2 votes
                              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

                                3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                              • [Bug] Install-Module -Force prompts for user input when NuGet-anycpu.exe is not present

                                Steps to reproduce:

                                1. Install WMF5 RTM on a fresh Windows 2012 R2 system
                                2. Open an Administrator PS prompt and run "Install-Module Pester -Force"

                                Expected result: The -Force parameter causes the NuGet client to be installed without user intervention.

                                Actual result: The following message is displayed:

                                NuGet-anycpu.exe is required to continue.
                                PowerShellGet requires NuGet-anycpu.exe to interact with NuGet based galleries. NuGet-anycpu.exe must be available in
                                'C:\Program Files\PackageManagement\ProviderAssemblies' or
                                'C:\Users\Administrator\AppData\Local\PackageManagement\ProviderAssemblies'. For more information about NuGet provider,
                                see http://OneGet.org/NuGet.html. Do you want PowerShellGet to download NuGet-anycpu.exe now?
                                [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):

                                The MSDN…

                                7 votes
                                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

                                  4 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
                                • DSC ESENT Database management

                                  In a recent change, the new database for the on-prem Pullserver is now ESENT. Had a question for clarification.

                                  As an old Exchange guy, I have fears that immediately pop into mind. The logs files do not appear to be using circular logging (a way of self cleaning and restricting the amount of log files) – Is this true?

                                  If so, then I’m guess that the log files will continue to grow until the disk is full – which happens to exchange if the log files are not truncated. Is there a way today or in the future we will…

                                  28 votes
                                  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

                                    investigating  ·  5 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                                  • #region / #endregion code folding tokens in ISE should not be case sensitive

                                    Votes from Connect: 17

                                    Original Date Submitted: 5/23/2012 8:29:13 PM

                                    Description:
                                    ********Contact Information********
                                    Handle: HalR
                                    Site Name: PowerShell
                                    Feedback ID: 743272
                                    ***************************************

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

                                    Problem Description:
                                    I've been using #REGION/#ENDREGION tokens in my code for some time to trigger code folding in various editors (e.g. PowerShellPlus and PowerGUI). The new v3 ISE supports this too which is great--but it's case sensitive for some reason. I consider that a bug and would love to see it made case-insensitive.

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

                                    22 votes
                                    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 →
                                    • Out-GridView needs a -DisplayProperty parameter

                                      Votes from Connect: 42

                                      Original Date Submitted: 4/10/2015 11:19:28 PM

                                      Description:
                                      ********Contact Information********
                                      Handle: Trevor Sullivan [MVP]
                                      Site Name: PowerShell
                                      Feedback ID: 1238786
                                      ***************************************

                                      Problem Description:
                                      The Out-GridView command displays all of the properties of each object that is fed into it. Consequently, in order to make the tool more usable, the Select-Object command can be used to inclusively filter the key properties of each object, to display to the end user. Unfortunately, this process results in a modified object, that cannot be used for all intended purposes.

                                      Instead of using Select-Object, a -DisplayProperty parameter should be added to Out-GridView,…

                                      28 votes
                                      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

                                        2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Enable PowerShell module auto-discovery in DSC

                                        I recently discovered that in my DSC resource I can't call a powershell cmdlet that internally calls into another powershell cmdlet - that fails because DSC doesn’t explicitly import the full powershell module, but only imports specific .psm1 files.

                                        Note, same (cmdlet calling another cmdlet) works perfectly fine when executed from Powershell cmd prompt. Let's fix it for DSC.

                                        12 votes
                                        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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →

                                          Thank you for your feedback!

                                          Based on its current ranking compared to other feedback items and product schedule, work on this item is pending (and will be driven by) further customer input. If you did not open this issue and are also impacted by it, please vote this item up.

                                          MarkG

                                        • WMF5.1(?) Code completion fails to complete a parameter

                                          In the PowerShell console type

                                          Export-ModuleMember -a

                                          and press `Tab` in order to complete the parameter `Alias`.
                                          As a result, nothing happens. Take a look at `$Error`:

                                          PS> $Error
                                          Exception calling "CompleteInput" with "3" argument(s): "Index was out of range. Must be non-negative and less than the size of the collection.
                                          Parameter name: index"
                                          At line:38 char:16
                                          + ... return [System.Management.Automation.CommandCompletion]::Complet ...
                                          + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                          + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
                                          + FullyQualifiedErrorId : ArgumentOutOfRangeException

                                          Note that completion of other parameters works.

                                          2 votes
                                          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

                                            1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4
                                          • Don't see your idea?

                                          Feedback and Knowledge Base