`Write-Output` broken

[KevinWGagel]

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

Edit: Changed title to remove "for elevated accounts" as it is now not working at all regardless of account used.

The PowerShell Extension is not starting correctly. I worked with folks over at discord who guided me through finding the issue.
Attaching diagnostic log files for review as well as screen shots of the symptoms.
Essentially I cannot get output from scripts I'm writing in VSCode in the PowerShell Extension terminal window

WARNING: In development mode but PowerShellEditorServices dev module path cannot be found (or has not been built yet): c:\Users\u598743a.vscode\extensions\PowerShellEditorServices\module

PowerShell Version

PS C:\Users\u598743a\.vscode> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.19041.1682
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1682
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Visual Studio Code Version

PS C:\Users\u598743a\.vscode> code --version
1.67.2
c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
x64

Extension Version

PS C:\Users\u598743a\.vscode> code --list-extensions --show-versions | select-string powershell

ms-vscode.powershell@2022.5.1

Steps to Reproduce

Just run a script, run a code snippet and nothing gets returned.
Interestingly though if I change my code to write-host instead of write-output then I get results to the Extension's terminal.

Visuals

Logs

vscode-powershell.log
EditorServices.log
StartEditorServices.log

[KevinWGagel]

I have two domain accounts I can login with. This problem is affecting the elevated level account, not the regular account.

[andyleejordan]

Ah! That's super helpful @KevinWGagel. Also, thanks for pushing us onto further investigation, we figured out that the "development mode" problem was a red herring caused by really dumb code I wrote a few months back, but is now fixed via #3992

[KevinWGagel]

I didn't bring it up sooner because I have the executable set to launch as administrator. I do a lot of remote ps. I wanted to keep going with a script that didn't do remote ps so I switched over to regular launching and found it working. So, sorry for the extra work in the wrong direction. Glad you're getting to the bottom of it. Any idea on a timeline for a fix?

[SydneyhSmith]

@KevinWGagel thanks for the report-- we are finding time to investigate this issue...once we do that we will have a better sense of if this is fixable or not. Thanks!

[KevinWGagel]

Just wanted give an update. I've been using VS Code in my non-elevated account. Today after a bunch of debugging I had the same problem. No more output from write-output. This time it was right after I added a bunch of write-verbose statements, saved the file, then ran it in the VS Code terminal using -verbose. After all the verbose messages came through the final output which was to show the end results didn't appear. Just like what I get when I'm using an elevated VS Code session. I tried remarking the write-verbose lines to see if it would change anything. It didn't. I ran the script from an elevated PS shell with -verbose and it displayed all the verbose and the final output.

I then exited VS Code and restarted it in a non-elevated session and tried the script again - then the final output displayed as it should. I unremarked the write-verbose statements and ran it from the VS Code terminal and it continued to work as expected.

I'm wondering if there is a memory corruption of some kind that happens after a lot of runs with break points set. I often run to a break point, check some things in the terminal and then stop the script. Make whatever changes I must then try again.

[SeeminglyScience]

Thanks for the update! If that happens again in a non-elevated session can you grab the logs? Might be helpful to see a before and after

[KevinWGagel]

I will.