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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  WMI  ·  Flag idea as inappropriate…  ·  Admin →

    This issue was recently reported via another channel, and is being actively investigated.
    Don’t have an ETA at this time, but will update this thread as we learn more.

  2. 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$ * BUILTIN\Backup Operators Allow Full …

    6 votes
    Sign in
    Sign in with: Facebook Google
    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