Unsolved Issue starting brand new projects
-
You are the only one on Linux. So, possibly limited to Windows or even Win10.
I'd even say probable. I don't experience any strange behavior by changing the target to the problematic one.
This does not do the trick.
Well, my "shot in dark" approach has met its demise ... sadly I have nothing further to suggest. :|
-
it doesn't even like
e:\build-mysetup-Desktop_Qt_5_6_0_MinGW_32bit-Debug\debug\mysetup.exeI mean mysetup. ?!
occult name. i say..
Maybe others with win 10 can try.
-
Hi, I remember Windows can be very sensitive to .exe filenames containing the words "setup" or "update", see discussion here
-
@hskoglund
I was also my guess that it is a windows/AV scanner issue. However @mrjj could start the exe in the deploy folder. See further above. -
Hi
Just for test.
On windows 7, you can name it anything setup.
Still runs.So its a win 10 feature. :)
Tonight I will reset my UAC and see if it actually try to warn. -
Hi, just tested with an empty widgets app, named TestSetup :-)
Compile/building it with a Microsoft compiler, for example MSVC2013 or MSVC2015 (32-bit or 64-bit same result) will give you an .exe which you can start both from Qt Creator and from File Explorer, without anyone complaining, in any version of Windows.
However compile/build with a MinGW compiler, for example 4.9.2 32-bit, will give you an .exe file that will fail to start from Qt Creator and give you a UAC prompt when started from File Explorer in Windows 7, Windows 8 and Windows 10 (but not in Windows XP).
The reason is that the MinGW does not include a manifest XML file, the crucial part of the manifest is this part:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level='asInvoker' uiAccess='false' /> </requestedPrivileges> </security> </trustInfo>
(i.e. if I blank out that text in the .exe file which was compiled with a MSVC compiler, it will then also give you a UAC prompt.)
-
@hskoglund
Doesn't this mean you're bound to use the M$ compiler (if there isn't a way to generate and embed the manifest with MinGW)? If so, this'd be terrible ... -
But funny enough, it works on my win 7, Qt 5.5 and mingw :)
Here at work. -
@mrjj
Yep, windows is funny that way. ;)
You probably had disabled the "new security features" at some point in the past, and that's why it works. -
@kshegunov
Yes, I have obligated the UAC on win 7. ( User Annoying Component ;)Will try the same on win 10 if still possible.