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. Notification option for authors when publishing to PS Gallery

    When an author publishes an update to their module hosted on the gallery it should provide an option to push a notification to their configured social media accounts.

    So an author configures Twitter and LinkedIn profiles on their account/profile. A configuration option within the module being published should allow for a setting that will push a notification to their social media, on their behalf, announcing a new release of that module.

    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

      1 comment  ·  PowerShell Gallery  ·  Flag idea as inappropriate…  ·  Admin →
    • [datetime] type accelerator only uses en-US culture

      The [datetime] when used as a type accelerator only uses the en-US culture and therefore other date formats either error out or they are interpreted incorrectly, This makes using the ConvrtFrom-String difficult when adding type accelerators to automatically discover the property type from text. If we use the Get-Date command then the correct culture is used. It appears to be just the [datetime] type accelerator that is not consistent with this? Please fix!!

      4 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

        1 comment  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
      • Remove the implied Get- verb

        Please remove the ability to use the implied Get verb. It is cryptic, expensive and unnecessary.
        Thanks.

        6 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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
        • copy-item progress

          Add an optional switch to show the progress of an ongoing copy operation. Could be useful for large operation. Basically replicate as much information as the Explorer does, without the performance graph.

          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

            0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
          • RMDIR bug - causing "Access is denied"

            :** z:\ca\WinRdBug.cmd *** L=001 --- 2017/12/05 13:02:28
            : The RMDIR command has a bug that, as well as not working,
            : causes the target directory to become inaccessible.
            : i.e. operation on it all result in "Access is denied" or similar :messages.

            : The problem is easily demonstrated using the sequence of :commands below.

            : This bug is causing significant inconvenience and we need a fix or
            : reasonable work-around quickly please. (just upgraded to Win10
            : from XP where this is not an issue).

            mkdir c:\t1229
            echo *** >c:\t1229\x.x
            type c:\t1229\x.x
            rmdir c:\t1229 /s /q
            type c:\t1229\x.x
            pause

            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 →
            • Bug: Slow function when setting a parameter to Mandatory and specifying its Type

              There is a bug that causes a function to be called much more slowly than it should if an array parameter has both Mandatory and Type specified. I'm guessing something is causing the system to iterate through the array, so the larger the array, the longer to call the function.

              With both Mandatory and Type specified, it takes a whole second to call a function with a 10MB byte array. If a 1byte array is used, it takes less than a millisecond to call the function. If only one, the other, or neither are specified, then it takes less than…

              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

                0 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
              • Move-Item's -Verbose causes $ErrorActionPreference to be ignored

                Move-Items's -Verbose parameter causes the global $ErrorActionPreference = "Stop" to be ignored. This is a bug. Here's a repro script:

                BugRepro.ps1:

                $ErrorActionPreference = "Stop"
                Write-Host "ErrorActionPreference is $ErrorActionPreference"
                mkdir folder -ErrorAction SilentlyContinue | Out-Null
                "" > a.txt
                Copy-Item a.txt folder
                Write-Host "About to trigger error"
                Move-Item a.txt folder -Verbose | Out-Null
                Write-Host "If you're reading this, then execution didn't stop!"
                Write-Host "Remove the Verbose paramter and it does stop, like it should."

                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

                  1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                • PowerShell StackOverFlowException: get-childitem -path HKLM:\ -recurse -include *Windows*

                  PowerShell has a bug in it which causes a "StackOverFlowException" when running the following command:
                  get-childitem -path HKLM:\ -recurse -include *Windows*

                  It was originally reproduced while looking for something different than:
                  Windows

                  This is consistently reproducible in latest updates applied of Windows 10 x64 Business and Home, with both PowerShell.exe, and ISE, x86 and standard.

                  $PSVersionTable.PSVersion

                  Major Minor Build Revision
                  ----- ----- ----- --------
                  5 1 16299 98

                  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 →
                  • Fix LoadDefaultTypesFiles when using out of process runspace

                    Fix for "Object reference not set to an instance of an object." when using LoadDefaultTypeFiles() with out of process runspace

                    Reproduce:
                    TypeTable.LoadDefaultTypeFiles()

                    Reproduce underlying cause:
                    Copy C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml to another name and run:
                    var typeTable = new TypeTable(new List<string> { @"C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types-debug.ps1xml" });
                    Console.WriteLine(typeTable);

                    The error is:
                    "There were errors loading TypeTable. Look in the Errors property to get detailed error messages."
                    , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types-debug.ps1xml(3003) : Error in type "System.Security.AccessControl.ObjectSecurity": The "Type" node must have "Members", "TypeConverters", or "TypeAdapters".
                    , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types-debug.ps1xml(3036) : Error: CodeProperty should use a getter or setter method.
                    , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types-debug.ps1xml(3037) : Error: Unable to find type [Microsoft.PowerShell.Commands.SecurityDescriptorCommandsBase].
                    , C:\Windows\SysWOW64\WindowsPowerShell\v1.0\types-debug.ps1xml(3029) :…

                    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 →
                    • Include function to show bytes human readable like linux.

                      In Linux in many commands like "ls", "df", and other have an option to show bytes sizes in human readable formats (bytes, KB, MB, GB, TB, etc).
                      In powershell is necessary to create a function to do this.
                      Would be interesting create some function to powershell convert the bytes value in the human readable value.

                      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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                      • Mandatory parameters value is not accessible in DynamicParam block if the value to the parameter is given when prompted.

                        Parameter value from param block is not available in DynamicParam block if not passed while calling the function/Script. Here if I set the parameter in param block as it as mandatory the script/function will prompt for the input and the input given is not available in DynamicParam block.

                        https://social.technet.microsoft.com/Forums/en-US/637bcff2-ab98-4ead-a036-38e7eb94a261/dynamicparams-with-mandatory-parameters?forum=winserverpowershell

                        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 →
                        • Fix .NET date formatting bug in .ToString()

                          PS D:\> gcim win32_operatingsystem | % caption
                          Microsoft Windows Server 2016 Standard

                          PS D:\> $PSVersionTable.PSVersion

                          Major Minor Build Revision
                          ----- ----- ----- --------
                          5 1 14393 1358

                          PS D:\> [DateTime]::Now.ToString('yyyy-MM-dd HH:mm:ss')
                          2017-07-27 12.29.37

                          9 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

                            10 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                          • Change default font of PS on OSX

                            on OSX, the shell is white, not black or blue.

                            The yellow is a really bad UI implementation.

                            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 →
                            • Define which as one of standard aliases of Get-Command

                              Users of Unix-like OSs(e.g. macOS & Linux) use the command `which` to know where the executable of a command is.

                              ```
                              $ which code
                              /usr/bin/code
                              ```

                              On the other hand, users of PowerShell uses the commandlet `Get-Command` or the alias `gcm`.

                              ```
                              PS C:\> (gcm code).Path
                              C:\Program Files\Microsoft VS Code\bin\code.cmd
                              ```

                              However, the users of Unix-like OSs have to learn `gcm` if they have to use PowerShell and want to know the place of a command, though they don't if they would like to, for example, change directories and show the contents of files because PowerShell defines the same aliases…

                              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: WMF 5.1 breaks SFC on Windows 8.1, and SFC might breaks DSC

                                After installing WMF 5.1 in Windows 8.1 / Server R12, running SFC integrity scan reports and "repairs" couple of localized DSCResources files
                                but it actually replaces new WMF 5.1 files with inbox DSCResources files, which would breaks DSC on non-english systems

                                this happens because the files are referenced (shared) in two different WinSxS components
                                in inbox Windows 8.1 the files are contained in:
                                Microsoft.PowerShell.DSC.Resources
                                but in WMF 5.1 they are now contained in:
                                Microsoft.PowerShell.DSCResources.Resources
                                hence the inbox files are not considered superseded, and SFC tries to restore them

                                this issue is similar to this one for Windows 7 (not Powershell…

                                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 →
                                • [Bug] Command line parsing: spaces and \"

                                  This is my powershell version
                                  ==========
                                  $PSVersionTable
                                  Name Value
                                  ---- -----
                                  PSVersion 5.1.15063.674
                                  PSEdition Desktop
                                  PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
                                  BuildVersion 10.0.15063.674
                                  CLRVersion 4.0.30319.42000
                                  WSManStackVersion 3.0
                                  PSRemotingProtocolVersion 2.3
                                  SerializationVersion 1.1.0.1
                                  =====END=====

                                  Let's see a use scene
                                  ========== WindowsPowershell
                                  function FormatReg([string]$value)
                                  {
                                  $value = $value -replace '"', '\"'
                                  $value = '"' + $value + '"'
                                  return $value
                                  }
                                  $temp = FormatReg '"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" "-Command" "if((Get-ExecutionPolicy) -ne ''AllSigned'') { Set-ExecutionPolicy -Scope Process Bypass }; & ''%1''"'
                                  reg.exe add HKEY_CLASSES_ROOT\Microsoft.PowerShellScript.1\Shell\0\Command /f /d $temp
                                  =====END=====
                                  > Error: Invalid syntax.
                                  > Type register Add/? "Learn about usage information.

                                  ========== cmd
                                  reg.exe add HKEY_CLASSES_ROOT\Microsoft.PowerShellScript.1\Shell\0\Command /f /d "\"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe\"…

                                  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

                                    1 comment  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                                  • code execution not synchronously when using "| Select-Object...."

                                    When using " | Select-Object......" then code execution behave like it's not running synchronously.
                                    Example:
                                    Get-WmiObject Win32_NetworkAdapter | Where-Object {$_.PhysicalAdapter -eq $true} | Select-Object DeviceID, Name
                                    Read-Host "Press key to continue"

                                    The result will be printed AFTER the Read-Host command, nut before as you would expect.

                                    A workaround is to add " | Out-Host"

                                    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 →
                                    • very inconsistent drive letter usage

                                      Hi there

                                      in this case I have to remove and reinstall an OS while booting from usb stick. But this is only one example - it´s not the first time im seeing this behaviour.

                                      if (Test-path c:) {Get-Volume -DriveLetter c | Get-Partition | Remove-PartitionAccessPath -AccessPath c:\}

                                      In this line the term C is used three times

                                      First time as c: (here would be c:\ also possible)
                                      Second time as c (neither c: nor c:\ is working here)
                                      Third time as c:\ (neither c nor c: is working here)

                                      I´m working with variables - this means I have to create 3…

                                      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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Bug: Loading a file with a class fails if the file's full path contains a comma

                                        Create a file, ClassExample.ps1 with the sample code below. Save the file in a location where the full path does not contain a comma.

                                        Class TestClass {
                                        [void] TestFunction ( [string]$Text = "" ) {
                                        Write-Host $Text
                                        }
                                        }
                                        $TestObj = New-Object TestClass
                                        $TestObj.TestFunction("Hello World!")

                                        Start a PS shell and run the script:

                                        PS C:\Users\don\Desktop\PSBug> .\ClassExample.ps1
                                        Hello World!

                                        Rename the folder or class file and include a comma in the new name and run the script again:

                                        PS C:\Users\llf\Desktop\PSBug> & '.\Class,Example.ps1'
                                        The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
                                        At line:1 char:1
                                        + & '.\Class,Example.ps1'
                                        +…

                                        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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Order of output not intuitive/ not sequential

                                          Example Code:
                                          $proc = Get-Process | Select-Object -Property ProcessName

                                          $proc[5]

                                          "A"
                                          "B"
                                          Write-Host "$proc[5]"

                                          The output of Write-Host precedes the output of the strings beforehand. This is a non-sequential behaviour.

                                          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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4 5 62 63
                                          • Don't see your idea?

                                          Feedback and Knowledge Base