MaintenanceTool.exe of my Qt installation is not starting!

SGaist

Hi,

Do you mean that the application doesn't start ?

amahta

@SGaist yes that is what I mean.

SGaist

Did you try running it from the command line ?

amahta

@SGaist yes and actually that was the reason I got so disappointed. No messages. Nothing.

SGaist

What version of Windows are you using ?

JKSH

Hi @amahta,

Three things to do:

Check Task Manager. Is MaintenanceTool in the list? If so, kill it.
Go to the folder which contains MaintenanceTool.exe. Is there a lock file there? (lockmyApp1234865.lock) If so delete it.
Go to the folder which contains MaintenanceTool.exe. Open InstallationLog.txt -- can you find any hints inside?

Also, what version of Qt do you currently have?

Previously there was some kind of a network error but not npthing shows up

What did the message say?

amahta

@SGaist I am using Windows 8.1 64 bit

amahta

@JKSH about the three tips, I checked and here are the answers, 1. no, 2. no, 3. nothing but can you be more specific? what should be in the log?
I am using Qt version 5.4

amahta

and by the way I have already tried lots of possible things (except debugging the exe) but to no avail. I have already installed 5.5 on another machine by wiping out Qt folder and installing everything from scratch, but on this one which I can't update from 5.4 I am going to keep it the way it is for a few more days in case a solution is found. It maybe useful for others anyway.

JKSH

@amahta said:

@JKSH about the three tips, I checked and here are the answers, 1. no, 2. no, 3. nothing but can you be more specific? what should be in the log?

I'm out of ideas then, sorry.

I don't know what should be in the log, but it might have captured some error messages.

amahta

@JKSH I tried a few things and it seems it's an access violation error. Normally it should crash but I think it is an unhandled try-catch block. Probably I am going to do the same on this machine too that is, Delete Qt folder manually and install 5.5, and hope that this issue is fixed in the new version :)