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

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

    Problem 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
    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. Windows 8.1 - Powershell 4.0 Get-ADComputer -Properties * bug

    Votes from Connect: 72

    Original Date Submitted: 10/24/2013 11:12:10 PM

    Description:
    Contact Information
    Handle: jbarkl3y
    Site Name: PowerShell
    Feedback ID: 806452


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

    Problem Description:
    When running the Get-ADComputer command I run into the following. There has been a couple of posts on this error but they are related to Powershell 3.0 and can be fixed by changing your AD Schema to version 47. This bug still exists except now my Schema version is 47 and the bug still persists.

    Get-ADComputer : One or more properties are invalid.
    Parameter name: msDS-AssignedAuthNPolicy …

    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. Centralized Package Management for Power Shell

    Votes from Connect: 11

    Original Date Submitted: 9/10/2013 2:56:23 AM

    Description:
    Contact Information
    Handle: deadlydog
    Site Name: PowerShell
    Feedback ID: 800050


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

    Problem Description:
    Centralized Package Management would be a huge win for PowerShell. Modules are a great part of PowerShell, but writing scripts for other people/computers that depend on them can be problematic, as you can't guarantee that the modules will be installed on those computers. If PowerShell had something similar to Ruby Gems that would be great, where at the top of the script you specify the modules…

    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. Need a clean way to splat a hashtable against the various commands that take an ArgumentList

    Votes from Connect: 11

    Original Date Submitted: 8/16/2013 7:15:31 AM

    Description:
    Contact Information
    Handle: Keith Hill MVP
    Site Name: PowerShell
    Feedback ID: 797536


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

    Problem Description:
    There are several commands that have an ArgumentList parameter that take arguments bound for a PowerShell command. However, this parameter doesn't support splatting in any sort of easy and/or obvious way.

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

    Repro Steps:
    create a file $home\icmargs.ps1 with these contents:

    Param(

    [Parameter(Mandatory, Position=0)]
    
    [string]$Computername=$env:computername,
    [string]$log,
    [int]$newest=5

    ) …

    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. Get-Acl should produce nonterminating errors when it fails to access a file or directory

    Votes from Connect: 11

    Original Date Submitted: 7/20/2013 11:16:28 AM

    Description:
    Contact Information
    Handle: David Wyatt
    Site Name: PowerShell
    Feedback ID: 794618


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

    Problem Description:
    Get-Acl currently throws terminating errors anytime it fails to access a file or directory, even though it accepts an array of strings for the Path / LiteralPath parameters, and accepts pipeline input. Per Microsoft's guidelines for cmdlet error reporting (http://msdn.microsoft.com/en-us/library/windows/desktop/ms714412(v=vs.85).aspx), it seems like these should be non-terminating errors, as they are related to a specific input object, and should not prevent processing 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 →
  7. A cmdlet should be available for waiting for event log entries

    Votes from Connect: 17

    Original Date Submitted: 7/14/2013 10:21:11 PM

    Description:
    Contact Information
    Handle: Jan Egil Ring
    Site Name: PowerShell
    Feedback ID: 793869


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

    Problem Description:
    A cmdlet should be available for waiting for event log entries. Currently the user will need to manually configure an event subscription in order to listen for new event log entries.
    A new cmdlet (for example Wait-EventLog) should be available and capable of listening for new events in one or more specified event logs, both from local and remote computers.

    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 →
  8. 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 know. And if there's…

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

    7. ... and probably others I'm missing
    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. 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
    2)…

    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. 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 easier…

    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. 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 seen…

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

    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. 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 not…

    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. 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 by…

    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. 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 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 →
  17. 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 Studio…

    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. 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 753494 (…

    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. 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 this…

    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. 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 and…

    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