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
Apps cannot be launched from \\.\ volume paths #16349
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. To help make it easier for us to investigate your issue, please follow the contributing guidelines. |
I'm trying to understand how important this bug is, given that this surely never worked and we've never had any complaints. Why would you not just launch the app from a drive path? |
Hello @felixrieseberg. This matters for people using UNC path or accessing shared network folders. |
It works using NW.JS which uses Chromium and Node.js as well. |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue. |
Output of
node_modules/.bin/electron --version
: 6.5.0Operating System : Windows 10 x64
Electron version: 4.0.1
Actual behaviors
I cannot start my app from a volume path. Let's say:
\\.\Volume{1df47f9b-1263-11e9-8722-f46d04fd6ee0}\myapp.exe
.To Reproduce
Get the volume path of your drive using
mountvol
int the CMD and try to execute your electron app from it.Additional Information
C:\myapp.exe
.The text was updated successfully, but these errors were encountered: