Skip to content

Integrated Powershell terminating upon starting #1855

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
rayholtz opened this issue Apr 8, 2019 · 4 comments
Closed

Integrated Powershell terminating upon starting #1855

rayholtz opened this issue Apr 8, 2019 · 4 comments

Comments

@rayholtz
Copy link

rayholtz commented Apr 8, 2019

Issue Type: Bug

All I have to do is start VSCode and I get a popup message at the bottom right corner of the application:

"The PowerShell session has terminated due to an error, would you like to restart it?
Source: Powershell (Extension)"

Clicking Yes tries to restart the Powershell Integrated Console, but then it terminates again.

I enabled Verbose logging in the Powershell Extension. Here are the logs. There is an error near the bottom of the 'EditorServcies.log' file.

vscode-powershell.log
EditorServices.log

Here are the versions of code, extensions, and powershell:
Versions.txt

Extension version: 1.12.0
VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:14:28.026Z)
OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 15.88GB (8.84GB free)
Process Argv
Screen Reader no
VM 0%
@SydneyhSmith
Copy link
Collaborator

SydneyhSmith commented Apr 8, 2019

Your error looks similar to this one are you on a network share or is your environment restricted in any way (group policy etc.)?

@rayholtz
Copy link
Author

rayholtz commented Apr 8, 2019

Thank you @SydneyhSmith
I do save all my powershell scripts from my user directory on a network share. I copied a script to my C: Drive to open it, and Powershell did not crash within VSCode. It does seem like its the same issue as you linked #1830.
I will close this issue, and comment on that one. Thank you for your help!

@rayholtz rayholtz closed this as completed Apr 8, 2019
@TylerLeonhardt
Copy link
Member

Hi all, can you try one of these builds:

PowerShell and PowerShell Preview release candidates.zip

This should have the UNC path fix. Note, if you've never used the Preview extension, look at these steps.

If you've never installed a VSIX before, here are the steps.

@rayholtz
Copy link
Author

@TylerLeonhardt The Powershell Extension v1.12.1 .vsix file installed correctly, and upon initial use seems to be working correctly, a file opened from a UNC path does not crash the Powershell extension.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants