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. ~Status line

    I've noticed that if I have a lot of 'Undo's quickly, it's hard to tell what line I just 'undid'. Is it possible to have something show me what I just 'undid' or 'redid', such a s a status line of sorts to tell me where my cursor is...like at the bottom of the editor?

    2 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. Add proxy configuration on PowerShell ISE

    PowerShell ISE needs to have a proxy configuration!

    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 →
  3. ISE Bracket Shading

    I think that the ISE should have some user-customizable options - such as bracket shading. The grey isn't quite dark enough to spot. PowerGUI's shading is significantly darker, making it easier to detect the correlating bracket.

    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. Remember last command output eg PSLastItem - forgot to assign object to variable

    When you type in and run a cmdlet (especially one with side-effects) and forget to assign the output to a varialbe, it would be nice to be able to pick up the last output still stored in object form, from an automatic PS variable (eg PSLastItem) to feed into another command.
    Example: running Start-Process with -PassThru, then wanting the ExitCode of the result which I forgot to assign. Maybe even re-use $_ as shorthand, because we're not in the pipeline?

    2 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 →
  5. Use the type of variables in the same way as OutputTypeAttribute when doing tab completion

    Use the type of variables in the same way as OutputTypeAttribute

    Get-Process | % <tab> #completes members of [Diagnostics.Process].

    [Diagnostics.Process[]] $proc = Get-Process

    $proc | % <tab> # does not complete members of [Diagnostics.Process] although the type is known.

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

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow closing tabs by middle-clicking

    Closing tabs by middle-clicking is supported in Visual Studio and all web browsers. Please add support for it in ISE, as well.

    2 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 →
  7. ValidateScript intellisense shows only ScriptBlock

    Applies to: ISE, ISE-Preview, Powershell V5 console

    When you try to use completion inside ValidateScript() intellisense instead of completing cmdlet names inserts "ScriptBlock". There is no problem with completing parameter names.
    Screenshot: https://snag.gy/T6iomf.jpg

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

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  8. Editing remote files without interactive remoting active.

    At the moment it's possible to edit remote files using ISE (I love it!) but that requires interactive session to be active. It would be great if editing would require only PSSession to exist.That would enable scenarios like:
    -- modifying files on multiple endpoints
    -- modifying remote file and running local commands at the same time

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

    We’ll send you updates on this idea

    survey  ·  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:&gt; 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. PowerShell ISE Intellisense hotkey conflict with input method hotkey

    This is a situation with IntelliSense on a computer that has non-English input method enabled.

    The IntelliSense hotkey, Ctrl + Space, conflicts with the input method switch hotkey and the input mehtod hotkey takes precedence.

    It probably doesn't need to be changed but worth to be documented in the help.

    Thanks,

    Lawrence

    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 →
  11. ISE should not complain about improperly closed session

    Whenever ISE is started after a system reboot or logoff/logon sequence, and ISE was running before, it complains that "the previous session was not properly closed" even if no unsaved files were loaded.

    On WM_QUERYENDSESSION, it should just save its state and restore it seamlessly at the next startup.

    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 →
  12. Add Print and recently used File menu for ISE

    In short make ISE able to replace Notepad.exe (which lacks the line numbering feature)

    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 →
  13. PowerShell ISE: Support F7 (menu) and F8 (complete with history)

    F7 (menu) and F8 (complete with history) are extremely powerful features in the console window. Not having it available in the ISE puts actual GUI trade-offs into play. If I choose the ISE, I should expect to get the most capable GUI, but that's not what I get; instead I get a GUI that's more capable in some ways and less in others.

    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 →
  14. drag and drop bug?

    I can normally select a few lines of script and drag them elsewhere. I have noticed that once in a while that the drag fails to paste the text so that it is lost. I have to keep a copy of my file to be safe or I can lose stuff.

    I'm using Windows 7

    Name Value


    PSVersion 4.0

    WSManStackVersion 3.0

    SerializationVersion 1.1.0.1

    CLRVersion 4.0.30319.34209

    BuildVersion 6.3.9600.16406

    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}

    PSRemotingProtocolVersion 2.2

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

    We’ll send you updates on this idea

    3 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  15. { not working in ISE with SL keyboard, probably others as well

    Votes from Connect: 19

    Original Date Submitted: 10/29/2015 9:31:39 PM

    Description:
    Contact Information
    Handle: Jan Bocko Kuhar
    Site Name: PowerShell
    Feedback ID: 1958298


    Frequency: PowerShell ISE
    Regression: Switch to SL keyboard layout and try to type {, which is set to AltGr + B in this layout.

    Problem Description:
    { is set to AltGr + b or Ctrl + Alt + B on SL, HR, ... keyboard layouts, which is set to Debugger in PowerShell ISE. This is really annoying when you use this keyboard layouts as you have to switch to other layouts just for the one character, or…

    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 →
  16. Add ForEach-Object and Where-Object to the built-in ISE snippets

    Votes from Connect: 3

    Original Date Submitted: 11/23/2014 8:12:21 PM

    Description:
    Contact Information
    Handle: Martin Schvartzman
    Site Name: PowerShell
    Feedback ID: 1037606


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

    Problem Description:
    The snippets (CTRL+J) are very helpful for beginners, but the basic ForEach-Object and Where-Object snippets are missing.
    It would be great to have these added to the built-in snippets.

    As a workaround, they can be created using the New-IseSnippet cmdlet:
    New-IseSnippet -Title ForEach-Object -Description 'This snippet inserts the ForEach-Object syntax' -Text 'ForEach-Object { $ }' -CaretOffset 19 -Force
    New-IseSnippet -Title Where-Object -Description 'This snippet inserts

    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 →
  17. 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 object…

    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 →
  18. Command Pane and Output Pane combined... Why?????????

    Votes from Connect: 10

    Original Date Submitted: 12/7/2011 8:49:03 AM

    Description:
    Contact Information
    Handle: MMarcolini
    Site Name: PowerShell
    Feedback ID: 712014


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

    Problem Description:
    The Output pane is gone and the command pane has been transformed into the frankly clunky blue powershell command prompt. Why? This is like taking 3 steps backwards.

    I use the ISE to interactively manage my windows systems in much the same way that I use an xterm to manage my unix systems. I typically have many local and remote command tabs open separated…

    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 →
  19. 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 →
  20. I ran command which was executable in cmd but not recognized in Powershell ISE.

    Command which is recognized in cmd but not in Powershell ISE.

    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  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base