Ошибка the application failed to run

Нажмите

Compatible with Microsoft Windows
Compatible with OS X

Still having problems?
If you failed to fix your error using Reimage, reach our support team for help. Please, let us know all details that you think we should know about your problem.

Edit:
Some people started to mark my question as a duplicate. Do not forget that many similar questions existed when I asked this one (see e.g. the list below). However, none of these answers solved my problem. After a long search I found a comment which had been ignored by all users pointing to the missing lib. Now, many months later, the comment has been changed to an answer. However, when I answered this question by msyself I intended to help other people by directly providing the solution. This should not be forgotten and so far my answer helped a lot of people. Therefore my question is definitely not a duplicate. By the way: The accepted answer within the provided link on top does not solve the problem!

Yes, i used the search:

Failed to load platform plugin «windows». Available platforms are : Error

Deploying Qt C++ Application from Visual Studio qwindows.dll error

failed to load platform plugin «windows» Available platforms are: windows, minimal

However, in my case the problem still persists. I am using Qt 5.1.1 with Visual Studio 2012 and developed my Application on Windows 7 with Qt Creator 2.8.1. Application is compiled in «Release»-mode and can be executed if directly started with Qt Creator.

However, when starting from the «release»-Folder, i get the following message:

This application failed to start because it could not find or load the
Qt platform plugin «windows». Available platform plugins are:
minimal, offscreen, windows.

Folder structure looks like this:

release
+ gui.exe
+ icudt51.dll
+ icuin51.dll
+ icuuc51.dll
+ libGLESv2.dll
+ Qt5Core.dll
+ Qt5Gui.dll
+ Qt5Widgets.dll
+ platforms

Platforms is the folder directly copied from QtQt5.1.15.1.1msvc2012pluginsplatforms including e.g. qwindows.dll. Does not matter if I rename it to «platform» as some other users did. Qt is still not finding the «platform plugin windows», where is my mistake?

For anyone coming from QT version 5.14.0, it took me 2 days to find this piece statment of bug:

windeployqt does not work for MinGW QTBUG-80763 Will be fixed in
5.14.1

https://wiki.qt.io/Qt_5.14.0_Known_Issues

So be aware. Using windeployqt withMinGW will give the same error stated here.

answered Jan 17, 2020 at 3:41

I had this problem while using QT 5.6, Anaconda 4.3.23, python 3.5.2 and pyinstaller 3.3.
I had created a python program with an interface developed using QTcreator, but had to deploy it to other computers, therefore I needed to make an executable, using pyinstaller.

I’ve found that the problem was solved on my computer if I set the following environment variables:

QT_QPA_PLATFORM_PLUGIN_PATH: %QTDIR%pluginsplatforms

QTDIR: C:Miniconda3pkgsqt-5.6.2-vc14_3Library

But this solution only worked on my PC that had conda and qt installed in those folders.

To solve this and make the executable work on any computer, I’ve had to edit the «.spec» (file first generated by pyinstaller) to include the following line:

datas=[(
‘C:Miniconda3pkgsqt-5.6.2-vc14_3Librarypluginsplatforms*.dll’,
‘platforms’ ),]

This solution is based on the answers of Jim G. and CrippledTable

answered Oct 3, 2017 at 12:34

answered Apr 29, 2019 at 13:23

Most of these answers contain good (correct) info, but in my case, there was still something missing.

My app is built as a library (dll) and called by a non-Qt application. I used windeployqt.exe to set up the Qt dlls, platforms, plugins, etc. in the install directory, but it still couldn’t find the platform. After some experimentation, I realized the application’s working directory was set to a different folder. So, I grabbed the directory in which the dll «lived» using GetModuleHandleExA and added that directory to the Qt library path at runtime using

QCoreApplication::addLibraryPath(<result of GetModuleHandleExA>);

This worked for me.

answered May 9, 2018 at 13:14

answered Oct 11, 2017 at 9:40

Use this batch file: RunWithQt.bat

@echo off
set QTDIR=C:QtQt5.1.15.1.1msvc2012bin
set QT_QPA_PLATFORM_PLUGIN_PATH=%QTDIR%pluginsplatforms
start %1

