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. 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,…

    101 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

      20 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
    • Test-DscConfiguration returns a String instead of a Boolean value

      Test-DscConfiguration returns a String instead of a Boolean value.

      Contrary to what is mentionned in the documentation, the function Test-DscConfiguration does not return a boolean value.

      When you do a GetType() of the return value of Test-DscConfiguration you get a string with 'true' or 'false'.

      It's impossible to do a simple if (Test-DscConfiguration) because the string 'false' enter inside the if, we are forced to cast the return value of this cmdlet in boolean or to do the comparison with -eq $True, which seems to cast it automatically.

      6 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  ·  Desired State Configuration (DSC)  ·  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…

        35 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

          12 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
        • "Using module" statement does not reload module after changes are made

          Problem Description
          ------------------
          If you are using the `using module` statement, it will load the module without any issues. However, if you make a change to the module and run the `using module` statement again without restarting your PowerShell session, it will not load the new modified module into memory, and instead will continue to use the old existing module that was loaded. This makes doing development with `using module` statements very tedious as you must continually reload your PowerShell session whenever you make changes to the module.

          Ideally we would just use `Import-Module -Name [module name] -Force` to avoid…

          8 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 →
          • Reset LCM configuration

            Reset LCM configuration.

            Hi and sorry for my funny English.
            When I configure my LCM, it's impossible to reset state.
            If I want a default configuration, I send a new configuration this default value for all Settings (here, no value, just settings).

            [DscLocalConfigurationManager()]
            Configuration ResetLCM {
            Node MyNode {
            Settings {
            ActionAfterReboot =
            AllowModuleOverwrite =
            CertificateID =
            ConfigurationDownloadManagers =
            ConfigurationID =
            ConfigurationMode =
            ConfigurationModeFrequencyMins =
            DebugMode =
            MaximumDownloadSizeMB =
            RebootNodeIfNeeded =
            RefreshFrequencyMins =
            RefreshMode =
            ReportManagers =
            ResourceModuleManagers =
            SignatureValidations =
            StatusRetentionTimeInDays =
            }}

            I think it's easier to use command.

            For example, there is a reset configuration for DSCConfigurationDocument. …

            5 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  ·  Desired State Configuration (DSC)  ·  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.

              22 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

                3 comments  ·  ISE and tooling  ·  Flag idea as inappropriate…  ·  Admin →
              • Receive-Job duplicates Write-Host output

                Starting in PowerShell 5.1, if a background job uses Write-Host, the Receive-Job cmdlet shows each line of output twice.

                # Steps to Reproduce
                1. Run this command: `Start-Job { 1..10 | % { Start-Sleep -Milliseconds 10 ; Write-Host $_ } } | Wait-Job | Receive-Job`
                2. Note the duplicate numbers. This error does not happen in Powershell 6.0.4.

                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 Engine  ·  Flag idea as inappropriate…  ·  Admin →
                • Backport Powershell 6.x to Windows Powershell

                  To keep Windows Powershell up to date please backport any new features from Powershell 6.x to Windows Powershell.

                  3 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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                  • No paid modules in the module repository

                    I recently posted this on TechNet, and was directed here...

                    I couldn't remember how many times I've heard Jeffrey Snover talk about the experience that the Powershell team are after being one where you can start at a PS prompt and find and finish everything you need.

                    First, great job, because it is actually shaping up to an environment that is just that. However, I just ran in to something that made me curse out loud alone in my office, and I want to believe that the majority of the community will be with me on this.

                    I started, as…

                    5 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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                    • New-SmbShare -Whatif not working

                      New-SmbShare with -Whatif switch NOT working, it runs the command instead of showing the whatif massage

                      Test with vscode insider

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

                      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

                        1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                      • Bug: Invoke-WebRequest keeps downloading beyond the file's size

                        Migrated from here: https://github.com/PowerShell/PowerShell/issues/7822.

                        To repro:

                        powershell wget https://storage.googleapis.com/chrome-infra/depot_tools.zip

                        The file size is ~19MB, but the download progress goes way beyond that and has to be manually stopped.

                        At the same time, (New-Object System.Net.WebClient).DownloadFile() works correctly.

                        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 →
                        • Module Cmdlets missing after Import-Module

                          I have started experiencing an issue on multiple machines where modules that once worked fine now stop functioning correctly.

                          The issue appears to affect Windows 10 machines that have been in service for some time, but does not affect new Windows 10 installs. This leads me to believe that something like a windows update broke the correct functioning of the module import functionality on these machines at some point in the past.

                          The modules in question have been SQLPS (installed with SSMS), SqlServer (from PSGallery), and AWSPowerShell (also from PSGallery). The issue is that after installing the module and importing…

                          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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                          • ¿Pienso?

                            Creo, que si los Hispano-Hablantes, pudiesen tener acceso a los comentarios e ideas que la gente detendrían mas de 1000.000.000, si en números, Por favor empecemos por respetar a todos, no solo los Anglo-Sajones, y la gente de sus colonias (coman GUEL ) lo pongo en Español, por dignidad, Creo (estoy, seguro) que pagan lo mismo.

                            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

                              1 comment  ·  Desired State Configuration (DSC)  ·  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.

                              14 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 →
                              • Bug: wrong encoding in some *.format.ps1xml files

                                It's probably useless and a shame that M$$ is usually not fixing this kind of bugs:

                                Some PowerShell xml Files have the wrong encoding, for example this one:
                                c:\Windows\System32\WindowsPowerShell\v1.0\Event.Format.ps1xml

                                It states that it is using:
                                <?xml version="1.0" encoding="utf-8" ?>
                                but in fact, it's utf-16.

                                Test it:
                                $xmldoc = New-Object xml.XmlDocument
                                $xmldoc.Load('c:\Windows\System32\WindowsPowerShell\v1.0\Event.Format.ps1xml')
                                Exception calling "Load" with "1" argument(s): "'.', hexadecimal value 0x00, is an invalid character. Line 2, position 1."

                                Change the header to:
                                <?xml version="1.0" encoding="utf-16" ?>
                                and it will work.

                                M$ still does not have the most basic unit tests to assure that config files must have the right…

                                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 →
                                • Bug: wrong encoding in some *.format.ps1xml files

                                  It's probably useless and a shame that M$$ is usually not fixing this kind of bugs:

                                  Some PowerShell xml Files have the wrong encoding, for example this one:
                                  c:\Windows\System32\WindowsPowerShell\v1.0\Event.Format.ps1xml

                                  It states that it is using:
                                  <?xml version="1.0" encoding="utf-8" ?>
                                  but in fact, it's utf-16.

                                  Test it:
                                  $xmldoc = New-Object xml.XmlDocument
                                  $xmldoc.Load('c:\Windows\System32\WindowsPowerShell\v1.0\Event.Format.ps1xml')
                                  Exception calling "Load" with "1" argument(s): "'.', hexadecimal value 0x00, is an invalid character. Line 2, position 1."

                                  Change the header to:
                                  <?xml version="1.0" encoding="utf-16" ?>
                                  and it will work.

                                  M$ still does not have the most basic unit tests to assure that config files must have the right…

                                  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 →
                                  • BUG: Get-DnsServer* cmdlets with -ErrorAction SilentlyContinue mask pipeline exceptions

                                    PS > Get-DnsServerZone -ComputerName proper_dns_server -ZoneName existing_dns_zone -ErrorAction SilentlyContinue| % { throw "OOPS!" }

                                    # NO ERROR !

                                    PS > Get-DnsServerZone -ComputerName proper_dns_server -ZoneName existing_dns_zone | % { throw "OOPS!" }
                                    Exception calling "EndProcessing" with "0" argument(s): "OOPS!"
                                    At line:354 char:17
                                    + $__cmdletization_objectModelWrapper.EndProcessing()
                                    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                    + CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
                                    + FullyQualifiedErrorId : RuntimeException

                                    PS >Get-Item . -ErrorAction SilentlyContinue | % { throw "OOPS" }
                                    Get-Item : OOPS
                                    At line:1 char:1
                                    + Get-Item . -ErrorAction SilentlyContinue | % { throw "OOPS" }
                                    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                    + CategoryInfo : OperationStopped: (OOPS:String) [Get-Item], RuntimeException
                                    + FullyQualifiedErrorId : OOPS,Microsoft.PowerShell.Commands.GetItemCommand

                                    # As expected

                                    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 →
                                    • Import-Certificate need example to import into local machine.

                                      Import-Certificate need example to import into local machine.

                                      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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Get-Item / Get-ChildItem returns wrong Target-Property if Item is on a Directory Junction to another drive

                                        It's annoying that we have to report Bugs in UserVoices
                                        and its a shame that M$$ is fixing BUGS only if there are enough UserVoices.

                                        Anyway:

                                        Hello

                                        If we create this Directory Junction between local Drives:
                                        mklink /J C:\Temp D:\Data\Temp\

                                        So that accessing: C:\Temp\
                                        in fact works here: D:\Data\Temp

                                        Now, if we call e.g.
                                        (Get-Item C:\Temp\MyFile.txt).Target

                                        We get:

                                        Wrong: Target : {C:\Data\Temp\MyFile.txt}
                                        Should be: Target : {D:\Data\Temp\MyFile.txt}
                                        It's a shame that M$ still does not have Unit Tests to validate the most basic situations.
                                        (Assuring to return the right Target on different LinkTypes, is the most important reason for this…

                                        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 →
                                        • Get-Item / Get-ChildItem returns wrong Target-Property if Item is on a Directory Junction to another drive

                                          It's annoying that we have to report Bugs in UserVoices
                                          and its a shame that M$$ is fixing BUGS only if there are enough UserVoices.

                                          Anyway:

                                          Hello

                                          If we create this Directory Junction between local Drives:
                                          mklink /J C:\Temp D:\Data\Temp\

                                          So that accessing: C:\Temp\
                                          in fact works here: D:\Data\Temp

                                          Now, if we call e.g.
                                          (Get-Item C:\Temp\MyFile.txt).Target

                                          We get:

                                          Wrong: Target : {C:\Data\Temp\MyFile.txt}
                                          Should be: Target : {D:\Data\Temp\MyFile.txt}
                                          It's a shame that M$ still does not have Unit Tests to validate the most basic situations.
                                          (Assuring to return the right Target on different LinkTypes, is the most important reason for this…

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

                                          Feedback and Knowledge Base