I've tried starting the programs many times. On the last occasion, for the first time, an error was displayed. It is the same error in another thread, not able to find exiftool. I will close this thread, then.
Thanks.
Environment:
Windows 10 64 Bit
exiftool executable in /Windows directory
ExiftoolGui files in c:/ExiftoolGui
Files:
Workspace folder
Exiftoolgui.exe
When I double-click to start the program, a window opens up for a short time. It appears that it is trying to set up. The headers in the window in which files are displayed flash and then the window disappears.
Anyone have this problem and found a solution?
Thanks
I had the same problem. The only solution I found was everytime removing the ini-file.
I made a batch file for removing the file before starting ExiftoolGui.
The batchfile is:
cd c:\[Program directory]\ExiftoolGui
del *.ini
ExifToolGUI.exe
This works for me.
Interesting. The problem sounds like it could have to do with permissions writing the .ini file. I wonder if running as administrator would help.
- Phil
I tried running as administrator but it did't work.
Quote from: rvdkrogt on January 15, 2019, 03:30:41 AM
The only solution I found was everytime removing the ini-file.
I always have the ini file open in Sublime text editor https://www.sublimetext.com/ (https://www.sublimetext.com/).
If ExifToolGUI don't want to open, i just change the
DefaultDir to a reachable path, e.g.
DefaultDir=D:\Data\
In my case the program closes, if in the ini file StartMax is set to 1. When I set StartMax=0 (the default value) it works fine. But as I like to use the GUI full screen, I always have to reset this. Any solution to avoid this?
I have ExifToolGUI installed on a thumb drive. I can take it to different computers and it works fine until I get to a Windows 10 computer. On Win10 it opens momentarily and then closes immediately. The ini file has StartMax=0. When I move the .ini file to a temporary location (i.e., get rid of it), then ExifToolGUI open but displays the dialogue message shown as ExifGUIerror1.png (attachment). Then when "OK" is selected the program opens, and stays that way, until you select a directory in the file browser which results in ExifGUIerror2.png (attachment).
My Windows 7 computer just broke and given the status of Windows 7 it seems like it might be problematic to replace it with another Windows 7 computer. However, I use ExifToolGUI enough I would consider doing just that. I know ExifToolGUI has been stabilized but I'm thinking this is probably not a major problem. Is there any hope to get it working on Win10?
It works for some people but not for others. Unfortunately, as mentioned in this sub-forums sticky post (https://exiftool.org/forum/index.php?topic=4553.0), the gui is no longer has support.
The most common problem seems to be anti-virus/windows defender interfering, but that's not necessarily a guarantee.
Yes! When I turn off Windows Defender it seems to work. Not sure where that leaves me but it is very good to know that which is very helpful. Many thanks!!!
I'd suggest trying to add an exception to Defender for both the GUI and Exiftool rather than keep it turned off. See this page (https://support.microsoft.com/en-us/help/4028485/windows-10-add-an-exclusion-to-windows-security) for instructions.
When I said "it seems to work" that was based on an experiment which did succeed. However, I did other things and it is back to the same kind of failure. The first other thing was to boot a different instance of Win10 (i.e., my computers are setup to use multi-boot). When I first tried ExifToolGUI it seemed to work without even bothering to disable Windows Defender. Then I went back to the original instance of Win10 to see what would happen there. It now fails and turning off Windows Defender was NO help this time. It still failed. Then I went back to the instance of Win10 where it had just worked and now it fails. Note: The ExifToolGUI/ExifTool are stored on the same thumb drive used in every case.
Conclusion, it works very seldom. Certainly is very unreliable.
The first error indicates that ExifToolGUI cannot find ExifTool. Is it possible that there is some difference in how Win10 finds executable files that could be the cause? The ExifTool program is located in the same directory as ExifToolGUI.
Another bit of nuance is that I also use a program called XnViewMP which makes extensive use of ExifTool. It appears to have ExifTool stored in one of its sub-directories but seems to never have any such problem. Might there be some problem caused by using different instances of ExifTool. I had run XnViewMP on the secondary instance of Win10 between the time that ExifToolGUI succeeded and when it failed.
Quote from: ajax on January 20, 2020, 05:34:52 PMConclusion, it works very seldom. Certainly is very unreliable.
That's pretty much my experience. Sometimes it will work for a couple of files, but then it crashes. When it works, it never works longer than 2-3 commands.
QuoteThe first error indicates that ExifToolGUI cannot find ExifTool. Is it possible that there is some difference in how Win10 finds executable files that could be the cause? The ExifTool program is located in the same directory as ExifToolGUI.
Has it been properly renamed?
QuoteMight there be some problem caused by using different instances of ExifTool. I had run XnViewMP on the secondary instance of Win10 between the time that ExifToolGUI succeeded and when it failed.
No. IMatch5, for example, runs 4 instances of exiftool simultaneously at all times. Even different versions extract to their separate folders when unpacked in the temp dir.
Sorry for slow response. I did post a question on Microsoft forums and received some feedback that calls for experimentation which takes time. Will reply hear with anything that proves to be positive. The on again off again nature of problem makes it difficult to know effectiveness of positive results.
QuoteHas it been properly renamed?
Having it installed on thumb drive means what I running on Win10 is no different from what works great on Win7. Wouldn't that imply that the name is OK? Wouldn't it always fail if name were a problem?
Quote from: ajax on January 23, 2020, 07:27:49 PMWouldn't that imply that the name is OK? Wouldn't it always fail if name were a problem?
Yeah, if it's working from a flash drive on Win7, then the name isn't the problem.
Quote from: GilExifUser on January 14, 2019, 03:29:15 PM
I've tried starting the programs many times. On the last occasion, for the first time, an error was displayed. It is the same error in another thread, not able to find exiftool. I will close this thread, then.
Thanks.
Environment:
Windows 10 64 Bit
exiftool executable in /Windows directory
ExiftoolGui files in c:/ExiftoolGui
Files:
Workspace folder
Exiftoolgui.exe
When I double-click to start the program, a window opens up for a short time. It appears that it is trying to set up. The headers in the window in which files are displayed flash and then the window disappears.
Anyone have this problem and found a solution?
Thanks
Quote from: Phil Harvey on January 15, 2019, 07:16:15 AM
Interesting. The problem sounds like it could have to do with permissions writing the .ini file. I wonder if running as administrator would help.
- Phil
Hi All,
I have been gathering some info before posting to this thread. I have the Windows 10 Blues, every time they run an update something else on my laptop breaks!
I have had most of my success with getting "ExifTool & ExiftoolGui" running on my :
Windows 10
Version 10.0.18363 Build 18363
HP Laptop 8gig
By using the install tool mentioned in this post by Phil Harvey: https://exiftool.org/forum/index.php?topic=10315.0 (https://exiftool.org/forum/index.php?topic=10315.0) which includes the "Install tool" created by Oliver Betz.
Although I still get an error if I try to "drag file to desktop icon" the ExiftoolGui still will sometimes crash!
Here is a copy of the crash log if any of you Programmer Types would care to investigate, hope it will help? ;D
Quote from: SharkyCA on February 19, 2020, 09:48:07 PM
I have the Windows 10 Blues, every time they run an update something else on my laptop breaks!
You might consider delaying future "function" updates for a few months. And don't click "search for updates" without a reason.
Quote from: SharkyCA on February 19, 2020, 09:48:07 PM
I have had most of my success with getting "ExifTool & ExiftoolGui" running on my :
Windows 10 Version 10.0.18363 Build 18363 HP Laptop 8gig
By using the install tool mentioned in this post by Phil Harvey: https://exiftool.org/forum/index.php?topic=10315.0 (https://exiftool.org/forum/index.php?topic=10315.0) which includes the "Install tool" created by Oliver Betz.
I don't think that this is a reason for your problems, but out of curiosity:
How (as user or admin) and where (directory) did you install ExifTool with this installer?
Advice for future ExifToolGUI users:
If you use ExifTool
only with ExifToolGUI, the ExifToolGUI directory might be the best place for ExifTool.
In this case, you can simply unzip the contents of the ZIP file from my web site to the ExifToolGUI directory so that ExifTool.exe is in the same directory as ExifToolGUI.exe. No need to "install" anything or dealing with the "path" variable.
Oliver
Quote from: obetz on February 20, 2020, 03:41:13 AM
Quote from: SharkyCA on February 19, 2020, 09:48:07 PM
I have the Windows 10 Blues, every time they run an update something else on my laptop breaks!
You might consider delaying future "function" updates for a few months. And don't click "search for updates" without a reason.
Quote from: SharkyCA on February 19, 2020, 09:48:07 PM
I have had most of my success with getting "ExifTool & ExiftoolGui" running on my :
Windows 10 Version 10.0.18363 Build 18363 HP Laptop 8gig
By using the install tool mentioned in this post by Phil Harvey: https://exiftool.org/forum/index.php?topic=10315.0 (https://exiftool.org/forum/index.php?topic=10315.0) which includes the "Install tool" created by Oliver Betz.
I don't think that this is a reason for your problems, but out of curiosity:
How (as user or admin) and where (directory) did you install ExifTool with this installer?
Advice for future ExifToolGUI users:
If you use ExifTool only with ExifToolGUI, the ExifToolGUI directory might be the best place for ExifTool.
In this case, you can simply unzip the contents of the ZIP file from my web site to the ExifToolGUI directory so that ExifTool.exe is in the same directory as ExifToolGUI.exe. No need to "install" anything or dealing with the "path" variable.
Oliver
I have installed & re-installed numerous times so not quite sure where it is running from now?
To the best of my knowledge it is from the directory as follows: (My user account is administrator account)
Hi Everybody,
I found this forum and topic while searching the Internet for the solution to a similar issue I was faced with, while trying to use the ExifToolGui under Windows 10 / 64 bit. Because I haven't found any solution that would work for me I have found my own one. ;)
Before upgrading OS from Windows 7 to Windows 10, the ExifTool with ExifToolGui were the most powerful EXIF manipulation software I knew and ever used. But Microsoft with their Windows 10 "destroyed" these and lots of other useful and great applications. >:(
After doing a lot of failed trials, including changing compatibility modes and administrator's privileges in the ExifToolGui shortcut properties, I decided to do the last trial that eventually appeared successful for me.
Finally I ran the ExifToolGui successfully on the virtual machine with the Windows 7 Professional 64 bit as a guest operating system installed. I used VMware Player (free for personal use) as a virtual machine engine but you could use any alternative VM software like e.g. VirtualBox. And there the ExifToolGui started to work fine and smooth with all of images it couldn't deal with before, under Windows 10.
I know that this won't be the best solution for everyone, but maybe it will help somebody. Good luck. :)
Regards - Maciek
Quote from: McVik on June 22, 2020, 05:42:04 PM
Microsoft with their Windows 10 "destroyed" these and lots of other useful and great applications. >:(
After doing a lot of failed trials, including changing compatibility modes and administrator's privileges in the ExifToolGui shortcut properties [...]
please don't blame Windows 10 for your specific problems. ExifTool and ExifTool Gui run fine in most Win 10 installations as well as they did in
most Win 7 installations.
You do not need any compatibility mode or administrator privileges.
Looking for some advice on this issue, sometimes it will work but most times it crashes with no indication!
Please see attached screen shots!
Hi,
I got the same error with Win10 (window closed after it just came up).
Error in the windowns log has something to do with shell32.dll.
After deletion of the "ExifToolGUIv5.ini" it's starting up and running.
Propably till next start.
So at least this is a kind of workaround to get ExifToolGui up and running.
I ran into this issue tonight for the first time. Saw the reply about deleting the ini file. I decided to look at the contents of the file (ini files are plain text files readable and editable in any text editor) And I saw and fixed the issue for me. The DefaultDir entry pointed to the mapped drive letter of the folder on my server where I usually store my photo archive. But I'm on vacation, thousands of miles from my now inaccessible server. I edited the entry to point to c: and ExifTool GUI now opens normally, allowing me to select the folder containing my photos while I'm traveling.
This is a quick and easy fix if that is your issue. If deleting the .ini file lets it open, look at the contents and correct the erroneous entry.
I just started getting this same error - ExifToolGUI window opens, and after 5 or so seconds it closes with no message or error. Running Windows 10 Home 64 bit version 22H2 with all updates as of this date.
In my case, the cause is having a network drive mapped. My drive is a USB plugged into my router, shared with Samba, mounted as Z:. When I run ExifToolGUI as Administrator, it runs fine. But when run normally - my account is a regular user - I get the crash. "Werfault.exe" runs under the ExifToolGUI process momentarily just before it crashes (logging?). exiftool.exe process is left running, and Windows actually thinks it has file(s) on Z: open. My guess is the GUI does some drive scan on startup that blows up on the network drive if the process does not have Admin privileges, and it doesn't check first or handle the error.
Also noticed that if the default dir is not C:\, then when ExifToolGUI crashes it displays that last dir in the window middle panel for a moment, then switches to C:\ before crashing. But it also changes the default dir to C:\ in .ini so the next time you won't see that.
The fix for me was to either run ExifToolGUI as Administrator, or to disconnect my network drive. You can also use Windows File Explorer, open Properties on ExifToolGUI.exe, go to Compatibility tab, under Settings, and check "Run this program as an Administrator" so it always runs as Admin. Hope this helps someone else having this problem.
While this is obviously an error in ExifToolGUI, a thought for Phil. If you think it's worth the bother, and can find what bad operation the GUI is trying to have ExifTool do, you could take a look to see if there's an internal error that is slipping by uncaught.
Thanks for the great tag editing tool! And to the GUI author for originally writing this, still useful a decade out of support. ;D