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. German installer for Microsoft Security Essentials has wrong messages

    Votes from Connect: 3

    Original Date Submitted: 1/2/2015 7:28:29 AM

    Description:
    Contact Information
    Handle: Roland Illig 2
    Site Name: PowerShell
    Feedback ID: 1073011


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

    Problem Description:
    The German version of the installer for Microsoft Security Essentials has two wrong translations:


    1. „Falls keine Firewall aktiviert ist, aktivieren Sie die Windows-Firewall (empfohlen).“

    This text should not even be in the installer in this form. Either the firewall is already activated, then the checkbox is useless and must not be shown at all. Or the firewall is not already activated, then the ”If…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. New-Object fails on a class whose GetEnumerator method throws NotSupportedException

    Votes from Connect: 3

    Original Date Submitted: 12/11/2014 7:11:16 AM

    Description:
    Contact Information
    Handle: Clint Stotesbery
    Site Name: PowerShell
    Feedback ID: 1051712


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

    Problem Description:
    I've run into a rare case. I can't use New-Object on a class whose GetEnumerator method throws NotSupportedException. System.Security.Cryptography.Xml.SignedInfo's GetEnumerator method throws a NotSupportedException: http://msdn.microsoft.com/en-us/library/system.security.cryptography.xml.signedinfo.getenumerator(v=vs.110).aspx

    The stack trace shows TypicalEnumerable as this method catches Exception and then rethrows it as an ExtendedTypeSystemException. I followed the complete stacktrace (hint: there are delegates involved not in the stack trace) and I can't figure out a way to…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add-Member cmdlet invokes ScriptProperty members when adding new member

    Votes from Connect: 3

    Original Date Submitted: 12/4/2014 3:29:25 AM

    Description:

    Contact Information
    Handle: Josef Nemec
    Site Name: PowerShell
    Feedback ID: 1045858


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

    Problem Description:
    When calling Add-Member over an object all ScriptProperty members are being invoked (script blocks from those properties are invoked). I found it during testing on PowerShell 5 preview (from Windows 10 preview build), but it also occurs in PS 4 (tested on Windows 8.1). It seems like it occurs only with System.Management.Automation.dll 6.3.9600.17400 and newer since it works for me on 8.1 machines with version…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. PS4.0: (Get-Variable MyInvocation -Scope 1).Value fails when powershell.exe run from MSBuild

    Votes from Connect: 3

    Original Date Submitted: 11/7/2014 10:07:44 PM

    Description:

    Contact Information
    Handle: sba
    Site Name: PowerShell
    Feedback ID: 1023770


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    I have a script that contains the following code:

    --------------8<----------------
    function Get-ScriptDirectory{

    $Invocation = (Get-Variable MyInvocation -Scope 1).Value
    
    try {
    Split-Path $Invocation.MyCommand.Path -ea 0
    }
    catch {
    Write-Warning &#39;You need to call this function from within a saved script.&#39;
    }

    }

    $scriptdir = Get-ScriptDirectory

    Set-Location $scriptdir -ErrorAction Stop
    --------------8<----------------

    (this originates from PS2.0 days)

    The script runs fine, except if it's run from MSBuild…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  5. Get-Command's System.Management.Automation.AliasInfo object should return an 'IntroducedIn' Property

    Votes from Connect: 5

    Original Date Submitted: 10/29/2014 11:53:04 PM

    Description:
    Contact Information
    Handle: Stephen Owen
    Site Name: PowerShell
    Feedback ID: 1014669


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

    Problem Description:
    Currently there is no easy method to determine which version of PowerShell a particular cmdlet will work within.

    Take the example of New-PSDrive. This command was introduced in PowerShell version 2.0, but the current Version property displayed when I run 'Get-Command New-PSDrive | Format-List' displays the value of 3.1.

    While this cmdlet was included in 3.0 and 4.0, it is misleading that the version of…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add -Wait and -Timeout parameters to Debug-Job

    Votes from Connect: 4

    Original Date Submitted: 10/6/2014 9:54:44 PM

    Description:
    Contact Information
    Handle: Trevor Sullivan [MVP]
    Site Name: PowerShell
    Feedback ID: 993661


    Frequency: Always Happens
    Regression: I don

    Problem Description:
    When writing a simple example to debug a PowerShell Background Job, the Background Job does not have enough time to initialize, before the Debug-Job command is invoked. Examine the following example:

    $ScriptBlock = {

    $Foo = 1;
    
    Wait-Debugger;
    $Foo++;
    };

    $Job = Start-Job -ScriptBlock $ScriptBlock;
    Debug-Job -Job $Job;

    When I run the above code in the PowerShell ISE, I receive an error message from Debug-Job, stating:

    "Debug-Job : The…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. Group Policy Powershell Script

    Votes from Connect: 28

    Original Date Submitted: 9/29/2014 7:28:00 PM

    Description:
    Contact Information
    Handle: Axel B. Andersen
    Site Name: PowerShell
    Feedback ID: 984532


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

    Problem Description:
    When running Powershell Logon or Logoff Scrips in GPO's the -NoProfile switch is not included in the command. This results in very long logon/logoff times, if users have filled their Powershell Profile with a lot of modules. It can take up to 10 minutes, if the profile needs user input to load.

    Product Studio item created by Connect Synchronizer due to creation of feedback…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide PowerShell ISE with better support for .Types.ps1xml and .Format.ps1xml

    Votes from Connect: 4

    Original Date Submitted: 9/15/2014 7:04:41 AM

    Description:
    Contact Information
    Handle: Derp McDerp
    Site Name: PowerShell
    Feedback ID: 972024


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

    Problem Description:
    Specifically:


    1. it should auto-complete the xml based on their doctypes

    2. it should recognize the interior of <ScriptBlock>s as PowerShell scripts rather than as text blobs and format and auto-complete those correctly.

    3. it should provide better outlining of the xml (e.g. if you put the caret on an end tag or start tag it should highlight the entire interior of that xml node)

    Product Studio item…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. Get-ChildItem -Recurse -LiteralPath doesn't find anything

    Votes from Connect: 4

    Original Date Submitted: 9/14/2014 4:22:48 PM

    Description:
    Contact Information
    Handle: sba
    Site Name: PowerShell
    Feedback ID: 971502


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

    Problem Description:
    When 'Get-ChildItem -Recurse -LiteralPath' is run against a directory whose name contains square brackets, no output is produced.

    Take a directory with the following contents:

    PS> cmd /c dir /s d:\tmp\dir[1]
    Volume in drive D is DATA
    Volume Serial Number is 0454-9DBF

    Directory of d:\tmp\dir[1]

    2014-09-14 09:23 <DIR> .
    2014-09-14 09:23 <DIR> ..
    2014-09-14 09:23 <DIR> subdir

               0 File(s)              0 bytes
    

    Directory of d:\tmp\dir[1]\subdir

    2014-09-14 09:23…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  10. Automatically add help links for all commands sharing the same noun

    Votes from Connect: 6

    Original Date Submitted: 9/11/2014 4:15:39 AM

    Description:
    Contact Information
    Handle: Kirk Munro
    Site Name: PowerShell
    Feedback ID: 968858


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

    Problem Description:
    Help documentation is more time consuming than it needs to be. My biggest pain point with help is that I like to include links to all other commands with the same noun to aid in discoverability. Sure, there is Get-Command -Noun ..., but it is useful in help documentation to include links to those commands as well. This also helps modern help tools link to…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. The call operator should support invoking .NET methods and also support splatting

    Votes from Connect: 5

    Original Date Submitted: 9/8/2014 11:00:11 PM

    Description:
    Contact Information
    Handle: Oisín Grehan
    Site Name: PowerShell
    Feedback ID: 966940


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

    Problem Description:
    As of v5, the call (&) operator cannot invoke .NET methods. With the implied deprecation of new-object in v5 by way of the "new(...)" synthetic static constructor method, this becomes a more obvious lack.

    One thing new-object has that the new v5 static method "new" does not is splatting support. Syntactically, this seems to make most sense when combined with support for invoking .NET methods…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  12. Desired State Configuration - Group resource

    Votes from Connect: 5

    Original Date Submitted: 8/21/2014 8:11:21 PM

    Description:
    Contact Information
    Handle: M.T.Nielsen
    Site Name: PowerShell
    Feedback ID: 951681


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    Adding a Domain user/group to a Local group, without providing explicit domain credentials, fails, even on a domain-joined machine with read-access to Active Directory.

    The MSFT_GroupResource.psm1 file in the PSDesiredStateConfiguration module has the following code for Test-TargetResource and Set-TargetResource (line 132 & 464):

    Create an instance of PrincipalContext.

    $credentialPrincipalContext = $null;
    if($PSBoundParameters.ContainsKey('Credential'))
    {

    $networdCredential = $Credential.GetNetworkCredential();
    
    $credentialPrincipalContext = New-Object System.DirectoryServices.AccountManagement.PrincipalContext -ArgumentList ([System.DirectoryServices.AccountManagement.ContextType]::Domain,
    $networdCredential.Domain, $networdCredential.UserName,
    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 →
  13. [System.Management.Automation.PSTypeNameAttribute] is undocumented

    Votes from Connect: 5

    Original Date Submitted: 8/16/2014 3:44:32 AM

    Description:
    Contact Information
    Handle: Derp McDerp
    Site Name: PowerShell
    Feedback ID: 947173


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

    Problem Description:
    1. The accelerator for [System.Management.Automation.PSTypeNameAttribute] should be changed from [PSTypeNameAttribute] to [ParameterType] to be consistent with PowerShell's naming conventions.


    1. The PSTypeNameAttribute is only obscurely documented in MSDN's System.Management.Automation.dll documentation instead of PowerShell's aboutFunctionsAdvanced_Parameters documentation.

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

    Repro Steps:
    Expected Results:

    Internal BugId: 8944

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. WMF 5 May Preview - PowerShellGet Nuget.exe won't launch when running as SYSTEM

    Votes from Connect: 4

    Original Date Submitted: 7/18/2014 5:22:57 AM

    Description:
    Contact Information
    Handle: R Jason Morgan
    Site Name: PowerShell
    Feedback ID: 922914


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    When you install the WMF 5 May preview on Windows 8.1 enterprise with update x64, KB2894868-x64, the nuget.exe file that gets placed at %winddir%\System32\config\systemprofile\AppData\Local\Microsoft\Windows\PowerShell\PowerShellGet\nuget.exe doesn't work. This issue is noticeable when you try and run the find and install *-Module cmdlets as SYSTEM. Specifically you notice it when trying to use them in DSC, like with cPSGet.

    I've added a link to…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Get-Help should provide the ability to exclude the path from all references to the script's name in the generated help

    Votes from Connect: 4

    Original Date Submitted: 7/16/2014 11:54:14 PM

    Description:
    Contact Information
    Handle: sba
    Site Name: PowerShell
    Feedback ID: 921889


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

    Problem Description:
    When I invoke:

    PS> Get-Help .\foo.ps1

    I get something like:

    NAME

    c:\users\sto\somedir\somesubdir\more\foo.ps1
    

    SYNOPSIS

    Some useful script
    

    SYNTAX

    c:\users\sto\somedir\somesubdir\more\foo.ps1 -logdir &lt;String&gt; -outputdir &lt;String&gt; [-debugmode]
    
    [&lt;CommonParameters&gt;]

    c:\users\sto\somedir\somesubdir\more\foo.ps1 -zipfile &lt;String&gt; -outputdir &lt;String&gt; [-debugmode]
    [&lt;CommonParameters&gt;]

    There should be a means to remove the (most often useless) "c:\users\sto\somedir\somesubdir\more&quot; paths, for instance when using the help text in documentation, or sharing it over email, the reader most likely won't have the script…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add-Type warns about no public members or properties on non-empty nested classes

    Votes from Connect: 3

    Original Date Submitted: 7/10/2014 7:08:54 PM

    Description:
    Contact Information
    Handle: Derp McDerp
    Site Name: PowerShell
    Feedback ID: 917335


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    PowerShell wrongly warns about the following valid code:

    <#PS#> Add-Type -TypeDefinition @'

    public static class Outer {

    public struct Inner {
    
    public int x;
    }

    }

    '@
    WARNING: The generated type defines no public methods or properties.

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

    Repro Steps:
    Expected Results:

    Internal BugId: 8884

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. Set-Acl Overwrites SACL when Run as Administrator

    Votes from Connect: 5

    Original Date Submitted: 7/4/2014 10:53:07 PM

    Description:
    Contact Information
    Handle: Rohn Edwards
    Site Name: PowerShell
    Feedback ID: 913134


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    The Set-Acl cmdlet overwrites the SACL (and appears to protect it) when called by an administrator (even when the security descriptor object contains no SACL information at all). This can cause a populated SACL to be completely cleared when a user is expecting just DACL modifications.

    This happens in PSv4. I think I recall seeing it in versions 2 and 3, but I…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. Get-ADComputer - Example 1 does not work

    Votes from Connect: 3

    Original Date Submitted: 6/24/2014 2:27:32 AM

    Description:
    Contact Information
    Handle: 8246jd
    Site Name: PowerShell
    Feedback ID: 903885


    Frequency: Always Happens
    Regression: No, this is new to the most recent version

    Problem Description:
    The help file contains the following example:

    PS C:&gt; Get-ADComputer -Identity "Fabrikam-SRV1" -Properties *

    When done in my environment with a Identity name in my AD I receive the following error:

    Get-ADComputer : One or more properties are invalid.
    Parameter name: msDS-AssignedAuthNPolicy
    At line:1 char:1
    + Get-ADComputer -Identity "Fabrikam-SRV1" -Properties *
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (Fabrikam-SRV1:ADComputer) [Get-ADComputer], ArgumentException
    
    + FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.ArgumentExcept
    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  19. Doubled double quotes in inline expressions within expandable strings

    Votes from Connect: 3

    Original Date Submitted: 6/23/2014 5:09:33 PM

    Description:
    Contact Information
    Handle: Ivan Akcheurov
    Site Name: PowerShell
    Feedback ID: 903486


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    "Fancy string - Hor""ray"

    outputs correctly (only one double quote): Fancy string - Hor"ray

    'Hor"ray'.Replace('"', '""')

    outputs correctly (two double quotes): Hor""ray

    "Fancy string - $('Hor"ray'.Replace('"', '"'+'"'))"

    outputs correctly (two double quotes): Hor""ray

    "Fancy string - $('Hor"ray'.Replace('"', '""'))"

    outputs INCORRECTLY (only one double quote): Fancy string - Hor"ray

    In my opinion, developers would intuitively expect, that within "$(inline expressions)" Powershell would treat text…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  20. Azure module conflict with Storage module

    Votes from Connect: 11

    Original Date Submitted: 6/5/2014 4:37:24 AM

    Description:
    Contact Information
    Handle: keseph
    Site Name: PowerShell
    Feedback ID: 888873


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:

    Using the latest versions of the Azure PowerShell module from the Web Platform Installer on an otherwise-clean image of Windows Server 2012 R2 Datacenter from the Azure Gallery, you cannot import the Storage module after importing the Azure module. You receive a long string of errors starting with:

    PS C:&gt; Import-Module Storage
    Import-Module : Cannot process Cmdlet Definition XML for the following file:

    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Storage\Disk.cdxml.

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base