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. Weekly tasks created via PowerShell using a different user immediately fail with error 0x41306

    Votes from Connect: 11

    Original Date Submitted: 1/18/2013 12:23:14 AM

    Description:
    Contact Information
    Handle: DanTup
    Site Name: PowerShell
    Feedback ID: 776801


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

    Problem Description:
    I've posted full details and a sample on StackOverflow here:

    http://stackoverflow.com/q/14378951/25124

    We're using PowerShell to create some scheduled jobs, but those that are set to be weekly instead of daily (using New-JobTrigger) always immediately fail with an exist code of 0x41306 when we try to execute them from the Task Scheduler UI. (However they seem to work in PowerShell if we use (Get-ScheduledJob x).Run()

    In…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 need…

    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 →
  3. Mandatory parameter prompts should accept variable input

    Votes from Connect: 10

    Original Date Submitted: 12/6/2012 12:15:54 AM

    Description:

    Contact Information
    Handle: Trevor Sullivan
    Site Name: PowerShell
    Feedback ID: 773554


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

    Problem Description:
    When writing a PowerShell function, script, or ScriptBlock that accepts named parameters, it is sometimes desirable to have the end user prompted for input. PowerShell input prompts work great for strings and integers, but fails with other data types (eg. bool, object).

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

    Repro Steps:
    function Test-Parameter {

    [CmdletBinding()]
    
    2 votes
    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 →
  4. PowerShell ISE v3 RTM: Intellisense does not show up consistently

    Votes from Connect: 34

    Original Date Submitted: 11/29/2012 11:18:12 PM

    Description:

    Contact Information
    Handle: Trevor Sullivan
    Site Name: PowerShell
    Feedback ID: 772736


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

    Problem Description:
    Intellisense does not consistently show up for all possible options. Consider the following scenario:

    You add the System.Speech assembly, and then want to reference a type in the System.Speech namespace. You might type the following code

    Add-Type -AssemblyName System.Speech; # Hit F8 to run this in ISE
    
    # Now type this next line out, and note how the System.Speech namespace is not
    # in
    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  5. PowerShell Should Ship all its Modules through a NuGet-like service

    Votes from Connect: 63

    Original Date Submitted: 11/29/2012 12:00:27 AM

    Description:
    Contact Information
    Handle: Joel 'Jaykul' Bennett
    Site Name: PowerShell
    Feedback ID: 772530


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

    Problem Description:
    The PowerShell team should ship it's modules via a Module Repository (like NuGet), and add commands for retrieving and installing modules to the Core module.

    They should use that mechanism to further separate releases from the Windows Server ship schedule. In fact, I suggest that you should externalize all of the non-core modules (everything which is currently loaded on-demand) to separate them from the…

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the suggestion. This is something we are investigating, but it requires some complex review to ensure proper operation across a range of Windows actions (eg: applying Windows updates). No decision has been made at this time.

  6. 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 →
  7. PSScriptRoot in ps1 script in PSv3 is empty in ISE

    Votes from Connect: 13

    Original Date Submitted: 11/1/2012 3:56:26 AM

    Description:
    Contact Information
    Handle: J Stangroome
    Site Name: PowerShell
    Feedback ID: 769359


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

    Problem Description:
    In the PSv3 documentation, $PSScriptRoot is now an automatic variable that is populated for both modules and ps1 scripts. It works from PowerShell.exe but not from the ISE

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

    Repro Steps:
    1. Create a new script (eg c:\test.ps1) with the contents: gv PSScriptRoot
    2. From PowerShell.exe, execute the…

    26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. Enable users to stop pipeline/making StopUpstreamCommandsException public

    Votes from Connect: 24

    Original Date Submitted: 10/25/2012 1:54:42 PM

    Description:
    Contact Information
    Handle: TobiasWeltner
    Site Name: PowerShell
    Feedback ID: 768650


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

    Problem Description:
    In PSv3, the pipeline can be stopped. Select-Object supports this with its -First parameter by raising a (non-public) StopUpstreamCommandsException exception.

    It is of great value to be able to stop the pipeline if your mission is completed before the emitting cmdlet has provided all results.

    In fact, the PS pipeline would gain a completely new "feature". Currently, it is a memory throttle and provides…

    19 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  9. ConvertFrom-StringData needs an -Ordered switch (to create an ordered hash table).

    Votes from Connect: 15

    Original Date Submitted: 10/21/2012 9:05:32 PM

    Description:
    Contact Information
    Handle: mjolinor
    Site Name: PowerShell
    Feedback ID: 768183


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

    Problem Description:
    ConvertFrom-StringData should have an -Ordered switch, to specify that you want to create an ordered hash table (to maintain the same order of elements as the string you're converting).

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

    Repro Steps:
    Expected Results:

    Internal BugId: 3895

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  10. PowerShell ISE consumes all memory on some systems when you run Invoke-WebRequest

    Votes from Connect: 15

    Original Date Submitted: 10/21/2012 3:38:47 AM

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


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

    Problem Description:
    Joel Bennett, myself, and Claus Nielsen can all reproduce this at will in our own independently managed environments. Others cannot reproduce it at all. On some systems when you invoke the Invoke-WebRequest command in PowerShell ISE and then later close PowerShell ISE, the process stays open even though the window closes, and much worse, the process memory consumption grows non-stop. I have twice…

    4 votes
    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. Select-Object's -First, -Last, -Skip, and -Unique parameters should not change the output type

    Votes from Connect: 10

    Original Date Submitted: 10/10/2012 11:44:45 PM

    Description:
    Contact Information
    Handle: Aleksandar Nikolić
    Site Name: PowerShell
    Feedback ID: 766908


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

    Problem Description:
    When you pipe something to Select-Object –First (or –Last, -Skip, and –Unique), the input and the output type should be the same, because you are not changing any member.

    And that’s true for every type (compare, for example, Get-Process | Get-Member and Get-Process | select -First 1 | Get-Member) , except for the PSCustomObject type. In case of the PSCustomObject type will be prefixed…

    2 votes
    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. 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 →
  13. In PowerShell V3 you can't redirect stderr to stdout

    Votes from Connect: 22

    Original Date Submitted: 10/1/2012 9:54:45 PM

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


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

    Problem Description:
    I should be able to execute an exe and redirect it's stderr output to stdout and then not get any error records generated. An error record is always generated even when 2>&1 is specified. This happens in both the console and ISE (at least it consistently fails).

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

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 parameters…

    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 →
  15. -ErrorAction Ignore is broken for Advanced Functions

    Votes from Connect: 15

    Original Date Submitted: 9/20/2012 4:25:37 AM

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


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

    Problem Description:
    If you create an advanced function and then invoke that function with -ErrorAction Ignore (a new value added to PowerShell 3), PowerShell sets $errorActionPreference to Ignore for the function scope before executing the body of the function. Yet in PowerShell 3, the value of Ignore is not supported for errorActionPreference, so you end up with a function that will return one replaced error…

    4 votes
    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. 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 →
  17. 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 →
  18. 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 →
  19. Events needed for module load/unload

    Votes from Connect: 10

    Original Date Submitted: 9/11/2012 2:44:04 AM

    Description:
    Contact Information
    Handle: Jason Shirk
    Site Name: PowerShell
    Feedback ID: 761976


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

    Problem Description:
    V3 added useful event handlers during command discovery including:


    • Pre command lookup

    • Post command lookup

    • Command not found

    It would be very useful to have similar events for modules:


    • Pre module lookup

    • Post module lookup

    • Module not found

    I'm most interested in post module lookup, but the others seem useful as well.

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

    2 votes
    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. ISE: Configurable tab size & convert tabs to spaces

    Votes from Connect: 107

    Original Date Submitted: 9/6/2012 7:43:17 PM

    Description:
    Contact Information
    Handle: HelgeKlein
    Site Name: PowerShell
    Feedback ID: 761424


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

    Problem Description:
    Any code editor really needs these two features:


    • configurable tab size (currently fixed at 4)

    • whether to convert tabs to spaces

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

    Repro Steps:
    Expected Results:

    Internal BugId: 3787

    13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base