Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10
-
@Tusharn
To clarify: did you copy & paste the error message? You are sure it namesCreateEvent, spelled like that, and not, say,CreateEventW?Also, do you compile to generate a 64- or 32-bit executable?
UPDATE
Oh, I see you posted a screenshot clearly showingCreateEventW, it's vitally important you put that in your text, notCreateEvent, to provide help accurately.In that case, I have a suspicion: could the Windows 10 machine where this happens have been previously upgraded from Windows 7 to 10?
Assuming that is true, I believe this is an issue with the target machine, not with Qt or deployment. Have a read of https://answers.microsoft.com/en-us/windows/forum/all/entry-point-not-found-when-winsows7-upgrade-to/90da2fb1-1f8e-4ee7-9109-a4c96c829db1. I think in some shape or form you have a missing/incorrect Windows system DLL on the target, and need to address that somehow.
-
@JonB
But in my pc i searched that .dll file there file is available still i am facing this issue. -
-
This file (and friends) is supposed to be a standard part of a Windows 10 install. The file can be present but not be properly registered or missing some other dependency. This might be a case where
sfc /scannowfrom an Administrator command prompt/Powershell on the target machine helps. (This was a standard file in Windows 7 and 8, which discounts the failed upgrade idea a bit.)Another option would be to download and install the latest version of all the Microsoft Visual C++ Redistributable packages. It is possible that one of these will replace or update the missing DLLS.
-
@Tusharn
To clarify: did you copy & paste the error message? You are sure it namesCreateEvent, spelled like that, and not, say,CreateEventW?Also, do you compile to generate a 64- or 32-bit executable?
UPDATE
Oh, I see you posted a screenshot clearly showingCreateEventW, it's vitally important you put that in your text, notCreateEvent, to provide help accurately.In that case, I have a suspicion: could the Windows 10 machine where this happens have been previously upgraded from Windows 7 to 10?
Assuming that is true, I believe this is an issue with the target machine, not with Qt or deployment. Have a read of https://answers.microsoft.com/en-us/windows/forum/all/entry-point-not-found-when-winsows7-upgrade-to/90da2fb1-1f8e-4ee7-9109-a4c96c829db1. I think in some shape or form you have a missing/incorrect Windows system DLL on the target, and need to address that somehow.
-
-
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
@hskoglund running Windows 10 sir
-
But the screenshot you posted at the top ("... - Entry Point Not Found.... "), also looks very much as a screenshot from a Windows 7 desktop :-)
@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? -
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" :-(
-
@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? -
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" :-(
-
@hskoglund No sir i will post
-
@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.
@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.dllas 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.dllis on both machines, compare the date/size/versions of those two, run Dependencies on both to see if the "bad" one is missing dependency. -
@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.dllas 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.dllis on both machines, compare the date/size/versions of those two, run Dependencies on both to see if the "bad" one is missing dependency. -
@hskoglund
Hello
As you said PF screenshot of error getting on windows 10 pc , where as file mention in error is available in directory.
@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.
