Unable to run scripts with integrated PowerShell Console in VSCode 1.47.1

[jlapchuk]

Since upgrading to v1.47.1 of VSCode, I can't run PS scripts using the built in console. Hitting F5 does nothing, and attempting to run a line of code using F8 gives an error: "command 'PowerShell.RunSelection' not found"

I also notice that the version of PS is not displayed in the bottom-right.

I suspect this has to do with the latest CVE patch.
https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2020-1416

My question is, am I doing it wrong? Or is this a bug that needs to be corrected? In my scenario, I have a regular (non-admin) account I use to login to my workstation. Depending on the PowerShell task/script, I may need to run VSCode as my secondary (admin) account (with elevated rights). To do that, I'll first run powershell.exe 'As Different User', authenticate with my secondary admin account, then run VSCode as admin (Start-Process code.exe -Verb RunAs) to get into an elevated session.

[soerenlambaek]

I have this problem too when i am running vscode as admin. I works when running as my normal loggedon non admin user

[beowulf005]

Might be the CVE, But running on a system that does not have the CVE installed yet and have a very similar error. PS was working fine before installing but after installing getting.

Have some personal computers that I tested and with fully patched they are working fine with the latest release. Just my company assigned assets have the issue.
Tested on my company desktop and has the same issue.
On my company laptop rolled VS Code back to V 1.46 PowerShell started working again as expected.

Does the CVE need to be installed with 1.47?
Is the PowerShell version a requirement?
My personal machines are running v7 but my company are on 5.1

[corbob]

I am able to reproduce this issue in 1.47 with both stable and preview extensions, but insiders (1.48) does not appear to have the issue with preview extension.

To be clear: I am only able to reproduce by creating a secondary account on my computer, and running elevated in that account as opposed to merely running elevated. I'd wager a guess that the issue would occur when just running as the different user, but since I have a user based install, I have to elevate it in order to access the files to run.

[jlapchuk]

Yeah, to clarify, I'm running a per-system install of VSCode. I can confirm, installing the Insiders version of VSCode (1.48.0-insider), also does not exhibit the problem, not sure if this version already contains the CVE patch.

[beowulf005]

Also to clarify. Per-system install and company requires separate accounts for user and admin. So launching VS Code as administrator.

[vall3yv]

+1Per-system install and company requires separate accounts for user and admin. So launching VS Code as administrator.

[SydneyhSmith]

Thanks everyone, sorry to hear that you are hitting this it would be really helpful if you could also attach the logs--instructions for how to do that are here , it would also be great if you could see if you are able to open a terminal in VSCode

[vall3yv]

Hey @SydneyhSmith it appears when enabling the Diagnostic logging no log files are being produced within the folder you mentioned? I see logs from this AM but nothing from when i opened and closed several times just now. When using the keyboard shortcut to open the folder (mentioned in the link you sent) i get the following error, any ideas? Just to note i am launching as a local admin account from a standard user account as mentioned above.

C:\Users\ADMINUSER\.vscode\extensions\ms-vscode.powershell-2020.6.0\logs\1594739523-e1096e54-2415-4ade-be03-f243d8f4b2521594739520990

[jlapchuk]

I'm seeing the same on my end as well. I can hit the + icon to start a new PowerShell terminal, and I can run commands. I enabled diagnostic logging, but when i try to open the logs folder from within vscode, I get the same error as above. Manually browsing to the logs directory shows no new logs generated since upgrading to v1.47.1

[TylerLeonhardt]

So odd... it doesn't seem like the PowerShell extension is being loaded... If you open the command pallet, can you run "Toggle Developer Tools" and give us the output?

[jlapchuk]

Seeing this in the console of the developer tools

abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.debug.start` appears multiple times in the `commands` section.
abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.closePanel` appears multiple times in the `commands` section.
abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.positionPanelLeft` appears multiple times in the `commands` section.
abstractExtensionService.ts:415 [ms-vscode.powershell]: Command `workbench.action.positionPanelBottom` appears multiple times in the `commands` section.
abstractExtensionService.ts:411 Activating extension 'ms-vscode.powershell' failed: The "path" argument must be of type string. Received type undefined.
_logMessageInConsole @ abstractExtensionService.ts:411