Running under Administrator - empty console

[wclr]

Any thoughts why can not run wsl from commanlines that are run under Adminstrator?

vs under current user:

[mintty]

That works fine here.
Please cross-check by calling bash.exe directly, without wsltty.
You may also try to trace your profiles (~/.profile, ~/.bashrc, /etc/profile, /etc/bash.bashrc).

[wclr]

Hm... right

It seems to come that way probably after update to Windows insiders preview. Didn't find the problme in google.

[mintty]

So can we close the issue?
Although we might still be bothered that there is no proper feedback if this happens within mintty.
@rprichard, any chance that wslbridge might catch this case and report an error?

[rprichard]

I would think wslbridge could do a better job of handling this situation. It looks like it hangs forever, waiting for the wslbridge-backend to connect. If I kill the wslbridge frontend (e.g. Ctrl-C), it leaves the bash wrapper running forever in its hidden console. I'm not precisely sure of the fix, but it could time out or kill the bash wrapper process. In new enough versions of Win10, I think wslbridge could redirect stdout and capture the error. It's possible in Win10 15063. (I just noticed that the bash.exe error is UTF-16, but ordinary WSL programs output a narrow encoding -- UTF-8 maybe? Yuck.)

[mintty]

I may have to add another option -h error to the invocation to make the error message visible (or the window will just flicker and close), or imply that under the --wsl option.
Then the error message output breaks after 255 bytes and mintty will insert its own error message /bin/wslbridge: Exit 1. inmidst of the /bin/bash message. Hmm, maybe, I can add a delay...