Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. The application was unable to start correctly (0xc000007b)
QtWS25 Last Chance

The application was unable to start correctly (0xc000007b)

Scheduled Pinned Locked Moved Solved General and Desktop
8 Posts 5 Posters 2.8k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    JakobJohannes
    wrote on 8 May 2019, 18:36 last edited by
    #1

    Recently I began programming applications with Qt (5.12.3). When building (with mingw730_64) and starting applications in Qt Creator (4.9.0) for Windows 10, everything is fine, but when trying to start the .exe (after deploying it with windeployqt.exe from mingw73_64), I get the error message "The application was unable to start correctly (0xc000007b)". I should say that I have a earlier installation of mingw32 (not bundled with Qt), so I'm not sure, if this two installations conflict or if this is a problem at all. I tried to run Dependency Walker (v2.2 x64 and x86), but after loading the .exe, the walker refused to operate. Anyway any hint to solve my problem would be very much appreciated. Thanks in advance!

    A O 2 Replies Last reply 8 May 2019, 18:43
    0
    • J JakobJohannes
      8 May 2019, 18:36

      Recently I began programming applications with Qt (5.12.3). When building (with mingw730_64) and starting applications in Qt Creator (4.9.0) for Windows 10, everything is fine, but when trying to start the .exe (after deploying it with windeployqt.exe from mingw73_64), I get the error message "The application was unable to start correctly (0xc000007b)". I should say that I have a earlier installation of mingw32 (not bundled with Qt), so I'm not sure, if this two installations conflict or if this is a problem at all. I tried to run Dependency Walker (v2.2 x64 and x86), but after loading the .exe, the walker refused to operate. Anyway any hint to solve my problem would be very much appreciated. Thanks in advance!

      A Offline
      A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on 8 May 2019, 18:43 last edited by
      #2

      @JakobJohannes I'd start inspecting the PATH variable. If there are directories with other MinGW or Qt versions in it, strange things can happen.

      On the other hand, I never saw Dependency Walker refusing it's work. You seem to hit a very heavy problem :)

      Have you already tried running the app on another PC?

      Qt has to stay free or it will die.

      1 Reply Last reply
      2
      • J JakobJohannes
        8 May 2019, 18:36

        Recently I began programming applications with Qt (5.12.3). When building (with mingw730_64) and starting applications in Qt Creator (4.9.0) for Windows 10, everything is fine, but when trying to start the .exe (after deploying it with windeployqt.exe from mingw73_64), I get the error message "The application was unable to start correctly (0xc000007b)". I should say that I have a earlier installation of mingw32 (not bundled with Qt), so I'm not sure, if this two installations conflict or if this is a problem at all. I tried to run Dependency Walker (v2.2 x64 and x86), but after loading the .exe, the walker refused to operate. Anyway any hint to solve my problem would be very much appreciated. Thanks in advance!

        O Offline
        O Offline
        ODБOï
        wrote on 8 May 2019, 19:58 last edited by
        #3

        @JakobJohannes you can put the exe in qt dir and try start it to quick test

        1 Reply Last reply
        1
        • F Offline
          F Offline
          fcarney
          wrote on 8 May 2019, 20:10 last edited by
          #4

          Perhaps look at the windeployqt log/output and check to see if its grabbing dlls from places it should not. Like is it grabbing dlls from the wrong version of mingw or something silly like that. Also, make sure the windeployqt is being run from the proper version of qt, if multiples installed.

          I ran into that issue with lupdate/lrelease as it is installed in Ubuntu and available, but does not catch everything that the version that ships with 5.12.2 does.

          C++ is a perfectly valid school of magic.

          1 Reply Last reply
          3
          • J Offline
            J Offline
            JakobJohannes
            wrote on 9 May 2019, 17:07 last edited by
            #5

            Thanks to all three replies I could solve the problem: The PATH variable contained the directory of the older MinGW. I had to replace it with the directory of the compiler (mingw730_64) coming with the installation of Qt. Then, after running again windeployqt.exe (from mingw73_64), the correct dlls were installed in the app directory and now my apps are running fine!
            Of great help was looking at the PATH-Variable, trying the .exe in the qt directory and checking the log/output of the windeployqt.exe.
            Thanks again for the quick and useful help!

            J 1 Reply Last reply 10 May 2019, 04:33
            2
            • J JakobJohannes
              9 May 2019, 17:07

              Thanks to all three replies I could solve the problem: The PATH variable contained the directory of the older MinGW. I had to replace it with the directory of the compiler (mingw730_64) coming with the installation of Qt. Then, after running again windeployqt.exe (from mingw73_64), the correct dlls were installed in the app directory and now my apps are running fine!
              Of great help was looking at the PATH-Variable, trying the .exe in the qt directory and checking the log/output of the windeployqt.exe.
              Thanks again for the quick and useful help!

              J Offline
              J Offline
              jsulm
              Lifetime Qt Champion
              wrote on 10 May 2019, 04:33 last edited by
              #6

              @JakobJohannes said in The application was unable to start correctly (0xc000007b):

              I had to replace it with the directory of the compiler (mingw730_64) coming with the installation of Qt

              You don't have to add the compiler directory to your PATH (unless you want to call the compiler manually from command line). In QtCreator you specify the full path to compiler anyway.

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              1
              • J Offline
                J Offline
                JakobJohannes
                wrote on 10 May 2019, 14:56 last edited by
                #7

                @jsulm: When executing windeployqt.exe without the compiler directory in the PATH, the output of windeployqt gives the warning:

                Warning: Cannot find GCC installation directory. g++.exe must be in the path.
                

                Then calling the .exe gives multiple error messages telling that dlls are missing:
                In my case: libgcc_s_seh-1.dll, libstdc++-6.dll, libwinpthread-1.dll.
                Actually my compiler is in another directory (Qtdir\Tools\mingw730_64\bin) than the windeployqt.exe (Qtdir\5.12.3\mingw73_64\bin). That may be the reason, why I need the PATH variable set to the compiler directory.

                A 1 Reply Last reply 10 May 2019, 17:47
                0
                • J JakobJohannes
                  10 May 2019, 14:56

                  @jsulm: When executing windeployqt.exe without the compiler directory in the PATH, the output of windeployqt gives the warning:

                  Warning: Cannot find GCC installation directory. g++.exe must be in the path.
                  

                  Then calling the .exe gives multiple error messages telling that dlls are missing:
                  In my case: libgcc_s_seh-1.dll, libstdc++-6.dll, libwinpthread-1.dll.
                  Actually my compiler is in another directory (Qtdir\Tools\mingw730_64\bin) than the windeployqt.exe (Qtdir\5.12.3\mingw73_64\bin). That may be the reason, why I need the PATH variable set to the compiler directory.

                  A Offline
                  A Offline
                  aha_1980
                  Lifetime Qt Champion
                  wrote on 10 May 2019, 17:47 last edited by
                  #8

                  @JakobJohannes If you set the compiler path only in the shell for windeployqt, that is Ok. Setting it in global environment can have the side effects you already noticed.

                  Btw, newer Creator versions allow using the selected run environment for shell or external tools.

                  Regards

                  Qt has to stay free or it will die.

                  1 Reply Last reply
                  1

                  2/8

                  8 May 2019, 18:43

                  6 unread
                  • Login

                  • Login or register to search.
                  2 out of 8
                  • First post
                    2/8
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved