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. Workflows using multiple InlineScripts with the PSComputerName does not get correct variables from the workflow when using "$Using" scoping.

    Votes from Connect: 12

    Original Date Submitted: 6/12/2014 7:30:42 PM

    Description:

    Contact Information
    Handle: Trond Hindenes
    Site Name: PowerShell
    Feedback ID: 894721


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    When a workflow uses multiple "InlineScript {} -PsComputerName" against the same remote computer, and the inlinescript scopes variables using "$Using", the workflow doesn't read variables correctly. I have documented this in a example which is located at https://gist.github.com/trondhindenes/5249e861eb4bb98f5e15

    Basically, my example contains a workflow which connects to a domain controller using InlineScript and attempts to create a computer account in the domain. I…

    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 →
  2. Azure module conflict with Storage module

    Votes from Connect: 11

    Original Date Submitted: 6/5/2014 4:37:24 AM

    Description:
    Contact Information
    Handle: keseph
    Site Name: PowerShell
    Feedback ID: 888873


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:

    Using the latest versions of the Azure PowerShell module from the Web Platform Installer on an otherwise-clean image of Windows Server 2012 R2 Datacenter from the Azure Gallery, you cannot import the Storage module after importing the Azure module. You receive a long string of errors starting with:

    PS C:> Import-Module Storage
    Import-Module : Cannot process Cmdlet Definition XML for the following file:

    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Storage\Disk.cdxml.

    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. SCVMM and SCDPM PowerShell Modules can't work together

    Votes from Connect: 13

    Original Date Submitted: 5/14/2014 10:32:59 PM

    Description:
    Contact Information
    Handle: Мухаметшин Наиль
    Site Name: PowerShell
    Feedback ID: 873348


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

    Problem Description:
    Good day everyone!

    Very strange issue: when i try to load together Virtual Machine Manager 2012 and Data Protection Manager 2012 modules - script fails:

    PS C:\Windows\system32> ipmo virtualmachinemanager
    PS C:\Windows\system32> ipmo DataProtectionManager
    Import-Module : Could not load type 'Microsoft.Internal.EnterpriseStorage.Dls.Utils.AlertTypes.AlertEnum' from assembly
    'Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
    At C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\Modules\DataProtectionManager\DataProtectionManager.psm
    1:2 char:1
    + Import-Module (Join-Path $cmdletDllPath ObjectModelCmdlet.dll)
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          :
    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. Powershell ConvertTo-Json Error when has string with trailing backslash

    Votes from Connect: 13

    Original Date Submitted: 5/9/2014 3:59:33 AM

    Description:
    Contact Information
    Handle: George Mauer
    Site Name: PowerShell
    Feedback ID: 869768


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    [The following bit of code generates an error](http://stackoverflow.com/questions/23552000/convertto-json-throws-error-when-using-a-string-terminating-in-backslash)

    W:\surge\ogre> @{SolutionDir='W:\Surge\ogre\'} | ConvertTo-Json
    
    ConvertTo-Json : The converted JSON string is in bad format.
    At line:1 char:35
    + @{SolutionDir='W:\Surge\ogre\'} | ConvertTo-Json
    + ~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (System.Collections.Hashtable:PSObject) [ConvertTo-Json], InvalidOperationException
    + FullyQualifiedErrorId : JsonStringInBadFormat,Microsoft.PowerShell.Commands.ConvertToJsonCommand

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

    Repro Steps: …

    9 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 →
  5. Tear-off ISE tabs

    Votes from Connect: 17

    Original Date Submitted: 5/2/2014 4:25:16 PM

    Description:
    Contact Information
    Handle: Sean E Gray
    Site Name: PowerShell
    Feedback ID: 865384


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

    Problem Description:
    It would be incredibly useful to me if we could 'tear off' tabs from the ISE to make new windows, or drag and drop tags between ISE windows. Ideally, this would work in exactly the same was as it does in Internet Explorer.

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

    Repro Steps:
    Expected Results:

    12 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 →
  6. The last thing PowerShell needs to have full parity with BASH is a Sudo Equivalent

    Votes from Connect: 26

    Original Date Submitted: 4/5/2014 3:29:10 AM

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


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

    Problem Description:
    Hi all,

    With this awesome new addition of official Chocolatey (I cannot spell this word) support, we at The Scripting Guys group on FB realized that the only thing missing to have full feature parity with BASH is Sudo!

    Sudo has become equivalent with nerdy coolness and now that PowerShell is growing in support and fandom at such a pace, we need our own…

    14 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 →
  7. Add a .version to comment-based help, that can also be called from script

    Votes from Connect: 14

    Original Date Submitted: 3/27/2014 6:05:55 AM

    Description:
    Contact Information
    Handle: are bee en zed
    Site Name: PowerShell
    Feedback ID: 841437


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

    Problem Description:
    I'd love to be have a .version added through comment based help on scripts and functions. This would be especially valuable if it was visible from within the script or function itself as well, perhaps as a member of $MyInvocation or $PSCmdLet.

    e.g.

    .Version 1.0.12 (March 26, 2014)

    ...

    {
    write-host "This is the FooBar script version $($MyInvocation.Version)!"
    }

    output on host:

    This…

    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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. PowerShell must support calling Async APIs

    Votes from Connect: 57

    Original Date Submitted: 3/24/2014 10:15:46 AM

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


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

    Problem Description:
    Currently PowerShell has it's own systems (based on "Jobs") for doing asynchronous tasks -- while this was admirable in the .Net 2.0 and 3.0 era, in the modern .Net Framework we have new "IAsyncResult" task APIs, and they do not work in PowerShell at all.

    As more and more of the .Net Framework itself and 3rd party APIs begin to depend on Tasks, IAsyncResult,…

    12 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 →
  9. TCP connection hanging in CLOSE_WAIT when using Invoke-RestMethod with PUT or DELETE

    Votes from Connect: 37

    Original Date Submitted: 3/19/2014 9:07:48 PM

    Description:

    Contact Information
    Handle: ChrisBanck
    Site Name: PowerShell
    Feedback ID: 836732


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

    Problem Description:
    When issuing more than two Invoke-RestMethod commands with the PUT or DELETE method against the same server, the third one fails with error: "Invoke-RestMethod : The operation has timed out." Only after closing the powershell and reopening will allow a new Invoke-RestMethod command run successfully.
    This behavior was tested with two different servers, offering a REST API. GET and POST methods are not affected.

    Using "netstat…

    7 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 →
  10. 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 →
  11. Provide expected Comparison handling for DBNull

    Votes from Connect: 15

    Original Date Submitted: 3/9/2014 12:24:59 AM

    Description:
    Contact Information
    Handle: Cookie.Monster
    Site Name: PowerShell
    Feedback ID: 830412


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

    Problem Description:
    Greetings,

    First, my apologies. I have little development experience and thus may use improper terminology. My suggestion is to have PowerShell provide handling of System.DBNull values as one might logically expect.

    Current situation:
    if(System.DBNull::Value){"I would not expect this to display"} #The text displays.

    Expected situation:
    if(System.DBNull::Value){"I would not expect this to display"} #The text does not display

    How this affects users:
    When…

    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. Add #requires –runasadministrator ability to Module Manifest

    Votes from Connect: 10

    Original Date Submitted: 2/10/2014 11:05:45 PM

    Description:
    Contact Information
    Handle: Jonathan Medd
    Site Name: PowerShell
    Feedback ID: 817081


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

    Problem Description:
    PowerShell v4 adds the below new statement:

    requires –runasadministrator

    It would be useful to have this same ability available in a Module Manifest, e.g.

    Requires Run As Administrator

    RunAsAdministrator = $true

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

    Repro Steps:
    Add the below to your Module Manifest:

    Requires Run As Administrator

    RunAsAdministrator =…

    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 →
  13. Need dedicated parameter attributes to simplify proper path handling

    Votes from Connect: 10

    Original Date Submitted: 2/1/2014 8:36:30 AM

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


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

    Problem Description:
    It is too difficult to write an advanced function that correctly handles various forms of path input e.g.:

    'foo.txt' | MyAdvFunc
    gci | MyAdvFunc
    MyAdvFunc foo.txt
    MyAdvFunc foo.txt,bar.txt
    MyAdvFunc *.txt
    MyAdvFunc -literalpath foo[bar].txt

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

    Repro Steps:
    You have to write code like this:

    [CmdletBinding(DefaultParameterSetName="Path")]

    param(
    
    [Parameter(Mandatory,
    Position=0,
    ParameterSetName="Path",
    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 →
  14. 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 →
  15. Allow Move-Item/Copy-Item Commands to work Across Compatible Providers

    Votes from Connect: 22

    Original Date Submitted: 12/27/2013 7:41:19 AM

    Description:
    Contact Information
    Handle: Mark Michaelis
    Site Name: PowerShell
    Feedback ID: 812361


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

    Problem Description:
    Hi,

    I have created several providers that work for files (e.g. Skydrive, Dropbox, photo sights, etc.). I would like to be able to copy files from the file system up to these providers and vice-versa. Please provide some means so that the provider copy-item and move-item operations will work across providers. Without this feature the following error is returned:

     "Source and destination did not resolve
    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 →
  16. Auto-completed values, with spaces, do not have quotes around them

    Votes from Connect: 26

    Original Date Submitted: 12/24/2013 3:09:38 AM

    Description:

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


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    When auto-completing a parameter value that has spaces in it, PowerShell is not adding single or double quotes around the value to contain it as a single entity.

    PowerShell should, by default, add single or double quotes around auto-completed values, when spaces are contained in the value.

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

    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 →
  17. Desired State Configuration help file is named about_DesiredStateConfiguration instead of about_Desired_State_Configuration

    Votes from Connect: 3

    Original Date Submitted: 12/10/2013 12:59:41 AM

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


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

    Problem Description:
    The TOPIC line of the help file says "aboutDesiredStateConfiguration", which is consistent with the naming of other PowerShell help files, but the actual file name is aboutDesiredStateConfiguration.

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

    Repro Steps:
    Expected Results:

    Internal BugId: 6515

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Subfolder bug with command "copy-item c:\folder\ c:\folder2\ -recurse" when done more times

    Votes from Connect: 15

    Original Date Submitted: 11/28/2013 1:25:47 AM

    Description:
    Contact Information
    Handle: RoviLuca
    Site Name: PowerShell
    Feedback ID: 809855


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    Hello,

    i'm using powershell 4.0 and unexpected behaviour happened when i ran the command : "copy-item c:\folder\ c:\folder2\ -recurse" and in the folder is contained another folder.

    after first run it completes correctly:
    source: c:\folder\temp\test.txt
    Destination: c:\folder2\temp\test.txt

    Done again "copy-item c:\folder\ c:\folder2\ -recurse" and:
    Destination: c:\folder2\temp\temp\test.txt

    Maybe that copy item finding an already existing temp folder, instead of skipping or rewriting, goes inside and…

    6 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 →
  19. Running as administrator and running "update-help" fails to update the module 'AppBackgroundTask'

    Votes from Connect: 11

    Original Date Submitted: 11/21/2013 7:25:26 AM

    Description:
    Contact Information
    Handle: Gary Bonie
    Site Name: PowerShell
    Feedback ID: 809166


    Frequency: Always Happens
    Regression: I do not know if this issue existed previously

    Problem Description:
    All help updates correctly except the help for AppBackgroundTask.

    Update-Help : Failed to update Help for the module(s) 'AppBackgroundTask' with UI culture(s) {en-US} : The value of the HelpInfoUri
    key in the module manifest must resolve to a container or root URL on a website where the help files are stored. The HelpInfoUri
    'http://technet.microsoft.com/en-us/library/dn296421.aspx' does not resolve to a container.
    At…

    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. DCR: Dismount-WindowsImage needs a -Force parameter

    Votes from Connect: 21

    Original Date Submitted: 11/21/2013 4:02:13 AM

    Description:

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


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

    Problem Description:
    We've all been there before.

    It was a dark, stormy night, and from within your home shines a bright light of several computer monitors. Empty beer bottles litter the place, but nonetheless you keep typing away at your PowerShell console.

    You try to dismount a WIM file using image.exe, dism.exe, or now in the modern day, the "dism" module for Windows PowerShell, and you get…

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

Feedback and Knowledge Base