Exiftool stops working in Windows 10

[leahcimi]

I am unable to run my trial version of imatch 5 because exiftool stops working on my Windows 10 system. Exiftool not working also affects Exiftoo GUI and Geosetter.

Has anyone else had this problem and will my 30 day trial period still expire?

[Mario]

I, and many users, use IMatch 5 on Windows 10 without any problem. ExifTool runs fine on Windows 10, in principle.

This sounds to me as some sort of access privilege problem or some sort of virus checker interfering.
ExifTool needs to be able to access it's files, and to create a folder in the TEMP folder on your system.

Did you try running ExifTool from the command line?
Just open a command prompt window, "cd" into the folder containing IMatch (c:\program files (x86)\photools.com\imatch5...) and then run exiftool like

exiftool -ver

this command displays the version number if everything is OK. If you get an error message instead, we may be wiser.

[leahcimi]

I still get a message that 'exiftool.exe has stopped working'.
If it helps here is a copy of the WER crash report :

Junk data removed by Admin. Please use the feature to attach files to your post, don't just copy/paste long log file data into your posts.

[Mario]

Please be sensible. Don't flood the community with garbage postings. This information is maybe decipherable for Microsoft but not for normal users. Posting this amount of junk is confusing also the search engine. Why not just attach the file instead?

This time I manually edited your post, put the junk into a text file and attached it - if somebody wants to look at it.

Did you try the test I described? Is this when Windows tells you that ET stopped responding? This would be unusual in a command line application...
I suspect you might want to check at your system policies or most likely at your virus checker or similar security software.

If you get this when ExifTool is used from IMatch, the IMatch log file may contain additional info. You can find this log file in the TEMP folder on your system. Please type log file into the IMatch system index help to find all the info.

But since ET fails on your box for IMatch and ETGui, it's probably your virus checker stopping it dead in the tracks. Or some weird security configuration or policy you have in place. The command line test may provide additional info, unless you did run it already but failed to mention it.

[attachment deleted by admin]

[RalfC]

I had a look to the log-file:

The log has no reference what so ever to Exiftool.
It states that IMatch stopped responding. (too busy in the background to respond to the regular requests from windows in time?)

As far as I remember there are other threads concerning IMatch not responding / Screen going white, etc.

Regards,
Ralf

[leahcimi]

Setting 'Exiftool.exe' to Run as Administrator seems to have cured the problem with imatch 'though oddly enough not with ExiftoolGUI or Geosetter. These aren't your prolems though. Apologies for not using the attachment button earlier.

[Mario]

IMatch uses it's own copy of ExifTool, and so do ExifToolGui and GeoSetter. Each has it's own version of exiftool.exe installed in some folder.
If you set one of these to run as Admin, this won't promote to the others...

If switching it to run as Admin solves the problem, you have an file system permission problem (ExifTool cannot write to the TEMP folder on your system, where it needs to store the Perl runtime files) or your virus checker is blocking the file from running or from creating files.

You can use a tool like sysinternals Process Monitor to monitor exiftool.exe on your system, and see where it gets "access denied" errors when it tries to create/access files. Or if it blocked by your security software...

https://technet.microsoft.com/en-us/sysinternals/bb896645