• to use it, drag your gui.exe file and drop it on the RunWithQt.bat in explorer,
• or call RunWithQt gui.exe from the command line

answered Feb 8, 2018 at 15:54

answered Mar 27, 2018 at 19:39

The application qtbase/bin/windeployqt.exe deploys automatically your application. If you start a prompt with envirenmentvariables set correctly, it deploys to the current directory.
You find an example of script:

@echo off
set QTDIR=E:QT5110vc2017

set INCLUDE=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFCinclude;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726include;C:Program Files (x86)Windows KitsNETFXSDK4.6.1includeum;C:Program Files (x86)Windows Kits10include10.0.14393.0ucrt;C:Program Files (x86)Windows Kits10include10.0.14393.0shared;C:Program Files (x86)Windows Kits10include10.0.14393.0um;C:Program Files (x86)Windows Kits10include10.0.14393.0winrt;C:Program Files (x86)Windows Kits10include10.0.14393.0cppwinrt

set LIB=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;C:Program Files (x86)Windows KitsNETFXSDK4.6.1libumx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0ucrtx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0umx86;

set LIBPATH=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86storereferences;C:Program Files (x86)Windows Kits10UnionMetadata10.0.17134.0;C:ProgramFiles (x86)Windows Kits10References10.0.17134.0;C:WindowsMicrosoft.NETFrameworkv4.0.30319;

Path=%QTDIR%qtbasebin;%PATH%
set VCIDEInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEVC
set VCINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVC
set VCToolsInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.11.25503
set VisualStudioVersion=15.0
set VS100COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 10.0Common7Tools
set VS110COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 11.0Common7Tools
set VS120COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools
set VS150COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7Tools
set VS80COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 8Common7Tools
set VS90COMNTOOLS=c:Program Files (x86)Microsoft Visual Studio 9.0Common7Tools
set VSINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017Enterprise
set VSSDK110Install=C:Program Files (x86)Microsoft Visual Studio 11.0VSSDK
set VSSDK150INSTALL=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVSSDK
set WindowsLibPath=C:Program Files (x86)Windows Kits10UnionMetadata;C:Program Files (x86)Windows Kits10References
set WindowsSdkBinPath=C:Program Files (x86)Windows Kits10bin
set WindowsSdkDir=C:Program Files (x86)Windows Kits10
set WindowsSDKLibVersion=10.0.14393.0
set WindowsSdkVerBinPath=C:Program Files (x86)Windows Kits10bin10.0.14393.0
set WindowsSDKVersion=10.0.14393.0
set WindowsSDK_ExecutablePath_x64=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Toolsx64
set WindowsSDK_ExecutablePath_x86=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Tools

mkdir C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
cd C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
copy /Y ..Releaseapplication.exe .
windeployqt application.exe
pause

answered Nov 23, 2018 at 9:03

Lets say, you wanted to have some CGAL-Demos portable. So you’d have a folder «CGAL», and in it, 1 subfolder called «lib»: all (common) support-dlls for any programs in the CGAL-folder go here. In our example, this would be the Dll-Download: simply unzip into the «lib» directory. The further you scroll down on the demos-page, the more impressive the content. In my case, the polyhedron-demo seemed about right. If this runs on my 10+ yo notebook, I’m impressed. So I created a folder «demo» in the «CGAL»-directory, alongside «lib».
Now create a .cmd-file in that folder. I named mine «Polyhedron.cmd». So we have a directory structure like this:

 CGAL - the bag for all the goodies
  lib - all libraries for all CGAL-packages
 demo - all the demos I'm interested in
[...] - certainly some other collections, several apps per folder...
Polyhedron.cmd - and a little script for every Qt-exe to make it truly portable.

In this little example, «Polyhedron.cmd» contains the following text:

@echo off
set "me=%~dp0"
set PATH=%me%lib
set "QT_PLUGIN_PATH=%me%libplugins"
start /b "CGAL Polyhedron Demo" "%me%demopolyhedronpolyhedron_3.exe"

