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, and would possibly have prevented me from publicly sharing my password with a group of people.

https://www.tecmint.com/show-asterisks-sudo-password-in-linux/

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 job will fail at the second command. The win2016 job will succeed with 3 lines of messages.
Here I use cmd to write stderr stream just for demo the bug. In my real case, I need this to work because git and yarn and other tools will write warning to stderr.

I also tried with my custom windows 2019 image. It is better. It will fail at the first command. At least it have a consistency behaviour. The different between custom 2019 and microsoft hosted 2019 is the .net framework 4.8.

There is an issue https://github.com/microsoft/azure-pipelines-image-generation/issues/1436 said that this is a powershell bug. I do think this is a powershell's bug.

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 even worse. Only ШЩХЪЫЯСТЬ can be entered in Russian keyboard layout and no capital letter at all can be entered in English layout.

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 when openssl is invoked directly from PowerShell on the hosted machine, which runs powershell 5.1.17763. I've been able to get it to succeed with other older versions of PowerShell (admittedly on different machines), so this seems like its probably a PowerShell issue to me

```
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 the "easy way" using return oder $MyObject does only return the members of the base object, not the additional custom one.

Using Get-Variable instead does work.

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 Runspace into PowerShell ISE to run script, but resources still didn't release.

During my research I found that this code still eat a bunch of memory. You can see it in "TestLeak" comment. But if we change this:
Get-Process *
to this:
$res = Get-Process *
then memory doesn't leak. Variable goes out of scope and then freed up by garbage collector. But in first case it looks like PowerShell stores results somewhere in inner structures. I have tried to add variable to my script to store cmdlet's results but nothing changed like my variable never goes out of scope!

I can't free memory no matter what I do! Do I do something wrong or it is some kind of problem?

P.S. Error appears when I try to attach the files so add code as comments!