@aha_1980
well its not an easy tool to use.

I'm currently fighting with it as well, my antivirus pushes it into quarantine because it may be a potential virus.

Only happens with my own created tools not the QtCreator one.

I'm still trying to figure that one out...

Glad you found out and thanks for sharing !

Can you also share which antivirus it is ? That might give clue for other people experiencing the same situation.

@Tsherr

Hello, I have the same issue, tell me please, did you found solution for this problem?

I stumbled upon this answer and added those links found in this this xml file:

http://download.qt-project.org/online/qtsdkrepository/linux_x64/desktop/tools_maintenance http://download.qt-project.org/online/qtsdkrepository/linux_x64/root/qt

Now I have repositories configured and everything is fine.

I remember having a problem similar but what I did to avoid losing time is to grab the online installer and get Qt 5.5 directly

Thanks SGaist, I built it on my end and seem to be working alright.

@vlada
well if u have a commercial licence that the right thing to do but if you are using open version then
skipping should be just fine :)

You can use "UNDOEXECUTE". For example: component.addOperation("Execute", "msiexec", "/i", "xxx.msi", "/quiet", "UNDOEXECUTE", "msiexec", "/x", "xxx.msi");

@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 :)

@sassanh said in Maintenance Tool reports corrupted installation:

@Asperamanca
How did you edit MaintenanceTool.dat file? It's a binary file containing xml data and some binary characters between tags. When I remove a single character in it running MaintenanceTool shows errors like this:
Cannot seek to -15118 to read the operation data.

I don't remember exactly. I changed only XML parts, and it worked for me. But that was before the major update to the Maintenance tool that came recently. Maybe they added a CRC check on the file, or something like this.

mcosta,

Yes, found it - not too blind but too stupid :)
thank you