Terminal does not display Variable output

[lotek4u]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed 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 the "PowerShell Extension" terminal, none of the values are ever echoed back to the terminal. When typing a bad command, i receive feedback, but not when attempting to display output.

I think this is the same issue as #4114 which was closed unresolved.

This is what I expect (regular psh window):

This is how the terminal responds:

As you can see, the variable contains data but the terminal will not show it.

Here the terminal is not reacting to any output from commands unless there is an actual error:
the "code" command returns no output
the $psversintable returns no output
get-aduser followed by real user alias (a valid command) returns nothing
get-aduser FAKEUSER is expected to produce an error, and it does.

Note that if I open a new terminal using a newer version of powershell, the output works as expected, but I must keep 5.1 for legacy scripts.

PowerShell Version

PS C:\WINDOWS\system32> $psversiontable

Name                           Value
----                           -----
PSVersion                      5.1.22621.963
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.22621.963}
BuildVersion                   10.0.22621.963
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

PS C:\> code --version
1.74.3
97dec172d3256f8ca4bfb2143f3f76b503ca0534
x64

Extension Version

[email protected]

Steps to Reproduce

Have script open, get input stored into variable (I think, save the script) - variables no longer output.

Visuals

No response

Logs

No response

[SydneyhSmith]

Thanks @lotekjunky looks related to #3991

[ghost]

This issue has been marked as duplicate and has not had any activity in a day. It has been closed for housekeeping purposes.

[lotek4u]

Why was this closed without fixing? #4114 was closed due to inactivity and it was stated to reopen the ticket in the future. Well, I recreated the ticket with sufficient data, it took a good hour to collect all that info... and it still doesn't work. Now this issue is closed too.

[lotek4u]

Thanks @lotekjunky looks related to #3991

Does that mean to close the issue, or to fix it?

[andyleejordan]

This is a duplicate of #3991, as was #4114, so we're already tracking it in the former and so closed the latter and this one as duplicates.

[lotek4u]

Oh, so why did #4114 say to reopen because there had not been any updates in a week. Whatever.

[andyleejordan]

Because we're not perfect and it got mislabeled.

[andyleejordan]

@lotekjunky do you know if you have Start-Transcript somewhere before all this happens?

[ghost]

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.

[lotek4u]

I wasn't using a start-trsnscript at all.