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. 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 versions

    Problem 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…

    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. 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 version

    Problem Description:
    When using the Get-WmiObject cmdlet, lots of WMI metadata is included with the resulting objects including:

    1. WMI qualifier names/values (and qualifier metadata: IsAmended, IsLocal, PropagatesToInstance, PropagatesToSubclass, IsOverriable)
    2. System properties
    3. WMI class path (eg. \\servername\root\cimv2:Win32_ComputerSystem.Name="servername")
    4. WMI instance path (eg. \\servername\root\cimv2:Win32_ComputerSystem)
    5. ManagementScope options via "Scope" property
    6. WMI class-level information: __DERIVATION, __DYNASTY, __SUPERCLASS, _SERVER, __NAMESPACE, __PATH, __GENUS, __RELPATH, et…

    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. 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 version

    Problem 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 …

    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. 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 versions

    Problem 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…

    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 →
  5. 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 version

    Problem 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…

    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. Please add documentation in French language for PowerShell 3.0

    Votes from Connect: 114

    Original Date Submitted: 1/11/2013 5:50:47 PM

    Description:
    ********Contact Information********
    Handle: Arnaud Petitjean
    Site Name: PowerShell
    Feedback ID: 776313
    ***************************************

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

    Problem Description:
    * Unlike the previous versions (1.0 and 2.0) *, in PowerShell 3.0 there are no help files available in French language.

    I would consider missing help as top priority here. 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 -online Help every time 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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 version

    Problem 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 fails

    An 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…

    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. 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 version

    Problem 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…

    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. Invoke-RestMethod is truncating results

    Votes from Connect: 11

    Original Date Submitted: 9/29/2012 1:53:59 AM

    Description:

    ********Contact Information********
    Handle: Trevor Sullivan
    Site Name: PowerShell
    Feedback ID: 765261
    ***************************************

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

    Problem Description:
    The Invoke-RestMethod cmdlet in PowerShell v3 is truncating the results that come back from the Windows Azure REST API (querying for a list of ServiceBus queues), formatted as a XML AtomPub document. Within the results of the AtomPub document, only every *other* AtomPub "title" is returned from Invoke-RestMethod, rather than a complete result set.

    This behavior can be confirmed by using 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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 version

    Problem 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…

    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. 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 version

    Problem 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…

    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. 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 versions

    Problem 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…

    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 →
  13. 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 version

    Problem 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…

    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. 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 versions

    Problem 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…

    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. 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 previously

    Problem 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…

    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. Make module availability network-discoverable

    Votes from Connect: 10

    Original Date Submitted: 4/21/2012 9:43:26 PM

    Description:
    ********Contact Information********
    Handle: PowerShellDon
    Site Name: PowerShell
    Feedback ID: 738071
    ***************************************

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

    Problem Description:
    I suggest a Register-Module cmdlet, which can be used to register a given module, on a given machine, optionally within a given AD site, as being publicly available. Registration would be in DNS, likely as SRV records (much like an AD domain controller).

    "Get-Module -List" would then list local modules as well as modules advertised in DNS *for the user's current site* (or…

    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 →
  17. PowerShell (pre-) compiled Scripts

    Votes from Connect: 17

    Original Date Submitted: 3/26/2012 6:09:59 PM

    Description:
    ********Contact Information********
    Handle: Peter Kriegel
    Site Name: PowerShell
    Feedback ID: 733298
    ***************************************

    Frequency: Sometimes Happens
    Regression: I don't know if this issue existed previously

    Problem Description:
    Make it Possible to save PowerShell scripts in a compiled format (binary byte-code).

    Since PowerShell V 3.0 uses the DLR, every PowerShell V 3.0 script has to be compiled during the first run of the script. This may have a speed disadvantage. To speed up the execution of scripts, it may be useful to store scripts in a compiled binary format and run…

    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 →
  18. Filtering Filesystem objects based on a DateTime value

    Votes from Connect: 13

    Original Date Submitted: 3/5/2012 6:41:31 PM

    Description:
    ********Contact Information********
    Handle: Shay Levi
    Site Name: PowerShell
    Feedback ID: 728747
    ***************************************

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

    Problem Description:
    In PowerShell 3.0, the Test-Path cmdlet supports two new parameters: NewerThan and OlderThan. Both parameters accepts a DateTime object and return $true if the object's LastWriteTime is less/greater than the specified date.

    One of the tasks IT admins need to perform often is getting old files. It would be great if Get-ChildItem could support those parameters as well, allowing us to filter objects based…

    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 →
  19. $OutputRedirectionEncoding --- like $OutputEncoding

    Votes from Connect: 2

    Original Date Submitted: 2/4/2012 8:58:39 AM

    Description:
    ********Contact Information********
    Handle: S.K. _
    Site Name: PowerShell
    Feedback ID: 723240
    ***************************************

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

    Problem Description:
    Please modifiable Encoding of '>'.

    $OutputRedirectionEncoding = [Text.Encoding]::Default
    ls > file.txt # output as Default Encoding

    $OutputRedirectionEncoding = [text.encoding]::GetEncoding("euc-jp")
    ps > process.txt # output as EUC-JP

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

    Repro Steps:
    Expected Results:

    Internal BugId: 3324

    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 →
  20. V3 TypeAccelerator cmdlets

    Votes from Connect: 10

    Original Date Submitted: 2/3/2012 4:36:38 AM

    Description:
    ********Contact Information********
    Handle: jrich
    Site Name: PowerShell
    Feedback ID: 722645
    ***************************************

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

    Problem Description:
    cmdlets for working with the type accelerators would be nice, get/add/remove

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

    Repro Steps:
    using old method to get type accelerators no longer works
    [type]::gettype("System.Management.Automation.TypeAccelerators")::get

    Expected Results:
    a way to view type accelerators

    Internal BugId: 3323

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

Feedback and Knowledge Base