While deploying qt in windows, the official docs recommend using windeployqt.exe

However, once the outputs of windeployqt.exe are packaged and executed in a different machine without any qt installments, I encountered “msising libgcc_s_seh-1.dll” error.


When I ran windeployqt.exe, I just ran it from powershell.

When I used the Qt 5.12.6(MinGW 7.3 64-bit) terminal, and executed windeployqt.exe the same way as I did before, the outputs were different, and this time it had copied “libgcc_s_seh-1.dll” to the output directory.

After packaging this output and running in a different machine, the executable ran okay without errors.

So the solution is to run windeployqt.exe from the QT’s mingw terminal that is installed in your computer.


Tapiwa · December 2, 2021 at 6:37 pm

What’s executable name of the Mingw terminal?

    chadrick_author · December 2, 2021 at 7:36 pm

    something like “C:\Users\chadrick\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Qt 5.12.6\5.12.6\MinGW 7.3.0 (64-bit)\Qt 5.12.6 (MinGW 7.3.0 64-bit).exe”

    you can easily search it by typing ‘mingw’ on Windows Desktop Search(the search bar on the left of the taskbar)

Anonymous · February 25, 2023 at 2:06 pm

Perfect. This helped me a lot! Thanks!

Leave a Reply

Your email address will not be published.