Error "The procedure entry point CreateEvent could not be located" during installation of Qt C++ application on Windows 10
-
Dear Qt Forum Team,
I hope this message finds you well. I am writing to request assistance and guidance regarding an issue I encountered while attempting to create an application for Windows 10 using Qt C++. I have followed the necessary steps to create an executable (.exe) file of my Qt C++ project, and I proceeded to create an installer for distribution on another Windows 10 PC.
Steps to Create .exe File of Qt C++ Project:
Development Environment:
OS: Windows 10
Qt Version: Qt Creator 10.0.2
Compiler: Qt 6.4.3 (MSVC 2019, x86_64)
Qt Project:
a. Developed a Qt C++ application using Qt Creator.
b. Wrote the necessary code, designed the user interface using Qt Designer, and added any required resources.Build Configuration:
a. Opened the Qt project in Qt Creator.
b. Selected the target build configuration (e.g., Release or Debug).
c. Configured any project settings, including Qt modules required for the application.Build Process:
a. Clicked on "Build" or "Build All" from the menu bar in Qt Creator.
b. Waited for the build process to complete successfully.Locate the .exe File:
a. Once the build is successful, the generated .exe file can be found in the build directory of the project.
b. The default path for Release build: build-anglo-Desktop_Qt_6_5_1_MinGW_64_bit-Release
c. The default path for Debug build: build-anglo-Desktop_Qt_6_5_1_MinGW_64_bit-Debuganglo.exe File:
a. Double-clicked on the .exe file to ensure that the application runs correctly on the development machine.However, during the installation process on the target Windows 10 machine, an error message appeared, stating: "The procedure entry point CreateEvent could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll."
I am seeking help from the Qt community to understand the root cause of this error and to find a resolution to successfully install and run the Qt application on other Windows 10 PCs without encountering this issue and also suggest how to make installer fiile of qt project.
I have researched extensively to find a solution but have been unable to resolve the issue on my own. Therefore, I am kindly requesting the Qt community's support to shed some light on the possible causes of this error and provide guidance on how to fix it.
Any insights, recommendations, or steps to troubleshoot and resolve this issue would be greatly appreciated. I am open to providing further information or code samples, if necessary, to better diagnose the problem.
Thank you very much for your time and consideration. Your assistance will be of great help in ensuring a successful deployment of my Qt C++ application on Windows 10 machines.
Best regards,
Tushar NemadeYou have built your app but did not deploy it properly. Therefore linked libraries cant be found.
-
Hi, if you trying compiling the app with Qt 6.4.3 MSVC 2019 instead of Qt 6.5.1 MinGW you still get the same error?
-
@hskoglund Yes still gate same error
@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.
-
@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
