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. ActiveDirectory PowerShell module isn't thread-safe

    Accessing Active Directory Web Services (ADWS) by launching and running a number of PowerShell Runspaces in parallel from within the same process makes ADWS fail with error message "invalid enumeration context".

    Apparently, the ActiveDirectory PowerShell module is not thread-safe.

    Please fix soon. There is no workaround for this issue.

    See this repository for steps to reproduce:

    https://github.com/SetTrend/powershell-test

    2 votes
    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. Fix powershell Get-SecureUEFI to support the variable dbt.

    Get-SecureBootUEFI used the wrong GUID (EFIGLOBALVARIABLE_GUID) so cause it can not get dbt.

    In UEFI spec 2.8, define the EFIIMAGESECURITYDATABASE2(dbt) should use the EFIIMAGESECURITYDATABASE_GUID, so this is the power shell command issue, you can refer to UEFI spec 2.8 - 32.6.1 UEFI Image Variable GUID & Variable Name for detail.

    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. UpdateServices Module - Request for UpdateReleaseDate

    UpdateServices Module, cmdlet Get-WsusUpdate. This cmdlet does not allow filtering by updates' "ReleaseDate". It also does not return value of updates' "ReleaseDate". GUI tool (WSUS mmc) does show "Release Date" column when showing updates, and allows updates sorting by "Release Date". I would ask that UpdateServices Module includes "UpdateReleaseDate" both as input (filtering) value and output value. Thanx.

    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. PowerShell Basic Statistics Module

    It will be fantastic if powershell have a simple or basic module for statistics and data analytics ..... calculating average and min , max is not enough .... please more data analytics functions would make powershell able to meet the new technology expectations

    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. Wrong path delimiters in archive (non-UNC)

    The "compress-archive" module stores path delimiters in non UNC format (backslashes instead of slashes) which differs from the builtin zipper in Win10 (Send to Zip-Archive).
    This leads to unrecognized files on decompression by i.e. Microsoft Dynamics NAV 2016 (decrompression of an imported zipfile "ControlAddIn.Zip")
    If you build the same archive with the Win10-Zipper, the files are recognized correctly.
    Used PS-Version : 5.1 build 18362 rev 145
    Win10-Pro 64bit version: 10.0.18362.267
    Command executed from Visual Studio:
    powershell Compress-Archive -Path ".\ControlAddIn\AddIn*" -CompressionLevel Fastest -DestinationPath "$(SolutionDir)ControlAddIn.zip"
    I cannot append the two Zip-Archives to let you compare these files by yourself therefore I post…

    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. Scheduledtask commands should support whatif

    The -ScheduledTask commands that modify state should support the WhatIf parameter. They don't appear to currently as of Server 2016.

    Specifying -WhatIf to Disable-ScheduledTask says the parameter is unknown.

    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 →
  7. Honour -Confirm and -WhatIf on Remove-PrintJob Cmdlet

    -Confirm & -WhatIf Optional Parameters not honoured on Remove-PrintJob even though they are included in documentation.

    2 votes
    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. Bug: Write-Output -InputObject (,'Test') -NoEnumerate

    The -NoEnumerate switch doesn't work when when the input is named using the -InputObject argument in PowerShell version 5.1.

    The following script returns False:

    Function Test {Write-Output -InputObject (,'Test') -NoEnumerate}
    
    (Test) -is [Array]

    While this script returns True:

    Function Test {Write-Output (,'Test') -NoEnumerate}
    
    (Test) -is [Array]

    $PSVersionTable

    Name Value


    PSVersion 5.1.17134.858
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.17134.858
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

    This issue doesn't appear with PowerShell Core 6.2

    2 votes
    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. Import-json

    json is becoming the new standard (if not already)
    It would be nice to have an import-json and a export-json as we have in xml/csv instead of the two steps process with get-content and convertfrom-json and convertto-json.

    15 votes
    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. ConvertFrom-String

    Make ConvertFrom-String available in PowerShell core as it's super useful when parsing txt files.

    2 votes
    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. Creating a symbolic link requires administrator privilege

    Since some version of Windows 10, creating a symbolic link should not require administrator privilege. In cmd, using mklink to create a symbolic link without administrator privilege works, but New-Item in PowerShell doesn't work.

    2 votes
    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 →
  12. BUG: Get-RDSessionCollection always generates exception on Windows Server 2019

    Get-RDSessionCollection of the RemoteDesktop module always throws an exception:

    PS C:\windows\system32> Get-RDSessionCollection
    New-Object : Exception calling ".ctor" with "1" argument(s): "Invalid parameter "
    At C:\windows\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\SessionDesktopCollection.psm1:520 char:14
    + ... $scope = New-Object System.Management.ManagementScope("\" + $Conn ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException 
    
    + FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

    CollectionName Size ResourceType CollectionType CollectionDescription


    mycollection 0 RemoteApp programs PooledUnmanaged My first collection

    PS C:\windows\system32>

    --

    Changing C:\Windows\System32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\SessionDesktopCollection.psm1 line 520

    $scope = New-Object System.Management.ManagementScope("\" + $ConnectionBroker + "" + $wmiNamespace, $connectionOptions)

    into

    $msuri = "\" + $ConnectionBroker + "" + $wmiNamespace
    $scope = New-Object System.Management.ManagementScope($msuri, $connectionOptions)

    fixes the problem.

    This issue breaks…

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

    We’ll send you updates on this idea

    2 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  13. Get-ChildItem -LiteralPath doesn't support long path

    Get-ChildItem -LiteralPath doesn't support long path, for example:

    Get-ChildItem -LiteralPath 'D:\aaaaaaaaaabbbbbbbbbbccccccccccddddddddddeeeeeeeeeeffffffffffgggggggggghhhhhhhhhhiiiiiiiiiijjjjjjjjjjkkkkkkkkkkllllllllllmmmmmmmmmmnnnnnnnnnnooooooooooppppppppppqqqqqqqqqqrrrrrrrrrrssssssssssttttttttttuuuuuuuuuuvvvvvvvvvvwwwwwwwwwwxxxxxxxxxxyyyyyyyyyyzzzzzzzzzz.txt'

    Which path is longer than 260 bytes, even if the file DO exists in that path.

    But Get-ChildItem WITHOUT -LiteralPath works well with that long-path file.

    $PSVersionTable

    Name Value


    PSVersion 5.1.17763.134
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.17763.134
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

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

    We’ll send you updates on this idea

    2 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  14. Set-DfsrConnectionSchedule doesn't change a replication partner of a group to use custom settings

    Set-DfsrConnectionSchedule doesn't change a replication partner of a group to use custom settings. I've even waited a day and it didn't change it.

    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. Cmdlet "New-Mailbox" cannot use -encoding UTF-8

    While the UI for ExchangeOnline and Office365 can use UTF-8 when creating new resources, the Powershell cmdlet cannot.

    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 →
  16. Extraneous results returned with Resolve-DnsName (dnsclient)

    Quoted feedback from documentation feedback provided by MSFT team below. (via @jordanmills)

    > When resolving SRV records (example: Resolve-DnsName -Name "kerberos.tcp.dc._msdcs.$env:userdnsdomain" -Type SRV), the cmdlets also attempts to resolve any returned A or AAAA records and sends them to the pipeline as a separate object collection. This breaks pretty much any attempt to sort, group, filter, or otherwise process the data. How can we make it not return A and AAAA records for SRV queries?

    https://github.com/MicrosoftDocs/windows-powershell-docs/issues/302

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

    We’ll send you updates on this idea

    2 comments  ·  Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
  17. Make NetAdaper group accept -InterfaceIndex as well as -name

    With the "NetAdapter" group why do most of them not accept InterfaceIndex Number for selection? I would like to select my card by its Index so that even if its off / not active I can rename it, change its IP, powersettings etc. Lastly why can we not disable Netbios for the same cards this way?

    2 votes
    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. new-azvm BUG

    Hey every body,

    "New-AzVM" has a strange behaviour (maybe a bug), if you pass vn and subnet as parameters and
    the vn exists but the subnet doesn't, it will try try to delete the vn (cascading) and recreate it. This
    will fail if you have other VMs in the vnet but will succeed if you have empty subnets deleting all of them (OUCH!).

    Steps to reproduce:


    1. login to portal and create 1 vnet (say vnProd2 ) and 2 subnets (say snProd, snDev)

    2. login to Azure from powershell (module AZ)

    3. run the following command:
      New-Azvm -Location "northeurope" -ResourceGroupName "rgTest" -virtualnetworkname vnProd2…
    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. "Test-NetConnection" add timeout

    please add timeout to "Test-NetConnection" see https://superuser.com/q/805621/216033

    8 votes
    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. Get-AuthenticodeSignature does not return TimeStamperCertificate

    Hello, we've been using command Get-AuthenticodeSignature to validate a signed/time stamped file, and this works as expected in Server 2008 R2 and Server 2016 machines. But targeting the same file from Server 2012 R2 Powershell ISE, returns empty TimeStamperCertificate property. I've confirmed PS1, .NET framework and Authenticode module versions to be latest, and server patches are up to date. It seems that the root issue is within Microsoft.Powershell.Security library.

    Thanks

    Vlad

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

Feedback and Knowledge Base