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. Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10
Forum Updated to NodeBB v4.3 + New Features

Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10

Scheduled Pinned Locked Moved Unsolved General and Desktop
33 Posts 7 Posters 6.8k Views 1 Watching
  • 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.
  • hskoglundH Online
    hskoglundH Online
    hskoglund
    wrote on last edited by
    #13

    Hi, since you get the same error both for both MinGW and MSVC compilers, are you sure the PC you are trying to install your app to is really running Windows 10 and not Windows 7?

    To check, please click the start button and type winver and Enter

    T 1 Reply Last reply
    0
    • hskoglundH hskoglund

      Hi, since you get the same error both for both MinGW and MSVC compilers, are you sure the PC you are trying to install your app to is really running Windows 10 and not Windows 7?

      To check, please click the start button and type winver and Enter

      T Offline
      T Offline
      Tusharn
      wrote on last edited by
      #14

      @hskoglund running Windows 10 sir

      1 Reply Last reply
      0
      • hskoglundH Online
        hskoglundH Online
        hskoglund
        wrote on last edited by
        #15

        But the screenshot you posted at the top ("... - Entry Point Not Found.... "), also looks very much as a screenshot from a Windows 7 desktop :-)

        JonBJ 1 Reply Last reply
        0
        • hskoglundH hskoglund

          But the screenshot you posted at the top ("... - Entry Point Not Found.... "), also looks very much as a screenshot from a Windows 7 desktop :-)

          JonBJ Offline
          JonBJ Offline
          JonB
          wrote on last edited by JonB
          #16

          @hskoglund said in Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10:

          also looks very much as a screenshot from a Windows 7 desktop :-)

          That's an interesting observation :)

          @Tusharn
          It might be really helpful if you can find a another machine to try installing on. If you have access to a different Windows 10 and/or 11 (preferably not upgraded from 7!) I would try on those. We need to establish whether it's just the current target machine which has the issue.

          Also did you ever try @ChrisW67's sfc /scannow?

          T 1 Reply Last reply
          0
          • hskoglundH Online
            hskoglundH Online
            hskoglund
            wrote on last edited by hskoglund
            #17

            Another indication that the screenshot is from a Windows 7 PC: that error dialog "... - Entry Point Not Found" still gave you information about which .dll that failed to export that symbol (i.e. api-ms-win-core-synch-l1-2-0.dll)

            But Windows 10 (and Windows 11 etc.) instead, for the same error, states which file (usually an .exe) that failed to import the symbol. So if this really was a Windows 10 desktop, the error message should have been:
            "The procedure entry point CreateEventW could not be located in the dynamic link library Elab_license_otp.exe"

            BTW: I think this is regression since it still says: "dynamic link library" :-(

            T 1 Reply Last reply
            0
            • JonBJ JonB

              @hskoglund said in Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10:

              also looks very much as a screenshot from a Windows 7 desktop :-)

              That's an interesting observation :)

              @Tusharn
              It might be really helpful if you can find a another machine to try installing on. If you have access to a different Windows 10 and/or 11 (preferably not upgraded from 7!) I would try on those. We need to establish whether it's just the current target machine which has the issue.

              Also did you ever try @ChrisW67's sfc /scannow?

              T Offline
              T Offline
              Tusharn
              wrote on last edited by
              #18

              @JonB yes sir i tried sfc/scannow .

              1 Reply Last reply
              0
              • hskoglundH hskoglund

                Another indication that the screenshot is from a Windows 7 PC: that error dialog "... - Entry Point Not Found" still gave you information about which .dll that failed to export that symbol (i.e. api-ms-win-core-synch-l1-2-0.dll)

                But Windows 10 (and Windows 11 etc.) instead, for the same error, states which file (usually an .exe) that failed to import the symbol. So if this really was a Windows 10 desktop, the error message should have been:
                "The procedure entry point CreateEventW could not be located in the dynamic link library Elab_license_otp.exe"

                BTW: I think this is regression since it still says: "dynamic link library" :-(

                T Offline
                T Offline
                Tusharn
                wrote on last edited by
                #19

                @hskoglund Yes sir i installed the application on windows 7 and after installation i got this error when i run the application and also i did it on windows 10 but getting same error.

                JonBJ 1 Reply Last reply
                0
                • hskoglundH Online
                  hskoglundH Online
                  hskoglund
                  wrote on last edited by
                  #20

                  Could you post a screenshot of that error from the Windows 10 PC?

                  T 2 Replies Last reply
                  0
                  • hskoglundH hskoglund

                    Could you post a screenshot of that error from the Windows 10 PC?

                    T Offline
                    T Offline
                    Tusharn
                    wrote on last edited by
                    #21

                    @hskoglund No sir i will post

                    1 Reply Last reply
                    0
                    • T Tusharn

                      @hskoglund Yes sir i installed the application on windows 7 and after installation i got this error when i run the application and also i did it on windows 10 but getting same error.

                      JonBJ Offline
                      JonBJ Offline
                      JonB
                      wrote on last edited by
                      #22

                      @Tusharn said in Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10:

                      @hskoglund Yes sir i installed the application on windows 7 and after installation i got this error when i run the application and also i did it on windows 10 but getting same error.

                      I no longer understand. Your first post states "during the installation process on the target Windows 10 machine", your screenshot (according to @hskoglund) shows Windows 7, and now you seem to say you did install on Windows 7 after all. It is difficult to be sure what you are saying.

                      At this point you need to:

                      • Write the absolute minimal Qt program, 10 lines long.
                      • Build for Release.
                      • Use windeployqt to create an installable image.
                      • Install on a Windows 10+ machine, preferably one which has not been upgraded from Windows 7.
                      • And if possible install on more than one machine, to rule out something on that machine being the issue.

                      You can see that people are running out of useful ideas to help. You can Google for

                      The procedure entry point CreateEventW could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll

                      as I have done, there are a couple of hits.

                      If your development machine runs the same Windows version as the one with that error you could find where api-ms-win-core-synch-l1-2-0.dll is on both machines, compare the date/size/versions of those two, run Dependencies on both to see if the "bad" one is missing dependency.

                      T 1 Reply Last reply
                      0
                      • JonBJ JonB

                        @Tusharn said in Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10:

                        @hskoglund Yes sir i installed the application on windows 7 and after installation i got this error when i run the application and also i did it on windows 10 but getting same error.

                        I no longer understand. Your first post states "during the installation process on the target Windows 10 machine", your screenshot (according to @hskoglund) shows Windows 7, and now you seem to say you did install on Windows 7 after all. It is difficult to be sure what you are saying.

                        At this point you need to:

                        • Write the absolute minimal Qt program, 10 lines long.
                        • Build for Release.
                        • Use windeployqt to create an installable image.
                        • Install on a Windows 10+ machine, preferably one which has not been upgraded from Windows 7.
                        • And if possible install on more than one machine, to rule out something on that machine being the issue.

                        You can see that people are running out of useful ideas to help. You can Google for

                        The procedure entry point CreateEventW could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll

                        as I have done, there are a couple of hits.

                        If your development machine runs the same Windows version as the one with that error you could find where api-ms-win-core-synch-l1-2-0.dll is on both machines, compare the date/size/versions of those two, run Dependencies on both to see if the "bad" one is missing dependency.

                        T Offline
                        T Offline
                        Tusharn
                        wrote on last edited by
                        #23

                        @JonB Thanks sir i will try as you said

                        1 Reply Last reply
                        0
                        • hskoglundH hskoglund

                          Could you post a screenshot of that error from the Windows 10 PC?

                          T Offline
                          T Offline
                          Tusharn
                          wrote on last edited by
                          #24

                          @hskoglund
                          Hello
                          As you said PF screenshot of error getting on windows 10 pc , where as file mention in error is available in directory.

                          90ae0e39-fce9-4509-9b4f-099bbe5cb229-image.png

                          JonBJ 1 Reply Last reply
                          0
                          • T Tusharn

                            @hskoglund
                            Hello
                            As you said PF screenshot of error getting on windows 10 pc , where as file mention in error is available in directory.

                            90ae0e39-fce9-4509-9b4f-099bbe5cb229-image.png

                            JonBJ Offline
                            JonBJ Offline
                            JonB
                            wrote on last edited by JonB
                            #25

                            @Tusharn
                            While it is true that I cannot spot why you get this error message given the directory's contents, this is a quite different error message from the one you said you get, you show at the top and we have been discussing throughout this topic. Why are you now getting a different message if you said Win 10 gave you the original message? Is this a different Win 10 machine from the one you said produced the first error? It is difficult to help when you report one thing and then show something different.....

                            It is possible that you could get the latest error message if the named DLL is missing one of its dependencies. You might like to load up the Windows Dependencies tool to examine this.

                            1 Reply Last reply
                            0
                            • hskoglundH Online
                              hskoglundH Online
                              hskoglund
                              wrote on last edited by
                              #26

                              Hi, just guessing but that missing dll error can occur if your app for example starts a printout and that Windows 10 PC has a older (perhaps not Qt) installation of MinGW that lacks libgcc_s_seh-1.dll and that other MinGW is in ithe path environment variable.

                              To check, try building a simple app, say the Calculator Example using your MinGW 6.5.1. Then use the same windeployqt procedure you did for Elab_license_otp.exe and try the Calculator app on that Windows 10 PC.

                              T 1 Reply Last reply
                              0
                              • hskoglundH hskoglund

                                Hi, just guessing but that missing dll error can occur if your app for example starts a printout and that Windows 10 PC has a older (perhaps not Qt) installation of MinGW that lacks libgcc_s_seh-1.dll and that other MinGW is in ithe path environment variable.

                                To check, try building a simple app, say the Calculator Example using your MinGW 6.5.1. Then use the same windeployqt procedure you did for Elab_license_otp.exe and try the Calculator app on that Windows 10 PC.

                                T Offline
                                T Offline
                                Tusharn
                                wrote on last edited by
                                #27

                                @hskoglund now i am run application on windows 7 & 10. I tried as you said but getting same error.

                                1 Reply Last reply
                                0
                                • hskoglundH Online
                                  hskoglundH Online
                                  hskoglund
                                  wrote on last edited by
                                  #28

                                  If you try the same Calculator example app again, but this time built with Qt 6.4.3 MSVC2019, do you get the same error?

                                  1 Reply Last reply
                                  0
                                  • M Offline
                                    M Offline
                                    MaxKozak
                                    wrote on last edited by
                                    #29

                                    I wrote application on windows 11 and find way to deploy it correctly, but on windows 7 this app doesn’t work and go to same error as yours. I try to reinstall dlls, sfc /scan, Visual Redistributable but still nothing. I try this app on windows 10 if it works

                                    1 Reply Last reply
                                    0
                                    • hskoglundH Online
                                      hskoglundH Online
                                      hskoglund
                                      wrote on last edited by
                                      #30

                                      Qt 6.4.3 MSVC 2019 or Qt 6.5.1 MinGW do not support deploying to Windows 7 :-(
                                      Qt6 requirements here

                                      1 Reply Last reply
                                      0
                                      • T Offline
                                        T Offline
                                        Tusharn
                                        wrote on last edited by
                                        #31

                                        Anyone tell me which version of qt creator is stable for windows or suitable for windows 10

                                        JonBJ 1 Reply Last reply
                                        0
                                        • T Tusharn

                                          Anyone tell me which version of qt creator is stable for windows or suitable for windows 10

                                          JonBJ Offline
                                          JonBJ Offline
                                          JonB
                                          wrote on last edited by JonB
                                          #32

                                          @Tusharn
                                          Are you really asking about Qt Creator version here? Do you understand that it is the Qt version, nothing to do with Creator, which determines whether your application will or won't run under Windows 7, 10 or whatever? So far as I know any version of Creator will run under Windows 10.

                                          1 Reply Last reply
                                          1

                                          • Login

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