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. 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 →
  2. Please add Management Framework v4 to the Update Catalog website

    Management Framework v5 is already available on the Update Catalog website and can be manually imported into a private WSUS instance for distribution (via WSUS or SCCM.) But v5 requires WMF v4 to be installed first.

    If WMF v4 was available in the Update Catalog then it could be imported into our private WSUS instance - and then we could deploy the WMF v4 as a prereq in the same reliable manner that we will be deploying WMF v5 to enterprise workstations.

    Please add WMF v4 to the Update Catalog website.

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

    We’ll send you updates on this idea

    2 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Bug? Invoke-DscResource and PsDscRunAsCredential in WMF5

    Hi Powershell Team,

    When I try to invoke the get method for a custom DSC resource using PsDscRunAsCredential, I get an error. This does not happen with either the set or test methods.

    The same custom resource works fine in a normal configuration though. I'm not sure if that's because the get method is not called there.

    Setup:
    Windows Server 2012 R2
    WMF5 RTM

    PS C:\Users\username> Invoke-DscResource -Name cWhoAmI -Method get -ModuleName cWhoAmI -Property $props -Verbose
    Invoke-DscResource : The PowerShell DSC resource returned results in a format that is not valid. The results from
    running Get-TargetResource should be in a…

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Thanks for the feedback Antonio! We will look into this and create a bug when we reproduce the issue. If we need more information we will request it from you here.

    Regards,

    MarkG

  4. Fix the remotedesktop module

    It seems that the RemoteDesktop module for RDS isn't working correctly. When trying to configure constrained endpoints in powershell it seems nearly impossible to restrict the session to only use the RemoteDesktop-module. It appears as if the modules isn't loading in a constrained endpoint due do the use of aliases in the modules.

    https://powershell.org/forums/topic/creating-jea-endpoint-for-remote-desktop-services/

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. DSC File Resource Recurse directory description is wrong

    The documentation for the DSC File Resource states that the Recurse is a) only valid for directories and b) only for sub-directories. This would imply that any files in a SourcePath would be copied. However, they are not. $Recurse has to be $true to pull files. If not, it just makes sure the directory exists.

    However, this requires that I have the whole recursive directory kept on my sourcepath as well vs. just a few files.

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add a favicon to the gallery

    The poor PS gallery tab and bookmark look so sad and grey... :,-(

    https://imgur.com/GwfMpzd

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

    We’ll send you updates on this idea

    investigating  ·  1 comment  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  8. Empty pipeline input has single $null item on slow ring build

    I noticed this a few fast ring builds ago and now see it on the slow ring build #14295. For functions that declare at least one parameter and are marked [CmdletBinding()], $input.count is 1 even when no input is sent either on the pipeline or via param. The one element is $null. So if you had code that checks to see if input is from the pipeline using something like if($input.count) and expect 0 to mean no pipeline input is present, that breaks. Here is an example function:

    function my-test {

    [CmdletBinding()]
    
    param(
    [String]$blah
    )

    write-host $input.count

    }

    Calling my-test…

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

    We’ll send you updates on this idea

    3 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. Publish-Script - Allow the use of RequiredModules [Bug]

    currently it is not possible to specify RequiredModules for a script published to a repository.
    This is awkward as it is quite likely for simple scripts to have a dependency on a module.

    The goal would be for the module to be installed automatically during install-Script; using the same logic and conditions as the a REQUIREDSCRIPT
    1) Interestingly there appears to be (partial) logic to test for RequiredModules, however this always fails as a .Name addtibute of the module cannot be found.
    and the syntax used in modules :
    .RequiredModules @{ModuleName = 'foo'; GUID = '1234565-2784-48bf-af15-70ba837a64d0'; ModuleVersion = '3.5'; } …

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

    We’ll send you updates on this idea

    investigating  ·  3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow "Invalid" keys in module manifests

    Just ... STOP worrying about keys that you don't care about.

    That way, 10 years from now, when all the old versions are gone, you'll finally be able to add keys to the manifest instead of stuffing more and more things into the module's PrivateData

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  11. JEA is not correctly showing VisibleAliases

    Aliases exported from imported module are not shown if role capabilities file contains VisibleAliases="*"
    Module
    <PRE>
    function Test
    {
    [Alias("TestAlias")]
    param()
    Write-Output 1
    }

    Export-ModuleMember -Function Test -Alias TestAlias</PRE>

    Without VisibleAliases set in RoleCapabilites file TestAlias is visible tested with Get-PsSessionCapability cmdlet but if VisibleAliases="*" appears in rolecapabilites file then TestAlias is not imported

    2 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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  12. BUG: WMF 5.0 RTM PSSession management throws WERFault exception

    v5.0.10586.122

    Connecting to an existing PSSession sometimes throws an exception error in the PS host. Using a script developed in WMF 4 to handle and re-use sessions now causes exceptions. I suspect something has changed in how WMF 5 handles sessions but I can't seem to get to the bottom of it.

    Fault bucket 125744894502, type 5
    Event Name: PowerShell
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: PowerShell_ISE.exe
    P2: 10.0.10586.122
    P3: System.ObjectDisposedException
    P4: System.ObjectDisposedException
    P5: SessionTransportManager+WSManAPIDataCommon.Dispose
    P6: Runtime.InteropServices.SafeHandle.DangerousAddRef
    P7: unknown
    P8:
    P9:
    P10:

    Attached files:
    C:\Users&lt;home>\AppData\Local\Temp\WERB13.tmp.WERInternalMetadata.xml

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\CriticalPowerShellISE.ea2d14b4791b93fd183c2c1c6aadb549cfe61527700000000_1ad123ac

    Analysis…

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

    We’ll send you updates on this idea

    investigating  ·  2 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow for publishing Profile Paths with Spaces

    when using publish module if a user has a space in their profile it fails to publish the module:
    PS C:&gt; Publish-Module -Tags Twitter -Name Posh-Tweet -NuGetApiKey xxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxx -Verbose
    VERBOSE: The specified assembly 'C:\Users\Carlos Perez\AppData\Local\PackageManagement\ProviderAssemblies\nuget-anycpu.exe' is installed at top level directory. However it is recommended that the assemblies should be installed under its ProviderName\Version folder.
    VERBOSE: Skipping previously processed provider 'NuGet'.
    VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
    VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'False'; IsRegistered = 'True'.
    VERBOSE: Publish Location:'https://www.powershellgallery.com/api/v2/package/'. …

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

    We’ll send you updates on this idea

    investigating  ·  6 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow LCM to accomodate module dependencies that get installed by earlier steps in the configuration

    Currently, if you have a configuration that installs a Windows feature then has another step that configures settings using a module that gets installed with that particular feature, the LCM fails its check because that module is not currently present on the node.

    For example, we have a configuration that installs the Web-Server role. There are later steps which use the xWebAdministration resource to configure things like Application Pools and Application Pool defaults. The problem is, when the LCM pulls the configuration and runs it's checks, it fails because the xWebAdministration resource uses cmdlets that are present in the WebAdministration…

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

    We’ll send you updates on this idea

    2 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Thanks for the feedback! This behavior is not by design and is not something I have ever seen before. We will look into it and get back with an answer or more questions.

  15. DSC File Resource - Modify Attributes Without Having to Delete

    File resource does not allow modifications to the target without first having to delete the target.

    Example:
    File HiddenFiles {

    DestinationPath = &quot;C:\Deploy\HiddenFile.txt&quot;
    
    Contents = &quot;HiddenFile Contents&quot;
    Attributes = &quot;ReadOnly&quot;,&quot;Hidden&quot;,&quot;System&quot;
    Ensure = &quot;Present&quot;

    }

    This should change the file attributes but it doesn't unless the file is manually deleted

    File resource does not allow modifications to the target without first having to delete the target.

    Example:
    File HiddenFiles {

    DestinationPath = &quot;C:\Deploy\HiddenFile.txt&quot;
    
    Contents = &quot;HiddenFile Contents&quot;
    Attributes = &quot;ReadOnly&quot;
    Ensure = &quot;Present&quot;

    }

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    investigating  ·  Mark Gray responded

    Josh,

    Thanks for the feedback. The file resource should set the attributes on an existing file. I have not been able to duplicate your issue in Windows 10. If you are still experiencing it, please add more details.

    Thanks,

    MarkG

  16. DSC ESENT Database management

    In a recent change, the new database for the on-prem Pullserver is now ESENT. Had a question for clarification.

    As an old Exchange guy, I have fears that immediately pop into mind. The logs files do not appear to be using circular logging (a way of self cleaning and restricting the amount of log files) – Is this true?

    If so, then I’m guess that the log files will continue to grow until the disk is full – which happens to exchange if the log files are not truncated. Is there a way today or in the future we will…

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

    We’ll send you updates on this idea

    investigating  ·  5 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  17. install-package policy execution

    To install packages with package manager it's necessary to set the execution policy. It's not said in the API, and I think is not trivial for someone who is learning poershell. In fact if you don't set the policy, you can install packages, there is not error neither feedback about it is not being really installed, and when the process finishes you can see the status as installed whe you do get-package <package-name>. It is very confusing

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

    We’ll send you updates on this idea

    2 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →

    This is an issue specific to the Chocolatey provider, which we acquired from that team. We will continue to work to get it resolved, but have no solution available at this time.

  18. Would be better if the exit command in PowerShell ISE only closed the current tab

    In PowerShell ISE, if you invoke the exit command, it closes the entire application regardless of how many tabs you have open. It would be better if the exit command simply closed the current tab (if you have multiple tabs open) or the entire application if you only have one runspace open. This would prevent accidentally closing runspaces that you wanted to go back to just because you used the all-too-familiar exit command.

    Also, making this change would address this issue within PowerShell ISE: when you invoke exit, the Runspace.StateChanged event is only fired for the current/active runspace (tab), even…

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

    We’ll send you updates on this idea

    2 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  19. KB3000850

    KB3000850 is not part of the Azure SQL 2014 image, and takes over an hour to install (often timing out) before DSC Extension can run. When update fails to install, causes DSC to fail as well. Easy to reproduce - configure VM image based on SQL 2014 and install DSC using templates.

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

    We’ll send you updates on this idea

    2 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Lastest Windows Insider Builds - Collection is read-only

    Attempting to import a module and run a PowerShell script is now resulting in an error about the collection is read-only.

    C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NoLogo -ExecutionPolicy Bypass -Command "[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1'"

    Results in
    C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1 : Collection is read-only.

    At line:1 char:210
    + ... ller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunn .
    ..
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     + CategoryInfo          : NotSpecified: (:) [chocolateyScriptRunner.ps1] 
    
    , NotSupportedException
    + FullyQualifiedErrorId : System.NotSupportedException,chocolateyScriptR
    unner.ps1

    This is new and unexpected behavior. Here is the issue log for more information: https://github.com/chocolatey/choco/issues/659

    Here is the actual script in question - https://github.com/chocolatey/choco/blob/0.9.9.11/src/chocolatey.resources/helpers/chocolateyScriptRunner.ps1 - it could be that we…

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

    We’ll send you updates on this idea

    investigating  ·  4 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base