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. Add PowerShell tab and examples to .NET reference pages in MSDN

    Votes from Connect: 391

    Original Date Submitted: 5/21/2015 12:20:32 AM

    Description:
    Contact Information
    Handle: June Blender
    Site Name: PowerShell
    Feedback ID: 1351032


    Problem Description:
    PowerShell users often read .NET reference pages in MSDN. It's all but required, because Get-Help doesn't describe object members. However, in the Examples section of .NET reference pages, there are no PowerShell examples; not even a PowerShell tab.

    MSDN says they cannot demonstrate a demand for PowerShell examples. I'd like to use this feature request to demonstrate the demand.

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

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

    We’ll send you updates on this idea

    22 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  2. about_Language_Keywords is missing 4.0-5.0 keywords

    aboutLanguageKeywords for PowerShell 5.0 (https://technet.microsoft.com/library/hh847744.aspx) is missing all of the new keywords for PowerShell 4.0 and 5.0, including critical keywords, such as Configuration, Class, and Enum.

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

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  3. Comment-Based Help: Allow multi-line examples

    Votes from Connect: 8

    Original Date Submitted: 8/22/2014 11:58:54 PM

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


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

    Problem Description:
    Currently, when using comment-based help, you're limited to one line of code for an example. This is extremely limiting, especially when trying to document DSC resources, since they span multiple lines by default. Also, some examples would be more useful with some extra lines. The current alternative is to use XML-based help, but the MAML schema is extremely verbose and complicated.

    What I'd like to…

    18 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 →
  4. Duplicate help files in PSWorkflow module break Get-Help

    At some point in the 5.0 time period, Update-Help installed About topic files in the en-US directory for the PSWorkflow module with .txt (not .help.txt) file name extensions.

    e.g. about_Foreach-Parallel.txt

    Later, this was fixed and Update-Help installed the same help files in the same directory with the (correct) ".help.txt" file name extension.

    e.g. about_Foreach-Parallel.help.txt

    Now, the PSWorkflow\en-US directory has 9 pairs of files that are identical except for the file name extension.

    aboutActivityCommonParameters.help.txt
    about
    ActivityCommonParameters.txt
    aboutCheckpoint-Workflow.help.txt
    about
    Checkpoint-Workflow.txt
    aboutForeach-Parallel.help.txt
    about
    Foreach-Parallel.txt
    aboutInlineScript.help.txt
    about
    InlineScript.txt
    aboutParallel.help.txt
    about
    Parallel.txt
    aboutSequence.help.txt
    about
    Sequence.txt
    aboutSuspend-Workflow.help.txt
    about
    Suspend-Workflow.txt …

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

    We’ll send you updates on this idea

    survey  ·  3 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. Get-Help cmdlet should skip error and continue updating help doc.

    I know that there are many cmdlets help documentation not completed yet. But, it's a pain when trying to use the "Update-help" cmdlet and see it error-out due to an unfinished module help.

    I think it should be a good idea to display the error and continue (or try) update the rest of our installed module(s).

    In my case, I'm getting an error update the help on the new SQLServer module. But this is now completing the update for the rest of my existing module.

    If this update is done alphabetically then the update is stopping at the SQLServer module…

    6 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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  7. Get-Help Certificate -ShowWindow

    Pretty sure this is a bug. When I run

    Get-Help Certificate -ShowWindow

    The window outputs:

    @{CmdletHelpPaths=@{CmdletHelpPath=@{command=System.Management.Automation.PSObject[]; id=Certificate}}; DetailedDescription=System.Management.Automation.PSObject[]; Notes=; Capabilities=System.Management.Automation.PSObject[]; Drives=System.Management.Automation.PSObject[]; Synopsis=Provides access to X.509 certificate stores and certificates in Windows PowerShell.; DynamicParameters=@{DynamicParameter=System.Management.Automation.PSObject[]}; RelatedLinks=@{navigationLink=System.Management.Automation.PSObject[]}; Filters=System.Management.Automation.PSObject[]; Tasks=@{Task=System.Management.Automation.PSObject[]}; Name=Certificate; Category=Provider; Component=; Role=; Functionality=}

    I'm not a programmer (yet!) but I think this shouldn't be happening.

    6 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. Syntax changes when using help like .Synopsis

    When I add a help section to my script, the Get-Help cmdlet displays a different syntax. Here is a MWE:

    Require -Version 4.0

    function global:Test-Syntax {

    &lt;#
    
    .Synopsis
    Cmdlet tests ValidateSet
    #&gt;
    [CmdletBinding()]
    # parameter check
    param (
    [ValidateSet(&quot;one&quot;, &quot;two&quot;, &quot;three&quot;)]
    [string]$testparam
    )
    Write-Verbose &quot;`$testparam: $testparam&quot;

    }

    Get-Help Test-Syntax shows the following in syntax section:

    SYNTAX

    Test-Syntax [[-testparam] &lt;String&gt;] [&lt;CommonParameters&gt;]
    

    After I remove .Synopsis or the whole help section, I receive the following from Get-Help:

    SYNTAX

    Test-Syntax [[-testparam] &lt;string&gt; {one | two | three}]  [&lt;CommonParameters&gt;]
    

    I would like to have the second one, because a user directly get the information…

    6 votes
    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 →
  9. Better documentation on writing Providers in .NET

    Votes from Connect: 4

    Original Date Submitted: 5/9/2015 3:36:45 AM

    Description:
    Contact Information
    Handle: TofuBug
    Site Name: PowerShell
    Feedback ID: 1315394


    Problem Description:
    It would be a VERY nice thing to see an expanded set of documentation and examples related to writing PowerShell providers that go beyond the simple examples currently related to access databases.

    A webcast or training video would be awesome! Especially to go over things like

    -How to determine what type of provider would best suit my specific need with actual examples showing those reasons)
    -What are some things I can do to "think" about things through…

    6 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 →
  10. Dynamic Parameters and Positional parameters do not work as expected

    Problem description and example: https://stackoverflow.com/questions/45021674/how-do-you-specify-both-static-and-dynamic-positional-parameters-in-powershell

    1) It is not clear that the position attribute is relative to other parameters of the same type, and that static parameters always come before dynamic parameters.
    2) If you run get-help (full) on the function described in the link it will show the literal position assignment, not their position as PowerShell expects them (i.e. the static parameter is listed as position 3, when it is actually position 0)
    3) Tabbing through the options list (using ISE or PowerShell) behaves according to the literal position assignment, not their position as PowerShell expects them (i.e. if…

    5 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 →
  11. 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 →
  12. Documentation on Remoting Session Configuration is missing for PS5.0

    Help is missing on new options for WinRM remoting in PS 5.0

    get-help : No parameter matches criteria TranscriptDirectory.
    At line:1 char:1
    + get-help New-PSSessionConfigurationFile -Parameter TranscriptDirector ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (System.Manageme...CommandHelpInfo:ProviderCommandHelpInfo) [Get-Help],
    
    PSArgumentException
    + FullyQualifiedErrorId : NoParmsFound,Microsoft.PowerShell.Commands.GetHelpCommand

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

    We’ll send you updates on this idea

    2 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  13. Correction: about_requires

    In the about_requires documentation, when using a hashtable to provide a required module version or GUID, it's not clear that the values in the hash table need to be quoted. The example in the documentation is:

    Requires -Modules PSWorkflow, @{ModuleName="PSScheduledJob";ModuleVersion=1.0.0.0}

    and should be

    Requires -Modules PSWorkflow, @{ModuleName="PSScheduledJob";ModuleVersion="1.0.0.0"}

    5 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 →
  14. Typo on Page Export-WindowsDriver

    Typo on page: https://docs.microsoft.com/en-us/powershell/module/dism/export-windowsdriver

    Where: Examples
    Example 1: Export drivers from the running operationg system

    "operationg" rather than "operating"

    4 votes
    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 →
  15. Register-ArgumentCompleter is not documented

    The cmdlet Register-ArgumentCompleter is not documented.

    4 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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 →
  17. Remove-EventLog help appears nonsensical

    Someone on powershell team ought to have a look at this: https://technet.microsoft.com/en-us/library/hh849786(v=wps.640).aspx

    The syntax section 'source' parameterset doesn't show usage of the source param.

    The documentation text under "-InformationAction<System.Management.Automation.ActionPreference]>" and "-InformationVariable<System.String]>" are identical, and appear irrelevant to this command.

    (Also, for the love of god, can we have a bigger text entry box here?)

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  18. 3 votes
    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 →
  19. Help not updating for Whea module shipped with Windows Server 2016

    When running Update-Help on Windows Server 2016, failure occurs against the Whea module.

    Not sure if this is the correct UserVoice to lodge this against, sorry if it's not!

    PS C:\Windows\system32> update-help -force
    update-help : Failed to update Help for the module(s) 'Whea' with UI culture(s) {en-US} : Unable to retrieve the
    HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri property in the module manifest is valid or check
    your network connection and then try the command again.
    At line:1 char:1
    + update-help -force
    + ~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : ResourceUnavailable: (:) [Update-Help], Exception
    
    + FullyQualifiedErrorId : UnableToRetrieveHelpInfoXml,Microsoft.PowerShell.Commands.UpdateHelpCommand
    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  20. Cmdlet version compatibility

    We need to define with wich version of Powershel and which operating system cmdlets are compatible.

    Could we have this compatibility matrix for each cmdlet in the documentation and also in the help section of each cmdlet?

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base