Installer Can’t Download ExifTool? Pair It Manually

The V6 installer for ExifToolGui — Frank Bijnen’s maintained continuation of Bogdan Hrastnik’s Windows front-end for ExifTool — offers to fetch ExifTool for you during setup. When that fetch fails, you are left with a GUI and no engine: the program is installed, but the separate program it drives is missing. The good news is that nothing about the installer route is magic. The manual pairing is the same pairing the installer performs, done by hand, and it always remains available. This page explains what the installer was trying to do, then walks the manual steps. Files for both programs are linked from our download page; more fixes live in the Troubleshooting hub.

What the installer download step actually does

ExifTool is a separate, required program — Phil Harvey’s command-line tool and Perl library, which has no GUI of its own. At install time, the V6 installer gives you a choice of how to obtain it: the ExifTool zip by Phil Harvey, which the installer downloads and renames into the install folder, or the self-installing package by Oliver Betz. One detail worth knowing: the updated installer asset, versioned 6.3.12.1, was released specifically so that the ExifTool package is downloaded from SourceForge during install if selected — and the release notes state explicitly that this installer update brought no functional changes to the GUI itself. So if your installer’s download step failed, the failure is in fetching a file, not in your PC’s compatibility with the program. Fetch the file yourself and the result is identical.

The manual pairing, step by step

  • 1. Finish or close the installer. The GUI side can stay exactly as installed; you are only adding the missing engine.
  • 2. Download the ExifTool Windows zip yourself from the download page. The current version is 13.59 (the 64-bit zip measures 11,183,675 bytes). Which version to choose — and why the production release is a different number — is explained in Which ExifTool Version Should You Pair.
  • 3. Extract the whole zip before moving anything. Inside you will find the executable under its shipped name, exiftool(-k).exe, plus a folder named exiftool_files.
  • 4. Rename exiftool(-k).exe to exiftool.exe (or to plain exiftool, if your Windows hides extensions). This rename is the step the installer normally does for you, and it is mandatory: the (-k) name is for drag-and-drop use, the GUI drives the renamed file.
  • 5. Move the exe and the exiftool_files folder together to where the GUI expects its engine — ExifTool’s own documentation is explicit that if you move the exe, the exiftool_files folder must move with it.
  • 6. Start ExifToolGui and test: select a photo and confirm its metadata loads in the panels. Reading works means the pairing works, and saving an edit then works on the same foundation.

If the test in step 6 fails, do not reinstall at random — diagnose with the ExifTool not-found guide, which checks the name and the folder pairing in isolation. In practice, manual pairing fails for the same two reasons installer pairing would: the rename was skipped during the hurry to finish setup, or the exiftool_files folder was left behind in the extraction folder when the executable was moved on its own. Both take under a minute to put right once identified.

Verifying the file you fetched

Because the point of this page is fetching a file the installer could not, it is worth thirty seconds of verification. The exiftool-13.59_64.zip downloaded for this site’s research measured 11,183,675 bytes, and its SHA-256 — 44b512b25af500724ba579d0a53c8fc5851628b692dd5e5d94ae4a15c2cba9ec — matches the value in Phil Harvey’s published checksum file for 13.59 exactly. The publisher provides checksums for each release (checksums-13.59.txt for this one), so you can compare the file you downloaded against the publisher’s own record rather than trusting any intermediary, this site included. A file whose size is short of the measure above was truncated in transit — download it again in full before pairing.

The other installer option, for next time

If the Harvey zip route fails repeatedly on your connection, the installer’s alternative exists for a reason: the self-installing ExifTool package by Oliver Betz. The Windows builds of ExifTool are based on Oliver Betz’s launcher work, and he provides self-installing versions of the executables — choosing that option at install time changes who packages the engine, not which engine you get. Whichever route supplies it, the end state the GUI cares about is the same: a correctly named exiftool.exe with its exiftool_files folder beside it. The distribution question on the GUI side — whether you should be using the installer at all — is covered in Portable vs Installer.

Frequently asked questions

The installer failed at the download step. Is my installation broken?

No. The GUI is installed; only the optional fetch of a separate program failed. Pair ExifTool manually with the steps above and the installation is complete — the end state is the same one a successful installer fetch would have produced.

Can I just copy an exiftool.exe from another PC?

You can move the engine, with one condition from ExifTool’s own documentation: the exiftool_files folder must move with the exe. Copy both together, keep the name exiftool.exe, and the pairing survives the move.

Why does the installer mention SourceForge?

Because that is where the files are served from: the download links on exiftool.org currently redirect to SourceForge to reduce load on the project’s own server, and the 6.3.12.1 installer update fetches the ExifTool package from SourceForge during install when that option is selected.

Similar Posts