Error reading images with v10.67 on Windows

[mceachen]

I love ExifTool--I've been using it for over a decade on personal and open source projects now (and wrote popular ruby and node wrapper libraries). The fact that this is the first post I've made is a testament to how stable this codebase has been, and how thorough your documentation is. Thank you!

It looks like something went afoul in the latest Windows build. The perl version of 10.67 works fine on linux and mac (and thanks for the stay_open bugfix!). Version 10.66 works fine against Windows 10 Home v10.0.16299:

Code Select Expand

$ ./exiftool-10.66.exe -Make -j Apple/Apple_iPhone7.jpg
[{
  "SourceFile": "Apple/Apple_iPhone7.jpg",
  "Make": "Apple"
}]


but 10.67 fails with the following error:

Code Select Expand

$ ./exiftool-10.67.exe -Make -j Apple/Apple_iPhone7.jpg
Error while attempting to call Image::ExifTool::VerboseDir
Image/ExifTool/Writer.pl did not return a true value at Image/ExifTool.pm line 4138, <EXIFTOOL_FILE> chunk 2.


Please don't hesitate to email me if there's any more debug information I can provide.

(The example image is from your Apple.tar.gz samples archive, attached here for convenience).

Thanks again for ExifTool!

[Phil Harvey]

This looks like a bad install.  I've seen this on occasion in Windows (don't know why).  Follow the uninstall instructions here, then try again (Note "b" just above the Uninstalling section describes this problem).

- Phil

[mceachen]

Thanks for your help--after following step ii in the Uninstalling section of https://exiftool.org/install.html#Windows the error was resolved.

Thanks!

[RSI]

Just for Information (as this is a top google result):

This also helped to get the exiftool within the RunAnyCommand LR Plugin working again.
Exiftool stopped working after I had a system crash (blue screen) while a Lightroom Export and the exiftool was running. By calling it from the command line I got the error message: Image/ExifTool/XMP2.pl did not return a true value at Image/ExifTool.pm line 7158.

I also "reinstalled" it and it's working again.