Cygwin window closes immediately












2















The configuration:




  • Windows 10 (64-bit) (Fresh installation)

  • Cygwin64 fresh installation (downloaded setup-x86_64.exe)


Installation looks like it worked. However, when I try to launch the newly created shortcut, the window closes immediately.



The shortcut target is C:cygwin64binmintty.exe -i /Cygwin-Terminal.ico -.



If I modify it to C:cygwin64binmintty.exe -h always -i /Cygwin-Terminal.ico -, the window stays open, but the message inside is Failed to run /Cygwin-Terminal.ico: Permission denied.



The following might be a red herring, but I suspect it is actually related to the problem:
If I run cmd and cd c:cygwin64, I can run Cygwin.bat, however the prompt is Unknown+User@DESKTOP-6SQ80GV ~, which is not actually my username. /cygdrive/c/cygwin64/Cygwin-Terminal.ico is owned by Unknown+User with group of Administrators, and has permissions of 644. If I chmod +x it, the error message in the window changes to:



C:/cygwin64/sbin/nologin.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
/sbin/nologin: Exit 127


I've done some quick searching and my google-fu is apparently failing, as I'm not finding much to go on. I'm guessing I could thrash around and eventually make things work, but I'm wondering if anyone here knows "what is the right way to fix this problem?".










