-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Can’t launch VScode - hangs in citrix environment #146923
Comments
Similar problem with failing to launch directly from elevated command prompt. Normal command prompt works fine. I have Citrix installed, but I'm not using it. C:\Users\XXXXX\AppData\Local\Programs\Microsoft VS Code>code C:\Users\XXXXX\AppData\Local\Programs\Microsoft VS Code> |
VSCode About: Version: 1.66.2 (user setup) |
Also maybe worth mentioning that I tried launching VSCode elevated from a shortcut, powershell 5 & 7 sessions...none of them worked and all did basically the same thing with the outline for the VSCode app window briefly flashing on screen before it dies. Rerunning with --verbose --disable-extensions produced the following: Also maybe worth mentioning that I tried launching VSCode elevated from a shortcut, powershell 5 & 7 sessions...none of them worked and all did basically the same thing with the outline for the VSCode app window briefly flashing on screen before it dies. Rerunning with --verbose --disable-extensions produced the following: PS C:\Users\XXXXXX\AppData\Local\Programs\Microsoft VS Code> .\Code.exe --verbose --disable-extensions |
VSCode does not support launching as elevated due to the application sandbox from the runtime. @brocawernicke are you also running the application as elevated ? |
Ok, thanks deepak for that. If I can't launch VSCode with admin privileges how do I debug Powershell scripts or anything for that matter that has OS APIs that demand elevated privileges to run? I've gone looking and I've search VSCode settings to see if maybe the debugging session can simply be elevated and I can't find any "admin" or "elevated" related settings. Searching online points to a bunch of dated articles with little value. "Run as admin" is a really basic and common Windows OS level feature and whether it supported or not, VSCode should simply not be dying on it. Not ever. Not really sure what level of information is being logged to the console but it sure doesn't appear like a proper exception identifying the error. |
Hey @deepak1556, this issue might need further attention. @brocawernicke, you can help us out by closing this issue if the problem no longer exists, or adding more information. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Can you try launching with |
I always used |
Please continue to use those flags if elevation is required. Merging to #122951 |
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
[6300:0407/004202.981:ERROR:gpu_process_host.cc(977)] GPU process launch failed: error_code=18
[6300:0407/004202.981:WARNING:gpu_process_host.cc(1288)] The GPU process has crashed 9 time(s)
[6300:0407/004202.981:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
The text was updated successfully, but these errors were encountered: