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. Jbzuzgsjaahvsjshhbbbsjkkkw

    موهتءحشنسةءهءتشكشءاءخنشخششخاءاءنءنءتءءخ

    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 →
  2. ISE should not switch focus automatically to the console pane

    Starting from Windows 10 1803, when you run a selected block of code using F8, ISE switches focus to the console pane. This means that when you run several of these, you have to manually switch the focus back to the script pane after each execution.

    This is much more difficult than before, so please fix this.

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

    We’ll send you updates on this idea

    14 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  3. BUG: [System.Windows.Forms.SystemInformation]::PrimaryMonitorSize returns display size inconsistently between PS and PS ISE

    Reproducibility: always.

    1) Set display scaling not at 100%
    2) Start new PS and PS ISE sessions
    3) Run:
    Add-Type -AssemblyName System.Windows.Forms
    4) Notice difference when running in PS ISE to PS standard

    PS ISE takes no notice of display scaling and reports screen resolution. PS does take notice of display scaling and reports virtual screen resolution, e.g. 1920x1080 for a 3840x2160 screen with 200% scaling.

    $PSVersionTable:
    PSVersion 5.1.18362.145
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.18362.145
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

    Windows 10 Pro v1903 OS Build 18362.418

    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 →
  4. Add-VPNConnection AlwaysOn

    Trying to create a script to Add Always On VPN connections for remote users. The available scripts are so convoluted. I could easily do what I need if I could simply add the -AlwaysOn switch to Add-VPNConnection.

    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. Is anyone here aware of any tools that can help with automated naming conventions validation?

    Is anyone here aware of any tools that can help with automated naming conventions validation?

    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 →
  6. Powershell ISE win10 1803 Cursor swaping panes on run

    Since windows 10 1803 when running a script from the script pane, the cursor switches from the script pane to the console pane.

    To reproduce: Open powershell ise on windows 10 1803. Enter in a basic script (ex: Write-Host "test") and hit F5. The cursor will move to the console pane so if you start typing the output will be in the console pane.

    The expected behavior would be to leave the cursor in the script pane so that you can continue to edit the script. This was the behavior previous to windows 10 1803.

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

    We’ll send you updates on this idea

    6 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  7. Bug?: The Powershell call operator breaks my ISE

    Hello Community

    I hope that i have finally hit the correct place to post my question, since i have been unable to find it so far. Here is my situation:

    I have been developing a Powershell script using Powershell ISE, and for the most part i am very happy about it, however i have encountered what i believe to be a bug in the call operator (&).

    When i use the call operator followed by a "pure" string everything works as it should, the command works and ISE runs as usual, but when i use the call operator followed by…

    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 →
  8. after you install server role on server 2016, configure the internal servernetwork interface and the external server network interface to us

    module doesnot seem to agree with the command.

    set-dnsclientserveraddress -interfacealias internal -serveraddress 127.0.0.1
    set-dnsclienserveraddress -interfacealias externalnat -serveraddress 127.0.0.1

    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 →
  9. Bug: powershell ISE theme, Set the color for control panel/Text Background is useless

    Set the color for control panel/Text Background is useless, whatever you set, it stil the default color(Red:1,Green:36, Blue:86).

    there are 3 items regarding the ConsolePane and 2 items regarding the ScriptPane for editing theme. I am not sure "ConsolePaneTextBackgroundColor" is needed as "ConsolePaneBackgroundColor" is existed.

    My understanding is when we edit color for ConsolePane, we need to make sure "ConsolePaneBackgroundColor" and "ConsolePaneTextBackgroundColor" the same, in order to aligned, but it is work for other color. only the default color(Red:1,Green:36, Blue:86) works.

    <string>ConsolePaneBackgroundColor</string>
    <string>ConsolePaneForegroundColor</string>
    <string>ConsolePaneTextBackgroundColor</string>

    <string>ScriptPaneBackgroundColor</string>
    <string>ScriptPaneForegroundColor</string>

    please find my version information below.

    PS C:\WINDOWS\system32> $PSVersionTable

    Name Value


    PSVersion 5.1.16299.1146
    PSEdition…

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

    Can ise support change keyboard shortcut?
    The intellisense key 'ctrl + space ' is conflict with my input method, which language is not english.

    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. powershell ISE crashes when module manifest nested module is itself

    If you define a module manifest where the nested modules has the current module, ISE terminates.

    Here is an example manifest:
    @{
    RootModule = 'Acme.MyApp.Install.psm1'
    ModuleVersion = '1.0'
    GUID = 'c2419ceb-c2ef-4d2c-bb1d-6ec6de24ab86'
    Author = 'Justin Marshall'
    CompanyName = 'Acme'
    RequiredModules = @('Acme.Common.Misc', 'Acme.Common.WinForms', 'Acme.MyApp.Admin', 'Acme.Common.XMLXSL')
    NestedModules = @('Acme.MyApp.Install')
    FunctionsToExport = ''
    CmdletsToExport = '
    '
    VariablesToExport = ''
    AliasesToExport = '
    '
    FileList = @('Acme.MyApp.Install.psm1')

    }

    this same module loads fine in powershell console.

    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. Escape Char with Powershell ISE

    I am attempting to use the b orr sequence as per https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/aboutspecialcharacters?view=powershell-6
    if I use the example in that page and issue the command write-host “backupbb out” in Powershell (non ISE) you get “back out” as the output as per the example however if you do this in ISE you get “backup out” instead.
    It would appear that ISE cannot handle these two special characters. From what I can tell all the others such as t andn work fine.
    This is verified by DoctorDNS in the following issue post
    PowerShell/PowerShell-Docs#3151
    Thanks
    Robert

    4 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 →
  13. Saving file in the remote session has failed with error: Exception has been thrown by the target of an invocation..

    Since a few weeks, when I edit a file in a PSSession in ISE I get this error message when I save the modifications:

    Saving file: C:\path\file.ps1 in the remote session has failed with error: Exception has been thrown by the target of an invocation..

    Not sure there is a link, but this problem appeared around the moment when this post has been published.

    https://devblogs.microsoft.com/powershell/windows-security-change-affecting-powershell/

    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. New PowerShell Tab should place cursor into console pane input line (Regression)

    After opening "New PowerShell Tab" either using Ctrl+T shortcut or by clicking menu item, tab title gets keyboard focus. Instead, cursor should be placed into input line of console pane.
    This was the way previous versions of ISE worked (before Windows 10).

    See video demo: https://www.youtube.com/watch?v=0fzk1VEQpo0

    (Opening new tab using Ctrl+T, look closely at tab title with dashed line border).

    Windows 10 version 10.0.17763.134
    PowerShell ISE version 5.1.17763.134

    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 →
  15. Powershell ISE ability to mark line(s) for review

    Hi All,

    I've searched for this, but I don't believe it's currently possible:

    I'd like the ability to mark a line or lines of code for review later on and an ability to filter my script to show only marked lines and an ability to quick jump to marked lines.

    To give a scenario: We have a number of PS scripts in the 1000+ line region for configuration of various Applications. As we move from one version of said application to another, we review the PS script - modifying it to meet current business requirements or changing work-around scripts to…

    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. PowerShell ISE CurrentPowerShellTab AddFile focus not on the editor pane

    When running ISE commands like $psISE.CurrentPowerShellTab.Files.Add(...) to open a new script file in ISE the focus should be in the editor pane.
    However, with the Windows update of Windows 10 Pro (1803) 10.0.17134 when a file is opened using $psISE.CurrentPowerShellTab.Files.Add(…) the focus is not on the editor window of the file but the ISE editor tab. Why has this changed?

    This is extremely annoying since we now have to refocus the cursor on to the editor windows before typing or selecting a command to run.

    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. Support for powershell files with "," in the file name

    It seems like this is the only place to report bugs, is that correct?

    Powershell ISE is not able to open files with "," in their name, if you rightclick, and choose Edit. It seems like the ISE thinks, that it should open multiply files (separated by a comma).
    I can drag'n'drop files, with comma in their names, into the ISE, and that works as expected.

    Steps to reproduce:
    1. Create a .ps1 file with a comma in the name (example: test1,test2.ps1)
    2. Right click on file, and press edit
    3. Note "Unable to load"-error.

    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. Windows PowerShell ISE freezes in windows 10

    Windows powershell ISE freezes very often after running even simple command. This has been happening since we moved to Windows 10.

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

    We’ll send you updates on this idea

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

    Hey there,

    We haven’t heard anything about this from anyone else, so I’m guessing there might be something messed up with your machine configuration. Would you mind posting the output of $PSVersionTable. Also, is this happening on all Win10 machines across your deployment? Do you have similar issues when using powershell.exe isnstead of PowerShell ISE, or is it limited to the ISE?

    Thanks,
    Joey

  19. Collapsed region in dark mode is hardly visible

    When using the dark theme in ISE, a collapsed region is hardly visible because the font color is black and the background darkblue. There is no way the set the colors for a collapse region in the theme editor.

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

    We’ll send you updates on this idea

    survey  ·  4 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  20. Keep/Do not reset PowerShell settings on Windows upgrade

    Keep fonts, colors, sizes etc on Windows upgrade.

    3 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 →
← Previous 1 3 4 5 8 9
  • Don't see your idea?

Feedback and Knowledge Base