-
Notifications
You must be signed in to change notification settings - Fork 814
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
Unable to launch Windows applications from WSL #3809
Comments
I was able to reproduce here on 18323. I guess something went south that roll. Nothing to see in the strace. WSL thinks the
On a lark I tried launching |
Something wrong in
syscall 20 is If I launch in |
This is an issue with path translation that will be fixed shortly. |
Is there any issue in new 20H1 builds? If I type
|
I will say that in at least one instance, I've seen different results in launching Windows EXE files, depending on the starting directory in WSL: whether it is a Windows file system from fwiw - cmd.exe does not seem to be affected on my machine:
I will say that on more than one occasion, I've done a rip-n-replace of WSL Ubuntu, fully removing and installing fresh. |
@Biswa96 - This is an expected warning. cmd.exe does not support UNC paths. |
Just checking, is this expected to still not be working fully in build 18890? |
@benhillis is there workaround to this? |
how would one launch it without the warning? |
I work-around with The problem is worthy of a standalone new issue / feature request (categorization academic) for someone motivated. [The warning was not the OP submission, which was a failure to launch an interop app period, long addressed some eons back in Feb 2019.] Spewing a warning (however well meaning) is not Linux behavior (or *nix behavior). The warning message is notably incorrect when the command doesn't involve a UNC path to begin with. Whether addressing the problem would be entertained I can't say, but would get my thumbs-up on a well-formed OP from me, anyway. The fix is to have a In principle it could be worked-around harder for someone super-motivated enough to do their own |
Please fill out the below information:
Your Windows build number: Microsoft Windows [Version 10.0.18323.1000]
What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
skuzzer@skuzlaptop:~$ notepad
What's wrong / what should be happening instead: Notepad should launch, nothing happens instead.
Strace of the failing command, if applicable: notepad.strace
The text was updated successfully, but these errors were encountered: