Version 2025.5.2 installation

Started by rlgroff, September 24, 2025, 07:31:14 AM

Previous topic - Next topic

rlgroff

I just installed the 2025.5.2 update.  Unlike previous update installations, it never provided a link to install a new version of ExifTool, and it did not require updating my databases.  After installation, Help/About reports IMatch 2025.5.2 and ExifTool version 13.33. Is this the expected behavior for the 2025.5.2 installation, or is there something wrong with my new installation?

Mario

IMatch ships with ExifTool. It does not provide a link to install new version, it would be unwise to use a version I have not tested. According to the https://www.photools.com/release-notes/ for 2025.2, it ships with ExifTool 13.33, released in July.

Every time a new ExifTool is shipped with IMatch, the database will import the new ExifTool tag data and update. So does the 2025.2. This is a required step, because new ExifTool versions may bring in new tags or tag groups.

I don't know if ExifTool now has a build-in auto update. I've never heard about that.
Maybe you have multiple ExifTool versions installed (IMatch will only ever use the version it ships with, for security reasons) and this was somehow triggered?

When did you see the message?
What did it say? Did you make a screen shot?



rlgroff

I was pleased to verify that, in my installation, the ExifTool listed in Help/About is version 13.33, which is what you expected to accompany Imatch 2025.5.2.

I have come to realize that I probably confused the Imatch installation process with the installation of another photo software product I use that requires a separate action to install a third-party tool it needs.

Regarding conversion of my 3 databases, I was expecting them all to converted in a single process after installation, but I realize now that this occurs separately for each database when it is first opened after the new Imatch installation.

Therefore, I am concluding that there is nothing wrong with my installation (it appears to be functioning perfectly).  I think it is appropriate to close this issue now.   Thank you for your help.