Opening a wsl shell from another windows application











up vote
0
down vote

favorite












I'm trying to configure Tower (git client) to launch a wsl bash shell. I've tried a whole bunch of things, but it seems this isn't intended.



enter image description here



What I tried:



command:     c:windowssystem32wsl.exe
parameters: bash -i

command: c:windowssystem32bash.exe
parameters: -i

command: c:windowssystem32cmd.exe
parameters: /c "bash -i"

command: c:windowssystem32bash.exe
parameters: -i

command: c:WINDOWSSystem32windowspowershellv1.0powershell.exe
parameters: wsl bash -i

command: cmd
parameters: /c start start bash -i

command: C:WindowsSysWOW64cmd.exe
parameters: /c start start bash -i


All of these just pop-up a console window for a very short time and then return to Tower.



Most of these commands work from the explorer window...



windows cmd










share|improve this question
























  • Did you try any other open source free git client like GitHub desktop?
    – Biswapriyo
    Dec 3 at 19:26










  • @Biswapriyo not sure how that would help. I simply want to launch a wsl bash shell directly from Tower. I already like and use Tower. I'm not looking for another git client replacement.
    – jessehouwing
    Dec 3 at 19:27










  • Looks like this may be an issue for x86 windows applications not picking up the Windows x64 Filesystem redirection (stackoverflow.com/a/41757861/736079)
    – jessehouwing
    Dec 3 at 19:36










  • Looks like github.com/goreliu/wsl-terminal is an option, though I'd like to not depend on a 3rd party tool.
    – jessehouwing
    Dec 3 at 19:41















up vote
0
down vote

favorite












I'm trying to configure Tower (git client) to launch a wsl bash shell. I've tried a whole bunch of things, but it seems this isn't intended.



enter image description here



What I tried:



command:     c:windowssystem32wsl.exe
parameters: bash -i

command: c:windowssystem32bash.exe
parameters: -i

command: c:windowssystem32cmd.exe
parameters: /c "bash -i"

command: c:windowssystem32bash.exe
parameters: -i

command: c:WINDOWSSystem32windowspowershellv1.0powershell.exe
parameters: wsl bash -i

command: cmd
parameters: /c start start bash -i

command: C:WindowsSysWOW64cmd.exe
parameters: /c start start bash -i


All of these just pop-up a console window for a very short time and then return to Tower.



Most of these commands work from the explorer window...



windows cmd










share|improve this question
























  • Did you try any other open source free git client like GitHub desktop?
    – Biswapriyo
    Dec 3 at 19:26










  • @Biswapriyo not sure how that would help. I simply want to launch a wsl bash shell directly from Tower. I already like and use Tower. I'm not looking for another git client replacement.
    – jessehouwing
    Dec 3 at 19:27










  • Looks like this may be an issue for x86 windows applications not picking up the Windows x64 Filesystem redirection (stackoverflow.com/a/41757861/736079)
    – jessehouwing
    Dec 3 at 19:36










  • Looks like github.com/goreliu/wsl-terminal is an option, though I'd like to not depend on a 3rd party tool.
    – jessehouwing
    Dec 3 at 19:41













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm trying to configure Tower (git client) to launch a wsl bash shell. I've tried a whole bunch of things, but it seems this isn't intended.



enter image description here



What I tried:



command:     c:windowssystem32wsl.exe
parameters: bash -i

command: c:windowssystem32bash.exe
parameters: -i

command: c:windowssystem32cmd.exe
parameters: /c "bash -i"

command: c:windowssystem32bash.exe
parameters: -i

command: c:WINDOWSSystem32windowspowershellv1.0powershell.exe
parameters: wsl bash -i

command: cmd
parameters: /c start start bash -i

command: C:WindowsSysWOW64cmd.exe
parameters: /c start start bash -i


All of these just pop-up a console window for a very short time and then return to Tower.



Most of these commands work from the explorer window...



windows cmd










share|improve this question















I'm trying to configure Tower (git client) to launch a wsl bash shell. I've tried a whole bunch of things, but it seems this isn't intended.



enter image description here



What I tried:



command:     c:windowssystem32wsl.exe
parameters: bash -i

command: c:windowssystem32bash.exe
parameters: -i

command: c:windowssystem32cmd.exe
parameters: /c "bash -i"

command: c:windowssystem32bash.exe
parameters: -i

command: c:WINDOWSSystem32windowspowershellv1.0powershell.exe
parameters: wsl bash -i

command: cmd
parameters: /c start start bash -i

