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. Get-PartitionSupportedSize and MSFT_Partition class report wrong partition max size

    The cmdlet Get-PartitionSupportedSize as well as the CIM class MSFT_Partition (https://docs.microsoft.com/en-us/previous-versions/windows/desktop/stormgmt/msft-partition#members) either report wrong values for the maximum supported partition size or the documentation is not clear enough.

    Creating a new partition that uses the maximum size produces partitions that fall 0.98MB short of the maximum supported size. It looks like the CIM class calculates some default offset into the reported SizeMax, since changing the offset did not change the issue.

    Steps to reproduce:

    foreach ($off in 1,10,15,20,50)
    {
    $null = Clear-Disk -Number 1 -RemoveData -Confirm:$false
    $null = Initialize-Disk -Number 1 -PartitionStyle GPT
    $reservedpartition = get-partition -number 1…

    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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
    • Get-NetQosFlowControl -InterfaceAlias

      Hi,

      I`m trying to implement "Get-NetQosFlowControl -InterfaceAlias <name>" cmdlet using WMI. I want to query adapter specific NetQosFlowControl configuration.

      I don't see any available API in WMI to do this.

      How could I get adapter specific NetQosFlowControl configuration using only WMI?

      Thanks,
      Alexander

      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  ·  WMI  ·  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.

        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

          2 comments  ·  WMI  ·  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
            Signed in as (Sign out)

            We’ll send you updates on this idea

            0 comments  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
          • [bug] ConverttoDateTime

            The ConvertToDateTime() ScriptMethod is incorrect / broken and does NOT take into account the current time zone as defined by System.Management.ManagementDateTimeConverter.ToDateTime() method. In fact, it's not applying any time zone at all. Full analysis and test scripts at my blog - https://goo.gl/b4ZTqf

            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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
            • Win32_ComputerSystem Username does not show disconnected sessions

              Yet another script to determine if it will be disruptive to reboot a workstation. Win32_ComputerSystem.Username is blank if the user(s) have locked the computer (I'm pretty sure this is considered session disconnect). Is there a way to find the users who are logged on but not actively?

              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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
              • Support for Query Language CQL lacks documentation: CIM_QueryCapabilities missing

                The Get-Ciminstance -QueryDialect parameter accepts CQL
                https://technet.microsoft.com/en-us/itpro/powershell/windows/cimcmdlets/get-ciminstance#-querydialect
                Official tutorials
                http://www.wbemsolutions.com/tutorials/DMTF/wbem-cql.html
                and specifications say the standard class CIM_QueryCapabilities reveals the features supported by the CQL implementation.
                However, this class is missing, and documentation is not to be found.
                Would Microsoft care to spare us the mystery?

                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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                • ResourceUriSessionSet of Get-CimInstance doesn't filter

                  Observe this sample output: same -Filter, different results.
                  Equal parity for general CIM would be nice.

                  > Get-CimInstance -ResourceUri http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk -Filter "DeviceID='D:'" -KeyOnly -CimSession $cs | % { '{{{0}}}' -f $_.DeviceId }
                  {C:}
                  {D:}
                  > Get-CimInstance -ClassName Win32_LogicalDisk -Filter "DeviceID='D:'" -KeyOnly -CimSession $cs | % { '{{{0}}}' -f $_.DeviceId }
                  {D:}
                  > $PSVersionTable

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

                  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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                  • Get-Wmiobject

                    I am trying to get the details of the user logon to server and using the get-wmiobject in PS but not able to get details output is blank.

                    PS C:\Users\username> Get-WmiObject -Class win32_computersystem -ComputerName localhost | Select-Object UserName

                    UserName
                    --------

                    PS C:\Users\username> Get-WmiObject -Class win32_computersystem -ComputerName localhost | Select-Object Name

                    Name
                    ----
                    servername

                    i tried to run it on PS v.4 and v.5 on Win 2k8 r2 server and on 2k12 r2 as well but no luck .
                    but if i run same on my laptop its provide me the user name logon on to my laptop. This is bit…

                    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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                    • Make it easier to use BITS with powershell remoting

                      Votes from Connect: 23

                      Original Date Submitted: 5/22/2012 8:58:19 AM

                      Description:
                      ********Contact Information********
                      Handle: somedude321
                      Site Name: PowerShell
                      Feedback ID: 743030
                      ***************************************

                      Frequency: Always Happens
                      Regression: Yes, this happens in all previous versions

                      Problem Description:
                      Currently you need to do some serious developing to be able to use bits in a remoting session. Because bits doesn't allow a user logged in with powershell remoting to start jobs: "The remote use of BITS is not supported".

                      The remoting session has to impersonate System, or call via a process running as System, to be able to call bits.

                      I want the winrm…

                      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

                        1 comment  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                      • Wrong output in CIM cmdlets like Get-SmbShareAccess, Enable-NetAdapterChecksumOffload, etc.

                        (Originally posted in https://connect.microsoft.com/PowerShell/feedback/details/1852524)

                        Standard CIM cmdlets can produce invalid output. I reproduced the problem with
                        two commands — Get-SmbShareAccess and Enable-NetAdapterChecksumOffload.
                        I also believe that the problem is not limited to these particular commands.

                        Below is an example of me executing 'Get-SmbShareAccess C$, D$' twice. Please
                        note that the first output is incorrect and it shows 6 entries for C$, instead
                        of expected 3 entries for C$ and 3 entries for D$:

                        PS C:\> Get-SmbShareAccess C$, D$

                        Name ScopeName AccountName AccessControlType AccessRight
                        ---- --------- ----------- ----------------- -----------
                        C$ * BUILTIN\Administrators Allow Full
                        C$ * BUILTIN\Administrators Allow Full
                        C$…

                        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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                        • CIM Methods are hard to discover

                          Votes from Connect: 11

                          Original Date Submitted: 6/29/2013 6:19:21 AM

                          Description:
                          ********Contact Information********
                          Handle: Keith Hill MVP
                          Site Name: PowerShell
                          Feedback ID: 791819
                          ***************************************

                          Frequency: Always Happens
                          Regression: No, this is new to the most recent version

                          Problem Description:
                          Folks are so conditioned to using Get-Member to discover properties and methods on types that it is a bit unnerving to not find methods on CIM instances with Get-Member. It is also unintuitive IMO to have to use this:

                          Get-CimClass Win32_Process | % CimClassMethods

                          ... to find CIM methods when Get-Member will happily show CIM properties. It would be nice to…

                          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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                          • Enable-PSremoting fails when loopback address is missing

                            Votes from Connect: 13

                            Original Date Submitted: 1/10/2012 7:54:16 AM

                            Description:

                            ********Contact Information********
                            Handle: Doug Finke
                            Site Name: PowerShell
                            Feedback ID: 717747
                            ***************************************

                            Frequency: Always Happens
                            Regression: Yes, this happens in all previous versions

                            Problem Description:
                            Do a "netsh http sh iplisten" and machines are listed, but not the loopback address.

                            Tried Enable-PSRemoting and got the error below. Once the 127.0.0.1 is added to the IP listener list, this works.

                            It's something that "winrm quickconfig" should catch.

                            WinRM already is set up to receive requests on this machine.
                            Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot; Code="2150858770" M
                            achine="IIS.lab49.com"><f:Message>The client cannot connect…

                            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  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →
                            • Don't see your idea?

                            Feedback and Knowledge Base