All scripts can be the same apart from the last line, obviously. The only caveat is: the «DOS-Window» stays open for as long as you use the actual program. Close the shell-window, and you kill the *.exe as well. Whereever you copy the «CGAL»-folder, as the weird «%~dp0»-wriggle represents the full path to the *.cmd-file that we started, with trailing «». So «%me%lib» is always the full path to the actual library («CGALlib» in my case). The next 2 lines tell Qt where its «runtime» files are. This will be at least the file «qwindows.dll» for Windows-Qt programs plus any number of *.dlls. If I remember rightly, the Dll-library (at least when I downloaded it) had a little «bug» since it contains the «platforms»-directory with qwindows.dll in it. So when you open the lib directory, you need to create a folder «plugins» next to «platforms», and then move into «plugins». If a Qt-app, any Qt-app, doesn’t find «qwindows.dll», it cannot find «windows». And it expects it in a directory named «platforms» in the «plugins» directory, which it has to get told by the OS its running on…and if the «QT_PLUGIN_PATH» is not exactly pointing to all the helper-dlls you need, some Qt-programs will still run with no probs. And some complain about missing *.dlls you’ve never heard off…

answered Jan 20, 2019 at 4:09

I ran into the same error and solved it with a different method than those mentioned in other posts. Hopefully this will help future readers.

BUILD:

Windows 10 (64bit)
Minicoda (using python 3.9.4) (pkgs are from conda-forge channel)
pyqt 5.12.3

My scenario:

I was building a GUI application for some embedded work. I had two machines that were used for development (same OS and architecture), one had zero internet connection. After packaging up my environment and installing on the offline machine, I ran into the error that you got.

Solution:

locate the qt.conf file in your conda environment.
for me: C:Users»name»miniconda3envs»env_name»qt.conf

Make sure the paths are correct. I needed to update the «name» as this was left over from the old machine.

Hopefully this helps someone.

answered Jun 3, 2021 at 20:34

I had the same problem of running a QT5 application in windows 10 ( VS2019).
My error was

..DebugQt5Cored.dll
Module: 5.14.1
File: kernelqguiapplication.cpp
Line: 1249

This application failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.

Solution

Since I was using QT msvc2017, I copied plugins folders from «C:QtQt5.14.15.14.1msvc2017plugins» location to the binary location

it worked.

Then check visual studio output window and identify the dlls loaded from plugin folder and removed unwanted dlls

answered Dec 17, 2020 at 22:54

answered Jan 7, 2021 at 5:57

answered Sep 9, 2021 at 2:50

Talking mainly about the Windows platform

Faced the same issue when trying to debug the app build using the vcpkg installed Qt library, while having my app build using cmake. Had trouble for some hours until found the solution. The simplest way is to do the following:

• in your build folder, find the folder where the final executable is located.

• in that folder, you’ll find some Qt libraries, like Qt6Core.dll.

• pay attention to whether or not the library file has the d suffix in its name, i.e. Qt6Cored.dll instead of Qt6Core.dll

• in the vcpkg folder, you have 2 options

  1. ./installed/x64-windows/Qt6/plugins/platforms
  2. ./installed/x64-windows/debug/Qt6/plugins/platforms

• if the d suffix was present, copy the content of the ../debug/.. folder (otherwise the other one) into the platforms folder in the same folder, where your executable and the Qt libraries are located (if there’s no such folder, create on your own).

You can somehow automate this process. Leaving that task to you. If I do that on my own, will update the answer.

Edit

If you are using CMakeLists you may want to give this a try. Add the following to your app’s CMakeLists.txt

# assuming your target's name is app

if(WIN32)
    add_custom_command(
        TARGET app POST_BUILD
        COMMAND ${CMAKE_COMMAND} -E copy_directory
            ${Qt6_DIR}/../../$<$<CONFIG:Debug>:debug/>Qt6/plugins/platforms/
            $<TARGET_FILE_DIR:app>/platforms/
    )
endif()

answered Mar 18, 2022 at 11:52

