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. Support new-pssession with powershell direct

    The new copy-item options to use a possession to copy files is great, please also support making an new-pssession with a vm name so it can be used with copy-item

    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  ·  Flag idea as inappropriate…  ·  Admin →
    • Migrate Sconfig.vbs to PowerShell

      With all Microsoft Tools going to PowerShell, I think it would be better for this config tool to be a PowerShell rather than VB Script.

      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

        0 comments  ·  Flag idea as inappropriate…  ·  Admin →
      • PowerShell Remoting using private key authentication

        Enable PowerShell Remoting login using private key authentication similar to the SSH protocol. Entering passwords all the time the log into remote PowerShell is tedious. Being able to use local secure private key to log into many cloud server instances would ease the process of creating new remote sessions.

        28 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

          2 comments  ·  Flag idea as inappropriate…  ·  Admin →
        • Enable Kerberos pass-trough for nested WinRM sessions

          A second or third hop WinRM session should support the usage of the primary session's ticket if Kerberos delegation is enabled for WinRM. CredSSP is not always wanted or might be limited due to security policies

          10 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  ·  Flag idea as inappropriate…  ·  Admin →
          • Provide PowerShell module to manage Local Security Policy

            We've now got the the DSC modules for this, but a standalone module for use outside of DSC would be extremely useful

            0 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 →
            • Mount-DiskImage fails with: "Access is denied" 0x5 occurred while reading the console output buffer

              After upgrade from Windows 1803 to Windows 1809 `Mount-DiskImage $iso_path` starts failing with the following error:

              ```
              Exception calling "EndProcessing" with "0" argument(s): "Win32 internal error "Access is denied" 0x5 occurred while reading the console output buffer. Contact Microsoft Customer Support Services."
              At line:352 char:17
              + $__cmdletization_objectModelWrapper.EndProcessing()
              + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              + CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
              + FullyQualifiedErrorId : HostException

              ```

              The powershell command is executed under Administrator user in packer. It actually mounts specified image path, but throws this exception on attempt to interact with stdout.

              0 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 →
              • BUG: Preserve the current directory name as stored in the filing system and not as entered by the user

                The PowerShell console uses the path as entered by the user and not as stored in the filing system. This is inconsistent with the Command Console behaviour and causes applications that rely on the correct casing of the path to fail. IMHO the console should be case insensitive when searching for fils system paths but should preserve the case when returning the file path.

                0 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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                • Powershell Core should have a nuget package for release

                  It would be awesome if powershell core was released as a package on nuget.org as well as the regular means.

                  The reason for this is build systems like cake build can have tools referenced via nuget packages and will pull them down as part of the build.

                  0 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

                    survey  ·  0 comments  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                  • Bug: Installing WMF4.0 then WMF5.0 on Win7 SP1

                    Hello,
                    I understand that on Windows 7 SP1-Machines we have to install WMF 4.0 before upgrading to WMF 5.0.
                    On all our Windows 7 machines, before installing WMF 4.0 KB2819745, a sample output for Path Environmental Variable, getting with [Environment]::GetEnvironmentVariable(“Path”), looks like this:
                    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
                    After installing WMF 4.0 KB2819745, it looks like this:
                    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;
                    There is a multiple path to the Powershell.exe.
                    After installing KB3134760 to upgrade to WMF 5.0, it’s getting even worse as path-variable looks like this:
                    C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;
                    Is this a known issue?
                    Thanks in advance
                    Norbert

                    0 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  ·  Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                    • Error in Keywords section of About_WorkFlowCommonParameters

                      In the help text about_WorkFlowCommonParameters, in the KEYWORDS section of the full text, it shows two about_* files. The first (About_WorkFlowCommon_Parameters) does not exist.

                      0 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  ·  Documentation  ·  Flag idea as inappropriate…  ·  Admin →
                      1 2 71 72 73 75 Next →
                      • Don't see your idea?

                      Feedback and Knowledge Base