Solved Problem during Installer Framework procedure - unable to start correctly (0xc000007b)

[Bruschetta]

Hello to everyone.
I'm trying to use the Qt Installer Framework , i have compiled the project as RELEASE, got the EXE, opened the console and called the "windeployqt.exe . " command inside the "QTProjects\build-Beta-Desktop_Qt_5_7_0_MinGW_32bit-Release\release" path for my "Beta" application.

All seems to be ok but when i try to launch the application get this error:

The application was unable to start correctly (0xc000007b). 
Click OK to close the application.

Now i think that the problem is caused by a mix of 32-64 bit architectures.
Let me say that:
I have Qt Creator 4.1.0
Based on Qt 5.7.0 (MSVC 2013, 32 bit)
And under the QT folder i have "C:\Qt\5.7\mingw53_32"
My SO is Windows 10 64bit

I have set the path to the DLL using qtenv2.bat that i found inside "C:\Qt\5.7\mingw53_32\bin"
The script that was inside that bat is :

echo off
echo Setting up environment for Qt usage...
set PATH=C:\Qt\5.7\mingw53_32\bin;C:/Qt/Tools/mingw492_32\bin;%PATH%
cd /D C:\Qt\5.7\mingw53_32

I have used dependncy Walker too and i foun that MANY DLLs where missing, here a screen of it

Can someone help me to understand what i'm doing wrong?Thanks a lot

[koahnig]

@Bruschetta

I see a couple of potential issues.

MSVC and MinGW cannot be mixed for sure. This might be an origin already, if the path are not separated well.

You have two different MinGW versions in your path.
set PATH=C:\Qt\5.7\mingw53_32\bin;C:/Qt/Tools/mingw492_32\bin;%PATH%
MinGW is typically less of an issue with mixed versions, but I am not sure with those particular versions.

The OS as windows 10 64 bit should not be the origin of the problem. I am using win10 64 bit with MinGW 32 bit as well. However, the dependency walker is not as reliable anymore as it was in the past. I see similar warnings when using the depencewalker on my apps, which are running. You need to go through the list and look for missing own, Qt and compiler dlls.

Try to run the exe with the command prompt.

[Bruschetta]

@koahnig

I have resolved the problem... The .bat file didn't set anything.
I have updated the path now and all is working fine ;)