Sending a Crash Report

Occasionally, in the event of EasyCatalog crashing, we may ask you to send us a crash dump file.  The dump file contains information showing what EasyCatalog was doing when InDesign crashed and will assist us with the debugging process.


By default, Windows Error Reporting (WER) will not produce a crash dump so a change to the registry on your machine is required.

WARNING: Back up your registry before attempting these modifications.  We recommend creating a System Restore Point before making these changes.

  1. Quit InDesign if it is already running
  2. Download the registry file from this link.
  3. Once downloaded, double click on the file.  You may be asked to enter your Administrator password to make changes to the registry.
  4. Answer ‘yes’ when asked to confirm adding the values to the registry
  5. OK the confirmation dialog that appears
  6. Relaunch InDesign

If InDesign crashes again, a log file will be written to the ‘C:\Dumps’ folder.  Please email this file to us with a description of what you were doing when the issue occurred.

The ‘Dumps’ folder will only ever contain the last two dump files, so if you need to collect more please copy the files out after each crash.


Crash logs are automatically collected and are available from the ‘Console’ application.

  1. Launch the ‘’ application.  Typically this is in your Applications:Utilities folder.
  2. On the left of the dialog that appears, under ‘Diagnostic and Usage Information’ should be a ‘User Diagnostic Reports’ folder.
  3. Inside of the ‘User Diagnostic Reports’ folder is a series of ‘.crash’ files. The name of the application that crashed and – importantly – the date and time of the crash will be shown in the filename of the crash file. Please ensure that the crash file you’re sending to us was written when your issue occurred.
  4. Select the crash file you would like to send to us
  5. Use the ‘File > Save a Copy As’ menu option to export the crash file
  6. Please email this file to us with a description of what you were doing when the issue occurred.