ExifTool stops working under Windows 10

[leahcimi]

I have recently upgraded my Windows 7 system to Windows 10 and now, when I try to run ExifTool either from the desktop, or from within a system prompt, it crashes Windows simply says that 'Exiftool has stopped working'.


Please help!

[leahcimi]

Here is an XML version of the error report:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2015-09-13T11:01:26.000000000Z" />
  <EventRecordID>2788</EventRecordID>
  <Channel>Application</Channel>
  <Computer>computer13</Computer>
  <Security />
  </System>
- <EventData>
  <Data>exiftool.exe</Data>
  <Data>0.0.0.0</Data>
  <Data>448016b9</Data>
  <Data>KERNELBASE.dll</Data>
  <Data>10.0.10240.16384</Data>
  <Data>559f3b2a</Data>
  <Data>80000003</Data>
  <Data>00132bd2</Data>
  <Data>434</Data>
  <Data>01d0ee1388c567b1</Data>
  <Data>C:\Users\user\AppData\Local\Temp\par-user\cache-exiftool-10.01\exiftool.exe</Data>
  <Data>C:\WINDOWS\SYSTEM32\KERNELBASE.dll</Data>
  <Data>636f9b31-ca1c-4274-a3a1-fca7d8783598</Data>
  <Data />
  <Data />
  </EventData>
  </Event>

[StarGeek]

Try deleting the temp directory.  From the uninstall instructions:

"Drag the directory "par-USER" from your temporary directory to the Recycle bin. Here "USER" is your Windows user name and the location of the temporary directory depends on the value of the TEMP environment variable (typically "C:\Documents and Settings\USER\Local Settings\Temp" for Windows XP, or "C:\Users\USER\AppData\Local\Temp" for Windows 7)."

[leahcimi]

Thanks for the tip but it did not solve the problem.

[Phil Harvey]

We have also had had some issues with Windows 10 and the GUI I think.

- Phil

[leahcimi]

Is there a hoped for date for a Windows 10 compatible version?

[Phil Harvey]

If this is a Windows 10 problem then I need some help because I don't have access to a machine that runs Windows 10.

- Phil

Edit:  I'll try upgrading the version of the package archiver that produces the Windows EXE version to see if this helps.  I'll post here with a link to a test version for you if I can do this.

Edit2: Wow.  OK, that sucks.  Upgrading PAR is more difficult than it should be, and requires upgrading (at least) 10 other packages.  I was working away at upgrading the necessary modules, but ran into a snag trying to install one of the dependencies on Windows because it seems to require a compiler that I don't have.   I hope I haven't broken my existing version of PAR, because if I have it may be a while before I can build an EXE version again.

[Phil Harvey]

OK.  I finally have success after spending hours sorting through various problems while installing the 15 packages required to upgrade PAR.

Here is a link to the test version of ExifTool 10.02 built with PAR 1.010.

The executable size has bloated from 5.4 MB to 8.1 MB due to this update.

Please let me know if this works on Windows 10 (or any other Windows version for that matter -- I only tested it on XP).

- Phil

[ryerman]

It seems to work on my Windows 7.
The %TEMP%\par-username directory increased from 13 MB to 25 MB.

[Phil Harvey]

Thanks ryerman.  I imagine that the first launch of exiftool is now correspondingly slower as well.

- Phil

[ryerman]

Maybe, but not obvious to me.
Definitely not a problem.

[leahcimi]

I still get the message that 'exiftool.exe has stopped working' under Windows 10.

If it's any use to you, here is a copy of the crash report:

Version=1
EventType=APPCRASH
EventTime=130876417139085481
ReportType=2
Consent=1
UploadTime=130876417140006094
ReportIdentifier=aeb1bb02-635b-11e5-9bcf-50e5499e37e0
IntegratorReportIdentifier=9aaf068f-0926-4f05-a82c-6546e204f12c
WOW64=1
NsAppName=exiftool.exe
Response.BucketId=0c2b3ca47c73e3dd2796fbc8c14fe4e1
Response.BucketTable=1
Response.LegacyBucketId=107492953465
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=exiftool.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=448016b9
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.10240.16384
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=559f3b2a
Sig[6].Name=Exception Code
Sig[6].Value=80000003
Sig[7].Name=Exception Offset
Sig[7].Value=00132bd2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=12b5
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=12b5cec8f64d98e3437645b90831beb3
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=d44d
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=d44dc791c6b04893c6684a8c97c7309b
UI[2]=C:\Users\user\AppData\Local\Temp\par-user\cache-exiftool-10.02b\exiftool.exe
UI[3]=exiftool.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Users\user\AppData\Local\Temp\par-user\cache-exiftool-10.02b\exiftool.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[6]=C:\Users\user\AppData\Local\Temp\par-user\cache-exiftool-10.02b\perl58.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\IMM32.DLL
LoadedModule[15]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\WS2_32.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\NSI.dll
LoadedModule[18]=C:\Program Files (x86)\IP Hider Pro\IPHiderLib.dll
LoadedModule[19]=C:\WINDOWS\system32\mswsock.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=exiftool.exe
AppPath=C:\Users\user\AppData\Local\Temp\par-user\cache-exiftool-10.02b\exiftool.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=FCF52767178B40B939FE833CBABF339A

[Phil Harvey]

Darnit.

[leahcimi]

Is exiftool failing to work in Windows 10 a general problem or is it likely to be something specific to my system?

[Phil Harvey]

Other people have had similar (but intermittent?) problems with Windows 10.  But apparently it does work on some Windows 10 systems.

- Phil