ExifToolGui Won’t Start? Run These Checks
ExifToolGui is the Windows front-end for Phil Harvey’s ExifTool — the original GUI by Bogdan Hrastnik, continued today as V6 by Frank Bijnen on GitHub. When it will not start at all, the cause is usually something plain about the setup rather than something deep about your PC: an incomplete download, the wrong build for your Windows, a version of Windows outside what V6 documents, or a missing ExifTool pairing that stops the program at launch. Work through the checks below in order. If you have not installed yet, the known-good files are linked from our download page; the rest of this series lives in the Troubleshooting hub.
First, separate two different failures
A GUI that opens and then complains is not the same problem as a GUI that never opens. If ExifToolGui starts and reports that ExifTool was not found, the program itself is fine — its engine is missing or misnamed, and the fix is the pairing: rename exiftool(-k).exe to exiftool.exe and keep the exiftool_files folder with it, as the not-found guide explains step by step. The original GUI’s documentation already noted that the program shows an error at startup when the ExifTool preparation is wrong, so a launch-time error message about ExifTool points at the pairing, not at the GUI. The checks below are for the other case: the window never appears, or the program closes again immediately.
Check your Windows version against what V6 documents
ExifToolGui is Windows-only software — there is no Mac or Linux build of either the original or the V6 fork. The V6 documentation states that the GUI should run on Windows 7 and 8 (32- and 64-bit), and that using Windows 10 or 11 is highly recommended. If you are on an older or unusual Windows setup, you are outside the configuration the current documentation describes, and upgrading the GUI will not change that. On Windows 10 or 11, platform support is not your problem — move on to the file checks. (On a non-Windows system entirely, the honest options are different software; see ExifToolGui on Linux for how that works out in practice.)
Check the file you downloaded is complete
An interrupted download produces an executable that Windows cannot run properly. The V6.3.12 release files were downloaded and measured for this site on 2026-10-23, so you can compare sizes exactly: the portable Win64 executable, ExifToolGUI_X64.exe, is 21,758,464 bytes, and the portable Win32 executable, ExifToolGUI.exe, is 15,870,976 bytes. If your file is noticeably smaller, the download was cut off — download it again in full rather than trying to repair it. This check matters more than it sounds: a truncated file is one of the most common reasons a freshly downloaded program does nothing when launched.
Check you have the right build for your Windows
V6.3.12 ships two portable executables: ExifToolGUI.exe (Win32) and ExifToolGUI_X64.exe (Win64), plus the installer. A 64-bit Windows runs either build; a 32-bit Windows can only run the Win32 build. If you are unsure which Windows you have, the Win32 portable executable is the one that runs on both. The installer makes this choice for you: on 64-bit Windows it installs the Win64 files by default. Choosing between the installed and portable routes is covered in full in Portable vs Installer, including the /Win32 installer switch. If the GUI ran before and stopped after you tidied its folder, suspect a partial move: for the portable program, keep the whole extracted set together, and remember its settings live in an .ini file beside the executable (ExifToolGUIV6.ini for V6) — deleting files from the program folder can break a setup that was working.
Update to V6.3.12 if you run an older V6
V6.3.12 (released May 8, 2026) is the current release, and its notes include a fix for an access violation when changing styles — a crash-class bug in the program itself. If your copy is an older V6 build and it closes unexpectedly, moving to the current release is a legitimate diagnostic step, not a superstition: you remove a known crash from the list of suspects. Download the current files from the download page, keep your photos untouched — the GUI only edits metadata when you ask it to — and test the new build with the same folder. What changed in this release is summarised in ExifToolGui V6.3.12: What’s New.
Frequently asked questions
ExifToolGui opens, shows an error about ExifTool, and closes. Is that this problem?
It is the pairing problem wearing a startup costume. The original documentation warns that the GUI shows an error at startup if the ExifTool preparation is wrong. Fix the pairing first — correct name exiftool.exe, exiftool_files folder beside it — using the not-found guide linked above.
Do I need to install anything else for the GUI itself to run?
The documented requirements are ExifTool (required, separate) and, only if you want the map feature, the WebView2 pieces: WebView2Loader.dll plus the Microsoft Edge (WebView2) runtime. A missing map component affects the map, not the program’s startup — that case is covered by the map troubleshooting page in the Troubleshooting hub.
Should I just reinstall Windows components or edit settings?
Nothing in the program’s documentation calls for that, and this page will not invent fixes its sources do not support. The documented failure points are the pairing, the build, the platform and the completeness of the download. Check those four first; they account for the realistic cases.