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. Help for FileSystem dynamic parameters of Get-ChildItem are broken

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

    PS C:> (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:> $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:>…

    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 →
  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. 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 →
  5. CheckPoint-Workflow points to non-existent help for how to checkpoint

    At the bottom, this URL goes to a "This topic is no longer available":

    SEE ALSO

    How to Add Checkpoints to a Workflow (<a rel="nofollow noreferrer" href="http://go.microsoft.com/fwlink/?LinkId=261993">http://go.microsoft.com/fwlink/?LinkId=261993</a>)
    

    1 vote
    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 →
  6. 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.

    17 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 →
  7. 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 →
  8. Get-FileHash Help is missing, and fwlink is wrong

    Despite the existence of great help online
    https://technet.microsoft.com/en-us/library/dn520872.aspx

    The in-the-box help for Get-FileHash is missing, and the fwlink that's in the HelpUrl for the function goes nowhere...

    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 →
  9. Fix the requirements on the download page please

    https://www.microsoft.com/en-us/download/details.aspx?id=50395

    The download page is where most admins will grab the installer for WMF5. Unfortunately, it only lists .NET Framework 4.5 or above. Windows 7 has an unenforced requirement for WMF4 to be installed first, per https://msdn.microsoft.com/en-us/powershell/wmf/5.0/requirements?f=255&MSPPError=-2147217396

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  10. PowerShell SDK is missing XML comment files

    It's really awesome that there are SDK assemblies in NuGet for PowerShell now, but...

    We need xml documentation. It's traditional to include the XML file for each assembly you ship in NuGet, and none of them were included in any of the packages...

    P.S. Did you really mean to release those under MIT?

    1 vote
    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 →
  11. PSv5 ConvertTo-Html online help shows ConvertTo-Xml instead

    The v5 online help for ConvertTo-Html shows the content for ConvertTo-Xml instead. Switching to v4 or v3 show the correct content. All languages seem to affected

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

    We’ll send you updates on this idea

    In Queue  ·  0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 →
  13. Get-ChildItem has misleading command syntax

    Current discrepancy:
    User can specify the -File switch to indicate only files which to be targeted. However, if you do not specify wildcards in the -Path value to specifically target files, this -File switch returns nothing.

    Working example:
    Get-ChildItem -Path ("{0}*." -f $projectDir.FullName) -File -Include ".csproj")

    Non-Working example:
    Get-ChildItem -Path ("{0}" -f $projectDir.FullName) -File -Include "*.csproj")

    Why does it require explicitly targeting files when the whole nature of this is to target files within a path? Why do I have to do the same thing twice?

    2 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 →
  14. Consolidate all of the Powershell 'documentation' web pages into a downloadable document that can be searched by keyword.

    Consolidate all of the Powershell 'documentation' web pages into a downloadable document that can be searched by keyword.

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  15. Bug in description of ComputerName parameter for Install-WindowsFeature

    Documentation says "Installs one or more available on a specified remote computer. "

    Should say something among the lines: "Installs one or more available roles, role services, or features on a specified remote computer."

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  16. epoch time

    So I was able to finally figure out how to convert time to epoch time for talking with linux systems, but I don't feel it should be this difficult and/or hard to find documentation.

    $epochTime = ( get-date(get-date).ToUniversalTime() -UFormat "%s" )

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  17. urgh: can't you put up a picture of all the different profile precedent rules - very confusing.

    Short Version: Please put up a diagram showing exactly which profiles get called by which hosts in which order !

    I have recently starting using ISE - having previously just used the Console. Now I am using both. So they apparently have two different profiles. So I tried to copy my existing one - but then (because I use aliases) I get a 'double-loading' effect. Also I'm on powershell 4.0, but my $pshome still have v1.0 in the path ? Additionally: when I tried editing a profile.ps1 from a Windows explorer - it was showing as an empty file in…

    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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  18. Needs a robust interactive help

    It really needs some sort of interactive help option that can be turned on where it gives the user a heads up display of what options are available and what arguments, if any, are required for the command... Sort of like how VBA for Office worked or the Visual Studio editor... Complete with a mouse hover detailed description and links like the normal Windows Help has...

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

Feedback and Knowledge Base