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. We need a proper set of built-in, easy-to-use, dedicated registry cmdlets

    Managing registry keys and values on local and remote systems with PowerShell is a pain.

    Reviewing the articles, forums and blogs on the Internet clearly shows that new PowerShell users struggle to understand how to use registry provider drives and the cmdlets like New-Item, Get-ItemProperty, New-ItemProperty, and so on. This has prompted the creation of a variety of home-brew modules and functions to deal with the problem, like this one, which is extremely useful, but is not built into PowerShell by default of course:

    https://gallery.technet.microsoft.com/RegistryLibrarypsm1-b38a81ba

    PowerShell needs a proper set of built-in, dedicated registry cmdlets that 1) are easy to…

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

      2 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    • update-help : Failed to update Help for the module(s) 'Provisioning'

      I receive the following error when running Update-Help in PowerShell.

      PS C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Provisioning> update-help
      update-help : Failed to update Help for the module(s) 'Provisioning' with UI culture(s) {en-US} : Unable to retrieve
      the HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri property in the module manifest is valid or
      check your network connection and then try the command again.
      At line:1 char:1
      + update-help -force
      + ~~~~~~~~~~~~~~~~~~
      + CategoryInfo : ResourceUnavailable: (:) [Update-Help], Exception
      + FullyQualifiedErrorId : UnableToRetrieveHelpInfoXml,Microsoft.PowerShell.Commands.UpdateHelpCommand

      PowerShell info:
      PS C:\> $PSVersionTable.PSVersion

      Major Minor Build Revision
      ----- ----- ----- --------
      5 1 15063 138

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

        3 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
      • Bug: Integrated Modules are not loaded if you have a Network Path in $env:PSModulePath which is not reachable

        Integrated Modules are not loaded if you have a Network Path in $env:PSModulePath which is not reachable.

        ##############
        I have customized the PSModulePath:

        PS C:\Users\username> ($env:PSModulePath).split(';')
        C:\Users\username\Documents\WindowsPowerShell\Modules
        C:\Program Files\WindowsPowerShell\Modules
        C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
        c:\Program Files\Microsoft Security Client\MpProvider\
        C:\Program Files\Microsoft Monitoring Agent\Agent\PowerShell\
        \\my.domain\share\Modules\

        ##############
        If i try to execute e.g. Invoke-RestMethod

        PS C:\Users\username> Invoke-RestMethod
        Invoke-RestMethod : The 'Invoke-RestMethod' command was found in the module 'Microsoft.PowerShell.Utility', but the
        module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Utility'.
        At line:1 char:1
        + Invoke-RestMethod
        + ~~~~~~~~~~~~~~~~~
        + CategoryInfo : ObjectNotFound: (Invoke-RestMethod:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CouldNotAutoloadMatchingModule


        PS C:\Users\username> Get-Command Invoke-RestMethod
        Get-Command : The term…

        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

          1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
        • PowerShell Core - Workflow Support

          Workflows in Windows PowerShell are extremely powerful, we've started investigating their use for our user provisioning tasks which need to gracefully handle timing issues, connectivity issues, throttling, etc.

          We'd really like to be able to run workflows in lightweight configurations like Docker Containers, the Nano Server image is especially attractive as it is so small. Unfortunately PowerShell Core on the Nano Server doesn't currently support workflows, we'd like to see that support added in PowerShell Core.

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

            3 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
          • [Bug] Test-Path -PathType Containers Allows Users to Bypass Security Restrictions on Existence Testing

            Under PowerShell 5.1, the Test-Path command will return a [UnauthorizedAccessException] when you try to test a path the current user does not have access to. Normally this error is uncatchable, but it becomes so if you set the PathType to Container. Despite the name, Test-Path will verify the existence of both Containers and Leafs in this mode. Because the [UnauthorizedAccessException] error is ONLY returned for extant files and folders, a user can use it to confirm the existence of files and folders they should not be able to see or access.

            This one-liner allows you to bypass security restrictions:
            try{…

            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

              1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
            • Powershell on Raspberry pi

              add Powershell support for Raspberry Pi devices running Raspbian OS

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

                2 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
              • ExecutionPolicyOverride-Problem with GPO in place on Server 2016

                I'm preparing some "Windows Server 2016" machines. While testing I stumbled across some issues with PowerShell.
                I invested some time and narrowed it down a bit.

                I also posted the issue on Microsoft Technet Forum and got the recommendation to file a Bug/Request here. Other users were also able to reproduce it quite easily:
                (see: https://social.technet.microsoft.com/Forums/en-US/842c2cc2-c7f6-41b7-9561-31b2c65262b0/executionpolicyoverrideproblem-with-gpo-in-place-?forum=winserverpowershell)

                Steps to reproduce:

                I create a new VM, insert the Server 2016 ISO, boot up and install. After first start I change the network-settings for my environment and join the domain. I move the new computer-object to an OU where the group policy…

                2 votes
                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 →
                • Bug: DSC Decryption across Servers not Working

                  I have created a Pull Server Configuration. I have created the DSC Signing Certificate using a custom template on a Enterprise Root CA which has worked for 2012R2 nodes and also tested using xDSCUtils New-xSelfSignedDscEncryptionCertificate. Using the same Certificate to Compile and Execute the MOF on the same Computer works, it is only if you compile on one and execute on another that the problems arise.
                  I kept getting errors when passing in credentials. I therefore wrote a tiny custom DSC Resource that Displays the Password as clear text when I run Start-DSCConfiguration -Wait -Verbose
                  You can find it here …

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

                    3 comments  ·  Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
                  • Expand-Archive does not return a System.IO.FileInfo nor System.IO.DirectoryInfo

                    The docs clearly say that Expand-Archive should return a System.IO.FileInfo or System.IO.DirectoryInfo but it has no output

                    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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                    • WMF 5.1 breaks class registrations for the ConfigMgr client agent

                      I've localized this issue to WMF 5.1 on Windows 7. With this installed, the WMI namespace: root\ccm\policy\defaultmacine\requestedconfig becomes invalid. This is important because in In-Place upgrade scenarios from Windows 7 to Windows 10, the task sequence agent cannot resume the task sequence without being able to read this namespace. I know this is a combination of WMF and ConfigurationManager so I will post there as well.

                      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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                      • Bug in Get-Date when converting time ticks

                        The year given by get-date when translating a timer tick (as LastLogon from an AD user account) seems to be incorrect. Especially compared to other methods of translating timer ticks.

                        get-date(131406975810394085)
                        den 31 maj 0417 09:46:21

                        [datetime]::FromFileTime("131406975810394085").ToString()
                        2017-05-31 11:46:21

                        Year 2017 or 417?

                        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

                          1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                        • Slow "." hash lookups

                          Slow "." hash lookups (more than 100 times slower than []) from PowerShell Version 2 to Version 5.1

                          This could be either a documentation problem or a bug. The documentation never says that the "." hash lookup can be much slower than the [] lookup. I hope it is a bug (one less thing to remember). They both worked at the same speed in PS Version 2.0 and diverged sometime after that.

                          Two script files. The first calls the second forcing versions 1 thru 5 of PowerShell.

                          The "." hash lookups in PS Version 2.0 take .028 seconds.
                          The "."…

                          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 →
                          • PowerShell Query returns nothing

                            I am trying to do a query to obtain setting values of RSOP_SecuritySettingBoolean in PowerShell (and WMI) but it returned nothing. The following query I attempted:

                            E:\>PS E:\> Get-WmiObject -Namespace "root\RSOP\Computer" -Query "SELECT setting FROM RSOP_SecuritySettingBoolean Where KeyName='ClearTextPassword' and precedence='1'"

                            PS E:\>

                            For your extra information:

                            E:\>ver

                            Microsoft Windows [Version 10.0.14393]

                            PS E:\> $psversiontable

                            Name Value
                            ---- -----
                            PSVersion 5.1.14393.1198
                            PSEdition Desktop
                            PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
                            BuildVersion 10.0.14393.1198
                            CLRVersion 4.0.30319.42000
                            WSManStackVersion 3.0
                            PSRemotingProtocolVersion 2.3
                            SerializationVersion 1.1.0.1

                            My Windows 10 OS is still fresh, installed about 2 months ago via ISO. Why is it not returning any results? Please help.…

                            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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                            • BUG: PowerShell xml node assignment with where-method

                              Doing this works:
                              ($xmlDoc.unattend.settings.Where({$_.pass -eq "specialize"}).component.Where({$_.name -eq "Microsoft-Windows-Shell-Setup"}) | Where-Object {$true}).ComputerName = "Test02";
                              But without "| Where-Object {$true}" it fails.

                              https://social.technet.microsoft.com/Forums/en-US/6801cfda-4699-4c2b-8a84-7d12de76e51d/powershell-xml-node-assignment-bug?forum=ITCG

                              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 →
                              • DSC need to use full width of command processor in output

                                DSC output is not respecting width of console and wraps text around despite full width is not utilized.
                                Please see details here (https://github.com/PowerShell/PowerShell/issues/4030)

                                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 →
                                • Please Offer file attachment option for Feedback or Bug Report

                                  Please Offer file attachment option for Feedback or Bug Report! This Option makes issue Reporting much Simpler & Clearer to explain & describe a specific issue/s!

                                  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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Enable WINRM certificate mapping for domain user

                                    Currently I need to manage Windows DNS server. I would like to use a client certificate to connect to WinRM to manage it, since I want to expose it in RESTful interface. But WINRM certificate mapping only allows non-domain account.

                                    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  ·  WinRM  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Get-TargetResource should not use 'Required' parameters

                                      I'm not sure why this is, but for some reason Get-TargetResource requires not only the 'Key' parameters, but also the 'Required' parameters. My understanding is only 'Keys' should be necessary to find an existing resource and the 'Required' parameters are necessary when you want to create/update/delete something related to a resource.

                                      This really makes no sense and will hinder our ability to build higher level tech on top of DSC. If I have the key values for any piece of data in any system, I should be able to retrieve it without any additional information.

                                      In almost all of the…

                                      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 →
                                      • Inconsistant handling of native command stderr

                                        I discovered recently that the handling of `stderr` from native commands isn't being dealt with consistently between Windows PowerShell and Windows PowerShell ISE.

                                        Steps to reproduce
                                        ------------------

                                        ```powershell
                                        $errorActionPreference="stop"; try { cmd /c nosuchexe } catch { 'dang!' }
                                        ```

                                        Actual ISE behavior (expected)
                                        -----------------

                                        ```none
                                        dang!
                                        ```
                                        Native commands writing to `stderr` while `$errorActionPreference="stop"` generate a catchable `NativeCommandError` which encapsulates the original error message in a `ErrorRecord`. It is easy to capture, analyze, and reword error messages in context.

                                        Actual CLI behavior
                                        ---------------

                                        ```none
                                        'nosuchexe' is not recognized as an internal or external command,
                                        operable program or batch file. …

                                        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 →
                                        • what works?

                                          list what works?

                                          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 →
                                          ← Previous 1 3 4 5 57 58
                                          • Don't see your idea?

                                          Feedback and Knowledge Base