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. Export-ODataEndpointProxy duplicate key sequence errors on redfish endpoint

    I'm getting some parse issues with Export-ODataEndpointProxy. It creates 119 cdxml files from my Redfish endpoint, but 8 of them have "duplicate key sequence" errors. That's pretty good at 8 of 119, but I'm unable to run any cmdlets because when I Import-Module on the folder of cdxml files, it returns the "duplicate key sequence" errors.

    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

      1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    • WMF/WinRM 5.1 System File version issues after installing KB4103724

      My operating system environment is W8.1/WS12R2 with Windows Mangagement Framework 5.1 installed

      After installing KB4103724 (May, 2018 Preview of monthly Rollup for NT6.3), I found that some of the files in WMF/WINRM 5.1 were changed, and those changes were not listed on the update history.

      Let me say a few questions about this change:

      1: Generally speaking, the monthly Summary preview update is used to resolve performance and reliability issues, but this update history does not list the changes in WMF/WINRM 5.1. The affected file in WMF/WINRM 5.1 is listed only in file information for update 4103724.

      2: I noticed…

      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  ·  WinRM  ·  Flag idea as inappropriate…  ·  Admin →
      • Bug: The Get-ADGroupMember -Recursive option doesn't work correctly

        Get-ADGroupMember -Recursive only reads the Group Members property. It does not also add users to the list who have a group as their primary group. Here is what it should be doing...

        (Get-ADGroupMember -Identity "Domain Admins" | select distinguishedName).distinguishedName

        Here is what it is actually doing...

        Get-ADGroup -Identity "Domain Admins" -Properties Member | select -ExpandProperty member

        Which is a different answer!

        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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
        • CmdletsToExport publishing issue with large modules

          We (the AWS PowerShell Tools team) have hit an issue publishing the AWS modules to the gallery involving a limit of 4000 cmdlets in the CmdletsToExport manifest member. The gallery returns an error when we attempt to publish, which has forced us to revert to using "*-*" in the manifest, which gives a degraded user experience. I inspected the gallery publishing cmdlets and could see no sign of the limit there, so am assuming therefore that this was a gallery-side exception. The limit appears to be isolated to the CmdletsToExport manifest member as we're able to publish the module 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

            2 comments  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
          • Fatal error when using a class when the script is in the folder containing a single quote

            Create a script called "C:\Temp'Test\Test.ps1" and add the following lines:

            Write-Host "Test"
            Class MyClass {}

            Execute this script and you get this error:

            The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047) At line:1 char:1 + & 'C:\Temp''Test\Test..ps1' + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [], FileLoadException + FullyQualifiedErrorId : System.IO.FileLoadException

            Rename the folder as simply C:\Test and it runs without an error.

            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 →
            • ISE should not switch focus automatically to the console pane

              Starting from Windows 10 1803, when you run a selected block of code using F8, ISE switches focus to the console pane. This means that when you run several of these, you have to manually switch the focus back to the script pane after each execution.

              This is much more difficult than before, so please fix this.

              4 votes
              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  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
              • Terminating error in if statement script block generates duplicate errorvariable entries

                Consider the following 2 functions (contrived to illustrate the issue).

                function 1error { [CmdletBinding()] Param(); throw "This produces 1" }
                function 2error { [CmdletBinding()] Param(); if($true) {throw "This produces 2"} }

                If you call the function 1error with an error variable, the error variable will act as expected.

                1error -ErrorVariable +1var
                $1var.count #results in 1

                If you call function 2error with an error variable, the error variable will have 2 identical errors.

                2error -ErrorVariable +2var
                $2var.count # results in 2

                PSVersion is 5.1.14393.2189

                4 votes
                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 →
                • New-Volume does not work with SMR drives

                  I can create a storage pool with or without storage tiers and then use new-virtualdisk to create disks on the storage pool. I can then format-volume and add access paths with add-PartitionAccessPath. All the separate parts work fine.

                  but...if I make a storage pool and try something like:

                  New-Volume -StoragePoolFriendlyName Test_Pool -FriendlyName Test0 -Size 10TB -ResiliencySettingName Simple -FileSystem ReFS -AccessPath M:\access_path0

                  ...it will work one time. Any other volumes attempted on the same storage pool (with different names and access_paths) will fail on both ReFS and NTFS file systems. The same command run on PMR HDDs will work repeatedly just…

                  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 ISE win10 1803 Cursor swaping panes on run

                    Since windows 10 1803 when running a script from the script pane, the cursor switches from the script pane to the console pane.

                    To reproduce: Open powershell ise on windows 10 1803. Enter in a basic script (ex: Write-Host "test") and hit F5. The cursor will move to the console pane so if you start typing the output will be in the console pane.

                    The expected behavior would be to leave the cursor in the script pane so that you can continue to edit the script. This was the behavior previous to windows 10 1803.

                    2 votes
                    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  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                    • Using DontShow for a parameter should not hide all CommonParameters from auto-complete

                      Using "DontShow = $true" for a parameter has the unexpected side effect of hiding all CommonParameters from auto-complete. The function below demonstrates the issue.

                      function Get-Foo {

                      [CmdletBinding()]
                      param(
                      [Parameter()]
                      [string]
                      $Visible,

                      [Parameter( DontShow = $true )]
                      [string]
                      $NotVisible
                      )

                      process {
                      Write-Verbose 'foo'
                      }

                      }

                      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 →
                      • Powershell ISE crashes on Ctrl+Space Intellisense

                        my "Ideas" is Powershell ISE should not crash.

                        https://github.com/PowerShell/PowerShell/issues/6846

                        teps to reproduce
                        Use Windows Powershell ISE on Windows Build 17134
                        Enter the name of any cmdlet, a dash, then press ctrl+Space.
                        Get-Help -[Ctrl+Space]
                        Expected behavior
                        Should show intellisense popup.
                        Actual behavior
                        Instead of an intellisense dropdown, a small dot appears.
                        Messagebox as follows, followed by closing:
                        ---------------------------
                        Windows PowerShell ISE - Error
                        ---------------------------
                        An unexpected error has occurred, and Windows PowerShell ISE must close.
                        ---------------------------
                        OK
                        ---------------------------
                        Running in the visual studio debugger shows two exceptions, one from Xaml (associated with the appearance of the dot) the other a NullReferenceException…

                        25 votes
                        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

                          8 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                        • anaconda

                          Anaconda (Python Environments) Syntax Support

                          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 →
                          • Merge "Windows PowerShell" and "PowerShell Core", make result default on Windows

                            When sending code to someone, I don't want to have to qualify the post with "if it doesn't work, try the *other* PowerShell...". I know there will be OS-specific modules/commands, but there should *not* be two code bases for the shell itself, or two product names.

                            2 votes
                            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 →
                            • snippets

                              PowerShell ISE - Where are the default snippets after Win10 Upgrade?

                              So I've upgraded to Win10Pro 1803 17134.1, opened my trusty PowerShell ISE, pressed CTRL+J and nothing happens!? Even the Get-ISESnippet is not showing any results. I'm using the default snippets and don't have any custom snippets under my documents / PowerShell folder.

                              It seems to be related to OneDrive or Windows 10 update as both my Desktop and Laptop have the same problem.

                              According to JRV the same issue occurs on 1809 builds.

                              Link: https://social.technet.microsoft.com/Forums/en-US/47ded9fb-0501-4953-92cc-ef55dbf86fbe/powershell-ise-where-are-the-default-snippets-after-win10-upgrade?forum=winserverpowershell

                              Best Regards,
                              Glenn

                              $PSVersionTable

                              Name Value
                              ---- -----
                              PSVersion 5.1.17134.1
                              PSEdition Desktop
                              PSCompatibleVersions {1.0,…

                              62 votes
                              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

                                13 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
                              • Powershell 5.1 returns error on special characters when passing in an array of arguments

                                Hello,

                                I have Set the arguments in the code:

                                $installArguments = "`"-p`" `"$ISMFileFolder`" -o `"$MergeModuleFolder`" -y `"$VersionNumber`" $PathVariableArguments -b `"$MediaOutputFolder`""

                                and run the exe with arguments:
                                & $IScmdBldRootDir $installArguments
                                The same scripts is running fine on Windows server 2008 R2 that has the Powershell 4.0 and it fails and return error on Windows server 2016 that has the Powershell 5.1.
                                The error is:
                                -1113: The 'p E:\Builds\Installer' switch is not recognized.

                                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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                                • Set-mpioSetting -NewRetryInterval input validation is too strict

                                  When I run the following command in powershell
                                  (Windows Server 2012 R2, PS Version - 5.1.14409.1005)

                                  "Set-mpioSetting -NewRetryInterval 1 "
                                  returns the error
                                  "Set-MPIOSetting : Cannot validate argument on parameter 'NewRetryInterval'. The 1 argument is less than the minimum allowed range of 3. Supply an argument that is greater than or equal to 3 and then try the command again."

                                  The documentation at https://docs.microsoft.com/en-us/powershell/module/mpio/set-mpiosetting?view=win10-ps says that the default is 1 second, and we can use the GUI to be able to set the retry interval, but I want to be able to use powershell to automate the configuration of my…

                                  4 votes
                                  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

                                    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                                  • 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 →
                                    • Import-Module does not work with binary modules in exe files

                                      I've tried putting my commands in an exe module, but could not get this module loaded in PowerShell.

                                      1) If I try to load my module as-is, e.g. an .exe file I get "The extension '.exe' is not a valid module extension. "

                                      2) If I create a .psd1 manifest and put RootModule = 'MyModule.exe' there I get Object reference not set to an instance of an object.
                                      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleNamedInManifest(PSModuleInfo parentModule, ModuleSpecification moduleSpecification, String moduleBase, Boolean searchModulePath, String prefix, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags manifestProcessingFlags, Boolean loadTypesFiles, Boolean loadFormatFiles, Object privateData, Boolean& found, String shortModuleName, Nullable`1 manifestLanguageMode)
                                      at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath,…

                                      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 commandlets to configure NAT in the RemoteAccess module

                                        Please, expand the RemoteAccess module with commandlets that allow you to configure simple NAT like you would do with the RRAS GUI.
                                        So far, the module allow you to configure Direct Access and VPN but not NAT and it feels like it's missing.

                                        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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Add SNMP Cmdlets (Get, Walk, Table, etc.)

                                          Hi,

                                          it would be very useful to have SNMP cmdlets available. SNMP is still defacto standard for managing many kinds of 'network-devices'.

                                          It could help also considering IOT devices.

                                          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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4 5 67 68
                                          • Don't see your idea?

                                          Feedback and Knowledge Base