Get-Credential "eats" first character typed and will put it to console output later in debug

[MrFly72]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

When Using get-Credential in PS7.x and VSCode with Preview release of the PS-Extension, it eats the first character, a little bit to compare with this issue: #3881
This leads in copy pasting of the username in cropping the first letter of the login off the value.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.2.2
PSEdition                      Core
GitCommitId                    7.2.2
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.66.1
8dfae7a5cd50421d10cd99cb873990460525a898
x64

Extension Version

ms-vscode.powershell@2021.12.0
ms-vscode.powershell-preview@2022.3.1

Steps to Reproduce

Put
$test=Get-Credentials
into a editor window and start with F8 (debug)
First character will not be taken, it will be later on in the console
copy paste even does not show anything until you press another key on the keyboard

Visuals

No response

Logs

No response

[andyleejordan]

Hi there, we just released v2022.4.0-preview! Could you please try PowerShell Preview for VS Code and verify this is fixed? It seemed to be in my testing, so marking as resolved, but please let me know if it's still occurs (or if new bugs show up)!

[ghost]

This issue has been marked as fixed. It has been automatically closed for housekeeping purposes.

[MrFly72]

See #3881 for a video of the ongoing problem with this.
So it is not yet fixed completely, but better then before.