Edit:
Some people started to mark my question as a duplicate. Do not forget that many similar questions existed when I asked this one (see e.g. the list below). However, none of these answers solved my problem. After a long search I found a comment which had been ignored by all users pointing to the missing lib. Now, many months later, the comment has been changed to an answer. However, when I answered this question by msyself I intended to help other people by directly providing the solution. This should not be forgotten and so far my answer helped a lot of people. Therefore my question is definitely not a duplicate. By the way: The accepted answer within the provided link on top does not solve the problem!

Yes, i used the search:

Failed to load platform plugin «windows». Available platforms are : Error

Deploying Qt C++ Application from Visual Studio qwindows.dll error

failed to load platform plugin «windows» Available platforms are: windows, minimal

However, in my case the problem still persists. I am using Qt 5.1.1 with Visual Studio 2012 and developed my Application on Windows 7 with Qt Creator 2.8.1. Application is compiled in «Release»-mode and can be executed if directly started with Qt Creator.

However, when starting from the «release»-Folder, i get the following message:

This application failed to start because it could not find or load the
Qt platform plugin «windows». Available platform plugins are:
minimal, offscreen, windows.

Folder structure looks like this:

release
+ gui.exe
+ icudt51.dll
+ icuin51.dll
+ icuuc51.dll
+ libGLESv2.dll
+ Qt5Core.dll
+ Qt5Gui.dll
+ Qt5Widgets.dll
+ platforms

Platforms is the folder directly copied from QtQt5.1.15.1.1msvc2012pluginsplatforms including e.g. qwindows.dll. Does not matter if I rename it to «platform» as some other users did. Qt is still not finding the «platform plugin windows», where is my mistake?

For anyone coming from QT version 5.14.0, it took me 2 days to find this piece statment of bug:

windeployqt does not work for MinGW QTBUG-80763 Will be fixed in
5.14.1

https://wiki.qt.io/Qt_5.14.0_Known_Issues

So be aware. Using windeployqt withMinGW will give the same error stated here.

answered Jan 17, 2020 at 3:41

I had this problem while using QT 5.6, Anaconda 4.3.23, python 3.5.2 and pyinstaller 3.3.
I had created a python program with an interface developed using QTcreator, but had to deploy it to other computers, therefore I needed to make an executable, using pyinstaller.

I’ve found that the problem was solved on my computer if I set the following environment variables:

QT_QPA_PLATFORM_PLUGIN_PATH: %QTDIR%pluginsplatforms

QTDIR: C:Miniconda3pkgsqt-5.6.2-vc14_3Library

But this solution only worked on my PC that had conda and qt installed in those folders.

To solve this and make the executable work on any computer, I’ve had to edit the «.spec» (file first generated by pyinstaller) to include the following line:

datas=[(
‘C:Miniconda3pkgsqt-5.6.2-vc14_3Librarypluginsplatforms*.dll’,
‘platforms’ ),]

This solution is based on the answers of Jim G. and CrippledTable

answered Oct 3, 2017 at 12:34

answered Apr 29, 2019 at 13:23

Most of these answers contain good (correct) info, but in my case, there was still something missing.

My app is built as a library (dll) and called by a non-Qt application. I used windeployqt.exe to set up the Qt dlls, platforms, plugins, etc. in the install directory, but it still couldn’t find the platform. After some experimentation, I realized the application’s working directory was set to a different folder. So, I grabbed the directory in which the dll «lived» using GetModuleHandleExA and added that directory to the Qt library path at runtime using

QCoreApplication::addLibraryPath(<result of GetModuleHandleExA>);

This worked for me.

answered May 9, 2018 at 13:14

answered Oct 11, 2017 at 9:40

Use this batch file: RunWithQt.bat

@echo off
set QTDIR=C:QtQt5.1.15.1.1msvc2012bin
set QT_QPA_PLATFORM_PLUGIN_PATH=%QTDIR%pluginsplatforms
start %1

• to use it, drag your gui.exe file and drop it on the RunWithQt.bat in explorer,
• or call RunWithQt gui.exe from the command line

answered Feb 8, 2018 at 15:54

answered Mar 27, 2018 at 19:39

The application qtbase/bin/windeployqt.exe deploys automatically your application. If you start a prompt with envirenmentvariables set correctly, it deploys to the current directory.
You find an example of script:

