Key Options

Set options for the Key. You can enable features including computer-based signature extension, Key Data, and Key Value.


Specify the unique characteristics of the Key. Be default, the Key is based on the hard drive signature.

Enable Computer Specific Signatures

Enable the Key to utilize additional hardware signatures from the CPU, BIOS, and Ethernet LAN adapter. Enabling any of these signatures enables the computer-based software protection in which the protected application is only allowed to run on a specific computer.


There are two options for enabling the signature extensions. With the option All enabled signatures must be valid, all of the enabled signatures will be detected and they must be valid. With the option All or most signatures must be valid, all of the enabled signatures will be detected, but it is allowed if a signature may not be available, could be invalid. This option can give greater flexibility to support wider ranges of system environments. For example, a computer may not have one of the enabled hardware signatures (e.g. Ethernet LAN adapter), or a hardware signature could be varied such as deployment in the cloud or virtual machine environment.


         Generating a permanent Registration ID for the computer. As opposed to the randomly generated Registration ID, this option causes the protected application to generate a permanent Registration ID in which the Key is based on the enabled hardware signatures. Since the Registration ID is fixed, the user can always use the same License Key to activate the protected application. This option is useful when you grant the user to use the application with no limit. An advantage of this option is that the user requires little support from the developer. The user can format the hard drive or replace with a new one, and can still use the same Registration ID and License Key to reinstall and activate the protected application.


noteNOTE: If the Transfer utility detects that the permanent Registration ID is enabled, it blocks transferring the license of the protected application. Because the permanent Registration ID and its License Key are always valid, allowing the transfer could grant the user another license on another computer.

Also note that, when running the Destroy or Remake utilities, a new Registration ID will not be randomly generated. The user still gets the same permanent Registration ID in which the Key is based on the enabled hardware signatures.

Disable making Key on Virtual Machine
This option can help to increase the security of the protected program, especially in the virtual machine environment. Because virtual machines run on the same emulated hardware, a virtual machine may be backed up and restored, or copied from one to another computer. As a consequence, a user would be able to run the evaluation version of the protected program repeatedly by creating a new virtual machine. You can prevent this kind of problem by disabling making the Key on virtual machines such as VMware and Virtual PC.


If your application is protected as module/feature-based in which the modules are assigned a different Module ID, you can use the provided checkboxes to enable the Module IDs to initialize the Key.

Key Data

This option is available when you use ElecKey Integrator to Generate Initiate Codes for KeyCheck API (under the Select Integration Task dialog). Key Data is a 64-byte space in the Key that allows you to store data for any purposes such as configurations, username, password, etc. Besides, in advanced operation, you can also use Key Data to store custom licensing properties you may define such as upgradable values or credits for the protected application. You can enter the data in the provided fields to initialize the Key.


In addition, you can enable the Items mode of Key Data by clicking on the Items1, Items2, Items3, and Items4 buttons. The Items dialog box will appear. You can then use the provided checkboxes to enable the Item IDs to initialize the Key.


noteNOTE: Key Data is an advanced feature. You must use the full KeyCheck API to protect your application, to be able access and utilize the Key Data as well as the Item IDs.

Key Value

This option is available when you use ElecKey Integrator to generate an Initiate Code for the KeyCheck API. Key Value is a hash table of 10 key-value pairs, which you can define each a digit from 0 to 65535. The Key Value can be accessed by the KeyCheck API.

License Key

Select the License Key version, which sets the licensing scheme for the protected application. There are currently two License Key versions available.


         LK2.0.0.0 is the licensing scheme used in ElecKey since version

         LK2.0.8.24 is the new and default licensing scheme used in ElecKey version and onwards.


noteNOTE: If you owned ElecKey before version, you must update and deploy ElecKey version or higher to your system. For more details, see Appendix: License Key Version and Compatibility.


noteNOTE: The new License Key version LK2.0.8.24 is available in the licensed copy of ElecKey only. When you use the trial ElecKey copy, the License Key version is set to LK2.0.0.0.