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. INPUTS and OUTPUTS section of get-help not displaying properly

    Problem description

    INPUTS and OUTPUTS section of get-help -Full content shows some unwanted tab and new line characters for almost all cmdlets.

    For e.g.,

    get-help content with INPUTS and OUTPUTS section highlighted where extra new line and tab comes for every cmdlet help content.

    INPUTS

    PSObject OR array of PSObject OR String OR array of String
    
    

    You can pipe one IP address or a list of IP addresses as Strings, or one PSObject or list of PSObjects having
    the iLO details such as IP Address, Hostname, Username and Password to access the iLO.

    OUTPUTS

        PSObject[] is returned. Use Get-Member to
    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  2. Help for DocumentEncryptionCert dynamic parameter is missing

    There is no help content for the Document EncryptionCert dynamic parameter of Get-ChildItem.

    Because this dynamic parameter is added by the Certificate provider, it should be documented in the <providerHelp>&lt;cmdletHelpPaths> section of Microsoft.PowerShell.Security.dll-help.xml.

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

    We’ll send you updates on this idea

    investigating  ·  1 comment  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  3. Help for dynamic parameters of Add-Content is broken

    Dynamic parameters of a cmdlet that are added by a provider are documented in the <providerHelp>&lt;cmdletHelpPaths> element of the help XML file.

    The FileSystem provider adds the following parameters to Add-Content:

    PS C:&gt; (Get-Command Add-Content).ParameterSets.Parameters | Where IsDynamic | foreach Name | Sort -Unique
    Encoding
    NoNewline
    Stream

    However, the Encoding and Stream parameters are documented in the primary help file, Microsoft.PowerShell.Commands.Management.dll-help.xml, so they appear in Get-Help even in provider drives where the parameter is not valid.

    PS Function:&gt; (Get-Help Add-Content -Path function:).Parameters.Parameter | where Name -notin $common | foreach Name | Sort -Unique
    Credential
    Encoding # <----
    Exclude
    Filter
    Force …

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

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  4. Help for FileSystem dynamic parameters of Get-ChildItem are broken

    The FileSystem provider adds the following dynamic parameters to Get-ChildItem:

    PS C:&gt; (Get-Command Get-ChildItem).ParameterSets.Parameters | where IsDynamic | foreach Name | Sort -Unique

    Attributes

    Directory
    File
    Hidden
    ReadOnly
    System

    But, these are all failing in Get-Help in the file system drives.

    PS C:&gt; $dynam | foreach { if (!(Get-Help Get-ChildItem -Parameter $ -ErrorAction SilentlyContinue)) { $ } }
    Attributes
    Directory
    File
    Hidden
    ReadOnly
    System

    Unlike the related bugs I've filed, I can't find the error in the help file. These parameters are (correctly) not documented in the cmdlet help, and they are correctly documented in the provider help.

    PS C:&gt;…

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

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  5. Get-Help should process Alias parameter attribute in MAML help

    A parameter definition in the PowerShell MAML file allows an aliases attribute to be defined. However, when executing Get-Help -Full or Get-Help -Parameter, the table the Help Engine displays does not contain the Aliases row. If I remove reference to the ExternalHelp comment tag in a Cmdlet (within a PSM1), Get-Help will display the Aliases row. Comment-based or MAML help will not display the Aliases row.

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

    We’ll send you updates on this idea

    investigating  ·  1 comment  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  6. Get-NetFirewallRule help page parameters section correction

    Description of the parameter claims, wildcards are accepted, but the "Accept wildcard character?" value is false. Running
    get-netfirewallrule -description *
    results in the retrieval of a portion of the firewall rules retrieved without the parameter (535/556 when I ran it). I suggest editing the help file, as well as checking why the parameter discludes a portion of the firewall rules.
    -Description <String[]>

        Specifies that matching firewall rules of the indicated description are retrieved. Wildcard characters are
    
    accepted.

    This parameter provides information about the firewall rule. This parameter specifies the localized,
    user-facing description of the IPsec rule.

    Required? false
    Position? named …

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    investigating  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  7. Error in About_WorkflowCommonParameters

    In the About_WorkFlowCommonParameters, there is an error in the example describing the -PSParameterCollection, The example reads:
    -PSParameterCollection @{

         PSComputerName=&quot;Server01&quot;;  PSElapsedTimeoutSec=10;
    
    PSConnectionRetryCount=6},
    @{PSComputerName=&quot;*&quot;; PSElapsedTimeoutSec=20}

    In the second hash table, the example has '*' for the computer name. This is wrong - it needs a real computer name or PowerShell Gives and error.

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  8. Error in Keywords section of About_WorkFlowCommonParameters

    In the help text aboutWorkFlowCommonParameters, in the KEYWORDS section of the full text, it shows two about* files. The first (AboutWorkFlowCommonParameters) does not exist.

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

Feedback and Knowledge Base