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.

Please feel free to provide feedback or file bugs here.

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. WMF5 (KB3037315) install breaks Commands add-on in PowerShell ISE for admin

    Votes from Connect: 6

    Original Date Submitted: 4/24/2015 1:03:59 AM

    Description:

    ********Contact Information********
    Handle: Mathias JWD
    Site Name: PowerShell
    Feedback ID: 1272913
    ***************************************

    Frequency: PowerShell ISE
    Regression: 1. Install KB3037315
    2. Run ISE as administrator
    3. Commands addon does not show any commands or modules
    4. Click Run/Insert/Copy, ISE will crash.

    Problem Description:
    After I installed KB3037315 on my Windows 8.1 PC, the Commands Add-on in my PowerShell ISE did no longer show any commands, the Modules drop down box remained empty. When clicking any of the three buttons on the bottom (Run/Insert/Copy), the ISE would crash.

    This happened only…

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    • The PowerShell course that Microsoft is offering via edX should have a free audit option like the other Microsoft/edX courses

      Votes from Connect: 7

      Original Date Submitted: 4/23/2015 6:45:25 PM

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

      Problem Description:
      I discussed this with Kenneth at the PowerShell Summit this week, and he suggested I log an issue here. There is a PowerShell course on edX that can be found here:

      https://www.edx.org/course/windows-powershell-fundamentals-microsoft-inf201x

      This course costs $200 US.

      There are 6 other Microsoft courses on edX on C#, TypeScript, Bootstrap, Azure, O365, and Transact-SQL. Those courses offer both a paid certificate option and a free audit option. But the PowerShell one only has a $200 US…

      1 vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
      • PowerShell should have a cmdlet that supports best effort magic number parsing on files without extensions or incorrect extensions

        Votes from Connect: 4

        Original Date Submitted: 4/14/2015 8:18:28 AM

        Description:
        ********Contact Information********
        Handle: JasonHorner
        Site Name: PowerShell
        Feedback ID: 1246396
        ***************************************

        Problem Description:
        often we need to parse a file and not rely on its extension, while magic number parsing is imperfect it can provide some value.
        this could be used for general file parsing as well as some security scenarios

        Here is a script that implements this feature though I don't think it is completely robust:
        http://powershell.com/cs/blogs/tips/archive/2010/08/09/reading-file-quot-magic-number-quot.aspx

        unix support a similar capability via the file utility:
        http://en.wikipedia.org/wiki/File_%28command%29

        More info on magic number parsing:
        http://en.wikipedia.org/wiki/List_of_file_signatures

        Product Studio item created…

        1 vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
        • Script Analyzer - Severity for Custom Rule does not work

          Votes from Connect: 6

          Original Date Submitted: 3/20/2015 7:53:36 PM

          Description:
          ********Contact Information********
          Handle: Stefan Stranger
          Site Name: PowerShell
          Feedback ID: 1192179
          ***************************************

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

          Problem Description:
          When creating a custom script analyzer rule the severity does not seem to be executed.

          Example:
          <#
          .SYNOPSIS
          You should never use Write-Host to create any script output whatsoever.
          .DESCRIPTION
          It is generally accepted that you should never use Write-Host to create any script output whatsoever, unless your script (or function, or whatever) uses the Show verb (as in, Show-Performance).
          That verb…

          1 vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
          • about_Remote_Troubleshooting Group Policy incorrect for 2012 R2

            Votes from Connect: 4

            Original Date Submitted: 3/17/2015 8:27:30 PM

            Description:
            ********Contact Information********
            Handle: Ashley McGlone
            Site Name: PowerShell
            Feedback ID: 1186090
            ***************************************

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

            Problem Description:
            The about_Remote_Troubleshooting topic needs to be updated for 2012 (R2). The group policy setting name has changed:

            Allow automatic configuration of listeners (2008 R2)
            Allow remote server management through WinRM (2012 R2)

            The policy name appears twice in the help text:

            -- To configure listeners for remoting, enable the "Allow automatic
            configuration of listeners" group policy. For instructions, see
            "How to Enable Listeners by…

            1 vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
            • Love PowerShell but not a fan of one syntax requirement

              Votes from Connect: 6

              Original Date Submitted: 3/14/2015 4:56:44 AM

              Description:
              ********Contact Information********
              Handle: J. Michael Delaney
              Site Name: PowerShell
              Feedback ID: 1179419
              ***************************************

              Problem Description:
              Love PowerShell. It helps me so much in my daily tasks and I am constantly wowing co-workers with my skills.

              When scripting, the only thing I don't like about PowerShell is that when doing conditional statements with if/elseif/else and looping constructs, that I need to use brace brackets when the conditional or loop executes one line of code.

              For example, in other languages such as C++, I can do this:

              If(x=10)
              std::cout << "hello…

              1 vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
              • Enable authoring of DSC resources using c# in a similar way as with ps classes

                Votes from Connect: 3

                Original Date Submitted: 3/12/2015 9:51:57 PM

                Description:
                ********Contact Information********
                Handle: aL3891
                Site Name: PowerShell
                Feedback ID: 1175982
                ***************************************

                Problem Description:
                We're now able to write DSC resources using classes in powershell and that is really great!

                Please also enable writing resources in c# in a similar way using a single class and attributes to mark properties and methods as their DSC equivalent. that would reduce alot of the friction for developers coming in to DSC from c#

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

                Repro Steps:

                1 vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                • Add DefaultValue property to System.Management.Automation.CommandParameterInfo class

                  Votes from Connect: 8

                  Original Date Submitted: 3/3/2015 5:52:55 AM

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

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

                  Problem Description:
                  Currently, there is no way to detect whether a command parameter has a default value or what the default value is. It's important to help authoring and to command parsing.

                  I can use the AST to get the default value, but that works only for functions and scripts; not for cmdlets.

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

                  1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                  • Deep nested workflows don't recognize the erroraction parameter

                    Votes from Connect: 5

                    Original Date Submitted: 3/2/2015 8:58:03 PM

                    Description:
                    ********Contact Information********
                    Handle: Trond Hindenes
                    Site Name: PowerShell
                    Feedback ID: 1156994
                    ***************************************

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

                    Problem Description:
                    If a workflow uses deep nesting (at least 3 levels of nesting), erroraction does not work. This is reproducable in both the V4 and V5 feb preview of the WMF.

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

                    Repro Steps:
                    Consider the following 3 workflows
                    workflow one
                    {
                    Write-Output "one"
                    }

                    workflow two …

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                    • Flags Enumeration Bitwise Operations Fail With 'Specified cast is not valid' Error

                      Votes from Connect: 3

                      Original Date Submitted: 2/19/2015 11:08:09 PM

                      Description:

                      ********Contact Information********
                      Handle: Rohn Edwards
                      Site Name: PowerShell
                      Feedback ID: 1138469
                      ***************************************

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

                      Problem Description:
                      In the December 2014 and February 2015 WMF 5.0 previews, flags enumerations that have byte, sbyte, short, or ushort underlying types have to be cast or coerced to a numeric type before -band, -bor, or -bxor bitwise operations will work.

                      int, uint, long, and ulong underlying types still work as expected.

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

                      1 vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                      • Parameter validation

                        Votes from Connect: 5

                        Original Date Submitted: 2/6/2015 3:54:49 PM

                        Description:
                        ********Contact Information********
                        Handle: edi89
                        Site Name: PowerShell
                        Feedback ID: 1117495
                        ***************************************

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

                        Problem Description:
                        Using paramter validation in functions works just find - something like this:
                        function test{
                        Param (
                        [ValidateRange(3,8)]
                        [Int] $mytest )

                        write-host $mytest
                        }
                        test 4
                        test 9
                        The problem is, that it seems, that parameter validation is in fact just a special case of variable validation which leads to the circumstance, that the variable used (in this case $mytest) is beeing validated every time…

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                        • Add snippet support to the console as well

                          Votes from Connect: 3

                          Original Date Submitted: 1/30/2015 5:06:50 AM

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

                          Frequency: Always Happens
                          Regression: I don

                          Problem Description:
                          Now that I've gotten used to ISE-Snippets, I love them and I have a huge selection of them to help me with calculated properties, custom objects, and things like that. I'd love to be able to use ISE-Snippets in the PowerShell console as well.

                          We can already hit F7 to see a list of the last 40 or so commands in our window. How about adding a similar window…

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                          • DSC Please make sure key properties are unique for each resource in a node.

                            Votes from Connect: 3

                            Original Date Submitted: 1/29/2015 7:34:02 AM

                            Description:
                            ********Contact Information********
                            Handle: aL3891
                            Site Name: PowerShell
                            Feedback ID: 1106345
                            ***************************************

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

                            Problem Description:
                            i've investigated DSC but found it to be almost unusable on any kind of scale since it seems every variable is stored in some global scope, not even quantified with step names.

                            This makes it impossible to so something as simple as stopping and starting a service to update it, surely a common scenario. (Because the "Name" has to be unique)

                            Even worse, trying to…

                            1 vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                            • MKDIR and RM needs unix-like most pertinent switches

                              Votes from Connect: 3

                              Original Date Submitted: 1/3/2015 6:07:28 AM

                              Description:
                              ********Contact Information********
                              Handle: The Deeds
                              Site Name: PowerShell
                              Feedback ID: 1074131
                              ***************************************

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

                              Problem Description:
                              Part 1:

                              In bash, we say:

                              rm -f

                              In Powershell, the equivalent is:

                              rm -Force

                              Please add an alias -f, so to make it compatible with unix-like shells. It helps a lot in C/C++ CMAKE and other scripting scenarios like Nodejs etc.

                              Part 2:

                              We desperately need mkdir -p (or --parents) switch of Unix in Windows. Going by the man (manual); http://www.computerhope.com/unix/umkdir.htm, it…

                              1 vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                              • Cannot Connect to Office 365 since November's WMF5

                                Votes from Connect: 3

                                Original Date Submitted: 1/3/2015 3:54:37 AM

                                Description:
                                ********Contact Information********
                                Handle: rpseekell
                                Site Name: PowerShell
                                Feedback ID: 1074018
                                ***************************************

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

                                Problem Description:
                                I use this script to connect to Office 365 via PowerShell, which I think is pretty standard:
                                $cred = Get-Credential
                                $sess = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication basic -AllowRedirection
                                Import-PSSession -Session $sess

                                However, since updating to the November preview of PowerShell (WMF) 5, the new-PSSession command hangs and never finishes. I get a message like,
                                WARNING: Your connection has been…

                                1 vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                • German installer for Microsoft Security Essentials has wrong messages

                                  Votes from Connect: 3

                                  Original Date Submitted: 1/2/2015 7:28:29 AM

                                  Description:
                                  ********Contact Information********
                                  Handle: Roland Illig 2
                                  Site Name: PowerShell
                                  Feedback ID: 1073011
                                  ***************************************

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

                                  Problem Description:
                                  The German version of the installer for Microsoft Security Essentials has two wrong translations:

                                  1. „Falls keine Firewall aktiviert ist, aktivieren Sie die Windows-Firewall (empfohlen).“

                                  This text should not even be in the installer in this form. Either the firewall is already activated, then the checkbox is useless and must not be shown at all. Or the firewall is not already activated, then…

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                  • New-Object fails on a class whose GetEnumerator method throws NotSupportedException

                                    Votes from Connect: 3

                                    Original Date Submitted: 12/11/2014 7:11:16 AM

                                    Description:
                                    ********Contact Information********
                                    Handle: Clint Stotesbery
                                    Site Name: PowerShell
                                    Feedback ID: 1051712
                                    ***************************************

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

                                    Problem Description:
                                    I've run into a rare case. I can't use New-Object on a class whose GetEnumerator method throws NotSupportedException. System.Security.Cryptography.Xml.SignedInfo's GetEnumerator method throws a NotSupportedException: http://msdn.microsoft.com/en-us/library/system.security.cryptography.xml.signedinfo.getenumerator(v=vs.110).aspx

                                    The stack trace shows TypicalEnumerable as this method catches Exception and then rethrows it as an ExtendedTypeSystemException. I followed the complete stacktrace (hint: there are delegates involved not in the stack trace) and I can't figure out a way…

                                    1 vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Add-Member cmdlet invokes ScriptProperty members when adding new member

                                      Votes from Connect: 3

                                      Original Date Submitted: 12/4/2014 3:29:25 AM

                                      Description:

                                      ********Contact Information********
                                      Handle: Josef Nemec
                                      Site Name: PowerShell
                                      Feedback ID: 1045858
                                      ***************************************

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

                                      Problem Description:
                                      When calling Add-Member over an object all ScriptProperty members are being invoked (script blocks from those properties are invoked). I found it during testing on PowerShell 5 preview (from Windows 10 preview build), but it also occurs in PS 4 (tested on Windows 8.1). It seems like it occurs only with System.Management.Automation.dll 6.3.9600.17400 and newer since it works for me on 8.1 machines with…

                                      1 vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                      • PS4.0: (Get-Variable MyInvocation -Scope 1).Value fails when powershell.exe run from MSBuild

                                        Votes from Connect: 3

                                        Original Date Submitted: 11/7/2014 10:07:44 PM

                                        Description:

                                        ********Contact Information********
                                        Handle: sba
                                        Site Name: PowerShell
                                        Feedback ID: 1023770
                                        ***************************************

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

                                        Problem Description:
                                        I have a script that contains the following code:

                                        --------------8<----------------
                                        function Get-ScriptDirectory{

                                        $Invocation = (Get-Variable MyInvocation -Scope 1).Value
                                        try {
                                        Split-Path $Invocation.MyCommand.Path -ea 0
                                        }
                                        catch {
                                        Write-Warning 'You need to call this function from within a saved script.'
                                        }
                                        }

                                        $scriptdir = Get-ScriptDirectory

                                        Set-Location $scriptdir -ErrorAction Stop
                                        --------------8<----------------

                                        (this originates from PS2.0 days)

                                        The script runs fine, except if it's run from…

                                        1 vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Get-Command's System.Management.Automation.AliasInfo object should return an 'IntroducedIn' Property

                                          Votes from Connect: 5

                                          Original Date Submitted: 10/29/2014 11:53:04 PM

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

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

                                          Problem Description:
                                          Currently there is no easy method to determine which version of PowerShell a particular cmdlet will work within.

                                          Take the example of New-PSDrive. This command was introduced in PowerShell version 2.0, but the current Version property displayed when I run 'Get-Command New-PSDrive | Format-List' displays the value of 3.1.

                                          While this cmdlet was included in 3.0 and 4.0, it is misleading that the version…

                                          1 vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            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