PowerShell Integrated Console prompt does not appear

[Liturgist]

PowerShell Integrated Console

After installing the Microsoft PowerShell Extension, it appears that I can choose a TERMINAL of "powershell" or "PowerShell Integrated Console."

The "powershell" TERMINAL appears to work as expected, but no debugging can be done.

"""Cannot debug or run a PowerShell script until the PowerShell session has started. Wait for the PowerShell session to finish starting and try again. """

The "PowerShell Integrated Console" TERMINAL does not. It appears hung. It accepts no keyboard entry.

This is based on a fresh install of VS Code from VSCodeUserSetup-x64-1.45.1.exe.

Version: 1.45.1 (user setup)
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:35.169Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

PowerShell extension 2020.4.0
%USERPROFILE%\.vscode\extensions\ms-vscode.powershell-1.8.2\ms-vscode.powershell-1.8.2
    (PS: There is no "examples" subdirectory)

[PetrMa]

I have the same issue with 2020.6.0. Downgrade to 2020.4.0 and disable auto update solved the issue for now.

Version: 1.45.1 (system setup) Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a Date: 2020-05-14T08:27:35.169Z Electron: 7.2.4 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18363

[s12481632]

Thanks to everyone who commented! I have the same issue with 2020.6.0. Downgrade to 2020.4.0 and disable auto update solved the issue for now as well. Ran into the issue on a fresh vscode install with no other extensions.

[Benny1007]

I have this same issue. Where do you get the older version to rollback to?

[MoonRaker58]

I have this same issue. Where do you get the older version to rollback to?

See my comments from 15 days ago for a partial set of instructions on how to roll back to older versions. The older versions are on the release page. https://github.com/PowerShell/vscode-powershell/releases

[PetrMa]

I have this same issue. Where do you get the older version to rollback to?

You can click directly in VS Core the Manage image on PowerShell in Extensions and select "Install another version ...." from the menu. Remember that you must also disable Extensions auto update in global settings of VS Code.

[Liturgist]

@SydneyhSmith, does the Needs-Repro-Info label still apply?

[jdsanford]

I am on a corporate systems with many GPOs and McAfee. I have local administrator access. When running the current version of the extension the integrated session never finishes starting. This is the case when running as a user or as an administrator. Downgrading to 2020.4 resolves the issue.

Version: 1.47.2 (user setup) Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf Date: 2020-07-15T18:22:06.216Z Electron: 7.3.2 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.17763

PSVersion 6.2.4

[eoq]

Same issue with 2020.6.0 and 2020.4.0 works for me as well. I hope this issue is being worked on... Thanks Ed

[rjmholt]

Please try out this build of the extension and let us know how it goes.

That build is based on the changes on the linked PR.

[MoonRaker58]

@rjmholt I get a not authorized error with that build. I did try preview v2020.7.0 and it works so I'm going to use that one for a while. Thanks for the work.

[s12481632]

@rjmholt I get a not authorized error with that build. I did try preview v2020.7.0 and it works so I'm going to use that one for a while. Thanks for the work.

Same on both counts. Couldn't access the linked build, but the preview v2020.7.0 build of the extension worked.

[devedse]

@rjmholt it seems normal people 😄 don't have access the link you posted:

{"$id":"1","innerException":null,"message":"TF400813: The user 'Windows Live ID\..........@........' is not authorized to access this resource.","typeName":"Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server","typeKey":"UnauthorizedRequestException","errorCode":0,"eventId":3000}

[TylerLeonhardt]

Here's the file:

PowerShell-insiders.vsix.zip

Sorry about that...

code --install-extension /full/path/to/PowerShell-insiders.vsix

make sure you have the normal PowerShell extension disabled.

[devedse]

@TylerLeonhardt , I verified that this fixes the issue, thanks :)

[DeanGross]

2020.6.0 gave me this problem, i unistalled that and then installed 2020.7.0 and the problem still exists.

[corbob]

Here's the file:

PowerShell-insiders.vsix.zip

Sorry about that...

code --install-extension /full/path/to/PowerShell-insiders.vsix

make sure you have the normal PowerShell extension disabled.

@DeanGross you'll want to use the file Tyler mentioned here. This issue will be resolved in the published release once a new release is pushed.

[DeanGross]

@corbob thanks, I have installed v2020.8.0-CI.60063 and still have the problem. I have Windows 10, 1809 OS 17763.1339 if that matters

[corbob]

@DeanGross If you're still having the issue, and the CI build didn't solve it, I'd suggest opening a new issue and if possible attach the logs. It sounds like you might be seeing a different issue than originally reported in this issue.

[DeanGross]

@corbob i updated VSC to 1.49 and 2020.8.0-CI.60063 seems to be working properly now

[AyJizzy]

For windows users, when reinstalling vscode I noticed inside properties of the application that 'compatibility mode' was turned on to be be ran with settings for windows 8. Once I removed that it fixed my issue with a restart of the application.

[kaovilai]

I had problems after restarting VSCode many times with PowerShell extension v2021.2.2 installed. The problem went away as of now by restarting Powershell session without restarting VSCode