Update of MaintenanceTool on Windows behaviour

[koahnig]

I just updated my MaintenanceTool on Windows 10 64 bit. Now I have apparently 2 copies of the MaintenanceTool in the folder.

The folder shows after the update:

Obviously the MaintenanceTool.exe has still the old creation date. There is an apprent copy of the maintenanceTool with extensions exe.new and a date of today.

When I restart MaintenanceTool.exe I cannot update again. However, I cannot check which version it is, because there is no obvious extry for pulling the version info of the application.

Do I need both MaintenanceTool.exe and MaintenanceTool.exe.new ? Or can I remove either one (with renaming exe.new to exe)?

[hskoglund]

Hi, MaintenanceTool probably got stuck in the process of updating itself. Toss the old MaintenanceTool.exe, rename MaintenanceTool.exe.new to MaintenanceTool.exe and you should be good to go. (You might have to enter your account password again.)

[koahnig]

username and password were still fine, but I had to confirm the remaining stuff.

The strange thing was/is that the "old" MaintenanceTool did not bring up an update note.

Anyway thanks for response.

[koahnig]

Over the weekend I had the next update of MaintenanceTool required. Same story as before. Solved through renaming of .exe.new to .exe.

Now when starting Qt creator I have received this message:

This is related to same cause. IIRC I have not restarted Qt creator before.

[aha_1980]

@koahnig UpdateInfo ist not a super important plugin. You can just disable it in About > Plugins.

Regards

[koahnig]

@aha_1980

The actual error is in details window. Unfortunately the description is wrong. When I have checked lateron, there was no MaintenanceTool.exe. Wonder why this is gone by now.

Renamed back the last one and restarted. It found that Qt creator was not up-to-date, but apparently MaintenanceTool was?
Not really clear what happened.

[aha_1980]

Hi @koahnig,

can you please check if https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/32 is related to your problem?

Regards

[koahnig]

@aha_1980

Nope. It is an Intel i7-7700 CPU @3.60 GHz

I have run the small test of the post and there is no warning popping up. It seems to function properly.

[jazzco2]

Hi koahning,

I've had a similar problem. Maybe my bugreport helps:

https://bugreports.qt.io/browse/QTIFW-1003

After installing notepad++ and assigning ".vbs" extension to it, windows wasn't able to execute ".vbs" scripts anymore. Resetting the assignment in the regedit (HKEY_CLASSES_ROOT.vbs to "VBSFile") solves this issue.

Maybe this solves your issue, too.

Regards
Jazzco