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. PowerShell ISE v4/v3 doesn't handle stdout from children using the same charset conversion as the console host

    Votes from Connect: 3

    Original Date Submitted: 7/22/2014 4:37:07 PM

    Description:
    Contact Information
    Handle: sba
    Site Name: PowerShell
    Feedback ID: 926280


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

    Problem Description:
    Suppose I'm reading the output of some child command using

    $foo = $(& "something.exe")

    If the child's stdout contains accented characters, the PowerShell console host apparently (undocumentedly?) does an implicit conversion from the "IBM437" encoding to "windows-1252" encoding.

    The PowerShell ISE, however, does something different, breaking some scripts / making it impossible to get the same results in the console host and in the ISE. For…

    3 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. PowerShell doesn't support calling .NET methods created in C# that use optional parameters

    Votes from Connect: 7

    Original Date Submitted: 7/2/2014 9:17:42 AM

    Description:
    Contact Information
    Handle: Keith Hill MVP
    Site Name: PowerShell
    Feedback ID: 911280


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

    Problem Description:
    I would like to be able to call a C# method that use optional parameters and take advantage of the optional parameters i.e. only specify the optional parameters that I want to set.

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

    Repro Steps:
    AGiven this C# def:

    public class Class1
    {

    public static string Foo(string
    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Workflows using multiple InlineScripts with the PSComputerName does not get correct variables from the workflow when using "$Using" scoping.

    Votes from Connect: 12

    Original Date Submitted: 6/12/2014 7:30:42 PM

    Description:

    Contact Information
    Handle: Trond Hindenes
    Site Name: PowerShell
    Feedback ID: 894721


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    When a workflow uses multiple "InlineScript {} -PsComputerName" against the same remote computer, and the inlinescript scopes variables using "$Using", the workflow doesn't read variables correctly. I have documented this in a example which is located at https://gist.github.com/trondhindenes/5249e861eb4bb98f5e15

    Basically, my example contains a workflow which connects to a domain controller using InlineScript and attempts to create a computer account in the domain. I…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. Auto-completed values, with spaces, do not have quotes around them

    Votes from Connect: 26

    Original Date Submitted: 12/24/2013 3:09:38 AM

    Description:

    Contact Information
    Handle: Trevor Sullivan
    Site Name: PowerShell
    Feedback ID: 812233


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    When auto-completing a parameter value that has spaces in it, PowerShell is not adding single or double quotes around the value to contain it as a single entity.

    PowerShell should, by default, add single or double quotes around auto-completed values, when spaces are contained in the value.

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

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. DCR: Dismount-WindowsImage needs a -Force parameter

    Votes from Connect: 21

    Original Date Submitted: 11/21/2013 4:02:13 AM

    Description:

    Contact Information
    Handle: Trevor Sullivan
    Site Name: PowerShell
    Feedback ID: 809144


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

    Problem Description:
    We've all been there before.

    It was a dark, stormy night, and from within your home shines a bright light of several computer monitors. Empty beer bottles litter the place, but nonetheless you keep typing away at your PowerShell console.

    You try to dismount a WIM file using image.exe, dism.exe, or now in the modern day, the "dism" module for Windows PowerShell, and you get…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. In Windows 8(.1), the new Win+X menu should default to PowerShell.

    Votes from Connect: 42

    Original Date Submitted: 9/12/2013 8:38:38 AM

    Description:
    Contact Information
    Handle: Joel 'Jaykul' Bennett
    Site Name: PowerShell
    Feedback ID: 800323


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

    Problem Description:
    In the task bar properties dialog in Windows 8.1 there is a new tab "Navigation" which has on it a checkbox: "Replace Command Prompt with Windows PowerShell in the menu when I right-click the lower-left corner or press Windows key+X"

    Why is it that in a new OS, with a brand new menu, the defaults are still set to 1999? That is,…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. PowerShell ISE consumes all memory on some systems when you run Invoke-WebRequest

    Votes from Connect: 15

    Original Date Submitted: 10/21/2012 3:38:47 AM

    Description:
    Contact Information
    Handle: Kirk Munro
    Site Name: PowerShell
    Feedback ID: 768155


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

    Problem Description:
    Joel Bennett, myself, and Claus Nielsen can all reproduce this at will in our own independently managed environments. Others cannot reproduce it at all. On some systems when you invoke the Invoke-WebRequest command in PowerShell ISE and then later close PowerShell ISE, the process stays open even though the window closes, and much worse, the process memory consumption grows non-stop. I have twice…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. A cmdlet to create a proxy configuration settings object

    Votes from Connect: 58

    Original Date Submitted: 7/18/2012 1:09:59 AM

    Description:
    Contact Information
    Handle: Aleksandar Nikolić
    Site Name: PowerShell
    Feedback ID: 754102


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

    Problem Description:
    The problem: Update-Help, Save-Help, and Get-Help (when used with -Online parameter) don't support proxy servers. There might be some others too.

    Some cmdlets (Invoke-RestMethod, Invoke-WebRequest, New-PSSessionOption, and New-WSManSessionOption) have support for proxy servers. A support is provided per cmdlet with different parameters (Invoke-RestMethod and Invoke-WebRequest support Proxy, ProxyCredentail, and ProxyUseDefaultCredentials parameters; New-PSSessionOption and New-WSManSessionOption support ProxyAccessType, ProxyAuthentication, and ProxyCredentail).

    Wouldn't it be nice to have…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. Still cannot merge to any output stream except stdout (1)

    Votes from Connect: 11

    Original Date Submitted: 4/16/2012 10:30:46 AM

    Description:
    Contact Information
    Handle: Joel -Jaykul- Bennett
    Site Name: PowerShell
    Feedback ID: 737038


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

    Problem Description:
    We need to be able to get a single output file with more than one of the output streams in it

    With PowerShell 3 Beta, we can now redirect each of the output streams, but we still can't merge them except into the stdout stream. We should be able to redirect output into the other streams, if only because this does not work (It…

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

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  10. ConvertTo-JSON in PSv3 Beta does not support values containing double-quotes

    Votes from Connect: 22

    Original Date Submitted: 4/9/2012 12:35:27 PM

    Description:
    Contact Information
    Handle: J Stangroome
    Site Name: PowerShell
    Feedback ID: 735978


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    Passing a hashtable with a string value containing a double-quote causes an error "The converted JSON string is in bad format."

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

    Repro Steps:
    $ht = @{ name = "single quotes (') are fine"; value = 'double quotes (") are not' }
    $ht | ConvertTo-Json

    Expected Results:
    {

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

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  11. The Obsolete attribute

    Votes from Connect: 16

    Original Date Submitted: 3/23/2012 3:46:20 PM

    Description:
    Contact Information
    Handle: Shay Levi
    Site Name: PowerShell
    Feedback ID: 732745


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

    Problem Description:
    In PowerShell 3.0, we can use the Obsolete attribute to mark cmdlets that should no longer be used (deprecated). When a cmdlet that uses this attribute is invoked, a warning is issued.

    This option is great for developers but not for scripters. It only works for compiled code and not advanced functions. Similarly, it only works on a cmdlet level not on individual…

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

    We’ll send you updates on this idea

    1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  12. PowerShell 3 should have (l)user updateable help

    Votes from Connect: 15

    Original Date Submitted: 3/5/2012 11:07:50 AM

    Description:

    Contact Information
    Handle: Joel -Jaykul- Bennett
    Site Name: PowerShell
    Feedback ID: 728689


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

    Problem Description:
    The current plan seems to be for PowerShell to ship with just SYNTAX help and require an administrator to use UPDATE-HELP before the inline help actually works.

    We need a way for non-administrators to get help on the box. I suggest you should default to downloading help to a shared location like C:\ProgramData\ that any user can update.

    Product Studio item created…

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

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  13. ISE should accept -Version parameter like powershell.exe

    Votes from Connect: 29

    Original Date Submitted: 10/27/2011 8:28:57 AM

    Description:
    Contact Information
    Handle: JoshGav
    Site Name: PowerShell
    Feedback ID: 696970


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

    Problem Description:
    Once PSv3 is installed on a server, powershell_ise always starts in v3 mode with CLRv4. There should be a -Version parameter as there is for powershell.exe to open the ISE in v2 mode.

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

    Repro Steps:
    Expected Results:

    Internal BugId: 3115

    3 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 →
  14. Provide a simple way to reverse engineer Windows configurations using Windows PowerShell

    Votes from Connect: 13

    Original Date Submitted: 1/28/2011 2:06:24 PM

    Description:
    Contact Information
    Handle: Matt Neerincx [MSFT]
    Site Name: PowerShell
    Feedback ID: 639211


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

    Problem Description:
    Trying to figure out how to do anything with Windows Powershell is always challenging. Why not have a simple tool to reverse engineer the configuration of Windows and generate the associated PowerShell scripts? We have this feature in SQL Server, you just right click on something and say "generate script".

    I would like to have a way to generate scripts for Windows Failover Cluster…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable-PSRemoting support for ComputerName parameter

    Votes from Connect: 17

    Original Date Submitted: 11/23/2010 4:09:27 PM

    Description:
    Contact Information
    Handle: Aleksandar Nikolic
    Site Name: PowerShell
    Feedback ID: 623892


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

    Problem Description:
    I would like to see Enable-PSRemoting support for ComputerName parameter to enable remoting on a remote machine.

    If you are in a domain environment then the ComputerName parameter would not mean much because you could use GPO to enable PowerShell remoting wherever you like. However, in a workgroup environment it could be quite useful.

    Product Studio item created by Connect Synchronizer due to…

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

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  16. Test-ModuleManifest deletes exported variables!!!

    Votes from Connect: 11

    Original Date Submitted: 8/7/2010 12:50:32 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 584207


    Frequency: Always Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    If you use Test-ModuleManifest on the manifest of a module that's already been loaded, and that exports variables ... it deletes all exported variables.

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

    Repro Steps:

    Modules\Test\Test.psd1

    @{
    Author="Joel Bennett"
    ModuleVersion="1.0.0.0"
    ModuleToProcess=join-path $PSScriptRoot "Test.psm1"
    VariablesToExport="*"
    }

    Modules\Test\Test.psm1

    $GraciousVariable = "Hello, my name is gracious. I'm pleased…

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. Get-Credential should expose more options

    Votes from Connect: 24

    Original Date Submitted: 7/21/2010 9:51:10 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 577042


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

    Problem Description:
    At a minimum, Get-Credential needs to expose parameters (like) -Title and -Message for setting the text of the credential query dialog so that the user can tell which credential they are being prompted for.

    Ideally, you should support all of the new Vista / Windows 7 features of CredUIPromptForWindowsCredentials http://msdn.microsoft.com/en-us/library/aa375178%28VS.85%29.aspx ... specifically:


    • The option to display and default the SAVE checkbox to store credentials…
    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. PowerShell.exe can hang if STDIN is redirected

    Votes from Connect: 26

    Original Date Submitted: 7/2/2010 7:56:48 AM

    Description:

    Contact Information
    Handle: Jason Stangroome
    Site Name: PowerShell
    Feedback ID: 572313


    Frequency: Sometimes Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    The Microsoft.PowerShell.ConsoleHost class constructs a M.PS.WrappedDeserializer passing the STDIN TextReader as one of the parameters. By default, the WrappedDeserializer will call ReadLine() on this STDIN TextReader and wait indefinitely, effectively hanging PowerShell and the calling process.

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

    Repro Steps:
    1. Create a simple PowerShell script.
    2. Create a…

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

    We’ll send you updates on this idea

    0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  19. PowerShell's base dynamic object needs to implement IDynamicMetaObjectProvider

    Votes from Connect: 21

    Original Date Submitted: 6/28/2010 12:54:06 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 571301


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

    Problem Description:
    Unlike CLR classes, the members of dynamic objects are defined at runtime. DynamicObject is a new abstract class in the .NET Framework 4 that allows developers to easily implement IDynamicMetaObjectProvider.

    This is the standard way that C# and dynamic languages communicate, and it's the core requirement for WPF data-binding to dynamic objects and allowing the use of natural property syntax to access dynamic properties.

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  20. PowerShell should have a using statement

    Votes from Connect: 28

    Original Date Submitted: 6/8/2010 10:54:52 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 565815


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

    Problem Description:
    In order to manage disposing of object safely, PowerShell ought to have a using statement like CSharp's (or an equivalent construct).

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

    Repro Steps:
    $site = new-object Microsoft.SharePoint.SPSite($SiteCollectionURL)
    $web = $site.openweb()

    $web.SiteUsers | Where{ Get-QADUser -Domain $myDomain -user $_.LoginName.ToLower().Split('')[1] } | Select -Expand LoginName | out-File "OrphanedUsers.txt" -append

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

    We’ll send you updates on this idea

    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base