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. |
-
Need better formatting for type System.Management.Automation.ApplicationInfo
Votes from Connect: 12
Original Date Submitted: 4/11/2013 6:35:26 AM
Description:
Contact Information
Handle: Keith Hill MVP
Site Name: PowerShell
Feedback ID: 783409
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
The output of Get-Command for exes is pretty much worthless:PS> gcm mstest
CommandType Name ModuleName
Application MSTest.exe
I usually know it is an exe and I certainly know the name. What I want to know is the path for the exe. Don't make me go having to look for that when it's the most common thing folks want to know. And if there's…
1 vote -
DCR - CIM cmdlets not returning WMI metadata
Votes from Connect: 43
Original Date Submitted: 3/26/2013 1:25:17 AM
Description:
Contact Information
Handle: Trevor Sullivan
Site Name: PowerShell
Feedback ID: 782064
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
When using the Get-WmiObject cmdlet, lots of WMI metadata is included with the resulting objects including:- WMI qualifier names/values (and qualifier metadata: IsAmended, IsLocal, PropagatesToInstance, PropagatesToSubclass, IsOverriable)
- System properties
- WMI class path (eg. \servername\root\cimv2:Win32_ComputerSystem.Name="servername")
- WMI instance path (eg. \servername\root\cimv2:Win32_ComputerSystem)
- ManagementScope options via "Scope" property
- WMI class-level information: DERIVATION, DYNASTY, SUPERCLASS, _SERVER, NAMESPACE, PATH, GENUS, __RELPATH, et al.
- ... and probably others I'm missing …
1 vote -
Show-Command should (at least optionally) show default values
Votes from Connect: 12
Original Date Submitted: 3/5/2013 8:42:45 AM
Description:
Contact Information
Handle: Matthew Reynolds [MSFT]
Site Name: PowerShell
Feedback ID: 780634
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
The utility of Show-Command as a GUI front end enabling less skilled users to execute a task oriented script/function is impaired by the fact that default values cannot be shown.
Having the ability to display default values has two usability benefits:
1) It gives the user an idea of what they really need to configure and what they can leave alone
2)…1 vote -
Handling ownership on fileobjects
Votes from Connect: 11
Original Date Submitted: 2/27/2013 4:19:23 PM
Description:
Contact Information
Handle: Anders P
Site Name: PowerShell
Feedback ID: 780084
Frequency: Sometimes Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Functionality could be build into CMDlets could be Remove-Item, Copy-Item, Move-Item via the -force parameter, or if thats too risky, new CMDlets could be invented like Get-Owner or Set-Owner.I would really enjoy to see the integration of TakeOwn.exe, SubInACL.exe and iCacls.exe functionality into CMDlets
Windows transform so many windows-executables with different syntax into CMDlets, and that makes life as an admin so much easier…
1 vote -
Update-Help -SourcePath Failure on Computer Without Internet Connection
Votes from Connect: 16
Original Date Submitted: 1/21/2013 3:51:42 AM
Description:
Contact Information
Handle: Rohn Edwards
Site Name: PowerShell
Feedback ID: 777012
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
When running Update-Help using the -SourcePath parameter on a machine without an internet connection that has had the help updated already, the command fails with "Unable to connect to Help content. Make sure the server is available and then try the command again." The Save-Help and Update-Help combination works perfectly when updating the help on a system with no help installed. I've seen…1 vote -
Powershell in Windows RT fails to Run Implicit Remoting to Powershell 2.0
Votes from Connect: 11
Original Date Submitted: 11/5/2012 5:15:07 AM
Description:
Contact Information
Handle: Sean Kearney
Site Name: PowerShell
Feedback ID: 770035
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
When Executing a PS-Remoting Session from a Microsoft Surface Device with Windows RT using Powershell 3.0 to Powershell 2.0 on a remote server (with defined trusts in WinRM) Implicit remoting failsAn interactive session on the x64 Remote server works fine, but using an IMPORT-PSSESSION with -prefix parameter fails to produce any available cmdlets.
EXPORT-PSSESSION will produce a module on the local Windows…
1 vote -
Serious Get-ChildItem performance degradation in v3
Votes from Connect: 25
Original Date Submitted: 10/4/2012 10:09:17 PM
Description:
Contact Information
Handle: Kirk Munro
Site Name: PowerShell
Feedback ID: 766100
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
When you invoke Get-ChildItem in PowerShell 3.0 with a path that does not exist, it searches for all files instead (wtf?). If you combine that with -Recurse and -ErrorAction SilentlyContinue in a script, you're facing a huge performance degradation that won't be easy to spot. Consider the two transcripts below. They show that a single Get-ChildItem call using a path that does not…1 vote -
Accidental code execution in ISE by pressing F1
Votes from Connect: 12
Original Date Submitted: 9/19/2012 5:52:24 AM
Description:
Contact Information
Handle: TobiasWeltner
Site Name: PowerShell
Feedback ID: 763406
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
when you press F1 in ISE 3.0, the word the cursor is in is used as a keyword, and ISE executes this code:Get-Help "keyword" -ShowWindow
The problem here are the double-quotes. The keyword should be placed into single quotes. With double quotes, unexpected behavior and accidental code execution is possible.
See details section below for steps to repro.
Product Studio item created by…
1 vote -
Please add documentation in German language for PowerShell 3.0
Votes from Connect: 78
Original Date Submitted: 9/18/2012 6:29:36 PM
Description:
Contact Information
Handle: Peter Kriegel
Site Name: PowerShell
Feedback ID: 763246
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
In PowerShell 3.0 there are no help files available in German language. But I would consider missing help as top priority here. Most of the the east German peoples are never learned English (they learned Russia). Even for Peoples who can read English, there is a big danger to misunderstood something. Reading documentation in a foreign language can be very challenging.Calling the…
1 vote -
Help for Polish is missing.
Votes from Connect: 23
Original Date Submitted: 9/18/2012 3:37:35 AM
Description:
Contact Information
Handle: Bartek Bielawski
Site Name: PowerShell
Feedback ID: 763122
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
There is no help available in Polish both in previous versions and in current version of PowerShell. Actually - nothing is really localized to Polish (including menus in ISE, most of error messages). But I would consider missing help as top priority here: it's not big issue for people who are fluent in English, but reading documentation in foreign language can be challenging.Product Studio…
1 vote -
powershell v3-RC: specific comment line causes all scripts to fail
Votes from Connect: 11
Original Date Submitted: 7/13/2012 3:45:58 AM
Description:
Contact Information
Handle: RichardMcKenzie
Site Name: PowerShell
Feedback ID: 753494
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
A new bug has been introduced in powershell v3.0 - RC that does not exist in v3.0 CTP2.It appears that .ps1 scripts fail to execute and throw the runtime error "Executable script code found in signature block" if the following line appears in the script:
organizational unit filter
Product Studio item created by Connect Synchronizer due to creation of feedback ID 753494 (…
1 vote -
PowerShell 3.0 ISE needs '-version 2.0' option
Votes from Connect: 10
Original Date Submitted: 7/12/2012 9:58:36 PM
Description:
Contact Information
Handle: sba
Site Name: PowerShell
Feedback ID: 753454
Frequency: Always Happens
Regression: Yes, this happens in previous beta versionsProblem Description:
Given that PS3 will not be available for legacy operating systems, and that PS3 will not be deployed everywhere overnight, it is currently required to write scripts that are backwards-compatible with PS2.This can be achieved by:
- using 'Set-StrictMode-version 2.0'
- testing in a host created by running 'powershell -version 2.0'But it's not possible to develop using the ISE in PS2 mode.
IMVHO this…
1 vote -
PowerShell ISE v3 Release Preview: Intellisense does not show parameter name for parameter with existing value
Votes from Connect: 18
Original Date Submitted: 6/28/2012 2:16:48 AM
Description:
Contact Information
Handle: Trevor Sullivan
Site Name: PowerShell
Feedback ID: 751184
Frequency: Always Happens
Regression: I don't know if this issue existed previouslyProblem Description:
The PowerShell ISE v3 Release Preview does not show the parameter name in the Intellisense window, for a parameter that already has a value define (based on its position).Product Studio item created by Connect Synchronizer due to creation of feedback ID 751184 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=751184).
Repro Steps:
1. Open ISE v3 Release Preview
2. In a new script window, type a cmdlet and…1 vote -
Option for Format-Table to set color of a column
Votes from Connect: 16
Original Date Submitted: 2/27/2011 6:44:56 PM
Description:
Contact Information
Handle: Soós Tibor
Site Name: PowerShell
Feedback ID: 648076
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
There is currently an option for Format-Table to set the Label, FormatString, Width and Alignment of a table coulum. My suggestion is to extend these options with ForegroundColor and BackgroundColor of the column.Product Studio item created by Connect Synchronizer due to creation of feedback ID 648076 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=648076).
Repro Steps:
Expected Results:Internal BugId: 2825
1 vote -
v3 suggestion: PowerShell FileSystemProvider should support transactions (TxF)
Votes from Connect: 56
Original Date Submitted: 1/13/2011 12:03:33 AM
Description:
Contact Information
Handle: Oisin Grehan
Site Name: PowerShell
Feedback ID: 635713
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
From Vista onwards, Windows supports both a transacted registry (TxR) and transacted filesystem (TxF). With powershell v2, we got TxR support. For v3 or beyond, it would be great to have TxF support. A good example taking Pscx's archive cmdlets into account would be the following pipeline:PS> dir c:\logs\ -rec -inc *.log -usetx | write-zip -removeoriginal -usetx | move-item c:\archived_logs\ -usetx
This will recursively…
1 vote -
add Start-Transcript filters
Votes from Connect: 21
Original Date Submitted: 10/8/2010 4:46:21 PM
Description:
Contact Information
Handle: TobiasWeltner
Site Name: PowerShell
Feedback ID: 611703
Frequency: Always Happens
Regression: Yes, this happens in all previous versionsProblem Description:
Start-Transcript logs input and output. This creates huge log files.
There should be a switch that enables Start-Transcript to only log the inputs and omit the outputs. Optionally, there could be an indicator whether a command completed successfully, was aborted or raised an exception.Product Studio item created by Connect Synchronizer due to creation of feedback ID 611703 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=611703).
Repro Steps:
currently default behavior…
1 vote -
Get-Member and Online parameter
Votes from Connect: 16
Original Date Submitted: 8/9/2010 1:34:16 AM
Description:
Contact Information
Handle: Aleksandar Nikolic
Site Name: PowerShell
Feedback ID: 584518
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
I would like that Get-Member cmdlet supports Online parameter in V3 (similar to Get-Help in V2):Get-Process | Get-Member -Online
That command would open the .NET Framework page in MSDN (http://msdn.microsoft.com/en-us/library/system.diagnostics.process.aspx).
dir | Get-Member -Online
That command would open the .NET Framework pages in MSDN (http://msdn.microsoft.com/en-us/library/system.io.fileinfo.aspx and http://msdn.microsoft.com/en-us/library/system.io.directoryinfo.aspx).
Product Studio item created by Connect Synchronizer due to creation of…
1 vote -
PowerShell should implement an Unless operator
Votes from Connect: 15
Original Date Submitted: 7/21/2010 11:36:19 AM
Description:
Contact Information
Handle: bigjimslade80465
Site Name: PowerShell
Feedback ID: 576911
Frequency: Always Happens
Regression: No, this is new to the most recent versionProblem Description:
Currently, I need to do this:if(! ($bar)) { & foo}
I would like to be able to do this:
unless($bar) { & foo}
Product Studio item created by Connect Synchronizer due to creation of feedback ID 576911 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=576911).
Repro Steps:
Currently, I need to do this:if(! ($bar)) { & foo}
I would like to be able to do this:
unless($bar)…
1 vote -
ArgumentList parameter to Start-Job Incomplete
Votes from Connect: 15
Original Date Submitted: 5/29/2010 12:09:48 AM
Description:
Contact Information
Handle: Clint B.
Site Name: PowerShell
Feedback ID: 563695
Frequency: Always Happens
Regression: I don't know if this issue existed previouslyProblem Description:
The -ArgumentList parameter is described as passing arguments 'for the script that is specified by the FilePath parameter', which is true. But it also specifies the arguments to a scriptblock specified by the ScriptBlock parameter.Additionally the help says that "Because all of the values that follow the ArgumentList parameter name are interpreted as being values of ArgumentList, the ArgumentList parameter should be the…
1 vote -
v2 bug: test-path returns true for pure whitespace path.
Votes from Connect: 10
Original Date Submitted: 5/22/2010 3:29:42 AM
Description:
Contact Information
Handle: x0n
Site Name: PowerShell
Feedback ID: 560761
Frequency: Always Happens
Regression: I don't know if this issue existed previouslyProblem Description:
Calling test-path " " returns $true. I would expect $false unless a file named " " really did exist.Product Studio item created by Connect Synchronizer due to creation of feedback ID 560761 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=560761).
Repro Steps:
given there is no file or folder named " " in the root of C:\ps c:> test-path " "
TrueExpected Results:
ps> test-path " " …1 vote
- Don't see your idea?