ExifToolGui Troubleshooting

Fixes for the failures ExifToolGui users actually meet — each one sourced from the program’s own documentation, release notes or documented behaviour, not invented error lore.

Begin with the pairing

Before diagnosing anything exotic, confirm the foundation: exiftool.exe correctly named, its folder beside it, and a photo whose metadata loads.

Most ExifToolGui problems are not really about the GUI. The program is a front-end: Frank Bijnen’s V6 continuation of Bogdan Hrastnik’s Windows interface for Phil Harvey’s ExifTool. Underneath every read and every write sits the separate ExifTool program — which is why the single most common failure, the one this hub leads with, is the pairing between the two. If ExifToolGui says ExifTool was not found, the GUI is almost certainly fine and its engine is missing, misnamed or separated from its exiftool_files folder. Fix that first; a surprising share of other symptoms disappear with it.

The guides below follow a deliberate discipline: they only cover problems that the program’s documentation, its GitHub release notes, or plain operating-system behaviour can support. You will not find invented error codes, registry rituals, or ‘reinstall everything’ advice here. Where a cause is a general fact about Windows or storage media — a read-only attribute, a locked file, a card with its lock slider on — the guide says so plainly, because that is genuinely why the write failed, and any other program would have failed the same way.

Use this hub like a workshop, not a lottery. Change one thing at a time, and test on a copy of one ordinary photo before touching a folder of real ones. Confirm first that reading works — a selected photo’s metadata appearing in the panels proves the engine, the pairing and the file in one glance. Only then test a small write, such as one keyword, and re-read the file to see it land. That sequence separates a program problem from a file problem in about a minute, and it is the same isolation routine the individual guides keep returning to. If reading itself fails, stop and fix the pairing first; no setting inside the GUI can compensate for an engine it cannot find, and piling changes on a broken foundation only makes the eventual diagnosis harder.

All troubleshooting guides

Worked in order of likelihood: pairing first, then files and locations, then the map’s own extra requirements.

Still stuck?

Setting up fresh instead? The download page links the current V6.3.12 files and the ExifTool companion download, with measured file sizes you can compare against your own download to rule out a truncated file — itself one of the causes in the won’t-start guide. The Tutorials hub covers the install and first-launch checks that prevent most of these problems from happening at all.

If your problem is not in this hub, the honest next steps are the project’s own channels: issues for the V6 GUI belong in Frank Bijnen’s GitHub repository, and questions about ExifTool itself belong on the ExifTool forum. This site documents the failures it can source; the maintainers see the ones nobody has written down yet.