Skip to content

VS Code and VS Code Insider with same issue "PowerShell Integrated" is getting hung #26899

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MaximoTrinidad opened this issue May 19, 2017 · 4 comments
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@MaximoTrinidad
Copy link

  • VSCode Version: Code 1.12.2 (19222cd, 2017-05-10T13:20:36.315Z)
  • VSCode Version: Code - Insiders 1.13.0-insider (2fbc979, 2017-05-17T08:16:42.720Z)
  • OS Version: Windows_NT ia32 10.0.16193
  • Extensions:
Extension Author Version
python donjayamanne 0.6.4
code-runner formulahendry 0.6.16
csharpextensions jchannon 1.3.0
mssql ms-mssql 1.0.0
csharp ms-vscode 1.9.0
PowerShell ms-vscode 1.1.0
vscode-icons robertohuertasm 7.7.0

Steps to Reproduce:

  1. Open either VS Code or VS Code Insider.
  2. Select PowerShell script folder.
  3. Open a PowerShell script file.
  4. In the Terminal panel, the "PowerShell Integrated" gets hung only showing "Starting PowerShell..."

There are no errors.

By the way! This was working before I installed ".NET Core 2.0 Preview 1".

I configure the following lines so I can use PowerShell 6.0.0-beta.1 instead of Windows PowerShell:
"terminal.integrated.shell.windows": "C:\Program Files\PowerShell\6.0.0-beta.1\powershell.exe",
"powershell.developer.powerShellExePath": "C:\Program Files\PowerShell\6.0.0-beta.1\powershell.exe"

vscodeposhissue_2017-05-18_21-17-01

@MaximoTrinidad
Copy link
Author

FYI

I did uninstalled .NET Core 2.0 Preview 1, rebooted the machine and I can't still no table to make "PowerShell Integrated" Terminal section to work. It still hung trying to "Starting PowerShell...".

:(

@daviwil
Copy link
Contributor

daviwil commented May 19, 2017

This is a bug created by the latest Windows Insider Fast Ring builds. Something changed in the Windows console host that has broken a lot of stuff. The workaround is here: PowerShell/vscode-powershell#742 (comment)

@Tyriar
Copy link
Member

Tyriar commented May 19, 2017

Closing in favor of PowerShell/vscode-powershell#742

@Tyriar Tyriar closed this as completed May 19, 2017
@Tyriar Tyriar added the *caused-by-extension Issue identified to be caused by an extension label May 19, 2017
@MaximoTrinidad
Copy link
Author

@daviwil,

Thanks for the update!

:)

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

3 participants