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. Provide feedback during typing of password

    I just typed my password into a chatroom because although it looked like the PowerShell window had focus, I was entering a password where there is zero feedback. If I had seen a placeholder appear per character like text boxes on websites, I would have been able to tell that the text I was typing was not going to the right window.

    When typing into a password field, I would like to see feedback with something like ******, each * representing a character I typed.

    This is something you can enable with other shells like in this article about Linux,…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  2. Powershell command to show which versions of SSL/TLS enabled and disabled

    Since server 2016 has tls 1.0 -1.2 enabled by default but no corresponding registry keys, admins always feel a little in the dark about whether they are truyl enabled or not, and have to go look it up. It would be great to have a powershell command that showed which versions of TLS or SSL are enabled/disabled, instead of having to use sketchy 3rd party solutions.

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  3. Get-Content with cast to [xml] doesn't properly detect encoding of input file

    Get-Content with cast to [xml] doesn't properly detect encoding of input file

    [xml]$xml = Get-Content $sample

    where sample is an UTF-8 file and $xml is in CP-1251

    The expectation is to have encoding detected automatically like it happend in XmlDocument.Load method
    https://docs.microsoft.com/en-us/dotnet/api/system.xml.xmldocument.load?view=netframework-4.8

    Please check attached script with the example of the bug.

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  4. Get-Content with cast to [xml] doesn't properly detect encoding of input file

    Get-Content with cast to [xml] doesn't properly detect encoding of input file

    [xml]$xml = Get-Content $sample

    where sample is an UTF-8 file and $xml is in CP-1251

    The expectation is to have encoding detected automatically like it happend in XmlDocument.Load method
    https://docs.microsoft.com/en-us/dotnet/api/system.xml.xmldocument.load?view=netframework-4.8

    Please check attached script with the example of the bug.

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  5. Powershell 5.1.17763.1007 on Windows 2019 stops with NativeCommandError on Azure Pipelines

    How to reproduce:

    With this Azure pipelines yaml snippets:

    The special character are all encoded. And when I attach a file I get 500 error. Please see https://gist.github.com/chenbojian/6fcb3a8c3bbe42cc2851a1eefe9f4324

    - job: win2019
    
    pool:
    vmImage: windows-2019
    steps:
    - powershell: |
    $PSVersionTable
    cmd /c 'echo this will crash powershell 1>&2'
    cmd /c 'echo this will crash powershell 1>&2'
    cmd /c 'echo this will crash powershell 1>&2'
    - job: win2016
    pool:
    vmImage: vs2017-win2016
    steps:
    - powershell: |
    $PSVersionTable
    cmd /c 'echo this will crash powershell 1>&2'
    cmd /c 'echo this will crash powershell 1>&2'
    cmd /c 'echo this will crash powershell 1>&2'

    The win2019…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  6. Typing with Shift is not working in non-English keyboard layout

    In PowerShell console in Windows 10 there is a serious problem that prevents entering capitalized letters (i.e. pressing Shift+Letter does nothing). This happens with most but not all letters and depends on the keyboard layout that was active when PowerShell console was started. If PowerShell console is started with English (US) keyboard layout, than typing in English works without problems (only Shift+Space not work, but I see another issue about it). After switching to Russian keyboard layout, most letters with Shift not work. Only ЦУШЩХЪФЫСТ can be typed. But when PowerShell console is started with Russian keyboard layout, it is…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  7. OpenSsl fails on the second command in PowerShell

    When trying to execute two openssl commands one by one, the second one fails. I've created a repro on Azure Pipelines demonstrating 4 different cases, by name they are

    1) win2019 fails running:
    openssh help
    openssh help

    on Azure Pipelines hosted pool. This has the specs listed here - https://github.com/actions/virtual-environments/blob/7c96951971ca872b4f02469a3f945af20f517d2b/images/win/Windows2019-Readme.md

    2) default succeeded running:
    openssh help
    openssh help

    on my local box

    3) fromCmd fails running the following from the command prompt:
    powershell -command "openssl help | openssl help"

    4) fromPowerShellToCmd succeeds running the following from PowerShell:
    cmd /c "openssl help && openssl help"

    So basically the only failures happen…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  8. Powershell console regularly stucks when run from other console

    Issue:
    when I start new powershell process under different account from running powershell console (using start-process) consoles often freeze for several seconds/minutes. This doesn't happen if I start second console from START menu (using run as different user).

    I also noticed, that they somehow "synchronize" as can be seen on this video https://www.dropbox.com/s/9iq6bs9snxqlpba/PSstuckproblem.mp4?dl=0
    So when I start typing in first console, the second one (which is stucked at that moment) start typing chars, that are in queue or whatever...on its own

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  9. Write-Progress as Advanced Function

    Write-Progress has been discussed recently as adding overhead. What if we added capability to differentiate code:

    1) Not an advanced function: behaves like now
    2) Advanced function: adds a -Progress switch that will only do Write-Progress if it is passed.

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  10. Bug: Returning NoteProperty from Functions

    ```
    function TestObject(){
    $MyObject = (Get-Process | select Name) -as [pscustomobject]
    Add-Member -InputObject $MyObject -MemberType NoteProperty -Name "NP0" -Value "Ich bin ein NoteProperty"

    Add-Member -InputObject $MyObject -MemberType MemberSet -Name "SubSet"
    Add-Member -InputObject $MyObject.SubSet -MemberType NoteProperty -Name "NP1" -Value "Ich bin ein NoteProperty"
    Add-Member -InputObject $MyObject.SubSet -MemberType NoteProperty -Name "NP2" -Value "Ich bin ein NoteProperty"

    #This does not work
    #$MyObject

    #This does not work either
    #return $MyObject

    # This works
    Get-Variable -Name MyObject -ValueOnly
    }
    ```

    So basicly you create an object inside a function using a random cmdlet. After that you add NoteProperty members using Add-Member.
    Return that object…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  11. ValidateScript does not work for class properties

    ValidateScript does not work for class properties. All other validating seem to work.

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  12. "using module" does not provide a way to disable name checking

    The Import-Module cmdlet provides a way to silence the warning about unapproved verbs in function/cmdlet names (-DisableNameChecking). There does not seem to be a way to do this via the "using module" statement, which generates unwanted noise (we have our own internal naming conventions).

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  13. Disable or Restrict Powershell -EncodedCommand

    Powershell is targeted more often as a vector for breaching computer systems. Script signing prevents malicious use of scripted payloads, but an encoded command allows for complex command sequences to be executed in an obfuscated manner, outside of behavior based detection mechanism. Security Groups are calling for disabling of Powershell altogether because there are not security controls to lock down specific features. Disabling Encodedcommand for standard users would at least be a start to breaking the methodologies of those seeking to breach security by leveraging command and control utilities.

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  14. Get-ChildItem -Recurse -Attributes Directory lists $RECYCLE.BIN

    Hello!

    With Powershell 6, my target ist to list all folders.

    I find no way to exclude $RECYCLE.BIN
    :
    Get-ChildItem -LiteralPath 'D:' -Recurse -Attributes !Hidden+!System+!ReadOnly+!Encrypted+!IntegrityStream+Directory `

    -ErrorAction SilentlyContinue
    

    Thank You for advice me

    Erhie

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  15. Powershell much slower in export to excel

    I am using a script to export a configuration to excel
    running this scipt in powershell 7 (7.0.0) is much slower than in the native powershell for windows 10 (5.1.18362.628).
    This scipt can be found https://github.com/skippernl/Fortigate2Excel
    What could be the cause of 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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  16. Provide PublishedName in printmanagement cmdlet

    pnputil provides the PublishedName property. This can come in handy in rare cases where Windows does not properly register and unregister a driver.

    This is what I am looking for:

    Microsoft PnP Utility

    Adding driver package: cnp60ma64.inf
    Driver package added successfully.
    Published Name: oem20.inf <---- need this
    Driver package installed.

    Total driver packages: 1
    Added driver packages: 1

    Unfortunately, the printmanagement cmdlet does not provide this functionality when adding or enumerating driver objects. Add-WindowsDriver and Get-WindowsDriver do, but you can only use Add-WindowsDriver on offline images at the moment.

    Is there any plan to enhance or change this?

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  17. Start-Job on Windows Server 2016 hangs Powershell

    Start-Job seems to sometimes cause the calling thread to hang. If you create a loop in ISE and spin off a bunch of jobs, inevitably it will hang. This has only been tested using a ScriptBlock.

    As a workaround, you can use threads to do the heavy lifting and so if they fail to start the job, just recreate the thread.

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

    We’ll send you updates on this idea

    3 comments  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  18. Memory leaks while using powershell runspace in .NET

    I found a huge memory leak in project which appears after execution PS command. Here I create example that represent my problem in "TestCase" comment.

    After memory usage investigation I found that most of memory occupied by inner structures from System.Management.Automation. So I start to search the way to release resources and found that the same behavior can be reproduced in PS:
    Get-Module -ListAvailable | ForEach { Import-Module $_.Name }
    Get-Command -ListImported -CommandType Cmdlet,Alias

    I already have tried to initiated garbage collecting and to remove all new variables that appears after script execution. I even have tried to start new…

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  19. Chocolatey's refreshenv should be first-party

    Make the Chocolatey refreshenv part of Powershell. Manipulating environment variables is very difficult without 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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
  20. Remove-PrinterDriver with -Force option

    The Remove-PrinterDriver cmdlet currently does not offer a -Force option. This becomes a problem when there are network printers mapped via Group Policy that use the driver. When this is the case, PowerShell will return a "The specified driver is in use by one or more printers" error.

    PnPUtil offers the ability to force delete a driver even if it is in use. PowerShell's Remove-PrinterDriver cmdlet should offer the same behavior (clearly it is possible).

    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  ·  PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 23 24
  • Don't see your idea?

Feedback and Knowledge Base