share|improve this question



























    2















    The configuration:




    • Windows 10 (64-bit) (Fresh installation)

    • Cygwin64 fresh installation (downloaded setup-x86_64.exe)


    Installation looks like it worked. However, when I try to launch the newly created shortcut, the window closes immediately.



    The shortcut target is C:cygwin64binmintty.exe -i /Cygwin-Terminal.ico -.



    If I modify it to C:cygwin64binmintty.exe -h always -i /Cygwin-Terminal.ico -, the window stays open, but the message inside is Failed to run /Cygwin-Terminal.ico: Permission denied.



    The following might be a red herring, but I suspect it is actually related to the problem:
    If I run cmd and cd c:cygwin64, I can run Cygwin.bat, however the prompt is Unknown+User@DESKTOP-6SQ80GV ~, which is not actually my username. /cygdrive/c/cygwin64/Cygwin-Terminal.ico is owned by Unknown+User with group of Administrators, and has permissions of 644. If I chmod +x it, the error message in the window changes to:



    C:/cygwin64/sbin/nologin.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
    /sbin/nologin: Exit 127


    I've done some quick searching and my google-fu is apparently failing, as I'm not finding much to go on. I'm guessing I could thrash around and eventually make things work, but I'm wondering if anyone here knows "what is the right way to fix this problem?".










    share|improve this question

























      2












      2








      2








      The configuration:




      • Windows 10 (64-bit) (Fresh installation)

      • Cygwin64 fresh installation (downloaded setup-x86_64.exe)


      Installation looks like it worked. However, when I try to launch the newly created shortcut, the window closes immediately.



      The shortcut target is C:cygwin64binmintty.exe -i /Cygwin-Terminal.ico -.



      If I modify it to C:cygwin64binmintty.exe -h always -i /Cygwin-Terminal.ico -, the window stays open, but the message inside is Failed to run /Cygwin-Terminal.ico: Permission denied.



      The following might be a red herring, but I suspect it is actually related to the problem:
      If I run cmd and cd c:cygwin64, I can run Cygwin.bat, however the prompt is Unknown+User@DESKTOP-6SQ80GV ~, which is not actually my username. /cygdrive/c/cygwin64/Cygwin-Terminal.ico is owned by Unknown+User with group of Administrators, and has permissions of 644. If I chmod +x it, the error message in the window changes to:



      C:/cygwin64/sbin/nologin.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
      /sbin/nologin: Exit 127


      I've done some quick searching and my google-fu is apparently failing, as I'm not finding much to go on. I'm guessing I could thrash around and eventually make things work, but I'm wondering if anyone here knows "what is the right way to fix this problem?".










      share|improve this question














      The configuration:




      • Windows 10 (64-bit) (Fresh installation)

      • Cygwin64 fresh installation (downloaded setup-x86_64.exe)


      Installation looks like it worked. However, when I try to launch the newly created shortcut, the window closes immediately.



      The shortcut target is C:cygwin64binmintty.exe -i /Cygwin-Terminal.ico -.



      If I modify it to C:cygwin64binmintty.exe -h always -i /Cygwin-Terminal.ico -, the window stays open, but the message inside is Failed to run /Cygwin-Terminal.ico: Permission denied.



      The following might be a red herring, but I suspect it is actually related to the problem:
      If I run cmd and cd c:cygwin64, I can run Cygwin.bat, however the prompt is Unknown+User@DESKTOP-6SQ80GV ~, which is not actually my username. /cygdrive/c/cygwin64/Cygwin-Terminal.ico is owned by Unknown+User with group of Administrators, and has permissions of 644. If I chmod +x it, the error message in the window changes to:



      C:/cygwin64/sbin/nologin.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
      /sbin/nologin: Exit 127


      I've done some quick searching and my google-fu is apparently failing, as I'm not finding much to go on. I'm guessing I could thrash around and eventually make things work, but I'm wondering if anyone here knows "what is the right way to fix this problem?".







      windows-10 cygwin






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 12 '15 at 19:05









      Jed DanielsJed Daniels

      1,061814




      1,061814






















          3 Answers
          3






          active

          oldest

          votes


















          8














          I had the same issue after updating my Cygwin installation on Windows 7. The problem wasn't the update itself but the activation of the cygserver service. If you have any Cygwin service installed in your Windows machine try solving the problem by setting these services to either manual start or automatic start but delayed.



          The problem is that the service 'cygserver' will cache account information and provide it to other Cygwin applications and services like described in https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-caching. The account data is retrieved from Microsoft LDAP service which needs more time to start than the cygserver service. Setting the cygserver service to delayed automatic start will resolve this problem. But keep in mind that the start of the cygserver service may delayed a couple of minutes after (re)boot of Windows.



          Hope this helps :-)






          share|improve this answer































            1














            for the issue of

            Unknown+User@DESKTOP-6SQ80GV



            you need to read
            https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch



            as cygwin seems currently unable to recover from SSID your user profile.
            As W10 is recent, may be something in your configuration has not yet been considered, so best place for extra support is the main mailing list:
            https://www.cygwin.com/cygwin/lists.html
            https://www.cygwin.com/ml/cygwin/






            share|improve this answer































              1














              To expand on Izzet Beltir's answer, you can simply restart the service if you want to get Cygwin working immediately.



              Open an elevated command line or PowerShell window, and simply run these commands:



              net stop cygservice
              net start cygservice


              You should now be able to open Cygwin just fine.






              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',
                autoActivateHeartbeat: false,
                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%2f985719%2fcygwin-window-closes-immediately%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                3 Answers
                3






                active

                oldest

                votes








                3 Answers
                3






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                8














                I had the same issue after updating my Cygwin installation on Windows 7. The problem wasn't the update itself but the activation of the cygserver service. If you have any Cygwin service installed in your Windows machine try solving the problem by setting these services to either manual start or automatic start but delayed.



                The problem is that the service 'cygserver' will cache account information and provide it to other Cygwin applications and services like described in https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-caching. The account data is retrieved from Microsoft LDAP service which needs more time to start than the cygserver service. Setting the cygserver service to delayed automatic start will resolve this problem. But keep in mind that the start of the cygserver service may delayed a couple of minutes after (re)boot of Windows.



                Hope this helps :-)






                share|improve this answer




























                  8














                  I had the same issue after updating my Cygwin installation on Windows 7. The problem wasn't the update itself but the activation of the cygserver service. If you have any Cygwin service installed in your Windows machine try solving the problem by setting these services to either manual start or automatic start but delayed.



                  The problem is that the service 'cygserver' will cache account information and provide it to other Cygwin applications and services like described in https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-caching. The account data is retrieved from Microsoft LDAP service which needs more time to start than the cygserver service. Setting the cygserver service to delayed automatic start will resolve this problem. But keep in mind that the start of the cygserver service may delayed a couple of minutes after (re)boot of Windows.



                  Hope this helps :-)






                  share|improve this answer


























                    8












                    8








                    8







                    I had the same issue after updating my Cygwin installation on Windows 7. The problem wasn't the update itself but the activation of the cygserver service. If you have any Cygwin service installed in your Windows machine try solving the problem by setting these services to either manual start or automatic start but delayed.



                    The problem is that the service 'cygserver' will cache account information and provide it to other Cygwin applications and services like described in https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-caching. The account data is retrieved from Microsoft LDAP service which needs more time to start than the cygserver service. Setting the cygserver service to delayed automatic start will resolve this problem. But keep in mind that the start of the cygserver service may delayed a couple of minutes after (re)boot of Windows.



                    Hope this helps :-)






                    share|improve this answer













                    I had the same issue after updating my Cygwin installation on Windows 7. The problem wasn't the update itself but the activation of the cygserver service. If you have any Cygwin service installed in your Windows machine try solving the problem by setting these services to either manual start or automatic start but delayed.



                    The problem is that the service 'cygserver' will cache account information and provide it to other Cygwin applications and services like described in https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-caching. The account data is retrieved from Microsoft LDAP service which needs more time to start than the cygserver service. Setting the cygserver service to delayed automatic start will resolve this problem. But keep in mind that the start of the cygserver service may delayed a couple of minutes after (re)boot of Windows.



                    Hope this helps :-)







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jan 28 '16 at 15:28









                    Izzet BeltirIzzet Beltir

                    8112




                    8112

























                        1














                        for the issue of

                        Unknown+User@DESKTOP-6SQ80GV



                        you need to read
                        https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch



                        as cygwin seems currently unable to recover from SSID your user profile.
                        As W10 is recent, may be something in your configuration has not yet been considered, so best place for extra support is the main mailing list:
                        https://www.cygwin.com/cygwin/lists.html
                        https://www.cygwin.com/ml/cygwin/






                        share|improve this answer




























                          1














                          for the issue of

                          Unknown+User@DESKTOP-6SQ80GV



                          you need to read
                          https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch



                          as cygwin seems currently unable to recover from SSID your user profile.
                          As W10 is recent, may be something in your configuration has not yet been considered, so best place for extra support is the main mailing list:
                          https://www.cygwin.com/cygwin/lists.html
                          https://www.cygwin.com/ml/cygwin/






                          share|improve this answer


























                            1












                            1








                            1







                            for the issue of

                            Unknown+User@DESKTOP-6SQ80GV



                            you need to read
                            https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch



                            as cygwin seems currently unable to recover from SSID your user profile.
                            As W10 is recent, may be something in your configuration has not yet been considered, so best place for extra support is the main mailing list:
                            https://www.cygwin.com/cygwin/lists.html
                            https://www.cygwin.com/ml/cygwin/






                            share|improve this answer













                            for the issue of

                            Unknown+User@DESKTOP-6SQ80GV



                            you need to read
                            https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch



                            as cygwin seems currently unable to recover from SSID your user profile.
                            As W10 is recent, may be something in your configuration has not yet been considered, so best place for extra support is the main mailing list:
                            https://www.cygwin.com/cygwin/lists.html
                            https://www.cygwin.com/ml/cygwin/







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Oct 31 '15 at 6:58









                            matzerimatzeri

                            1,269156




                            1,269156























                                1














                                To expand on Izzet Beltir's answer, you can simply restart the service if you want to get Cygwin working immediately.



                                Open an elevated command line or PowerShell window, and simply run these commands:



                                net stop cygservice
                                net start cygservice


                                You should now be able to open Cygwin just fine.






                                share|improve this answer




























                                  1














                                  To expand on Izzet Beltir's answer, you can simply restart the service if you want to get Cygwin working immediately.



                                  Open an elevated command line or PowerShell window, and simply run these commands:



                                  net stop cygservice
                                  net start cygservice


                                  You should now be able to open Cygwin just fine.






                                  share|improve this answer


























                                    1












                                    1








                                    1







                                    To expand on Izzet Beltir's answer, you can simply restart the service if you want to get Cygwin working immediately.



                                    Open an elevated command line or PowerShell window, and simply run these commands:



                                    net stop cygservice
                                    net start cygservice


                                    You should now be able to open Cygwin just fine.






                                    share|improve this answer













                                    To expand on Izzet Beltir's answer, you can simply restart the service if you want to get Cygwin working immediately.



                                    Open an elevated command line or PowerShell window, and simply run these commands:



                                    net stop cygservice
                                    net start cygservice


                                    You should now be able to open Cygwin just fine.







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Jan 2 at 14:02









                                    Benjamin PaineBenjamin Paine

                                    111




                                    111






























                                        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.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function () {
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f985719%2fcygwin-window-closes-immediately%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

                                        Mouse cursor on multiple screens with different PPI

                                        Agildo Ribeiro

                                        Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”