Author Topic: Error reading images with v10.67 on Windows  (Read 995 times)


  • Newbie
  • *
  • Posts: 2
Error reading images with v10.67 on Windows
« on: December 01, 2017, 12:31:48 AM »
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]
$ ./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]
$ ./exiftool-10.67.exe -Make -j Apple/Apple_iPhone7.jpg
Error while attempting to call Image::ExifTool::VerboseDir
Image/ExifTool/ did not return a true value at Image/ 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

  • ExifTool Author
  • Administrator
  • ExifTool Freak
  • *****
  • Posts: 14425
    • ExifTool Home Page
Re: Error reading images with v10.67 on Windows
« Reply #1 on: December 01, 2017, 07:11:43 AM »
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
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).


  • Newbie
  • *
  • Posts: 2
Re: Error reading images with v10.67 on Windows
« Reply #2 on: December 01, 2017, 01:16:33 PM »
Thanks for your help--after following step ii in the Uninstalling section of the error was resolved.