Qt 5.5.1 for Windows installation fails to "Qt patch error"

robopoulos

I have been trying to install Qt 5.5.1 without luck. The installation constantly stops in "Qt patch error: Can not open /.../Qt5.5.1/5.5/msvc2013_64/bin/qmake.exe" claiming qmake is in use by some another process, but there should be no other programs running.

I have uninstalled my antivirus program and also tried the installation as Administrator but those did not help. The same error arises with mingw version too and for both the online or downloaded installers.

Help appreciated.

Thanks
Apu

SGaist

Hi,

Any chance of an Anti-virus software running ?

robopoulos

@SGaist

No, I have uninstalled/removed the F-secure I'm using totally.

It always stops in the very same spot:

"Installing component msvc2013 64 bit"

if that would give a clue.

SGaist

What version of Windows are you on ?

robopoulos

Win 7.

I did have Qt 5.4 installed prior to this but removed it before starting to install the latest version. Everything was fine with 5.4. I'm currently trying the 5.6 version I get the same error with that too.

SGaist

Offline installer ?

robopoulos

@SGaist

Same result, no luck.

SGaist

Silly question, did you reboot after uninstalling F-secure ?

robopoulos

@SGaist

Yes I did.

The error message must be (?) leading to wrong direction as there is no qmake before the installer installs it itself and then tries to use it ??? Nothing occupies qmake except the installer itself and I can start and run qmake from the 5.5./msvc2010/bin folder....currently trying the 2010 32-bit version.

robopoulos

This seems to be a bug that appears now and then, even going back to Nokia times. Several bug reports have been issued but I can't find if a solution has been found. Some links:

http://comments.gmane.org/gmane.comp.lib.qt.user/13669

https://bugreports.qt.io/browse/QTBUG-33290

This is a picture of the error message, exactly the same:

https://picasaweb.google.com/101710567599383688262/UntitledAlbum?gsessionid=A7o4Pp2CyPdTdXwSSj5S3w#5632107000469000818

hskoglund

Hi just guessing but try installing Qt with Windows Defender disabled (just turning off the real-time protection will suffice).

robopoulos

Thanks, but no, that is not the cure.

I actually got 5.5.1 msvc2013 32 bit version installed now but the actual problem is still there so I am not going to mark this problem as solved.

This is some sort of a compatibility issue problem. If I run the installer with <right click menu/Troubleshoot compatibility> and claim that this installer worked with XP SP3 then the installation goes thru without errors. Afterwards the troubleshooter marks the installer as incompatible with Windows 7. Sounds like if some too old stuff has been used ocassionally when compiling the installers. (Edit: however, it installed OK in my Win 10 laptop)

I decided to upgrade from 5.4.1 because of the improved opengl stuff. I hope this version is one to keep for a long time. The constant updates are becoming extremely tiresome. Some sort of LTS versions like with Ubuntu would be a bright idea.

-Apu

PS. (During this successfull installation I also did not open the "show details" window. I'm not going to try if that had anything to do with the installation not succeeding, because that would be too crazy. :-)

SGaist

Qt 5.6 is LTS and got released today

robopoulos

@SGaist

Well that is a must then, so here we go again. :-)

Thanks
-Apu

robopoulos

Just a last note. The same happens with the LTS 5.6.0 installer and a (temporary) remedy is to run the installer under

In the compatibility shells options I lied that it had previously worked with Win XP Service Pack 3. After the installation the compatibility program will mark the installer as incompatible with Windows 7 but Qt 5.6.0 seems to work anyway at least at this point. And yes, I had all windows updates up to date if someone wonders that.

-Apu

SGaist

That's strange… I wonder if it's something related to your Win7 installation or Win7 in general. You should check the bug report system to see if you find someting related.

robopoulos

As I wrote earlier this is a know problem/bug already from the Nokia days and bug reports have been issued. Check the links above.

SGaist

My bad, I managed to missed that post. There's seems to indeed be something fishy going on...