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

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    "col1tcol2" | 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  13. Better Write-Progress bar, like in yarn.

    The current Write-Progress bar is ugly, and shows at the top of the sreen. Showing yello text over dark cyan, representing progress with some weird circles...

    It should be more like the yarn progress bar, that shows immediately after the command.

    https://imgur.com/GfJRHfp

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  14. Bug: The Get-ADGroupMember -Recursive option doesn't work correctly

    Get-ADGroupMember -Recursive only reads the Group Members property. It does not also add users to the list who have a group as their primary group. Here is what it should be doing...

    (Get-ADGroupMember -Identity "Domain Admins" | select distinguishedName).distinguishedName

    Here is what it is actually doing...

    Get-ADGroup -Identity "Domain Admins" -Properties Member | select -ExpandProperty member

    Which is a different answer!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  15. TrimStart() method trimming more than specified

    Attempting to compare two strings. When constructing one of the strings, the TrimStart method is trimming more of the string than it should. Example:

    (Get-Content -Path 'C:\Program Files\SplunkUniversalForwarder\etc\system\local\server.conf' | Select-String -Pattern 'serverName').ToString().TrimStart('serverName = ')

    returns

    rver1.domain.company.com

    expected output is

    server1.domain.company.com

    I expanded the TrimStart method like so:

    (Get-Content -Path 'C:\Program Files\SplunkUniversalForwarder\etc\system\local\server.conf' | Select-String -Pattern 'serverName').ToString().TrimStart('serverName').TrimStart(' ').TrimStart('=').TrimStart(' ')

    and get the same erroneous output. The problem appears to be with trimming the last space character.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  16. Set-Location/Push-Location should update process' current directory

    The Set-Location/Push-Location cmdlets do not update the calling process' current directory. This leads to surprising behavior when working with non-PowerShell APIs. Simple example below.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  17. Powershell 5.1 returns error on special characters when passing in an array of arguments

    Hello,

    I have Set the arguments in the code:

    $installArguments = ""-p" "$ISMFileFolder" -o "$MergeModuleFolder" -y "$VersionNumber" $PathVariableArguments -b "$MediaOutputFolder""

    and run the exe with arguments:
    & $IScmdBldRootDir $installArguments
    The same scripts is running fine on Windows server 2008 R2 that has the Powershell 4.0 and it fails and return error on Windows server 2016 that has the Powershell 5.1.
    The error is:
    -1113: The 'p E:\Builds\Installer' switch is not recognized.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add commandlets to configure NAT in the RemoteAccess module

    Please, expand the RemoteAccess module with commandlets that allow you to configure simple NAT like you would do with the RRAS GUI.
    So far, the module allow you to configure Direct Access and VPN but not NAT and it feels like it's missing.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add SNMP Cmdlets (Get, Walk, Table, etc.)

    Hi,

    it would be very useful to have SNMP cmdlets available. SNMP is still defacto standard for managing many kinds of 'network-devices'.

    It could help also considering IOT devices.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  20. Write-Verbose should be controllable

    Hello

    Although "UserVoice" is misused by M$$ to silence customers(!) (e.g. errors(!), which are easy to correct, are ignored for years)
    I still write a suggestion for improvement.

    Usually, the -verbose switch is used if one would like to get more information about one module or script.
    The reality is, however, that we're flooded with verbose messages.

    Therefore it would be great if -verbose could be controlled. Just two ideas:
    - By specifying a nesting level, e.g. -Verbose <NestingLevel>
    -Verbose 2 would activate verbose messages in the directly called script and in all commands which are called by the script…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
1 2 5 7 9 12 13
  • Don't see your idea?

Feedback and Knowledge Base