command: C:WindowsSysWOW64cmd.exe
parameters: /c start start bash -i


All of these just pop-up a console window for a very short time and then return to Tower.



Most of these commands work from the explorer window...



windows cmd







windows-10 bash cmd.exe console windows-subsystem-for-linux






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 3 at 19:38

























asked Dec 3 at 19:05









jessehouwing

3452521




3452521












  • Did you try any other open source free git client like GitHub desktop?
    – Biswapriyo
    Dec 3 at 19:26










  • @Biswapriyo not sure how that would help. I simply want to launch a wsl bash shell directly from Tower. I already like and use Tower. I'm not looking for another git client replacement.
    – jessehouwing
    Dec 3 at 19:27










  • Looks like this may be an issue for x86 windows applications not picking up the Windows x64 Filesystem redirection (stackoverflow.com/a/41757861/736079)
    – jessehouwing
    Dec 3 at 19:36










  • Looks like github.com/goreliu/wsl-terminal is an option, though I'd like to not depend on a 3rd party tool.
    – jessehouwing
    Dec 3 at 19:41


















  • Did you try any other open source free git client like GitHub desktop?
    – Biswapriyo
    Dec 3 at 19:26










  • @Biswapriyo not sure how that would help. I simply want to launch a wsl bash shell directly from Tower. I already like and use Tower. I'm not looking for another git client replacement.
    – jessehouwing
    Dec 3 at 19:27










  • Looks like this may be an issue for x86 windows applications not picking up the Windows x64 Filesystem redirection (stackoverflow.com/a/41757861/736079)
    – jessehouwing
    Dec 3 at 19:36










  • Looks like github.com/goreliu/wsl-terminal is an option, though I'd like to not depend on a 3rd party tool.
    – jessehouwing
    Dec 3 at 19:41
















Did you try any other open source free git client like GitHub desktop?
– Biswapriyo
Dec 3 at 19:26




Did you try any other open source free git client like GitHub desktop?
– Biswapriyo
Dec 3 at 19:26












@Biswapriyo not sure how that would help. I simply want to launch a wsl bash shell directly from Tower. I already like and use Tower. I'm not looking for another git client replacement.
– jessehouwing
Dec 3 at 19:27




@Biswapriyo not sure how that would help. I simply want to launch a wsl bash shell directly from Tower. I already like and use Tower. I'm not looking for another git client replacement.
– jessehouwing
Dec 3 at 19:27












Looks like this may be an issue for x86 windows applications not picking up the Windows x64 Filesystem redirection (stackoverflow.com/a/41757861/736079)
– jessehouwing
Dec 3 at 19:36




Looks like this may be an issue for x86 windows applications not picking up the Windows x64 Filesystem redirection (stackoverflow.com/a/41757861/736079)
– jessehouwing
Dec 3 at 19:36












Looks like github.com/goreliu/wsl-terminal is an option, though I'd like to not depend on a 3rd party tool.
– jessehouwing
Dec 3 at 19:41




Looks like github.com/goreliu/wsl-terminal is an option, though I'd like to not depend on a 3rd party tool.
– jessehouwing
Dec 3 at 19:41










2 Answers
2






active

oldest

votes

















up vote
2
down vote



accepted










To launch a 64-bit executable from a 32-bit process, like launching wsl.exe from Tower, you need to use the sysnative filesystem redirector.



In this case, run: %windir%sysnativewsl.exe



You can test this by first launching a 32-bit version of Cmd by executing the following from the Run Dialog (Windows + R): %windir%SysWoW64cmd.exe



Then, inside the Cmd instance, you can execute the following:



%windir%sysnativewsl.exe



You should now see 64-bit WSL running attached to the same Console instance:
enter image description here






