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. Add an option to Invoke-RestMethod to send HTTP Basic Authentication immediatly

    Votes from Connect: 11

    Original Date Submitted: 6/5/2012 2:35:42 PM

    Description:
    Contact Information
    Handle: Markus Essl
    Site Name: PowerShell
    Feedback ID: 746546


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

    Problem Description:
    Currently, when you use Invoke-RestMethod, it will only send http basic authentication headers when a access denied response is coming from the server. Quite some REST web services (like Jira) do not do that, because they (a) allow anonymous users as well as authenticated ones and/or (b) they want to avoid the unneccessary round trip.

    wget and curl have corresponding options to allow to…

    4 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 →
  2. Pipe operator corrupts raw binary data

    Votes from Connect: 20

    Original Date Submitted: 9/29/2011 4:41:03 AM

    Description:
    Contact Information
    Handle: Noldorin
    Site Name: PowerShell
    Feedback ID: 691490


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

    Problem Description:
    The pipe operator in PowerShell 2.0 (| and similarly >) corrupts binary data, so that it is impossible to pipe the standard inputs and outputs of traditional programs / EXEs through each other using binary data. This makes me resort to cmd.exe for many tasks and is really prohibiting adoption in my view.

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

    5 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 →
  3. Exclude parameter doesn't work on Get-ChildItem (ls alias) at root drive folder

    Votes from Connect: 3

    Original Date Submitted: 10/30/2015 7:31:59 PM

    Description:
    Contact Information
    Handle: Aurélien Lustrement
    Site Name: PowerShell
    Feedback ID: 1961824


    Frequency: PowerShell
    Regression: Open PS and change directory to "C:"
    Enter command "ls -Exclude Users".
    The command returns nothing

    Problem Description:
    Command "ls -Exclude Something" always returns nothing if executed at root drive folder. Perfectly works on any other subfolder.
    Tested on Win7 (PS 2.0 & 5.0) and Win10.

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

    Repro Steps:
    Open PS and change directory to "C:"
    Enter command "ls…

    3 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 →
  4. Connecting to Office 365 crashes WMF5 PowerShell.exe

    Votes from Connect: 6

    Original Date Submitted: 9/1/2015 2:33:33 PM

    Description:

    Contact Information
    Handle: Michel de Rooij
    Site Name: PowerShell
    Feedback ID: 1738789


    Frequency: PowerShell
    Regression: Open PowerShell session in Windows 10 build 10532
    $SessionEOP = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/ -Credential (Get-Credential) -Authentication Basic -AllowRedirection

    Import-PSSession -Session $SessionEOP
    <Crash>

    Problem Description:
    When connecting to certain Office 365 services, like EOP, the PowerShell.exe in WMF5 crashes (Windows 10 builds 10525 and 10532 show this behavior). When connecting to the /powershell-liveid URL, session gets redirected to /powershell-liveid?PSVersion=5.0.10525.0 (or 10532 for that build) then abends with a 'PowerShell has stopped working'.

    Product…

    3 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 →
  5. Unexpected behavior with UNC paths

    Votes from Connect: 4

    Original Date Submitted: 7/17/2015 7:14:42 PM

    Description:
    Contact Information
    Handle: sba
    Site Name: PowerShell
    Feedback ID: 1556276


    Frequency: PowerShell
    Regression: 1. Set the current location to somewhere in the registry
    cd HKLM:/Software/Microsoft


    1. Copy a file from one "drive-specified path" to another one:
      Copy-Item -Destination h:\tmp -Path E:\tmp\foo.csv

    This works fine.


    1. Attempt to copy a file from one "drive-specified path" to a UNC path:
      Copy-Item -Destination //nas/users/sba/tmp -Path E:\tmp\foo.csv

    This fails:

    Copy-Item : Source and destination path did not resolve to the same provider.
    At line:1 char:1
    + Copy-Item -Destination //nas/users/sba/tmp -Path E:\tmp\foo.csv
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo
    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  6. IIF Statement (If Shorthand)

    Votes from Connect: 4

    Original Date Submitted: 7/2/2015 7:46:53 PM

    Description:
    Contact Information
    Handle: TheRealMartin9700
    Site Name: PowerShell
    Feedback ID: 1497806


    Problem Description:
    It would be great if PowerShell could get IIF-like functionality:

    IIF -Condition (condition) -True (true value) -False (false value)

    IIF ($a -gt 5) "Its bigger!" "Too small"

    IIF ($a -lt 5) { $b = "Too small" } { $b = "bingo!" }

    There are plenty of times where we need to make a quick value check and either set a variable or set a variable and going through the full IF syntax is a pain.

    Product Studio…

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

    We’ll send you updates on this idea

    2 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  7. Import-Csv does not correctly detect encoding for UTF-8 files without BOM

    Votes from Connect: 6

    Original Date Submitted: 5/27/2015 3:02:36 AM

    Description:
    Contact Information
    Handle: electricmonk
    Site Name: PowerShell
    Feedback ID: 1371244


    Frequency: PowerShell
    Regression:

    Problem Description:
    Using Import-Csv on a UTF-8 file without a BOM will result in unrecognized extended characters

    Import-Csv -Encoding UTF8 does not work correctly either.

    Thanks to Joakim Svendsen for finding this:
    http://www.powershelladmin.com/wiki/Convertfrommostencodingstoutf8with_powershell

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

    Repro Steps:
    Expected Results:

    Internal BugId: 14513

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  8. Get-AuthenticodeSignature should work with catalog-signed files.

    Votes from Connect: 5

    Original Date Submitted: 2/9/2015 6:05:29 PM

    Description:
    Contact Information
    Handle: Bryan Lockwood
    Site Name: PowerShell
    Feedback ID: 1121526


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

    Problem Description:
    Get-AuthenticodeSignature works great for files with embedded Authenticode signatures. It should work just as well for those using signed catalog files (as defined on page 12 of "Code Signing Best Practices" at http://goo.gl/O3IbiE ). If signtool and sigcheck can do this, PowerShell should be able to!

    Thanks for considering this.

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

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  9. Still cannot merge to any output stream except stdout (1)

    Votes from Connect: 11

    Original Date Submitted: 4/16/2012 10:30:46 AM

    Description:
    Contact Information
    Handle: Joel -Jaykul- Bennett
    Site Name: PowerShell
    Feedback ID: 737038


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

    Problem Description:
    We need to be able to get a single output file with more than one of the output streams in it

    With PowerShell 3 Beta, we can now redirect each of the output streams, but we still can't merge them except into the stdout stream. We should be able to redirect output into the other streams, if only because this does not work (It…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  10. ConvertTo-JSON in PSv3 Beta does not support values containing double-quotes

    Votes from Connect: 22

    Original Date Submitted: 4/9/2012 12:35:27 PM

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


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

    Problem Description:
    Passing a hashtable with a string value containing a double-quote causes an error "The converted JSON string is in bad format."

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

    Repro Steps:
    $ht = @{ name = "single quotes (') are fine"; value = 'double quotes (") are not' }
    $ht | ConvertTo-Json

    Expected Results:
    {

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  11. PowerShell 3 should have (l)user updateable help

    Votes from Connect: 15

    Original Date Submitted: 3/5/2012 11:07:50 AM

    Description:

    Contact Information
    Handle: Joel -Jaykul- Bennett
    Site Name: PowerShell
    Feedback ID: 728689


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

    Problem Description:
    The current plan seems to be for PowerShell to ship with just SYNTAX help and require an administrator to use UPDATE-HELP before the inline help actually works.

    We need a way for non-administrators to get help on the box. I suggest you should default to downloading help to a shared location like C:\ProgramData\ that any user can update.

    Product Studio item created…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  12. PowerShell.exe can hang if STDIN is redirected

    Votes from Connect: 26

    Original Date Submitted: 7/2/2010 7:56:48 AM

    Description:

    Contact Information
    Handle: Jason Stangroome
    Site Name: PowerShell
    Feedback ID: 572313


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

    Problem Description:
    The Microsoft.PowerShell.ConsoleHost class constructs a M.PS.WrappedDeserializer passing the STDIN TextReader as one of the parameters. By default, the WrappedDeserializer will call ReadLine() on this STDIN TextReader and wait indefinitely, effectively hanging PowerShell and the calling process.

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

    Repro Steps:
    1. Create a simple PowerShell script.
    2. Create a…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  13. The $foreach iterator does not behave properly when processing tokens

    This is a bug in PowerShell 2.0 and later versions (i.e. not a regression).

    The $foreach iterator does not advance inside of a foreach loop when processing tokens that come from the PowerShell parser. For example:

    $Filter = 'foo -eq $false'
    foreach ($token in [System.Management.Automation.PSParser]::Tokenize($Filter,([REF]$null))) {

    if ($token.Type -ne [System.Management.Automation.PSTokenType]::Command) {
    
    continue
    }
    $foreach.MoveNext() &gt; $null
    $foreach.Current

    }

    If you run this, $foreach.Current is $null in the first iteration of the loop (this is wrong), and when you advance the iterator using MoveNext(), it then gets assigned to the first item in the collection.

    The workaround is to force the…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  14. Scripts need better isolation from the user's global session state

    Votes from Connect: 4

    Original Date Submitted: 11/28/2015 5:59:49 AM

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


    Problem Description:
    Right now it is too hard to write a 100% reliable script that can run in any particular user's PowerShell console. The crux of the problem is that global session state is so varied amongst individual users it is hard to anticipate all possibilities such as:

    •Command proxies
    •Imported (auto or explicit) modules that implement the same named command (but semantically different)
    •Redirected aliases
    •Defined variables you weren't expecting to be defined
    •Removed globals you…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add a new $PSModule standard variable

    Votes from Connect: 11

    Original Date Submitted: 11/16/2015 11:31:50 PM

    Description:
    Contact Information
    Handle: Stephen Owen
    Site Name: PowerShell
    Feedback ID: 2024074


    Problem Description:
    I find it very tiresome to have to specify $env:ProgramFiles\WindowsPowerShell\Modules in all of my modules. What a pain in the butt!

    Why not add a new standard variable called $PSModulePath or something similar, to make this automatic?

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

    Repro Steps:

    Internal BugId: 15978

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  16. New #requires parameters: -DotSource/-CallOperator, to allow script authors to indicate how the script must be invoked

    Votes from Connect: 8

    Original Date Submitted: 11/5/2015 5:13:13 AM

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


    Problem Description:
    Scripts are designed to be either dot-sourced, called, or much less often, both. Yet the vast majority of scripts out there don't have anything in place to make sure that they were invoked the right way. This can lead to a lot of confusion for script consumers that could be easily avoided.

    I would like to see the #requires statement expanded with the addition of two new parameters: -DotSource and -CallOperator. When a script is invoked,…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  17. Powershell 5 enum definitions

    Votes from Connect: 3

    Original Date Submitted: 8/11/2015 6:16:25 PM

    Description:
    Contact Information
    Handle: SamiKoskivaara
    Site Name: PowerShell
    Feedback ID: 1654123


    Frequency: PowerShell
    Regression: Create two enums, explicitly define a variable to have named enum type, assign value to that variable from another enum type. It does not give an error message that the value is not from the right enum type.

    Problem Description:
    If I define two enums 'Size' and 'PizzaType'

    Enum Size {

    Small
    
    Medium
    Large

    }

    Enum PizzaType {

    Margherita
    
    Vegetariana
    Peperoni

    }

    and then I want to explicitly say that my variable $a is [PizzaType] it…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  18. Invoke-WebRequest doesn't work with protocol-relative URLs

    Votes from Connect: 4

    Original Date Submitted: 7/8/2015 11:36:23 AM

    Description:
    Contact Information
    Handle: Trevor Sullivan [MVP]
    Site Name: PowerShell
    Feedback ID: 1519608


    Frequency: PowerShell
    Regression: 1. Use the Invoke-WebRequest command to call a protocol-relative URL
    2. Exception occurs: "iwr : Invalid URI: The hostname could not be parsed."

    Problem Description:
    Invoke-WebRequest doesn't work with protocol-relative URLs.

    http://www.paulirish.com/2010/the-protocol-relative-url/

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

    Repro Steps:
    1. Use the Invoke-WebRequest command to call a protocol-relative URL
    2. Exception occurs: "iwr : Invalid URI: The hostname could not be parsed."

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  19. WMF5 April PowerShellGet Publish-Module NuGetAPIKey is Mandatory

    Votes from Connect: 3

    Original Date Submitted: 6/9/2015 1:49:33 AM

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


    Frequency: PowerShell
    Regression: Register-PSRepository -Name LocalFolder -Source "$Pwd" -Publish "$Pwd"
    Publish-Module -Name C:\Users\Joel\Projects\Modules\Autoload -Repository LocalFolder -NuGetApiKey (Get-Random)

    Problem Description:
    The NuGetApiKey should not be mandatory on Publish Module, because it's not actually mandatory.

    For instance, if I'm publishing to a local folder, I don't need to specify a key!

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

    Repro Steps:
    Register-PSRepository -Name LocalFolder -Source "$Pwd" -Publish "$Pwd"
    Publish-Module -Name…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  20. Wildcard in registry path causing high cpu / long enumeration

    Votes from Connect: 3

    Original Date Submitted: 5/23/2015 6:40:05 AM

    Description:
    Contact Information
    Handle: jskiba
    Site Name: PowerShell
    Feedback ID: 1357781


    Frequency: PowerShell
    Regression: within powershell console

    navigate to "HKLM:\SOFTWARE\Classes*"
    run "gci" to find an available subkey name (eg: "OpenWithList")
    run "get-acl .\OpenWithList
    Verify CPU load time, and registry enumeration via procmon

    Problem Description:
    The asterisk “” character is valid as a registry key name. When navigating to the path “HKLM:\SOFTWARE\Classes*” and attempting to query ACL for values such as those in “HKLM:\SOFTWARE\Classes*\OpenWithList” , everything under “Classes” is queried, treating the “” as a wildcard and not a…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base