Knowledge Base

Search Knowledge Base

KB #240018: Cyclic Redundancy Check Error (CRC) When Starting Application Using DE/NEP

Type: Information
What the CRC error means and how to fix it
Additional Information:
This applies only to applications that have been “Secured” with Encryptionizer via GUI, CLI or the associated API. If you are using the APIs only, it is unlikely that the problem is related to Encryptionizer. When you have secured your application with GUI or CLI, Encryptionizer ahs an option to generate a complex CRC to ensure that no one has replaced or modified the application’s executable. In fact, Encryptionizer acts as an additional anti-virus check on the executable. It could be modified/replaced

  • By accident (e.g., accidentally restoring an old version)
  • Deliberately but proper (e.g., a service pack or patch has been applied)
  • Deliberately but malicious (e.g., infected with a virus)

If the executable has been changed, the next time you go to start the application, Encryptionizer will generate the CRC error. What to do next depends on the cause of the message.

  • If replaced/modified by accident, restore or reinstall the correct executable.
  • If deliberate but proper, re-secure the application after all the patches and updates have been applied.
  • If deliberate but malicious, run a virus scan and then restore or reinstall the original.

By default, Encryptionizer will not check the CRC, however for custom modules, we recommend that you use this option.

Developer Note: If distributing a new version of your application, make sure to also distribute or generate a new SEC profile.


Last modified: 1/13/2016