share|improve this answer




























    up vote
    0
    down vote













    It looks like this workaround does the trick:



    command:    C:WINDOWSsysnativeWindowsPowerShellv1.0powershell.exe
    parameters: wsl bash


    It launches a 64-bit PowerShell instance to then load Windows Subsystem for Linux.



    See also:




    • https://jessehouwing.net/git-tower-launch-wsl-bash/


    enter image description here





    Alternative:



    Another option I found is to use wsl-terminal, but since that depends on a 3rd party terminal and a whole bunch of other dependencies, it'd rather not use it.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380488%2fopening-a-wsl-shell-from-another-windows-application%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      2
      down vote



      accepted










      To launch a 64-bit executable from a 32-bit process, like launching wsl.exe from Tower, you need to use the sysnative filesystem redirector.



      In this case, run: %windir%sysnativewsl.exe



      You can test this by first launching a 32-bit version of Cmd by executing the following from the Run Dialog (Windows + R): %windir%SysWoW64cmd.exe



      Then, inside the Cmd instance, you can execute the following:



      %windir%sysnativewsl.exe



      You should now see 64-bit WSL running attached to the same Console instance:
      enter image description here






      share|improve this answer

























        up vote
        2
        down vote



        accepted










        To launch a 64-bit executable from a 32-bit process, like launching wsl.exe from Tower, you need to use the sysnative filesystem redirector.



        In this case, run: %windir%sysnativewsl.exe



        You can test this by first launching a 32-bit version of Cmd by executing the following from the Run Dialog (Windows + R): %windir%SysWoW64cmd.exe



        Then, inside the Cmd instance, you can execute the following:



        %windir%sysnativewsl.exe



        You should now see 64-bit WSL running attached to the same Console instance:
        enter image description here






        share|improve this answer























          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          To launch a 64-bit executable from a 32-bit process, like launching wsl.exe from Tower, you need to use the sysnative filesystem redirector.



          In this case, run: %windir%sysnativewsl.exe



          You can test this by first launching a 32-bit version of Cmd by executing the following from the Run Dialog (Windows + R): %windir%SysWoW64cmd.exe



          Then, inside the Cmd instance, you can execute the following:



          %windir%sysnativewsl.exe



          You should now see 64-bit WSL running attached to the same Console instance:
          enter image description here






          share|improve this answer












          To launch a 64-bit executable from a 32-bit process, like launching wsl.exe from Tower, you need to use the sysnative filesystem redirector.



          In this case, run: %windir%sysnativewsl.exe



          You can test this by first launching a 32-bit version of Cmd by executing the following from the Run Dialog (Windows + R): %windir%SysWoW64cmd.exe



          Then, inside the Cmd instance, you can execute the following:



          %windir%sysnativewsl.exe



          You should now see 64-bit WSL running attached to the same Console instance:
          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 3 at 22:25









          Richard Turner

          64159




          64159
























              up vote
              0
              down vote













              It looks like this workaround does the trick:



              command:    C:WINDOWSsysnativeWindowsPowerShellv1.0powershell.exe
              parameters: wsl bash


              It launches a 64-bit PowerShell instance to then load Windows Subsystem for Linux.



              See also:




              • https://jessehouwing.net/git-tower-launch-wsl-bash/


              enter image description here





              Alternative:



              Another option I found is to use wsl-terminal, but since that depends on a 3rd party terminal and a whole bunch of other dependencies, it'd rather not use it.






              share|improve this answer



























                up vote
                0
                down vote













                It looks like this workaround does the trick:



                command:    C:WINDOWSsysnativeWindowsPowerShellv1.0powershell.exe
                parameters: wsl bash


                It launches a 64-bit PowerShell instance to then load Windows Subsystem for Linux.



                See also:




                • https://jessehouwing.net/git-tower-launch-wsl-bash/


                enter image description here





                Alternative:



                Another option I found is to use wsl-terminal, but since that depends on a 3rd party terminal and a whole bunch of other dependencies, it'd rather not use it.






                share|improve this answer

























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  It looks like this workaround does the trick:



                  command:    C:WINDOWSsysnativeWindowsPowerShellv1.0powershell.exe
                  parameters: wsl bash


                  It launches a 64-bit PowerShell instance to then load Windows Subsystem for Linux.



                  See also:




                  • https://jessehouwing.net/git-tower-launch-wsl-bash/


                  enter image description here





                  Alternative:



                  Another option I found is to use wsl-terminal, but since that depends on a 3rd party terminal and a whole bunch of other dependencies, it'd rather not use it.






                  share|improve this answer














                  It looks like this workaround does the trick:



                  command:    C:WINDOWSsysnativeWindowsPowerShellv1.0powershell.exe
                  parameters: wsl bash


                  It launches a 64-bit PowerShell instance to then load Windows Subsystem for Linux.



                  See also:




                  • https://jessehouwing.net/git-tower-launch-wsl-bash/


                  enter image description here





                  Alternative:



                  Another option I found is to use wsl-terminal, but since that depends on a 3rd party terminal and a whole bunch of other dependencies, it'd rather not use it.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Dec 3 at 20:08

























                  answered Dec 3 at 19:51









                  jessehouwing

                  3452521




                  3452521






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380488%2fopening-a-wsl-shell-from-another-windows-application%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                      Mangá

                      Eduardo VII do Reino Unido