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. |
-
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 versionsProblem Description:
The German version of the installer for Microsoft Security Essentials has two wrong translations:- „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 -
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 versionsProblem 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).aspxThe 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 -
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 versionsProblem 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 -
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 versionsProblem 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 -
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 donProblem 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 -
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 versionsProblem 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 -
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 versionsProblem Description:
Specifically:- it should auto-complete the xml based on their doctypes
- it should recognize the interior of <ScriptBlock>s as PowerShell scripts rather than as text blobs and format and auto-complete those correctly.
- 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 -
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 versionsProblem 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-9DBFDirectory of d:\tmp\dir[1]
2014-09-14 09:23 <DIR> .
2014-09-14 09:23 <DIR> ..
2014-09-14 09:23 <DIR> subdir0 File(s) 0 bytes
Directory of d:\tmp\dir[1]\subdir
2014-09-14 09:23…
1 vote -
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 versionsProblem 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 -
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 versionsProblem 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 -
[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 versionsProblem Description:
1. The accelerator for [System.Management.Automation.PSTypeNameAttribute] should be changed from [PSTypeNameAttribute] to [ParameterType] to be consistent with PowerShell's naming conventions.- 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 -
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 versionProblem 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 -
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 versionsProblem 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 <String> -outputdir <String> [-debugmode]
[<CommonParameters>]c:\users\sto\somedir\somesubdir\more\foo.ps1 -zipfile <String> -outputdir <String> [-debugmode]
[<CommonParameters>]There should be a means to remove the (most often useless) "c:\users\sto\somedir\somesubdir\more" 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 -
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 previouslyProblem 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 -
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 versionProblem Description:
The help file contains the following example:PS C:> 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.ArgumentExcept1 vote -
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 previouslyProblem 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 -
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 previouslyProblem 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:> 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 -
SCVMM and SCDPM PowerShell Modules can't work together
Votes from Connect: 13
Original Date Submitted: 5/14/2014 10:32:59 PM
Description:
Contact Information
Handle: Мухаметшин Наиль
Site Name: PowerShell
Feedback ID: 873348
Frequency: Always Happens
Regression: Yes, this happens in previous released versionsProblem Description:
Good day everyone!Very strange issue: when i try to load together Virtual Machine Manager 2012 and Data Protection Manager 2012 modules - script fails:
PS C:\Windows\system32> ipmo virtualmachinemanager
PS C:\Windows\system32> ipmo DataProtectionManager
Import-Module : Could not load type 'Microsoft.Internal.EnterpriseStorage.Dls.Utils.AlertTypes.AlertEnum' from assembly
'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
At C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\Modules\DataProtectionManager\DataProtectionManager.psm
1:2 char:1
+ Import-Module (Join-Path $cmdletDllPath ObjectModelCmdlet.dll)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
…+ CategoryInfo :
1 vote -
Update-Help shouldn't require running as admin
Votes from Connect: 12
Original Date Submitted: 3/12/2014 7:14:43 PM
Description:
Contact Information
Handle: Stephen Owen
Site Name: PowerShell
Feedback ID: 832660
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Hi all,I think that it is a constant annoyance having to update-help on new servers or workstations. In my opinion, there is really no reason that Update-help should require me to relaunch Help as an admin user, as that requires launching a separate instance of the console.
THanks,
Product Studio item created by Connect Synchronizer due to creation of feedback ID 832660 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=832660)…
1 vote -
Install-WindowsFeature docs incomplete
Votes from Connect: 28
Original Date Submitted: 1/4/2014 6:13:19 AM
Description:
Contact Information
Handle: PowerShellDon
Site Name: PowerShell
Feedback ID: 812950
Frequency: Always Happens
Regression: Yes, this happens in previous released versionsProblem Description:
Install-WindowsFeature is missing important instructions and caveats with regard to the -Source parameter.First, it does not provide examples of the correct path syntax when pointing to a WIM image (e.g., "wim:/c:/sources/install.wim:3", including an explanation of the numeric index). The help does suggest pointing to a WIM image, but without the right path syntax, it's hard to get it to actually work. The numeric index is…
1 vote
- Don't see your idea?