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. Change default behavior of module import

    Votes from Connect: 15

    Original Date Submitted: 3/31/2010 2:02:45 PM

    Description:
    Contact Information
    Handle: Martin Zugec
    Site Name: PowerShell
    Feedback ID: 546066


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

    Problem Description:
    Please re-consider default behavior of Import-Module. Current issue is that if you want to use namespaces (module\verb-noun), you still need to pay attention to name of your functions, because last one always wins.

    This forces us to use SCCM\Get-SccmObject always simply because of the fact that we never know which function we will overwrite. SCCM\Get-Object would overwrite Get-Object in this case. This makes modules less…

    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. switch statement should accept elements from the pipeline.

    Votes from Connect: 17

    Original Date Submitted: 12/9/2009 12:06:32 AM

    Description:
    Contact Information
    Handle: Xaegr
    Site Name: PowerShell
    Feedback ID: 518895


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

    Problem Description:
    When you need to send a array of objects to switch statement, you cannot just pipe it:
    PS > Get-EventLog security -newest 100 | Switch ($.EventId) {672 {$Id672++} 680 {$Id680++} }
    or
    Get-EventLog security -newest 100 | Select -expandProperty eventid | Switch {672 {$Id
    672++} 680 {$Id_680++}}

    You need to specify full expression as "argument" for a switch, like this:
    Switch (Get-EventLog security…

    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. v2: import-module failing should probably be a terminating error

    Votes from Connect: 12

    Original Date Submitted: 10/31/2009 4:57:26 AM

    Description:
    Contact Information
    Handle: x0n
    Site Name: PowerShell
    Feedback ID: 506808


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

    Problem Description:
    I see that trying to import a module where the module does not exist yields a non-terminating error. I think that really should be a full-blown terminating error; a failure to load a dependency like that really should stop the script. Having to use get-module -list available, or bump $erroractionpreference up to "stop" just to let try/catch work seems like a bit of a hack.

    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 →
  4. AutoHelp with Get-Help and Advanced Functions - needs improving

    Votes from Connect: 13

    Original Date Submitted: 12/27/2008 11:39:54 PM

    Description:

    Contact Information
    Handle: tfl
    Site Name: PowerShell
    Feedback ID: 389767


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

    Problem Description:
    I think the new auto-help stuff is fantastic. But it's a tad buggy and inconsistent.

    To demonstrate this, I've created a simle advanced function file (get-autohelp.ps1) attached. You will need to save this file then run get-help against it to see the errors I note.

    Here are the issues:


    1. You can not specify a .NAME section in auto-help. If you do, then the output…

    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 →
  5. Make all cmdlet parameters accept scriptblocks

    Votes from Connect: 14

    Original Date Submitted: 7/23/2008 3:57:45 AM

    Description:

    Contact Information
    Handle: Dmitry Sotnikov
    Site Name: PowerShell
    Feedback ID: 357352


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

    Problem Description:
    Some cmdlets accept scriptblocks for some parameters, while others don't. This is very inconsistent and confusing.

    On the one hand you can use this syntax for these examples: http://blogs.msdn.com/powershell/archive/2008/04/21/mindwarpingpower-cmdlets-scriptblock-parameters.aspx

    On the other, something like this would fail for no apparent reason:
    Get-DistributionGroup | Set-DistributionGroup -DisplayName {$_.name}

    This is actually (IMHO) a design flaw of PowerShell (unfortunately still present in v2 ) – you (if you…

    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. Support new-pssession with powershell direct

    The new copy-item options to use a possession to copy files is great, please also support making an new-pssession with a vm name so it can be used with copy-item

    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  ·  Flag idea as inappropriate…  ·  Admin →
  7. Documentation for Get-ScheduledTask does NOT indicate which versions of windows it applies to as EVERY component should.

    Documentation for Get-ScheduledTask does NOT indicate which versions of windows it applies to as EVERY component should.

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

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  8. Saving file in the remote session has failed with error: Exception has been thrown by the target of an invocation..

    Since a few weeks, when I edit a file in a PSSession in ISE I get this error message when I save the modifications:

    Saving file: C:\path\file.ps1 in the remote session has failed with error: Exception has been thrown by the target of an invocation..

    Not sure there is a link, but this problem appeared around the moment when this post has been published.

    https://devblogs.microsoft.com/powershell/windows-security-change-affecting-powershell/

    0 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 →
  9. BUG: Preserve the current directory name as stored in the filing system and not as entered by the user

    The PowerShell console uses the path as entered by the user and not as stored in the filing system. This is inconsistent with the Command Console behaviour and causes applications that rely on the correct casing of the path to fail. IMHO the console should be case insensitive when searching for fils system paths but should preserve the case when returning the file path.

    0 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. Powershell Core should have a nuget package for release

    It would be awesome if powershell core was released as a package on nuget.org as well as the regular means.

    The reason for this is build systems like cake build can have tools referenced via nuget packages and will pull them down as part of the build.

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

    We’ll send you updates on this idea

    survey  ·  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. Bug: Installing WMF4.0 then WMF5.0 on Win7 SP1

    Hello,
    I understand that on Windows 7 SP1-Machines we have to install WMF 4.0 before upgrading to WMF 5.0.
    On all our Windows 7 machines, before installing WMF 4.0 KB2819745, a sample output for Path Environmental Variable, getting with [Environment]::GetEnvironmentVariable(“Path”), looks like this:
    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
    After installing WMF 4.0 KB2819745, it looks like this:
    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;
    There is a multiple path to the Powershell.exe.
    After installing KB3134760 to upgrade to WMF 5.0, it’s getting even worse as path-variable looks like this:
    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;
    Is this a known issue?
    Thanks in advance
    Norbert

    0 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. Error in Keywords section of About_WorkFlowCommonParameters

    In the help text aboutWorkFlowCommonParameters, in the KEYWORDS section of the full text, it shows two about* files. The first (AboutWorkFlowCommonParameters) does not exist.

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

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
  13. Export-Csv - not quite right error message

    This command

    1 | Export-Csv

    gets an error

    > Export-Csv : You must specify either the -Path or -LiteralPath parameters, but not both.

    The command specifies none of the -Path or -LiteralPath, not both, as the message claims.

    PowerShell 5.0

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

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  14. New-ModuleManifest doesnt accept splatting because of the Path Parameter

    There is an issue with the Path Parameter that stops you using splatting for this cmdlet

    Although a workaround is to reference the object that you are using for splatting and then the property of that object this is not very friendly on the screen as it uses lots of screen space.

    Example is

    $psd1 = @{

    Path = 'C:\Test\Module.psd1' ;
    
    Author = 'Ryan Yates';
    CompanyName = '';
    Copyright = "© $(Get-date -Format yyyy) Ryan Yates";
    RootModule = 'TestModule.psm1' ;
    Description = 'Initial Description for TestModule;
    ProjectUri = [uri]$projectlink ;
    LicenseUri = [uri]'$ProjectLicense;
    ReleaseNotes = 'Initial starting release of this
    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
1 2 79 80 81 83 Next →
  • Don't see your idea?

Feedback and Knowledge Base