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 v3 Release Preview: Intellisense does not show parameter name for parameter with existing value

    Votes from Connect: 18

    Original Date Submitted: 6/28/2012 2:16:48 AM

    Description:

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


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

    Problem Description:
    The PowerShell ISE v3 Release Preview does not show the parameter name in the Intellisense window, for a parameter that already has a value define (based on its position).

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

    Repro Steps:
    1. Open ISE v3 Release Preview
    2. In a new script window, type a cmdlet and…

    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. Option for Format-Table to set color of a column

    Votes from Connect: 16

    Original Date Submitted: 2/27/2011 6:44:56 PM

    Description:
    Contact Information
    Handle: Soós Tibor
    Site Name: PowerShell
    Feedback ID: 648076


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

    Problem Description:
    There is currently an option for Format-Table to set the Label, FormatString, Width and Alignment of a table coulum. My suggestion is to extend these options with ForegroundColor and BackgroundColor of the column.

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

    Repro Steps:
    Expected Results:

    Internal BugId: 2825

    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. v3 suggestion: PowerShell FileSystemProvider should support transactions (TxF)

    Votes from Connect: 56

    Original Date Submitted: 1/13/2011 12:03:33 AM

    Description:
    Contact Information
    Handle: Oisin Grehan
    Site Name: PowerShell
    Feedback ID: 635713


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

    Problem Description:
    From Vista onwards, Windows supports both a transacted registry (TxR) and transacted filesystem (TxF). With powershell v2, we got TxR support. For v3 or beyond, it would be great to have TxF support. A good example taking Pscx's archive cmdlets into account would be the following pipeline:

    PS> dir c:\logs\ -rec -inc *.log -usetx | write-zip -removeoriginal -usetx | move-item c:\archived_logs\ -usetx

    This will recursively…

    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. add Start-Transcript filters

    Votes from Connect: 21

    Original Date Submitted: 10/8/2010 4:46:21 PM

    Description:
    Contact Information
    Handle: TobiasWeltner
    Site Name: PowerShell
    Feedback ID: 611703


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

    Problem Description:
    Start-Transcript logs input and output. This creates huge log files.
    There should be a switch that enables Start-Transcript to only log the inputs and omit the outputs. Optionally, there could be an indicator whether a command completed successfully, was aborted or raised an exception.

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

    Repro Steps:
    currently default behavior

    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-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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. Powershell Core should have a nuget package for release

    It would be awesome if powershell core was released as a package on nuget.org as well as the regular means.

    The reason for this is build systems like cake build can have tools referenced via nuget packages and will pull them down as part of the build.

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

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  16. Bug: Installing WMF4.0 then WMF5.0 on Win7 SP1

    Hello,
    I understand that on Windows 7 SP1-Machines we have to install WMF 4.0 before upgrading to WMF 5.0.
    On all our Windows 7 machines, before installing WMF 4.0 KB2819745, a sample output for Path Environmental Variable, getting with [Environment]::GetEnvironmentVariable(“Path”), looks like this:
    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
    After installing WMF 4.0 KB2819745, it looks like this:
    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;
    There is a multiple path to the Powershell.exe.
    After installing KB3134760 to upgrade to WMF 5.0, it’s getting even worse as path-variable looks like this:
    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;
    Is this a known issue?
    Thanks in advance
    Norbert

    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 →
1 2 20 21 22 24 Next →
  • Don't see your idea?

Feedback and Knowledge Base