Command 'PowerShell: Show Extension Terminal' resulted in an error (command 'PowerShell.ShowSessionConsole' not found)

[bender-the-greatest]

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

The current version of the PowerShell plugin does not load when I open .ps1 files any longer. When I try to launch the integrated terminal with PowerShell: Show Extension Terminal from the command pallete, I get the following error (re-stated from title):

Command 'PowerShell: Show Extension Terminal' resulted in an error (command 'PowerShell.ShowSessionConsole' not found)

Rolling back to the prior version fixes this (albeit with the old PowerShell Integrated Console name for the terminal). I've found at least one other person today experiencing the same issue. I've also tried the related PowerShell: Restart Current Session command which results in a similar "command not found" error.

Recently-created issue #4135 seems like it could be related although it's for a specific plugin feature. My issue here is that the terminal not launching causes the plugin to entirely not function.

PowerShell Version

> $psversiontable

Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.19042
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

> code --version
1.70.1
6d9b74a70ca9c7733b29f0456fd8195364076dda
x64

Extension Version

> code --list-extensions --show-versions | Select-String powershell

ms-vscode.powershell@2022.7.2

Steps to Reproduce

1. Open .ps1 file for editing.

2. No plugin features are available. Quick evidence of this is no syntax checking is performed against the opened file.

3. Try to open the plugin terminal with the PowerShell: Show Extension Terminal pallete command. Modal dialog with the following error is displayed:

   Command 'PowerShell: Show Extension Terminal' resulted in an error (command 'PowerShell.ShowSessionConsole' not found)

Visuals

No response

Logs

No logs are generated when running PowerShell: Show Extension Terminal from the command pallete. I set logging to Diagnostic before attempting this.

[andyleejordan]

Hello! The latest code is available in the PowerShell Preview for VS Code, and includes a myriad of fixes. Could you verify if this issue still reproduces using the preview extension? Please note that this preview is likely to include other bugs, and you should feel free to file new issues for those so we can work through them. Thanks again!

[andyleejordan]

Could you also check your workspace file and ensure it's valid JSON?

[dbaileyut]

I'm reproducing on v2022.7.2 when I have a workspace with no folders. If I add a folder, the extension behaves as expected.

I'm not seeing it on the preview v2022.8.2.

Test workspace is just:

{
	"folders": []
}

In the VSCode developer tools console, I see:

mainThreadExtensionService.ts:111 Activating extension 'ms-vscode.powershell' failed: Cannot read properties of undefined (reading 'uri').

TypeError: Cannot read properties of undefined (reading 'uri')
	at Object.<anonymous> (c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:57:23283)
	at Generator.next (<anonymous>)
	at c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:1:945
	at new Promise (<anonymous>)
	at vt (c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:1:765)
	at Object.tD (c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:57:22820)
	at c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:116:12087
	at Generator.next (<anonymous>)
	at c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:1:945
	at new Promise (<anonymous>)
	at vt (c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:1:765)
	at TN (c:\Users\myuser\.vscode\extensions\ms-vscode.powershell-2022.7.2\out\main.js:116:11768)
	at Function._callActivateOptional (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:97:17473)
	at Function._callActivate (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:97:17131)
	at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:97:14942
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async v._activate (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:85:8180)
	at async v._waitForDepsThenActivate (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:85:8122)
	at async v._initialize (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:85:7486)

[bender-the-greatest]

I will try the preview tomorrow, I am off for the rest of today. I saw that other issue mentioning the invalid JSON in the workspace file but my workspace is valid JSON. I checked that earlier. My workspace is also not completely empty as the other person mentioned in their reproduction of the issue.

[dbaileyut]

My workspace is also not completely empty as the other person mentioned in their reproduction of the issue.

Sorry, saw this on Reddit and it looked like what I experienced. My issue is actually a dupe of #4102

[andyleejordan]

If it's not reproducing with v2022.8.2 then it's fixed 😆

[andyleejordan]

Oh, you're not the OP.