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. PowerShellISE Command AddOn should show combobox when parameter type is enum

    When a parameter definition in cmdlet is of an enum type, the Command Add On just shows a string field instead of a combo box. It will only show a combobox when the parameter has the ValidateSet attribute defined

    A sample code to help

    Add-Type -TypeDefinition @"
    // very simple enum type
    public enum SimpleEnumType
    {

      Value1,
    
    Value2,
    Value3

    }
    "@

    function Test-ISEEnum {

    param(
    
    [Parameter(Mandatory=$true)]
    [SimpleEnumType]$WithoutValidateSet,
    [Parameter(Mandatory=$true)]
    [ValidateSet("Value1","Value2")]
    [SimpleEnumType]$WithValidateSet
    )

    }

    In command line tab-key auto completion uses all enum values for both parameters.
    ISE command add-on shows a combo box for only $WithValidateSet parameter and provided only the…

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

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  2. Format-Table

    "Get-WmiObject win32_operatingsystem | Format-Table -AutoSize"
    In the PowerShell ISE the AutoSize parameter didn't effects SerialNumber Column .

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

    We’ll send you updates on this idea

    5 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →

    Either I’m unable to repro this, or I am missing the issue. I get consistent output between the ISE and standard PS shell.

    Can you provide the following, please, so I can understand it better:
    > Copy & paste the output of the standard shell & the ISE for this command. Don’t worry that it doesn’t look right in this editor, I’ll convert it to a non-proportional font to understand it.
    > In one of the windows, run $psversiontable, and include that in the output.

    One last request – can you try replacing Get-WMIObject with Get-CimInstance & see if it does the same thing? The -WMI cmdlets have been replaced with the largely equivalent -Cim cmdlets for a while, and you should really be using the newer cmdlets.

  3. [type] should use type completion rather than directory completion

    It's strange that this uses type completion:

    New-Object -TypeName l

    <tab> completes to "long"

    but this uses directory completion:

    Update-TypeData -TypeConverter l

    <tab> completes to ".\Links&quot;

    Even though the former takes a [string] and the latter takes a [type]

    1 vote
    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 →
  4. Support large PowerShell projects

    My dayjob revolves mostly around PowerShell. The largest PowerShell project I've worked on has over 50 000 lines of PowerShell code, the second largest has nearly 20 000. As you can imagine, supporting projects that large is simply impossible with PowerShell ISE. The company I work for bought licenses for PowerShell Studio from Sapien, which made working on the projects tolerable.

    By far the biggest problem with the projects were exhaustingly numerous runtime errors. This was long before the era of PSScriptAnalyzer and Visual Studio Code.

    Even with recent improvements to PowerShell tooling, I still feel like PowerShell is lacking…

    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 →
  5. 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 →
  6. Allow for building front ends for power shell front ends within Visual Studio

    What would be great is to have a way to build a front end for power shell scripts, there is a way to build windows forms with the other object oriented languages VB.NET, C#, etc. Albeit they are programming languages not scripting languages. The best tool out there so far for this is sapien's power shell studio. It's nice but it's no visual studio :)

    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 →
  7. ise color bug:inlinescript

    【Cause of the bug】
    "inlinescript" is a keyword, but color wrong in ise,color as same as a command.

    【bug with powershell version】
    ise in win7 + powershell 2.0: not support PSWorkflow.
    ise in win7 + powershell 5.0: yes have this bug,tested.
    ise in win8 + powershell 3.0: unknown
    ise in win8.1 + powershell 4.0: yes have this bug,tested.
    ise in win10 10586:yes have this bug,tested.
    ise in win2016 tp5 :yes have this bug,tested.

    【test code】
    at first let font bigest,then test.
    workflow aaa
    {

    inlinescript #&lt;----color wrong
    
    {
    &quot;bbb&quot;
    }

    }

    【how to fix】
    unknown

    【reporter】
    By the chinese powershell…

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

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  8. ISE Preview, the ISE Alias, and the PsEdit Function

    In the PowerShell ISE Preview, the "ise" alias should not launch a new instance of the old powershell_ise.exe, it should open the script given to it as an argument in a new tab in the currently-running host ISE process (just the like psEdit function does).

    Personally, I prefer to open scripts into new tabs using "ise" instead of "psedit" because it is shorter (and also a habit burned in from years of use). When the new PowerShell ISE is released later this year, please make "ise" an alias for the psEdit function, or a function in its own right, or…

    1 vote
    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. I'd like to rename my variables and functions like in Visual Studio (.refactor.rename)

    implemented either in ISE and/or in VS with Posh Extension

    1 vote
    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 →

    Understand the difference now based on the comments about replace-all versus rename.refactor. Marking as Survey.

  10. Bug: built-in psEdit function

    When called w/o file name, the pre-defined psEdit function prompts for a file Name to be opened in a new ISE tab. If you then just hit the enter key the function will open each file it finds in the current directory. I consider this not a feature but rather a bug.

    Therefore, I've put the following function in my ISE Profile script to overwrite the original psEdit function:

    function psEdit {
    param(

    [Parameter(Mandatory=$true)]
    
    [string[]]
    $filenames

    )
    foreach ($filename in $filenames) {

    dir $filename | where {!$_.PSIsContainer} | %{
    
    $psISE.CurrentPowerShellTab.Files.Add($_.FullName) &gt; $null
    }

    }
    }

    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 →
  11. Add a regular expression option in Settings as default mode in 'Find'

    The flag mut be set each time the ISE is launched

    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 →
  12. Find should remember more than only the last searched string

    LIke done in Excel/VBA, and in Notepad++.
    Hitting down arrow in the search box should show the previous strings

    1 vote
    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 →
  13. ISE 5.1.1 Preview crashes and restarts but doesn't generate $env:APPDATA\PowerShell_ISE_Crash_Log.txt

    I just had a number of crashes in ISEP while editing code. Each time, ISEP restarted, but no $env:APPDATA\PowerShellISECrash_Log.txt was generated

    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 →
  14. ISE Preview: USB drive shows up twice in Get-PSDrive

    This should speak for itself:

    PS C:/tmp> get-psdrive -name 'I'

    Name Used (GB) Free (GB) Provider Root CurrentLocation


    i 52.88 5.99 FileSystem i:\ BUILD 2016
    I 52.88 5.99 FileSystem I:\

    Maybe this is related to inserting the USB key while ISEP was running?

    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 →
  15. Bug: String parameter with null as default: Different behavior if debugged!

    Function Test-StringDefaultParameter {

    Param (
    
    [String] $Str = [System.Management.Automation.Language.NullString]::Value
    )

    if ($Null -eq $Str) {
    Write-Host &quot;Str is null&quot;
    } else {
    Write-Host &quot;Str is &#39;$Str&#39;&quot;
    }

    }

    When debugging above function (that is just placing a breakpoint in it somewhere in Powershell ISE) then calling 'Test-StringDefaultParameter' without any parameter behaves as expected! (printing out 'Str is null'!).
    Not so though, if there is no breakpoint set! Then 'Str is ''' get printed on the console!

    This happens (at least) with Powershell 5 on Windows 7 64 bit.

    PS C:\Users\peh> Get-Host

    Name : Windows PowerShell ISE Host
    Version : 5.0.10586.117 …

    1 vote
    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 →
  16. Write-Error output posted to current active ISE tab

    When a Write-Error output is used with multiple powershell tabs in the ISE it is automatically posted to the currently active tab regardless of which tab it originated from.

    This was tested with the following command:

    1..20 | % {if ($ % 2) { start-sleep -s 2; write-output $} else {start-sleep -s 2; write-Error $_}}

    And across 3 different tabs in the same ISE.

    While it seems useful behaviour to have a script report errors to the currently active tab, it then can cause problems when trying to actually debug those errors when switching back and forth between tabs…

    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 →
  17. PRB: out-lineoutput : Unable to perform host dependent operation.

    Under some undetermined circumstances, the ISE (RTM or Preview) aborts the execution of the current script with the following error:

    out-lineoutput : Unable to perform host dependent operation.

    + CategoryInfo          : NotSpecified: (:) [out-lineoutput], InvalidOperationException
    
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.Out

    LineOutputCommand

    Restarting the script usually works, but can fail some time later.

    Any clue?

    1 vote
    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 →
  18. PowerShell ISE Preview: Remoting isn't working (connection takes forever)

    PowerShell ISE Preview: Remoting isn't working (connection takes forever)

    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 →
  19. Bug: Syntax highlighting for DSC node block

    Scenario: In a PowerShell DSC configuration block, you create a node block, by specifying a static node name. The node name has a dash in it.

    In this case, the node name is colored blue, like a command, instead of purple, like a parameter value.

    If the node name does not have a dash in it, then it is properly colored purple.

    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 →
  20. [BUG] PowerShell ISE hangs when opening multiple files if Files.CollectionChanged event has a subscriber

    Powershell ISE (both 5.0 and ISEpreview) hangs when you open multiple files at the same time (open dialoge) when you subscribe to the event $psISE.CurrentPowerShellTab.Files.CollectionChanged .

    Works fine when a single document is opened/closed.

    $action = {

    Write-Host &quot;Test&quot;
    

    }

    Register-ObjectEvent -InputObject $psISE.CurrentPowerShellTab.Files -EventName CollectionChanged -Action $action -SourceIdentifier "ToggeRegionExpansionOnOpen"

    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