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 DSC needs to support "Property Sets"

    Votes from Connect: 12

    Original Date Submitted: 3/24/2015 8:05:35 AM

    Description:
    Contact Information
    Handle: Trevor Sullivan [MVP]
    Site Name: PowerShell
    Feedback ID: 1199561


    Problem Description:
    NOTE: I believe this functionality is already in progress, but I wanted to make sure it was documented in the official PowerShell feedback channel.

    PowerShell DSC Resources need the ability to support multiple "property sets" similar to the "parameter sets" that are

    Suggested implementation:


    1. Add a "PropertySetName" property to the [DscProperty()] attribute (eg. [DscProperty(PropertySetName = "PropertySet1", Key)]

    2. Add a private property (eg. $PropertySetName) to the [DscResource()] attribute, to ensure that the Get(), Test(), and Set()…
    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  2. $_ should be accessible without curly brackets with Where-Object

    Votes from Connect: 5

    Original Date Submitted: 10/30/2014 6:04:29 AM

    Description:
    Contact Information
    Handle: Peter M10
    Site Name: PowerShell
    Feedback ID: 1014939


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

    Problem Description:
    I would like to access the pipeline object with Where-Object without curly brackets like so:

    1..10 | Where-Object $_ % 2 -eq 1

    to get only uneven numbers.

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

    Repro Steps:
    1..10 | Where-Object $_ % 2 -eq 1

    Expected Results:
    Gives an "Cannot validate argument on parameter 'Property'."…

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  3. Cmdlets in the WebAdministration module occasionally generates errors when used in a custom DSC configuration

    Votes from Connect: 5

    Original Date Submitted: 9/17/2014 2:30:56 AM

    Description:
    Contact Information
    Handle: Jan Egil Ring
    Site Name: PowerShell
    Feedback ID: 973480


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

    Problem Description:
    When using cmdlets from the WebAdministration (IIS) PowerShell module in a custom DSC resource, errors are thrown when invoking the Get/Set/Test-TargetResource functions (for example by running Test-DscConfiguration).

    The error thrown is:
    Unable to cast COM object of type 'Microsoft.IIs.PowerShell.Framework.AppHostQueryProcessor' to interface type 'Mic
    rosoft.IIs.PowerShell.Framework.IAppHostQueryProcessor'. This operation failed because the QueryInterface call on the COM component for the
    interface with IID '{6E0E6BE3-71C1-4A66-800E-11B9CBA00EAB}' failed…

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Incorrect default values when pass $null as splatting parameter

    Votes from Connect: 5

    Original Date Submitted: 8/29/2014 4:44:23 PM

    Description:
    Contact Information
    Handle: EricDong1989
    Site Name: PowerShell
    Feedback ID: 958702


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

    Problem Description:
    function test{

    param(        
    
    [Parameter(Mandatory=$false)][int]$age=20,
    [Parameter(Mandatory=$false)][string]$name = 'Name'
    )
    Write-Host $age
    Write-Host $name

    }
    $aa = $null
    test $aa

    You will see outputs:
    0
    Name

    However the age should be 20.
    Further more, modify the function above to
    function test{

    param(        
    
    

    [Parameter(Mandatory=$true)][int]$age,
    [Parameter(Mandatory=$false)][string]$name = 'Name'
    )
    Write-Host $age
    Write-Host $name

    }

    and run
    $aa = $null
    test $aa

    The result is same as above, but the $age…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  5. Write-Error allows both Message and Exception parameters without an error saying the parameters are mutually exclusive

    Votes from Connect: 3

    Original Date Submitted: 8/22/2014 2:01:53 AM

    Description:
    Contact Information
    Handle: Aaron Jensen
    Site Name: PowerShell
    Feedback ID: 951925


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

    Problem Description:
    Write-Error isn't supposed to take both a message and an exception (see help Write-Error), but you can pass both without getting the "Parameter set cannot be resolved using the specified named parameters." error message.

    Also, when you use Write-Error in a catch block, and use both parameters, the original exception bubbles up instead of what gets written with Write-Error.

    Product Studio item…

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  6. PowerShell ISE Intellisense does not work for Import-DscResource

    Votes from Connect: 9

    Original Date Submitted: 8/21/2014 11:08:39 PM

    Description:

    Contact Information
    Handle: Trevor Sullivan [MVP]
    Site Name: PowerShell
    Feedback ID: 951804


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

    Problem Description:
    NOTE: Please see attached video for example.

    When writing a PowerShell DSC configuration using the PowerShell ISE, and adding the Import-DscResource command to the configuration block, the PowerShell ISE does not show the Intellisense for parameter names or parameter values.

    Because there is no mention of Import-DscResource in the built-in PowerShell help, and because no documentation can be found in the Microsoft TechNet Library…

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Import-Module "less discoverable" warning should suggest using Get-Command

    Votes from Connect: 5

    Original Date Submitted: 8/8/2014 12:33:28 AM

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


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

    Problem Description:
    When importing a module with a lot of verbose logging or hundreds of commands, it's a pain to use Import-Module -Verbose as a way of detecting the less discoverable commands. This is especially the case since there are no verbose warnings for commands without verbs (see https://connect.microsoft.com/PowerShell/feedbackdetail/view/940569).

    I think that instead of suggesting Import-Module 'ModuleName' -Verbose ... you should suggest:

    Get-Command -Module 'ModuleName'…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. PowerShell 4.0 help has to be updated with update-help before any help content is available

    Votes from Connect: 4

    Original Date Submitted: 7/25/2014 2:11:19 AM

    Description:
    Contact Information
    Handle: b_mil
    Site Name: PowerShell
    Feedback ID: 928181


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

    Problem Description:
    PowerShell currently ships with no help content built in. Although it can be updated, it is still a regression to not have at least some help files available from the default install. Not all environments and hosts have internet connectivity to retrieve help content online. Not all environments have firewall and security configurations that make it practical to update the help content on all…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. Make F8 work for selected text in the ISE command prompt

    Votes from Connect: 5

    Original Date Submitted: 6/30/2014 2:10:42 PM

    Description:
    Contact Information
    Handle: Jeff Wouters
    Site Name: PowerShell
    Feedback ID: 909738


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

    Problem Description:
    When selecting text in the ISE script pane, you can press F8 to execute only what has been selected.
    My request is to make it possible when you select text in the command window, F8 should also be possible for that selection.
    Not a critical thing, but it would save me some copy-pasting.

    Product Studio item created by Connect Synchronizer due to creation of feedback…

    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 →
  10. Add a .version to comment-based help, that can also be called from script

    Votes from Connect: 14

    Original Date Submitted: 3/27/2014 6:05:55 AM

    Description:
    Contact Information
    Handle: are bee en zed
    Site Name: PowerShell
    Feedback ID: 841437


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

    Problem Description:
    I'd love to be have a .version added through comment based help on scripts and functions. This would be especially valuable if it was visible from within the script or function itself as well, perhaps as a member of $MyInvocation or $PSCmdLet.

    e.g.

    .Version 1.0.12 (March 26, 2014)

    ...

    {
    write-host "This is the FooBar script version $($MyInvocation.Version)!"
    }

    output on host:

    This…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. Weekly tasks created via PowerShell using a different user immediately fail with error 0x41306

    Votes from Connect: 11

    Original Date Submitted: 1/18/2013 12:23:14 AM

    Description:
    Contact Information
    Handle: DanTup
    Site Name: PowerShell
    Feedback ID: 776801


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

    Problem Description:
    I've posted full details and a sample on StackOverflow here:

    http://stackoverflow.com/q/14378951/25124

    We're using PowerShell to create some scheduled jobs, but those that are set to be weekly instead of daily (using New-JobTrigger) always immediately fail with an exist code of 0x41306 when we try to execute them from the Task Scheduler UI. (However they seem to work in PowerShell if we use (Get-ScheduledJob x).Run()

    In…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  12. PowerShell ISE v3 RTM: Intellisense does not show up consistently

    Votes from Connect: 34

    Original Date Submitted: 11/29/2012 11:18:12 PM

    Description:

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


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

    Problem Description:
    Intellisense does not consistently show up for all possible options. Consider the following scenario:

    You add the System.Speech assembly, and then want to reference a type in the System.Speech namespace. You might type the following code

    Add-Type -AssemblyName System.Speech; # Hit F8 to run this in ISE
    
    # Now type this next line out, and note how the System.Speech namespace is not
    # in
    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 →
  13. Tee-Object to support -Encoding parameter like other cmdlets (such as Add-Content)

    Votes from Connect: 11

    Original Date Submitted: 9/2/2012 11:59:59 AM

    Description:
    Contact Information
    Handle: Chris Woo
    Site Name: PowerShell
    Feedback ID: 760831


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

    Problem Description:
    It would be great if Tee-Object cmdlet can support -Encoding parameter like other cmdlets (such as Add-Content)

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

    Repro Steps:
    Expected Results:

    Internal BugId: 3778

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. PS3CTP1: Invoke-RestMethod fails to return the entire output

    Votes from Connect: 20

    Original Date Submitted: 9/30/2011 1:14:25 AM

    Description:

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


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

    Problem Description:
    When using Invoke-RestMethod on an OData feed, it does not return collection-level data (it returns only the entry objects).

    This means that we don't get the feed title, id, or last "updated" time, but it also means we miss out on the two new pieces of collection-level metadata that were added in OData v2: the entry count, and the "next links" (aka…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  15. New Get-Content parameter for XML content support

    Votes from Connect: 19

    Original Date Submitted: 12/19/2010 9:54:31 PM

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


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

    Problem Description:
    To load an XML file we usually do the following:

    $xml = xml

    To make it easier and type less I suggest to add a new parameter:

    $xml = Get-Content -Path .\file.xml -AsXml

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

    Repro Steps:
    Expected Results:

    Internal BugId: 2772

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  16. Get-Service cmdlets needs a Credential parameter

    Votes from Connect: 29

    Original Date Submitted: 6/13/2010 6:12:31 AM

    Description:
    Contact Information
    Handle: hrottenberg
    Site Name: PowerShell
    Feedback ID: 567007


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

    Problem Description:
    The Get-Service cmdlet has a Computername parameter in v2, but without support for supplying credentials, this is of limited use in non-domain or cross-domain scenarios. Please add a Credentials parameter that works similarly to the one on Get-WMIObject.

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

    Repro Steps:
    Expected Results:
    Get-Service should be able to work with…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. BUG: No coercion operator is defined between types 'System.String' and 'System.Char'

    After upgrading WMF to 5.0 RTM on windows 7 64 bit, with office 2013 32 bit.

    I get the following in my mail signature script:
    No coercion operator is defined between types 'System.String' and 'System.Char'.

    the powershell line:
    $objSelection.TypeText([char]13)

    this worked fine before: workaround is to use this instead:
    $objSelection.TypeText(([char]13).tostring())

    psversiontable:
    Name Value


    PSVersion 5.0.10586.51
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.10586.51
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

    .Net is version 4.6.01055 (4.6.1)

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  18. BUG : WMI does not return correct value from a remote session

    BUG : WMI does not return correct value from a remote session

    Querying SCCM from WMI works localy but not from within a remote session.

    when running this locally on the sccm server it works as expected :

    get-wmiobject -NameSpace "ROOT\SMS\siteCT1" -class SMSImagePackage

    but nothing is returned from a pssession
    etsn SCCM-SERVER
    [SCCM-SERVER]PS> get-wmiobject -NameSpace "ROOT\SMS\siteCT1" -class SMSImagePackage

    does not work also with invoke-command
    icm SCCM-SERVER -scriptblock{ get-wmiobject -NameSpace "ROOT\SMS\siteCT1" -class SMSImagePackage }

    From remote session I can list the class but can't find any method or property :

    icm sccm-server -scriptblock {get-wmiobject -NameSpace…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  19. Export-Csv - not quite right error message

    This command

    1 | Export-Csv

    gets an error

    > Export-Csv : You must specify either the -Path or -LiteralPath parameters, but not both.

    The command specifies none of the -Path or -LiteralPath, not both, as the message claims.

    PowerShell 5.0

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

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Powershell/ISE to Taskbar by default

    As Powershell is the most common Management Tool on a server, please re-add the Powershell icon to the Taskbar. And also, make it possible to start ISE directly without first starting powershell once.
    First searching for it through the Start menu is a burden, especially when we deploy several of servers each day and need access to posh each time.

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

Feedback and Knowledge Base