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. 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: 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 →
          • 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 →
              • Enable-ClusterStorageSpacesDirect Needs a -FORCE parameter for consistency

                The Enable-ClusterStorageSpacesDirect cmdlet does not have a -FORCE parameter.

                When you run the cmdlet, you get a pop-up confirmation prompt. To avoid this, the cmdlet should have a -FORCE parameter.

                It's true you can use -CONFIRM:$FALSE - but that is inconsistent with other cmdlets throughout PowerShell.

                For consistency add a -FORCE parameter to this cmdlet that avoids the popup confirmation. OF course, for compatibility, keep the $Confirm:$False.

                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 →
                • 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 →
                  • The task "Windows Defender Verification" is producing a restore point every day.

                    The task "Windows Defender Verification" is producing a restore point every day. There should be an additional parameter in "Set-MpPreference" to handle that issue.

                    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 →
                    • why isn't there a simple command to get the number of open connections to a specific share?

                      get-smbsession lists open share sessions and get-smbshare lists shares but where is the command to get the list who is connected to which share?

                      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 →
                      • Register-ScheduledTask

                        Register-ScheduledTask -password parameter should accept secure string or PScredential. Currently it accept plain text and the password shows up in event log when register

                        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  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
                        • PowerShell ISE - PackageManagement\Register-PackageSource : The property 'Name' cannot be found on this object.

                          Facing issue with PowerShell repository registering

                          PackageManagement\Register-PackageSource : The property 'Name' cannot be found on this object.

                          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 →
                          • BUG: Test-Certificate -AllowUntrustedRoot does not validate expiration

                            Test-Certificate with the -AllowUntrustedRoot parameter does not fail validation if the certificate has expired. This can be shown by creating a self-signed certificate with New-SelfSignedCertificate -NotAfter (Get-Date).AddMinutes(1) and waiting for expiration. This is contrary to the online documentation for Test-Certificate.

                            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 →
                            • PowerShell Compare-Object odd output when comparing recursive items with -Exclude

                              This works:

                              $one = Get-ChildItem -Recurse -Path $PathLocal
                              $two = Get-ChildItem -Recurse -Path $PathMirror
                              Compare-Object -ReferenceObject $one -DifferenceObject $two

                              This gets the wrong result:

                              $one = Get-ChildItem -Recurse -Path $PathLocal -Exclude *.txt
                              $two = Get-ChildItem -Recurse -Path $PathMirror -Exclude *.txt
                              Compare-Object -ReferenceObject $one -DifferenceObject $two

                              Somehow -Exclude is breaking the functionality.

                              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 →
                              • Out-Printer appears to mishandle tab characters

                                Tab characters in strings sent to Out-Printer appear to be mishandled:

                                * Printing to an XPS or PDF document quietly *strips* tab characters.

                                * Printing to the 'Generic / Text Only' printer results in a broken 2-line / 2-column layout.

                                Verify with the following commands:

                                ```powershell

                                "col1`tcol2" | out-printer 'Microsoft XPS Document Writer'
                                "col1`tcol2" | out-printer 'Microsoft Print to PDF'

                                "col1`tcol2" | out-printer 'Generic / Text Only'

                                ```

                                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 →
                                  • Powershell Windows defender bug

                                    I found a bug with windows defender cmdlets!
                                    Cmdlet:
                                    set-mppreference -scanscheduletime
                                    set-mppreference -scanschedulequickscantime

                                    Providing an argument in format HH:mm works for values from 00:00 to 16:59 works as expected and when running get-mppreference the scanscheduletime and scanschedulequickscantime fields show the time requested.

                                    Providing a time past 7pm (17:00) and then running get-mppreference shows the time in the format 2982615.22:16:00, which i believe means ~3 million days in the future.

                                    windows 10 enterprise build 171314
                                    windows server 2016 datacenter build 14393

                                    Please let me know if you would like any further details!

                                    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 →
                                    • 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 →
                                      • 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 →
                                        • BUG: Manage RDS certificates using powershell fails after WMF 5.1

                                          Trying to manage Remote Desktop certificates using powershell after installing WMF 5.1 on Windows Server 2012 fails with the following error message:
                                          PS C:\Users\MyUser> Import-Module RemoteDesktop
                                          PS C:\Users\MyUser> Set-RDCertificate -Role RDWebAccess

                                          Get-Server : The term 'Get-Server' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a
                                          path was included, verify that the path is correct and try again.
                                          At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\Certificate.psm1:304 char:22
                                          + $webaccess = Get-Server -ConnectionBroker $ConnectionBroker - ...
                                          + ~~~~~~~~~~
                                          + CategoryInfo : ObjectNotFound: (Get-Server:String) [], CommandNotFoundException
                                          + FullyQualifiedErrorId : CommandNotFoundException

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

                                          Feedback and Knowledge Base