Doesn't seem to work with Windows 10 Bash.

[MJBrune]

I can't get Qonsole to work with the Windows 10 bash. I have no clue why but it simply isn't seeing bash.exe in system32 as a cmd path. Nor can I modify the lnk to point to the bash exe because the script then crashes. I'd love to get more information on this for you guys but I feel like this project isn't supported heavily.

[mobbel]

This happens after installing the creators update from microsoft windows 10. Before this was working fine as the normal cmd-console.

[MJBrune]

Interesting so what happened to bash? Do you think it's the actual bash executable that is the issue? Anyone have a copy of the old one?

[mobbel]

Think it's more a Microsoft/Windows Problem, after updating the WSL-Version is the same. You have to uninstall and reinstall to get the new version.

[joedf]

Hmm, try it with console2, then from that shell-wrapper launch bash? On Apr 14, 2017 3:58 AM, Michael Brune <notifications@github.com> wrote: I can't get Qonsole to work with the Windows 10 bash. I have no clue why but it simply isn't seeing bash.exe in system32 as a cmd path. Nor can I modify the lnk to point to the bash exe because the script then crashes. I'd love to get more information on this for you guys but I feel like this project isn't supported heavily. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#4>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADq4G10RGswdXSLI0_CIOS6-bVPKBkvrks5rvycrgaJpZM4M9i0M>.

[joedf]

A quick fix to what @mobbel has mentionned is to use the "Legacy" cmd.
As described here: #1 (comment)
I think I might find a programmatic solution to automatically change that... or I refactor Qonsole all together... :/

[mobbel]

Tested with Legacy-Mode didn't useable. Qonsole quits with same Error-Message, and bash comment this option that it isn't possible to use.

[joedf]

hmmm.... Does it work with mintty or console2?

[joedf]

I think I might have to do significant rewrites of certain parts.... :/

[sorenpeter]

Found a workaround:

• Search for bash.exe in Windows Explorer.
• Copy the one of the long path like:
  C:\Windows\WinSxS\amd64_microsoft-windows-lxss-bash_31bf3856ad364e35_10.0.14393.351_none_79648c7a5a883c6f
• Open Qonsole and cd into the path you found
• Run bash.exe and it seems to work.

When I search for bash.exe I get two results beside the one in System32, and only one of them works, the other gives an error about non-supported 16-bit application (my windows in danish, so not sure about the translation)

[joedf]

that's very odd...
Ahh.... MSWindows... always restructuring everything...

[sorenpeter]

I created a shortcut to the "hidden" bash.exe in my qonsole folder and renamed it to cmd_Qonsole.lnk so now qonsol opens up in bash.

[XDracam]

espetes solution did not work for me. Double-clicking the shortcut opens the pre-store bash. However, launching Qonsole gives following error:

[joedf]

if you simply double click C:\Users\Cameron\Qonsole\cmd_Qonsole.lnk, what happens?

[XDracam]

Double-clicking the shortcut opens the pre-store bash.

Meaning that the shortcut works if used manually, but fails with Qonsole.

[joedf]

Oh whoops, my bad...
Looks like there might a general issue of cmd attachment... #8 (comment)
Probably broken by changes in windows. I will have to investigate further in my spare time...