-
Notifications
You must be signed in to change notification settings - Fork 511
PowerShell Integrated Console prompt does not appear #2719
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
PowerShell Integrated Console prompt does not appear #2719
Comments
The debugger and extension are the 'integrated terminal' The other one is a regular shell. |
When VS Code is first started, I get the Welcome doc and a regular shell PowerShell. Pressing F5:
The PowerShell Integrated Console terminal displays "=====> PowerShell Integrated Console <=====" and nothing else. Clicking on "Starting PowerShell..." brings up a notification:
How can I tell which PowerShell executable is being used? I have two (2) in the PATH on my system.
|
It has been "Starting PowerShell..." for over thirty (30) minutes. What should I expect? |
Thanks for the info! Can you also attach the logs here so we can get a better idea of what's going on? |
Also is this machine locked down in any way? |
Logs are attached from a recent run. I did not find any text about "error" or "fail" in them. The machine is not locked down in any way. vscode-powershell.log |
I have the same issue with the same vesion of VS Code that I installed 3 days ago. Version: 1.45.1 (user setup) vscode-powershell.log |
Does this machine use Avecto or BeyondSoft at all? Is there any enforcement via Group Policy on this machine? Is there any anti-virus on the machine? Have you configured the machine in any bizarre ways... That might be non-traditional? |
Does this machine use Avecto or BeyondSoft at all? No |
Requested Repro-Info provided. |
Thanks so much for all the information, we are still having some trouble diagnosing the crash...it would be really helpful if you could also attach the payloadlogs--instructions for how to do that are here |
@SydneyhSmith - Please let me know if I can provide anything else. Thanks. I would note that there is only "PowerShell Integrated Console" and no plain "powershell" terminal. There is no "PowerShell Editor Services" item in the drop-down listbox. I chose "PowerShell Extension Logs."
Output from PowerShell Integrated Console
|
The problem disappeared after I restarted my computer. |
I am glad it is working for you, @y-halin. I have restarted my computer many times and it continues to fail in the same way. |
Thanks @Liturgist for the additional information, unfortunately your logs do not look quite as expected, would you mind sharing what settings you have enabled? Thanks again! |
@SydneyhSmith - I would be happy to share the settings. How do I generate a list of the settings? Is it a .json file? If so, where? |
@Liturgist you'll wanna grab the file from here: https://code.visualstudio.com/docs/getstarted/settings#_settings-file-locations |
Here is the content of "%APPDATA%\Code\User\settings.json". There are a few .json files under "%USERPROFILE%.vscode", but the all appear to be related to azure or Plaster.
|
@Liturgist if you remove these settings:
does that help at all? |
If not, can you add:
and give us the logs? |
@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. |
@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} |
Here's the file: Sorry about that...
make sure you have the normal PowerShell extension disabled. |
@TylerLeonhardt , I verified that this fixes the issue, thanks :) |
2020.6.0 gave me this problem, i unistalled that and then installed 2020.7.0 and the problem still exists. |
@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. |
@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 |
@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. |
@corbob i updated VSC to 1.49 and 2020.8.0-CI.60063 seems to be working properly now |
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. |
I had problems after restarting VSCode many times with PowerShell extension v2021.2.2 installed. |
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.
The text was updated successfully, but these errors were encountered: