Skip to content
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 open more than one instance when VSCode is run as administrator #37962

Closed
joemaffei opened this issue Nov 9, 2017 · 5 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) windows VS Code on Windows issues workbench-run-as-admin Issues concerning running as administrator

Comments

@joemaffei
Copy link

  • VSCode Version: 1.19.0-insider
  • OS Version: Windows 10 Pro

Steps to Reproduce:

  1. Run VSCode as administrator (either by right-clicking the icon or setting it as the default in Properties -> Advanced)
  2. Try to start another instance, either by choosing "New Window" or "Visual Studio Code - Insiders"

Reproduces without extensions: Yes

It may be worth pointing out that I'm using cmder as my integrated terminal. I have not tried disabling it to see if it fixes the issue but will try that and report back.

@vscodebot vscodebot bot added the insiders label Nov 9, 2017
@vscodebot vscodebot bot added the workbench label Nov 9, 2017
@bpasero
Copy link
Member

bpasero commented Nov 10, 2017

@joemaffei does it work if you run from the command line?

@bpasero bpasero added info-needed Issue requires more information from poster workbench-os-integration Native OS integration issues windows VS Code on Windows issues workbench-run-as-admin Issues concerning running as administrator and removed workbench workbench-os-integration Native OS integration issues labels Nov 10, 2017
@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Nov 19, 2017
@bpasero bpasero assigned joaomoreno and unassigned bpasero Nov 19, 2017
@bpasero
Copy link
Member

bpasero commented Nov 19, 2017

I can reproduce:

Error: connect EPERM \\.\pipe\ebe3a8355186f99da77237014959374e-1.19.0-insider-main-sock
    at Object.exports._errnoException (util.js:1050:11)
    at exports._exceptionWithHostPort (util.js:1073:20)
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)

@joaomoreno Can we create the pipe with other permissions

Very similar to #6560

@joaomoreno joaomoreno assigned bpasero and unassigned joaomoreno Nov 20, 2017
@joaomoreno
Copy link
Member

You have to use different user data directories... We don't support sharing them across users.

@bpasero
Copy link
Member

bpasero commented Nov 21, 2017

@joaomoreno that is unfortunate. If we knew the user was running as admin, we could maybe use a different socket. Or actually we should detect this early enough that we force a different user data directory right from the beginning.

/duplicate #6560

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 21, 2017
@vscodebot
Copy link

vscodebot bot commented Nov 21, 2017

This issue has been closed because it is already tracked by another issue. See also our GitHub issues to search for existing issues and our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Nov 21, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) windows VS Code on Windows issues workbench-run-as-admin Issues concerning running as administrator
Projects
None yet
Development

No branches or pull requests

3 participants