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. Failed to update Help for the module(s) 'NetEventPacketCapture' with UI culture(s) {en-GB}

    Votes from Connect: 3

    Original Date Submitted: 7/31/2015 8:55:14 AM

    Description:
    ********Contact Information********
    Handle: David Gardiner
    Site Name: PowerShell
    Feedback ID: 1611008
    ***************************************

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

    Problem Description:
    Using Update-Help or Save-Help on a Windows 10 computer configured with en-GB as the Windows display language fails with an error.

    Update-Help : Failed to update Help for the module(s) 'NetEventPacketCapture' with UI culture(s) {en-GB} : 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…

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    • The call operator should support invoking .NET methods and also support splatting

      Votes from Connect: 5

      Original Date Submitted: 9/8/2014 11:00:11 PM

      Description:
      ********Contact Information********
      Handle: Oisín Grehan
      Site Name: PowerShell
      Feedback ID: 966940
      ***************************************

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

      Problem Description:
      As of v5, the call (&) operator cannot invoke .NET methods. With the implied deprecation of new-object in v5 by way of the "new(...)" synthetic static constructor method, this becomes a more obvious lack.

      One thing new-object has that the new v5 static method "new" does not is splatting support. Syntactically, this seems to make most sense when combined with support for invoking .NET…

      1 vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
      • Uninstall-Module needs Scope parameter

        Votes from Connect: 7

        Original Date Submitted: 8/6/2015 9:17:18 PM

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

        Problem Description:
        Add a Scope parameter to Uninstall-Module so I can uninstall a module from a specified scope.

        Install-Module has a scope parameter and multiple *Version parameters. On PowerShell 5.0+, you can install the same version in multiple scopes. However, because there's no Scope parameter for Uninstall-Module, you can specify only the version, not the scope.

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

        Repro Steps:

        Internal BugId:…

        1 vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
        • Automatically add help links for all commands sharing the same noun

          Votes from Connect: 6

          Original Date Submitted: 9/11/2014 4:15:39 AM

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

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

          Problem Description:
          Help documentation is more time consuming than it needs to be. My biggest pain point with help is that I like to include links to all other commands with the same noun to aid in discoverability. Sure, there is Get-Command -Noun ..., but it is useful in help documentation to include links to those commands as well. This also helps modern help tools link…

          1 vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
          • 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
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
            • LCM on clean Windows 2012R2 with WMF 5.0 Feb preview don't apply configuration from Current.mof file.

              Votes from Connect: 3

              Original Date Submitted: 4/24/2015 8:39:47 PM

              Description:
              ********Contact Information********
              Handle: Juris Krumins
              Site Name: PowerShell
              Feedback ID: 1274851
              ***************************************

              Frequency: Desired State Configuration (DSC)
              Regression: Install Windows 2021R2, install WMF 5.0 Feb preview and put your mof configuration file to the C:\Windows\System32\Configuration with the Current.mof file name. Wait at least 15 min and LCM should start apply configuration.
              Works with Windows 2012 and WMF 5.0 Feb preview installed.

              Problem Description:
              Clean Windows 2012R2 box with WMF 5.0 Feb preview installed and configuration have been pushed as C:\Windows\System32\Configuration\Current.mof file. I can't see any signs in DSC Evenlog,…

              1 vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
              • Get-ChildItem -Recurse -LiteralPath doesn't find anything

                Votes from Connect: 4

                Original Date Submitted: 9/14/2014 4:22:48 PM

                Description:
                ********Contact Information********
                Handle: sba
                Site Name: PowerShell
                Feedback ID: 971502
                ***************************************

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

                Problem Description:
                When 'Get-ChildItem -Recurse -LiteralPath' is run against a directory whose name contains square brackets, no output is produced.

                Take a directory with the following contents:

                PS> cmd /c dir /s d:\tmp\dir[1]
                Volume in drive D is DATA
                Volume Serial Number is 0454-9DBF

                Directory of d:\tmp\dir[1]

                2014-09-14 09:23 <DIR> .
                2014-09-14 09:23 <DIR> ..
                2014-09-14 09:23 <DIR> subdir
                0 File(s) 0 bytes

                Directory of d:\tmp\dir[1]\subdir

                2014-09-14…

                1 vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                • Provide PowerShell ISE with better support for .Types.ps1xml and .Format.ps1xml

                  Votes from Connect: 4

                  Original Date Submitted: 9/15/2014 7:04:41 AM

                  Description:
                  ********Contact Information********
                  Handle: Derp McDerp
                  Site Name: PowerShell
                  Feedback ID: 972024
                  ***************************************

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

                  Problem Description:
                  Specifically:

                  1. it should auto-complete the xml based on their doctypes
                  2. it should recognize the interior of <ScriptBlock>s as PowerShell scripts rather than as text blobs and format and auto-complete those correctly.
                  3. it should provide better outlining of the xml (e.g. if you put the caret on an end tag or start tag it should highlight the entire interior of that xml…

                  1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                  • Windows 8.1 - Powershell 4.0 Get-ADComputer -Properties * bug

                    Votes from Connect: 72

                    Original Date Submitted: 10/24/2013 11:12:10 PM

                    Description:
                    ********Contact Information********
                    Handle: jbarkl3y
                    Site Name: PowerShell
                    Feedback ID: 806452
                    ***************************************

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

                    Problem Description:
                    When running the Get-ADComputer command I run into the following. There has been a couple of posts on this error but they are related to Powershell 3.0 and can be fixed by changing your AD Schema to version 47. This bug still exists except now my Schema version is 47 and the bug still persists.

                    Get-ADComputer : One or more properties are invalid.
                    Parameter name:…

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                    • Add ExportedProviders to ModuleInfo object

                      Votes from Connect: 3

                      Original Date Submitted: 4/25/2015 10:51:47 PM

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

                      Frequency: PowerShell
                      Regression: PS C:\> (Get-Module Microsoft.PowerShell.Security).ExportedProviders
                      PS C:\>

                      Problem Description:
                      Please add an ExportedProviders key to the module manifest and add its value to the ModuleInfo object. This lets users easily detect whether a module will add a new PSProvider to their session.

                      This also lets us detect and support provider help in help tools.

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

                      Repro Steps:
                      PS C:\>…

                      1 vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                      • Script won't display help docs with -? if it uses #requires -RunAsAdministator

                        Votes from Connect: 5

                        Original Date Submitted: 4/27/2015 6:22:00 AM

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

                        Frequency: PowerShell
                        Regression: Run the script (call it test.ps1) from the Description above from a non-admin PowerShell prompt like so:

                        PS> .\test.ps1 -?

                        You will get this result:

                        .\test.ps1 : The script 'test.ps1' cannot be run because it contains a "#requires" statement for running as
                        Administrator. The current Windows PowerShell session is not running as Administrator. Start Windows PowerShell by
                        using the Run as Administrator option, and then try running the script again.
                        At line:1 char:1 …

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                        • 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…

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                          • PSBoundParameters arguments include values that were bound so far

                            Votes from Connect: 8

                            Original Date Submitted: 4/28/2015 1:48:05 AM

                            Description:

                            ********Contact Information********
                            Handle: Adam D. Bertram
                            Site Name: PowerShell
                            Feedback ID: 1283430
                            ***************************************

                            Frequency: PowerShell
                            Regression: I want -ShowWindow to be used for Get-Help only if I have "about_if" as the Name parameter argument.

                            I do this and expect a $true output if I'm using 'about_if' but it does not work.

                            $PSDefaultParameterValues["Get-Help:ShowWindow"] = { ($args[0].BoundParameters -contains 'Name') -and ($PSBoundParameters['Name'] -eq 'about_if') }

                            The reason is that $PSBoundParameters does not include param argument values for parameters that are already bound.

                            Problem Description:
                            When attempting to add a scriptblock value to…

                            1 vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                            • Error Installing Powershell Preview April 2015 on Windows 7

                              Votes from Connect: 3

                              Original Date Submitted: 4/30/2015 2:06:48 PM

                              Description:
                              ********Contact Information********
                              Handle: Holger Froebe
                              Site Name: PowerShell
                              Feedback ID: 1290413
                              ***************************************

                              Frequency: PowerShell
                              Regression: Windows 7 SP1 X64 - German
                              Following release notes:
                              Checked for all the updates - OK
                              Powershell 4.0 was installed - OK
                              Selecting package from MS Download Center:
                              Windows6.1-KB2908075-x64
                              Starting the Update-Package gives me the above error.

                              Maybe a Problem with UI Culture - I work with a german Windows and maybe the Preview is
                              only applicable to english Windows ?

                              Problem Description:
                              Installing Powershell 5.0 on Windows 7 gives me error:
                              This update…

                              1 vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                              • 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 "about_Desired_State_Configuration", which is consistent with the naming of other PowerShell help files, but the actual file name is about_DesiredStateConfiguration.

                                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
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  0 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                                • get-childitem does not work correctly if -recurse and -literalpath are both specified

                                  Votes from Connect: 4

                                  Original Date Submitted: 8/24/2015 10:15:01 PM

                                  Description:
                                  ********Contact Information********
                                  Handle: herzbube
                                  Site Name: PowerShell
                                  Feedback ID: 1707779
                                  ***************************************

                                  Frequency: PowerShell
                                  Regression: 1. Create a folder C:\[foo]
                                  2. Add a file "bar" to the folder
                                  3. Run the following commands in PowerShell:

                                  $path = 'C:\[foo]'
                                  get-childitem -literalpath $path -recurse

                                  Problem Description:
                                  Let's say I have this file:

                                  C:\[foo]\bar

                                  I then run these PowerShell commands:

                                  $path = 'C:\[foo]'
                                  get-childitem -literalpath $path

                                  Everything works fine, `get-childitem` shows me the file `bar`, then returns immediately.

                                  Now I add the `-recurse` option:

                                  $path = 'C:\[foo]'
                                  get-childitem -literalpath $path -recurse

                                  `get-childitem` no…

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Group Policy Powershell Script

                                    Votes from Connect: 28

                                    Original Date Submitted: 9/29/2014 7:28:00 PM

                                    Description:
                                    ********Contact Information********
                                    Handle: Axel B. Andersen
                                    Site Name: PowerShell
                                    Feedback ID: 984532
                                    ***************************************

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

                                    Problem Description:
                                    When running Powershell Logon or Logoff Scrips in GPO's the -NoProfile switch is not included in the command. This results in very long logon/logoff times, if users have filled their Powershell Profile with a lot of modules. It can take up to 10 minutes, if the profile needs user input to load.

                                    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
                                      I agree to the terms of service
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                    • PSPossibleIncorrectComparisonWithNull - $null should be on the left side of equality comparisons.

                                      Votes from Connect: 3

                                      Original Date Submitted: 5/3/2015 6:39:12 PM

                                      Description:
                                      ********Contact Information********
                                      Handle: Remco Kapinga
                                      Site Name: PowerShell
                                      Feedback ID: 1299466
                                      ***************************************

                                      Problem Description:
                                      Invoke-ScriptAnalyzer flags this as a Warning:

                                      if ($item -ne $null) { .. }

                                      And suggest that we should write this comparison as:

                                      if ($null -ne $item) { .. }

                                      That makes code less readable (yoda-speak). This reminds us of the c language defect with if(a = null) { .. } versus if(a == null) { .. }

                                      I don't see the point of this rule in PowerShell, and the suggested construct makes code less readable.

                                      1 vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Variables that are $null are not always $null

                                        Votes from Connect: 3

                                        Original Date Submitted: 5/4/2015 1:20:27 AM

                                        Description:
                                        ********Contact Information********
                                        Handle: David I McIntosh
                                        Site Name: PowerShell
                                        Feedback ID: 1300430
                                        ***************************************

                                        Frequency: PowerShell
                                        Regression: >function emptyArray() { @() }
                                        >$l_t = @() ; $l_t.Count
                                        0
                                        >$l_t1 = @(); $l_t1 -eq $null; $l_t1.count; $l_t1.gettype()
                                        0
                                        IsPublic IsSerial Name BaseType
                                        -------- -------- ---- --------
                                        True True Object[] System.Array
                                        >$l_t += $l_t1; $l_t.Count
                                        0
                                        >$l_t += emptyArray; $l_t.Count
                                        0
                                        >$l_t2 = emptyArray; $l_t2 -eq $null; $l_t2.Count; $l_t2.gettype()
                                        True
                                        0
                                        You cannot call a method on a null-valued expression.
                                        At line:1 char:38
                                        + $l_t2 = emptyArray; $l_t2 -eq $null; $l_t2.Count; $l_t2.gettype() …

                                        1 vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Add -Wait and -Timeout parameters to Debug-Job

                                          Votes from Connect: 4

                                          Original Date Submitted: 10/6/2014 9:54:44 PM

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

                                          Frequency: Always Happens
                                          Regression: I don

                                          Problem Description:
                                          When writing a simple example to debug a PowerShell Background Job, the Background Job does not have enough time to initialize, before the Debug-Job command is invoked. Examine the following example:

                                          $ScriptBlock = {
                                          $Foo = 1;
                                          Wait-Debugger;
                                          $Foo++;
                                          };

                                          $Job = Start-Job -ScriptBlock $ScriptBlock;
                                          Debug-Job -Job $Job;

                                          When I run the above code in the PowerShell ISE, I receive an error message from Debug-Job, stating:

                                          "Debug-Job :…

                                          1 vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            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