@echo off
set QTDIR=E:QT5110vc2017

set INCLUDE=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFCinclude;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726include;C:Program Files (x86)Windows KitsNETFXSDK4.6.1includeum;C:Program Files (x86)Windows Kits10include10.0.14393.0ucrt;C:Program Files (x86)Windows Kits10include10.0.14393.0shared;C:Program Files (x86)Windows Kits10include10.0.14393.0um;C:Program Files (x86)Windows Kits10include10.0.14393.0winrt;C:Program Files (x86)Windows Kits10include10.0.14393.0cppwinrt

set LIB=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;C:Program Files (x86)Windows KitsNETFXSDK4.6.1libumx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0ucrtx86;C:Program Files (x86)Windows Kits10lib10.0.14393.0umx86;

set LIBPATH=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726ATLMFClibx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86;S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.15.26726libx86storereferences;C:Program Files (x86)Windows Kits10UnionMetadata10.0.17134.0;C:ProgramFiles (x86)Windows Kits10References10.0.17134.0;C:WindowsMicrosoft.NETFrameworkv4.0.30319;

Path=%QTDIR%qtbasebin;%PATH%
set VCIDEInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEVC
set VCINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVC
set VCToolsInstallDir=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVCToolsMSVC14.11.25503
set VisualStudioVersion=15.0
set VS100COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 10.0Common7Tools
set VS110COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 11.0Common7Tools
set VS120COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio 12.0Common7Tools
set VS150COMNTOOLS=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7Tools
set VS80COMNTOOLS=C:Program Files (x86)Microsoft Visual Studio 8Common7Tools
set VS90COMNTOOLS=c:Program Files (x86)Microsoft Visual Studio 9.0Common7Tools
set VSINSTALLDIR=S:Program Files (x86)Microsoft Visual Studio2017Enterprise
set VSSDK110Install=C:Program Files (x86)Microsoft Visual Studio 11.0VSSDK
set VSSDK150INSTALL=S:Program Files (x86)Microsoft Visual Studio2017EnterpriseVSSDK
set WindowsLibPath=C:Program Files (x86)Windows Kits10UnionMetadata;C:Program Files (x86)Windows Kits10References
set WindowsSdkBinPath=C:Program Files (x86)Windows Kits10bin
set WindowsSdkDir=C:Program Files (x86)Windows Kits10
set WindowsSDKLibVersion=10.0.14393.0
set WindowsSdkVerBinPath=C:Program Files (x86)Windows Kits10bin10.0.14393.0
set WindowsSDKVersion=10.0.14393.0
set WindowsSDK_ExecutablePath_x64=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Toolsx64
set WindowsSDK_ExecutablePath_x86=C:Program Files (x86)Microsoft SDKsWindowsv10.0AbinNETFX 4.6.1 Tools

mkdir C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
cd C:VCProjectsApplicationBuildVS2017_QT5_11_32-Releasesetup
copy /Y ..Releaseapplication.exe .
windeployqt application.exe
pause

answered Nov 23, 2018 at 9:03

Lets say, you wanted to have some CGAL-Demos portable. So you’d have a folder «CGAL», and in it, 1 subfolder called «lib»: all (common) support-dlls for any programs in the CGAL-folder go here. In our example, this would be the Dll-Download: simply unzip into the «lib» directory. The further you scroll down on the demos-page, the more impressive the content. In my case, the polyhedron-demo seemed about right. If this runs on my 10+ yo notebook, I’m impressed. So I created a folder «demo» in the «CGAL»-directory, alongside «lib».
Now create a .cmd-file in that folder. I named mine «Polyhedron.cmd». So we have a directory structure like this:

 CGAL - the bag for all the goodies
  lib - all libraries for all CGAL-packages
 demo - all the demos I'm interested in
[...] - certainly some other collections, several apps per folder...
Polyhedron.cmd - and a little script for every Qt-exe to make it truly portable.

In this little example, «Polyhedron.cmd» contains the following text:

