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. Start-Transcript: poor error message on a bad -Path

    The following command

    Start-Transcript \zz*\z.log
    

    produces an error

    Start-Transcript : Transcription cannot be started.
    
    At C:\tmp\_160209_203322\test.ps1:2 char:1
    + Start-Transcript \zz*\z.log
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [Start-Transcript], PSInvalidOperationException
    + FullyQualifiedErrorId : CannotStartTranscription,Microsoft.PowerShell.Commands.StartTranscriptCommand

    The reason of the error is a bad -Path argument.
    It is difficult to get this from the error information.

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  2. v5 regression: Get-ChildItem -LiteralPath -Recurse ignores -Include and gets all items

    I have just installed Windows Management Framework (WMF) 5.0 RTM on my Windows
    7 SP1 and tested it. Get-ChildItem -LiteralPath -Include -Recurse started to
    work differently in v5.

    This command

    Get-ChildItem -Path $PSHOME -Include *.exe -Recurse
    

    gets expected powershell.exe and powershell_ise.exe.

    The same command with -LiteralPath instead of -Path

    Get-ChildItem -LiteralPath $PSHOME -Include *.exe -Recurse
    

    in PowerShell v5 RTM unexpectedly gets all items in $PSHOME.

    I cannot test this with previous versions right now (by the way,
    PowerShell.exe -Version 2 seems to have the same issue in v5 RTM). But I
    believe in PowerShell v3 and v4 this…

    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  3. Bug - PSv5 Workflow fails on downlevel systems

    There appears to be a problem when invoking a workflow created on a v5 computer but running an remote computer with earlier versions.

    Here is a transcript demonstrating the problem running in a new PowerShell session with no profiles loaded. It appears that the workflow is being generated with the new common parameter which doesn't exist on older computers.


    Windows PowerShell transcript start
    Start time: 20160118100405
    Username: WIN81-ENT-01\Jeff
    RunAs User: WIN81-ENT-01\Jeff
    Machine: WIN81-ENT-01 (Microsoft Windows NT 6.3.9600.0)
    Host Application: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noprofile
    Process ID: 10252
    PSVersion: 5.0.10586.51
    PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0.10586.51
    BuildVersion: 10.0.10586.51
    CLRVersion: 4.0.30319.34209
    WSManStackVersion: 3.0
    PSRemotingProtocolVersion: 2.3 …

    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 →
  4. Bug: PSWA 5.0 ignores Set-Location in profile script

    I had previously setup PSWA 4.0 that executed a profile.ps1 script at logon to resize the console, add snapins, and drop the user into a UNC network location where the scripts are contained. I upgraded to PS 5.0 on Friday and now when users login, all elements of the script work EXCEPT Set-Location. I have tried to cd to a local path instead of UNC, which also did not work. There are no errors or warnings. If I execute the startup script after I am already logged in to the PSWA, it executes properly and changes to the UNC path.…

    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. #region / #endregion code folding tokens in ISE should not be case sensitive

    Votes from Connect: 17

    Original Date Submitted: 5/23/2012 8:29:13 PM

    Description:
    Contact Information
    Handle: HalR
    Site Name: PowerShell
    Feedback ID: 743272


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

    Problem Description:
    I've been using #REGION/#ENDREGION tokens in my code for some time to trigger code folding in various editors (e.g. PowerShellPlus and PowerGUI). The new v3 ISE supports this too which is great--but it's case sensitive for some reason. I consider that a bug and would love to see it made case-insensitive.

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

    24 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. DSCPullServer needs improved client registration

    The DSCPullServer is basically a knock off of Puppet-OpenSource project .. so let's finish some of the critically missing tools

    I'm talking mainly about client registration (or lack thereof).

    How it's done in puppetOS:
    1. Make sure "puppet" CNAME is in DNS
    2. Install puppet_agent (no questions asked, just install)
    3. On the puppet server, use "puppet cert list" to see pending machines, and "puppet cert sign" to add it.

    That's it I'm ready to write manifests and go for it. It issues the cert, tracks the box, basically handles everything.

    Compare that to DSC:
    1. Create a CName to…

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Set-ClusteredScheduledTask should have an -Enable argument

    Set-ClusteredScheduledTask has a -Disable argument but no -Enable. My method of enabling a clustered scheduled task is fairly elaborate: modify the task via Task Scheduler, export the task to XML, and run Powershell to unregister the task and then register it from the exported XML. Being able to disable and enable these tasks via Powershell would be a significant help.

    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 →
  8. WMF 5.0 executing ScriptBlock over WinRM 2.0 fails

    Following c
    Code below will output only 1 but not when source from WMF 5.0 computer to WinRM 2.0

    Invoke-Command -ComputerName Windows2008box -ScriptBlock {Write-Output 1; Write-Output 2 }

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/679bb655-4322-445c-8b7d-1f736c105489/can-somebody-verify-if-this-is-a-bug-in-wmf-50?forum=winserverpowershell

    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 →
  9. PowerShell ISE should highlight commands that will be stopped on with command breakpoints

    It is very useful to set a command breakpoint in PowerShell when debugging. When a command breakpoint is set though, ISE does not provide any visual cues that it will stop on a breakpoint for that command. It should parse the AST that it already has and identify any commands that will trigger a command breakpoint, highlighting them with an alternate color or style than traditional breakpoints and only highlighting the commands, not the entire line, so that the breakpoints are visible in the editor, even if they cannot be changed using the editor itself.

    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  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow multiple values for ConfigurationModeFrequencyMins of LCM (Local Configuration Manager)

    With a single value, now all settings in the DSC configuration are re-applied at the same interval.

    I would like to have some settings (may be non-critical) once , to be re-applied less frequently.

    This flexibility shall make LCM less stressed as well.

    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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  11. PowerShellGet should automatically update PSModulePath on PowerShell 3.0

    When you run Install-Module to install one or more modules from the PowerShell Gallery, by default those modules will be placed into %ProgramFiles%\WindowsPowerShell\Modules, yet on PowerShell 3.0, that path is not part of PSModulePath by default. That path only became part of the default PSModulePath in PowerShell 4.0 or later.

    This is a big problem for PowerShell 3.0 because after a module is "installed", the commands within that module won't be discoverable and the module will not autoload without manual intervention (loading the module via the path or manual update of the PSModulePath environment variable).

    PowerShellGet should address this problem…

    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  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Issue with DSCFileDownloadManager Credentials

    So, it seems as though in WMF 5.0 there is a regression in functionality. In WMF 4.0, you could set up a DSCFileDownloadManager and Credential to have a Target Node contact a Pull Server SMB Share and download new mof files and resources. Everything worked perfectly including Certificate based encryption of the credentials. However, in WMF 5, it seems as though the LCM of the Target Node attempts to contact the SMB Share Anonymously, even in credentials are provided. Now, in a Non domain joined environment, you can just provide EVERYONE full control and then change Local Security Policy such…

    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 →
    planned  ·  Zachary Alexander responded

    This bug has been identified and the issue has been resolved. The fix will be available in future releases, including the Windows Insider Fast Ring preview

  13. The parser for variable names isn't implemented according to spec

    According to the PowerShell language specification, the following variable names are illegal but the current PowerShell implementation accepts them:

    $:: = 3
    $::a = 3
    $variable:foo: = 5
    $:a:3 = 3

    which means that things like "$:a:3" currently act as "${:a:3}" rather than the expected "${:a}:3".

    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 →
  14. PowerShell should support .Net extension methods

    Votes from Connect: 35

    Original Date Submitted: 9/22/2010 9:56:58 PM

    Description:
    Contact Information
    Handle: Joel "Jaykul" Bennett
    Site Name: PowerShell
    Feedback ID: 603415


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

    Problem Description:
    Currently PowerShell has it's own system (based on type.ps1xml files) for creating extension methods -- while this would have been admirable in the .Net 1.1 or 2.0 era, in the modern .Net Framework we already have Extension methods, and they do not work in PowerShell.

    As more and more of the .Net Framework itself and 3rd Party APIs begins to depend on extension methods…

    19 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 →
  15. Gallery Issue - LicenseURI & ProjectURI aren't added if not in the PSD1 file when Publish Module is used to Publish to Gallery

    When using Publish-Module you are prompted to provide a LicenseURI & ProjectURI - Or at least you should be according to Documentation on powershellgallery.com

    If you havent added this information the the PSD1 file then this information isnt passed to the Gallery Item used by Find-Module or the PowerShell Gallery

    Examples include the following
    ThePSGallery-Working
    ThePSGallery-Broken

    And the psd1 files are located at https://github.com/kilasuit/ThePSGallery

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

    We’ll send you updates on this idea

    3 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. BUG: Powershell -NoExit does not dot source when run from VB2010

    Just upgraded from Windows 7 to Windows 10 and encountered a bug in Powershell 5.
    When using Process.Start from VB2010 to run Powershell command (even one as simple as "dir") works as expected. If however you use the -NoExit switch Powershell fails to dot source my global file, but instead tries to load it as a module - and throws an error. The same commands typed on the Powershell consol or a command prompt work with or without -NoExit.

    Powershell -Command "& { dir }"
    Powershell -NoExit -Command "& { dir }"

    The first command works from VB2010 (via Process.Start)…

    1 vote
    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 →
  17. Make modules and cmdlets available for current script

    The ability to package a script with the cmdlets and modules used to make that script.

    E.g.

    The ability to put a cmdlet at the start of the script such as:
    Monitor-ScriptModule -All

    Then as a module is imported or a cmdlet is used, the script will include the modules and cmdlets in some file that allows an admin to deploy the script to other workstations and the script is able to include the modules and cmdlets on older versions that may not have the cmdlets or modules included.

    This would help avoid older versions from not working because 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  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
  18. int32 keys in a hashtable do not match/equal int64 variables with the same value

    int32 keys in a hashtable do not match/equal int64 variables with the same value. If you force a int64 on the key by adding [int64] in the hashtable definition then the lookup works.

    Example:
    $Event = @{

    [int64]12 = "Boot"
    
    13 = "Shutdown"

    }

    @($event[[int64]12],$event[12],$event[13],$event[[int64]13]) | % { Write-Output "Result: $_" }

    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 →
  19. #Requires -Module needs RequiredVersion option

    Votes from Connect: 4

    Original Date Submitted: 11/14/2015 5:05:21 AM

    Description:
    Contact Information
    Handle: June Blender
    Site Name: PowerShell
    Feedback ID: 2014667


    Problem Description:
    To require the exact version of a module, I need a RequiredVersion option in #Requires.

    The ModuleVersion key in the #Requires -Module hashtable: @{ModuleName=''; ModuleVersion=''} behaves as a minimum version requirement. Not all versions of all modules are backward-compatible. With the proliferation of versions, including side-by-side in PowerShell 5.0, we need to be able to require a particular version.

    Also, about_Requires describes the ModuleVersion, but does not mention that it's a minimum (because I didn't know…

    17 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. Windows Management Framework and PowerShell: Need consistent, supported way to detect version from the Operating System

    Votes from Connect: 8

    Original Date Submitted: 9/5/2014 9:43:02 PM

    Description:
    Contact Information
    Handle: NPherson
    Site Name: PowerShell
    Feedback ID: 964601


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

    Problem Description:
    With the WMF, there is no good consistent way to detect what version is installed. You can query for installed KB's, but that only works if the version of the WMF wasn't already baked into the operating system.

    With PowerShell, you can find out what version you have from within PowerShell with $psversiontable, but that information is not available in the OS itself through WMI or…

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

Feedback and Knowledge Base