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. converting multiple lines of code to comment

    Votes from Connect: 5

    Original Date Submitted: 2/20/2015 2:01:32 PM

    Description:

    Contact Information
    Handle: john.s2011n
    Site Name: PowerShell
    Feedback ID: 1139497


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

    Problem Description:
    in PS 4.0 and also previous versions, there is no option to easily convert multiple selected lines to comment block. so when we have selected multiple lines & we want to make them as comment, we have to insert comment block in another location on the pane, and then cut these multiple lines and paste them inside comment block which is a bit cumbersome.
    but in…

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

    We’ll send you updates on this idea

    1 comment  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

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

    We’ll send you updates on this idea

    4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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

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

    We’ll send you updates on this idea

    2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  4. Certain PowerShell ISE windows screws up alt+tabbing

    It looks like certain windows are screwed up in Windows 10 w.r.t. to it's alt+tab handling.


    1. The modal:

    a. Open PowerShell ISE
    b. Go to Tools | Options...

    Now try to alt+tab away from the "Options" window.

    The first alt+tab entry is the "main PowerShell ISE" window which if you alt+tab to that, takes you right back into the "Options" window. So it takes 2 alt+tabs to escape from the "Options" window rather than the expected 1 alt+tab.


    1. The non-modal "Edit | Find in Script..." suffers from the above problem as well.


    2. The modal "Edit | Go To Line..." seems…

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

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…

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

    We’ll send you updates on this idea

    2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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.

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

    We’ll send you updates on this idea

    8 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

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

    We’ll send you updates on this idea

    4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  8. Find in ISE needs to be able to wrap rather than stopping when it reaches the end of the file

    Find in ISE starts from the cursor position and stops at the end of the file. This is extremely annoying behavior since to perform a full file search you need to move the cursor to the beginning of the file before beginning "Find".

    Find needs the ability to find within an entire file from anywhere the search is started -- just like notepad++, notepad2, and any other modern text editor.

    19 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 →
  9. Bug in ISE Preview 5.1.1

    Hi Folks,

    I'm running ISE Preview 5.1.1 downloaded from the PowerShell Gallery. When I hit the 'Show Command Window' button in the menu bar (or type show-command) I get this error.

    PS Library:> show-command
    show-command : [A]System.Collections.Generic.List1[Microsoft.PowerShell.Commands.ShowCommandExtension.ShowCommandCommandInfo]
    cannot be cast to [B]System.Collections.Generic.List
    1[Microsoft.PowerShell.Commands.ShowCommandExtension.ShowCommandCommandInfo].
    Type A originates from 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' in the context 'LoadNeither' at
    location 'C:\Windows\Microsoft.Net\assembly\GAC64\mscorlib\v4.04.0.0.0b77a5c561934e089\mscorlib.dll'. Type B originates from
    'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' in the context 'LoadNeither' at location
    'C:\Windows\Microsoft.Net\assembly\GAC64\mscorlib\v4.04.0.0.0
    b77a5c561934e089\mscorlib.dll'.
    At line:1 char:1
    + show-command
    + ~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Show-Command], InvalidCastException
    
    + FullyQualifiedErrorId : System.InvalidCastException,Microsoft.PowerShell.Commands.ShowCommandCommand

    I'm running…

    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 →
  10. 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

    Problem Description:
    After using ShowDialog() to…

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

    We’ll send you updates on this idea

    4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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, so…

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

    We’ll send you updates on this idea

    2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  12. Move ISE add-ons to Powershellgallery

    ISE links currently to the ""Add-on Tools Website (http://social.technet.microsoft.com/wiki/contents/articles/2969.windows-powershell-ise-add-on-tools.aspx).

    Automated installation with a PSRepository (like Powershellgallery) would be nice.

    5 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 →
  13. #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 ID…

    24 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 →
  • Don't see your idea?

Feedback and Knowledge Base