@echo off
set "me=%~dp0"
set PATH=%me%lib
set "QT_PLUGIN_PATH=%me%libplugins"
start /b "CGAL Polyhedron Demo" "%me%demopolyhedronpolyhedron_3.exe"

All scripts can be the same apart from the last line, obviously. The only caveat is: the «DOS-Window» stays open for as long as you use the actual program. Close the shell-window, and you kill the *.exe as well. Whereever you copy the «CGAL»-folder, as the weird «%~dp0»-wriggle represents the full path to the *.cmd-file that we started, with trailing «». So «%me%lib» is always the full path to the actual library («CGALlib» in my case). The next 2 lines tell Qt where its «runtime» files are. This will be at least the file «qwindows.dll» for Windows-Qt programs plus any number of *.dlls. If I remember rightly, the Dll-library (at least when I downloaded it) had a little «bug» since it contains the «platforms»-directory with qwindows.dll in it. So when you open the lib directory, you need to create a folder «plugins» next to «platforms», and then move into «plugins». If a Qt-app, any Qt-app, doesn’t find «qwindows.dll», it cannot find «windows». And it expects it in a directory named «platforms» in the «plugins» directory, which it has to get told by the OS its running on…and if the «QT_PLUGIN_PATH» is not exactly pointing to all the helper-dlls you need, some Qt-programs will still run with no probs. And some complain about missing *.dlls you’ve never heard off…

answered Jan 20, 2019 at 4:09

I ran into the same error and solved it with a different method than those mentioned in other posts. Hopefully this will help future readers.

BUILD:

Windows 10 (64bit)
Minicoda (using python 3.9.4) (pkgs are from conda-forge channel)
pyqt 5.12.3

My scenario:

I was building a GUI application for some embedded work. I had two machines that were used for development (same OS and architecture), one had zero internet connection. After packaging up my environment and installing on the offline machine, I ran into the error that you got.

Solution:

locate the qt.conf file in your conda environment.
for me: C:Users»name»miniconda3envs»env_name»qt.conf

Make sure the paths are correct. I needed to update the «name» as this was left over from the old machine.

Hopefully this helps someone.

answered Jun 3, 2021 at 20:34

I had the same problem of running a QT5 application in windows 10 ( VS2019).
My error was

..DebugQt5Cored.dll
Module: 5.14.1
File: kernelqguiapplication.cpp
Line: 1249

This application failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.

Solution

Since I was using QT msvc2017, I copied plugins folders from «C:QtQt5.14.15.14.1msvc2017plugins» location to the binary location

it worked.

Then check visual studio output window and identify the dlls loaded from plugin folder and removed unwanted dlls

answered Dec 17, 2020 at 22:54

answered Jan 7, 2021 at 5:57

answered Sep 9, 2021 at 2:50

Talking mainly about the Windows platform

Faced the same issue when trying to debug the app build using the vcpkg installed Qt library, while having my app build using cmake. Had trouble for some hours until found the solution. The simplest way is to do the following:

• in your build folder, find the folder where the final executable is located.

• in that folder, you’ll find some Qt libraries, like Qt6Core.dll.

• pay attention to whether or not the library file has the d suffix in its name, i.e. Qt6Cored.dll instead of Qt6Core.dll

• in the vcpkg folder, you have 2 options

  1. ./installed/x64-windows/Qt6/plugins/platforms
  2. ./installed/x64-windows/debug/Qt6/plugins/platforms

• if the d suffix was present, copy the content of the ../debug/.. folder (otherwise the other one) into the platforms folder in the same folder, where your executable and the Qt libraries are located (if there’s no such folder, create on your own).

You can somehow automate this process. Leaving that task to you. If I do that on my own, will update the answer.

Edit

If you are using CMakeLists you may want to give this a try. Add the following to your app’s CMakeLists.txt

# assuming your target's name is app

if(WIN32)
    add_custom_command(
        TARGET app POST_BUILD
        COMMAND ${CMAKE_COMMAND} -E copy_directory
            ${Qt6_DIR}/../../$<$<CONFIG:Debug>:debug/>Qt6/plugins/platforms/
            $<TARGET_FILE_DIR:app>/platforms/
    )
endif()

answered Mar 18, 2022 at 11:52