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. Test-Connection should support suppressing errors and returning the full result objects

    Use case:

    Test-Connection (1..15 | % { "comp{0:00}" -f $ }) -Count 1 | select Address, IPV4Address, ResponseTime, @{Name='Success'; Expression={$.StatusCode -eq 0}} | ft

    Currently, the code above will produce a table with successful pings, interleaved with error records for unreachable machines. It would be very useful to be able to provide a switch so that Test-Connection would return objects with appropriate status instead of errors.

    As an icing on the cake, the objects returned by Test-Connection could be extended with a bool Success property, calculated based on StatusCode (like in the example above).

    9 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 →
  2. BUG : Test-PSSessionConfigurationFile : Key 'RunAsVirtualAccount' Fails

    The validation process done in Test-PSConfigurationFile for identifying valid keys in a configuration document is which is not working as it should.

    Test-PSSessionConfiguration file calls a method VerifyConfigTable, which as part of its validation routine checks against a set of constants contained in a collection, ConfigTypeEntry.

    RunAsVirtualAccount isn't in this list.

    System.Management.Automation.Remoting.ConfigFileConstants.ConfigFileKeys is the full qualified name

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add write-information logic to write-warning and error

    Please give Write-Warning and Error the same functionality as the new write-information in WMF5.0.

    Would especially like the tag functionaliy

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  4. "Logon as a Service"

    Please create Cmdlets allowing us to query, add and remove the "Logon as a Service" right to users and groups in a reasonably performant manner.

    I have found that all solutions involving secedit take far too long to execute across hundreds of servers. Whilst this I could work around this by creating background jobs and running them in parallel, it would be great if we had native PowerShell Cmdlets that work fast enough that we don't have to worry about this.

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. Update-ModuleManifest fails on UNC path

    Running Update-ModuleManifest on a psd1 saved on the network with a UNC path fails as the ScriptsToProcess, TypesToProcess and FormatsToProcess attributes are set incorrectly in the new manifest.

    Example against the AzureRM.profile manifest:

    Original AzureRm.Profile.psd1 contains

    Format files (.ps1xml) to be loaded when importing this module

    FormatsToProcess = @(

    '.\Microsoft.Azure.Commands.Profile.format.ps1xml'
    

    )

    Running
    Update-ModuleManifest -Path "\<some unc path>\AzureRm.Profile.psd1" -ModuleVersion 1.0.3

    Gives error

    Update-ModuleManifest : Cannot update the manifest file '\<some UNC path>\AzureRM.Profile.psd1' because the manifest is not
    valid. Verify that the manifest file is valid, and then try again.'The member 'FormatsToProcess' in the module manifest is not valid: Cannot find path…

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add Reverse-String cmdlet

    Votes from Connect: 9

    Original Date Submitted: 7/16/2015 4:32:00 PM

    Description:
    Contact Information
    Handle: happysysadm
    Site Name: PowerShell
    Feedback ID: 1551725


    Problem Description:
    Hi,

    it would be nice to have a Reverse-String cmdlet. One that takes a string and reverse it. For example, "asdf" becomes "fdsa".

    It could be aliased to rs (for reverse-string).

    The reverse method for [array] is ok, but having a cmdlet and/or a [string] method. would be better.

    Other well-known languages have routines for this:

    For instance in Perl 6 you have the flip routine, which returns the string reversed character by character.
    "Perl".flip; # lreP …

    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 →
  7. 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 →
  8. Get or Set-WebConfiguration and Get or Set-WebConfigurationProperty does not work for 32-bit applications when pspath is 'MACHINE/WEBROOT'

    When configuring IIS using Powershell, the cmdlets that read or write to configuration do not work when the application pool is 32-bit.

    There is no way of specifying the "bitness" of the application therefore by default the configuration is written to the web.config file in the Framework64 folder which is ignored for 32-bit applications.

    This is also the case for IIS manager when using "Configuration Editor". You can choose the location of "Root Web.Config <location path="my website"> however this ignores whether the application is 32 or 64 bit and always writes to the 64 bit location in the Framework64 folder.

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  9. Get-Clipboard returns one object too many in PS5.0

    If I copy three rows of text from Notepad or Excel into the clipboard, Get-Clipboard returns an array of four strings, instead of three.

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  10. $_ 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. `Get-ChildItem <wildcard-path>` may fail in a directory with backticks

    The script shows the issue:


    # make directory with backticks and cd to it
    
    $null = mkdir &#39;``test``&#39;
    Set-Location -LiteralPath &#39;``test``&#39;

    # it fails &quot;Cannot find path &#39;...\`test`&#39;
    Get-ChildItem *


    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
1 2 10 11 12 14 Next →
  • Don't see your idea?

Feedback and Knowledge Base