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. Get-Member and Online parameter

    Votes from Connect: 16

    Original Date Submitted: 8/9/2010 1:34:16 AM

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


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

    Problem Description:
    I would like that Get-Member cmdlet supports Online parameter in V3 (similar to Get-Help in V2):

    Get-Process | Get-Member -Online

    That command would open the .NET Framework page in MSDN (http://msdn.microsoft.com/en-us/library/system.diagnostics.process.aspx).

    dir | Get-Member -Online

    That command would open the .NET Framework pages in MSDN (http://msdn.microsoft.com/en-us/library/system.io.fileinfo.aspx and http://msdn.microsoft.com/en-us/library/system.io.directoryinfo.aspx).

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

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. PowerShell should implement an Unless operator

    Votes from Connect: 15

    Original Date Submitted: 7/21/2010 11:36:19 AM

    Description:
    Contact Information
    Handle: bigjimslade80465
    Site Name: PowerShell
    Feedback ID: 576911


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

    Problem Description:
    Currently, I need to do this:

    if(! ($bar)) { & foo}

    I would like to be able to do this:

    unless($bar) { & foo}

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

    Repro Steps:
    Currently, I need to do this:

    if(! ($bar)) { & foo}

    I would like to be able to do this:

    unless($bar)…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. ArgumentList parameter to Start-Job Incomplete

    Votes from Connect: 15

    Original Date Submitted: 5/29/2010 12:09:48 AM

    Description:
    Contact Information
    Handle: Clint B.
    Site Name: PowerShell
    Feedback ID: 563695


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

    Problem Description:
    The -ArgumentList parameter is described as passing arguments 'for the script that is specified by the FilePath parameter', which is true. But it also specifies the arguments to a scriptblock specified by the ScriptBlock parameter.

    Additionally the help says that "Because all of the values that follow the ArgumentList parameter name are interpreted as being values of ArgumentList, the ArgumentList parameter should be 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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. v2 bug: test-path returns true for pure whitespace path.

    Votes from Connect: 10

    Original Date Submitted: 5/22/2010 3:29:42 AM

    Description:
    Contact Information
    Handle: x0n
    Site Name: PowerShell
    Feedback ID: 560761


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

    Problem Description:
    Calling test-path " " returns $true. I would expect $false unless a file named " " really did exist.

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

    Repro Steps:
    given there is no file or folder named " " in the root of C:\

    ps c:> test-path " "
    True

    Expected Results:
    ps> test-path " " …

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. Get-ChildItem gets FileInfo constructed in different ways depending on parameters

    Votes from Connect: 12

    Original Date Submitted: 4/30/2010 9:13:05 PM

    Description:
    Contact Information
    Handle: Roman Kuzmin
    Site Name: PowerShell
    Feedback ID: 556004


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

    Problem Description:
    The more detailed question and investigation is in here:
    http://stackoverflow.com/questions/2744047/mysterious-different-conversion-to-string-of-seemingly-same-input-data

    Items returned by (Get-ChildItem <path>) and (Get-ChildItem <path> -Include *) are converted to strings differently. Different results of the two commands below, IMHO, do not make any practical sense and only lead to confusion and bugs:

    This command gets just file names

    string[]

    This command gets full file paths

    string[]

    Product Studio item created…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. Change default behavior of module import

    Votes from Connect: 15

    Original Date Submitted: 3/31/2010 2:02:45 PM

    Description:
    Contact Information
    Handle: Martin Zugec
    Site Name: PowerShell
    Feedback ID: 546066


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

    Problem Description:
    Please re-consider default behavior of Import-Module. Current issue is that if you want to use namespaces (module\verb-noun), you still need to pay attention to name of your functions, because last one always wins.

    This forces us to use SCCM\Get-SccmObject always simply because of the fact that we never know which function we will overwrite. SCCM\Get-Object would overwrite Get-Object in this case. This makes modules less…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. switch statement should accept elements from the pipeline.

    Votes from Connect: 17

    Original Date Submitted: 12/9/2009 12:06:32 AM

    Description:
    Contact Information
    Handle: Xaegr
    Site Name: PowerShell
    Feedback ID: 518895


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

    Problem Description:
    When you need to send a array of objects to switch statement, you cannot just pipe it:
    PS > Get-EventLog security -newest 100 | Switch ($.EventId) {672 {$Id672++} 680 {$Id680++} }
    or
    Get-EventLog security -newest 100 | Select -expandProperty eventid | Switch {672 {$Id
    672++} 680 {$Id_680++}}

    You need to specify full expression as "argument" for a switch, like this:
    Switch (Get-EventLog security…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. v2: import-module failing should probably be a terminating error

    Votes from Connect: 12

    Original Date Submitted: 10/31/2009 4:57:26 AM

    Description:
    Contact Information
    Handle: x0n
    Site Name: PowerShell
    Feedback ID: 506808


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

    Problem Description:
    I see that trying to import a module where the module does not exist yields a non-terminating error. I think that really should be a full-blown terminating error; a failure to load a dependency like that really should stop the script. Having to use get-module -list available, or bump $erroractionpreference up to "stop" just to let try/catch work seems like a bit of a hack.

    Product…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. AutoHelp with Get-Help and Advanced Functions - needs improving

    Votes from Connect: 13

    Original Date Submitted: 12/27/2008 11:39:54 PM

    Description:

    Contact Information
    Handle: tfl
    Site Name: PowerShell
    Feedback ID: 389767


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

    Problem Description:
    I think the new auto-help stuff is fantastic. But it's a tad buggy and inconsistent.

    To demonstrate this, I've created a simle advanced function file (get-autohelp.ps1) attached. You will need to save this file then run get-help against it to see the errors I note.

    Here are the issues:


    1. You can not specify a .NAME section in auto-help. If you do, then the output…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  10. Make all cmdlet parameters accept scriptblocks

    Votes from Connect: 14

    Original Date Submitted: 7/23/2008 3:57:45 AM

    Description:

    Contact Information
    Handle: Dmitry Sotnikov
    Site Name: PowerShell
    Feedback ID: 357352


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

    Problem Description:
    Some cmdlets accept scriptblocks for some parameters, while others don't. This is very inconsistent and confusing.

    On the one hand you can use this syntax for these examples: http://blogs.msdn.com/powershell/archive/2008/04/21/mindwarpingpower-cmdlets-scriptblock-parameters.aspx

    On the other, something like this would fail for no apparent reason:
    Get-DistributionGroup | Set-DistributionGroup -DisplayName {$_.name}

    This is actually (IMHO) a design flaw of PowerShell (unfortunately still present in v2 ) – you (if you…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support text-oriented configuration management

    ... in a folder at C:\config containing text files (and perhaps a similar folder in the user's home directory). Changing those text files would directly apply changes to Windows settings. Services could read those files directly or use a Windows text-based configuration management API.

    Text-oriented configuration has many advantages: it makes devops-style workflows much more simple, entire server configurations could be versioned in git or svn along with the apps they host, spinning up new servers would be much simpler, and tools like Chef and Puppet would integrate far more smoothly and simply with Windows.

    I suggest this as a…

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

    We’ll send you updates on this idea

    3 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Backwards Compatibility for cmdlets

    All new cmdlets only seem to support 2012+ however for those of us with a mixed estate means we have to use other methods for migrations than we do for live servers and would be really good if tools were backwards compatible.. rather than having to develop our own or rely on 3rd party alternatives.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support new-pssession with powershell direct

    The new copy-item options to use a possession to copy files is great, please also support making an new-pssession with a vm name so it can be used with copy-item

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Migrate Sconfig.vbs to PowerShell

    With all Microsoft Tools going to PowerShell, I think it would be better for this config tool to be a PowerShell rather than VB Script.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. PowerShell Remoting using private key authentication

    Enable PowerShell Remoting login using private key authentication similar to the SSH protocol. Entering passwords all the time the log into remote PowerShell is tedious. Being able to use local secure private key to log into many cloud server instances would ease the process of creating new remote sessions.

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

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enable Kerberos pass-trough for nested WinRM sessions

    A second or third hop WinRM session should support the usage of the primary session's ticket if Kerberos delegation is enabled for WinRM. CredSSP is not always wanted or might be limited due to security policies

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Find-Package has no -ScriptSourceLocation parameter

    C:> Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://www.powershellgallery.com/api/v2/items/psscript&#39;
    Find-Package : A parameter cannot be found that matches parameter name 'ScriptSourceLocation'.
    At line:1 char:37
    + Find-Package -ProviderName 'NuGet' -ScriptSourceLocation 'https://ww ...
    + ~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (:) [Find-Package], ParameterBindingException
    
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.FindPackage

    PS 21:22 C:\src
    C:>$PSVersionTable

    Name Value


    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

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

    We’ll send you updates on this idea

    0 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Documentation for Get-ScheduledTask does NOT indicate which versions of windows it applies to as EVERY component should.

    Documentation for Get-ScheduledTask does NOT indicate which versions of windows it applies to as EVERY component should.

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

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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/

    0 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. BUG: Preserve the current directory name as stored in the filing system and not as entered by the user

    The PowerShell console uses the path as entered by the user and not as stored in the filing system. This is inconsistent with the Command Console behaviour and causes applications that rely on the correct casing of the path to fail. IMHO the console should be case insensitive when searching for fils system paths but should preserve the case when returning the file path.

    0 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