-
Notifications
You must be signed in to change notification settings - Fork 19
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
wslbridge hangs when running elevated and non-elevated WSL instances simultaneously #13
Comments
Survey of Windows versions: I guess wslbridge can detect 15063 and up (how?), then redirect stdout to a pipe and detect the error. |
|
Maybe. I wonder about: (a) performance, (b) security/reliability, and (c) localization. I think I'd prefer if it queried the System32 directory and invoked cmd.exe without doing a PATH lookup. I'm guessing localization isn't an issue, because the string is I tried |
If the EXE had no manifest at all, then |
Wow! What a tremendous effort to capture an error message. Thanks a lot for committing this. |
@rprichard, can you make this a release, please? So I can again refer to a well-defined version from wsltty? |
Ok, the fix for this issue is now released in version 0.2.2. |
See mintty/wsltty#43 (comment).
wslbridge won't work in this situation, but it should try to fail gracefully.
The text was updated successfully, but these errors were encountered: