История версий драйверов HASP

История версий драйверов Sentinel HASP

Revision History of Enhancements and Issues Resolved in Sentinel Run-time Environment — Windows Platforms

Issues Resolved in Version 7.80

Reference Description

If a customer applies a V2C update from a remote machine that has the Vendor library but no license from the same vendor, the error returned was HASP_UPDATE_TOO_NEW, which was confusing. Now the error returned is HASP_KEYID_NOT_FOUND.

SM-18502 Defining an excessive number of User Restrictions in Admin Control Center would cause the License Manager Service to fail.
SM-19981 hasp_update would return an internal error for an HL Key when the license definition contains empty content in the default memory section.

The RTE installer adds a firewall rule (named “Sentinel License Manager”) that, in the past, allowed incoming connections from any network, including public networks, using port 1947. Starting with RTE version 7.80, the firewall rule added by the RTE Installer does not allow incoming connections from public networks. If you are upgrading from an earlier version of RTE, the installer replaces the existing rule (that allows connections from public networks) with a rule that blocks such connections.

You can manually allow access using this port from public networks, but Gemalto highly recommends against this.

If you do plan to allow access from public networks using port 1947, create a rule with a different name in order to prevent future RTE upgrades from removing this access.

SM-25600 The Run-Time Environment would require an excessive amount of time to install.
SM-26543 Under certain circumstances, Sentinel License Manager would crash on the REST interface with long packets.
SM-9841 HASP4 keys would stop working after the Run-time Environment was upgraded to  v.7.54.

Issues Resolved in Version 7.66

Reference Description
SM-25600 The Run-Time Environment would require an excessive amount of time to install.

Issues Resolved in Version 7.65

Reference Description
SM-21408 The Admin Control Center help system was missing information regarding the new “Idle Timeout of Session” configuration parameter.

Enhancements in Version 7.63

Reference Description
SM-13443 When a Sentinel HL (HASP configuration) key or HASP HL key is attached to a Windows machine, the Run-time Environment is no longer installed automatically by Windows Update. It is now the software vendor’s responsibility to ensure that the Run-time Environment is installed when required.

In the past, the timeout for an idle License Manager session was fixed at 12 hours. You can now set the timeout to any value between 10 minutes and 720 minutes (12 hours). The timeout value can be set as follows:

  • In Admin Control Center, on the Basic Configuration page. Use the Idle Timeout of Session parameter.
  • In the hasplm.ini file. Assign the timeout value to idle_session_timeout_mins.

Admin Control Center now adds the update counter in C2V files in clear text — for example: <update_counter>5</update_counter>
It is no longer necessary to decode the C2V file in order to view this information.

SM-19483 Admin Control Center now recognizes the new V2CP format to update protection keys. This supports planned enhancements in Sentinel LDK v.7.8.

Issues Resolved in Version 7.63

Reference Description
SM-15922 Admin Control Center no longer requires the <?xml header in a V2C file.

After system reboot/service restart, an SL AdminMode detached license would disappear from a recipient machine that had no other licenses.

SM-18015 On some machines, the License Manager service would start before the Secure Storage driver is loaded. This would cause the Secure Storage to become corrupted. Now, the License Manager service waits for the Secure Storage driver to start.
SM-18302 Cancelling a detached SL AdminMode license from the recipient VM machine would fail with the HASP_VM_DETECTED error.
SM-18502 In Admin Control Center, defining too many users in the User Restrictions field would cause the License Manager to fail.

Enhancements in Version 7.61

Reference Description

The Run-time Environment now supports the use of the VMType3 clone protection scheme.

Enhancements in Version 7.60

Reference Description

You can now enter the URL to access Sentinel EMS in your Web browser without changing the EMS URL to lowercase.


Admin Control Center (under Windows) can now display and apply updates to local SL UserMode keys. (Session information and certificate information for SL UserMode keys is not displayed.)


To display SL UserMode keys in Admin Control Station, License Manager runs an additional process (hasplmv) on the machine. If you are willing to accept that SL UserMode keys will not be displayed, you have the option to prevent hasplmv from executing by clearing the relevant check box on the Configuration page in Admin Control Center.


In the past, Admin Control Center and Admin API provided a configuration parameter that determined whether a remote user could access and perform actions in Admin Control Center. However, this parameter did not control remote access to Admin API.
Now, the parameter Allow Remote Access to ACC and Admin API (in Admin Control Center) and the tag <accremote> (in Admin API) control remote access to both Admin Control Center and Admin API.

Issues Resolved in Version 7.60

Reference Description

When a data file is protected with Version 2 data protection mode for Android platforms: If, for any reason (for example, no license was found), the protected application was not able to decrypt the protected data file, no error message was generated to explain why the file cannot be opened.


Under Windows 10, a physical machine would be detected as a virtual machine when only Hyper-V Hypervisor is enabled.

SM-515 It was possible to rehost a cloned license to another machine.

The Diagnostics report in Admin Control Center (Diagnostics > Generate Report) displays information on «Recent Clients» and «Recent Users». Each entry contained a time stamp but not a date stamp. The report has been corrected to display both a time stamp and a date stamp for each entry.


When building a Run-Time Environment installer using Wix, an error message similar to the following was generated:
Invalid product version ‘’ in package HASP_Setup.msi’. When included in a bundle, all product version fields in an MSI package must be less than 65536.
This error no longer occurs.


Under certain circumstances, Sentinel LDK License Manager Service would crash. The exception code would map to STATUS_STACK_OVERFLOW in __chkstk API.

Enhancements in Version 7.55

Reference Description

Sentinel Admin Control Center can now be used to configure the License Manager for the following additional considerations:

  • Allow specific named users to access specific Batch Codes, protection keys (haspID), or Product IDs.
  • Use the «*» wildcard character for IP and hostname.
  • Use subnet mask notation (for example: for IP addresses

For more information, see «Configuring User Settings» in the Admin Control Center online help.

Issues Resolved in Version 7.55

Reference Description

Various crash conditions in the License Manager that could be used for denial-of-service attacks or privilege-escalation attacks have been resolved.


When a user issues a «detach license» request from a remote Admin Control Center, the user name cannot be included in request. As a result, User Restrictions (defined in ACC on the license server machine) that are based on the user name are handled as follows:

  • “allow” user restrictions that are based on a specific user name are not applied because the user name is not available to the License Manager on the license server. If a different restriction such as deny=all@all is also specified, the detach request will be denied.
  • If any “deny” user restriction that is applicable for the request in all respects other than username exists, that restriction is applied even if the user name specified in the restriction does not match. For example: If the detach request was sent from a machine with the hostname host123, and a user restriction has been specified deny=skr@host123 on the license server machine, the detach request is denied even the user requesting the detach has a different username.

Sentinel Admin Control Center online help has been updated to describe these limitations.

Enhancements in Version 7.54

Reference Description
SM-889 Run-time Environment is supported under Windows Server 2016.

Issues Resolved in Version 7.54

Reference Description

Installation of a rebranded RTE would fail when the account name contains multi-byte characters (such as Japanese). The install log would contain an error similar to the following:

could not open C:\Users\userName\AppData\Local\Temp\EMSUrl.properties ../hhlinst.c,4659
OPEN file C:\Users\userName\AppData\Local\Temp\EMSUrl.properties processing error. ../hhlinst.c,4660,


The decrypt function in the HASP4 API would give incorrect results after RTE 7.52 or 7.53 was installed.

SM-3767 After installation of RTE 7.53, hasplms was unreachable to remote clients. The RTE installer did not add the firewall rule to allow Sentinel License Manager Service.

Issues Resolved in Version 7.53

Reference Description

Given the following scenario:

  1. Obtain a C2V file for an SL Legacy key.
  2. Prepare an update to upgrade the SL Legacy key to an SL AdminMode key in Sentinel License Generation API, but do not apply the update.
  3. Prepare a second update using the first update as the current state for the key.
  4. Apply the second update to the key.

The update would return a status of OK even though the update fails.


Given the following scenario:

  1. Connect a Sentinel HL (HASP configuration) key to a machine and generate a C2V file for the key.
  2. Create an update in Sentinel License Generation API to upgrade the key to a Sentinel HL (Driverless configuration) key, but do not apply the update.
  3. Prepare a second update to the key using the first update as the current state for the key.
  4. Apply the second update to the key.

The update would return a status of OK even though the update fails.

Enhancements in Version 7.52

Reference Description

The Features page in Admin Control Center now displays the peak number of consumed seats per Feature. The peak number is based on the current License Manager session. For each Feature, the peak number value is displayed as a tool tip for the seats value under the Logins column. This information enables end users and organizations to determine if the number of seats purchased is suitable for their needs.


The Run-time Environment can now be installed under Windows 10 when Device Guard is enabled.

Issues Resolved in Version 7.52

Reference Description

A Sentinel HL (HASP configuration) key would not be accessible by the protected application under the following circumstances:

The following conditions exist:

  • Windows 10 version 1607 is present on the machine.
  • The network is disabled.
  • The Run-time Environment is not present on the machine.

The following actions are performed:

  1. The HL key is connected to the machine and then disconnected.
  2. The Run-time Environment is installed on the machine.
  3. The HL key is connected again to the machine.

The HL key would not be accessible.


When using RTE 7.51, a Stop error (BSoD) would occur when the protected application attempted to retrieve the serial number of the disk drive that uses Intel RAID drivers.


Under certain circumstances, the uninstall of the Run-time Environment on a Windows 8 machine would fail.


The uninstall of the Run-time Environment would not provide proper notification if it failed to remove all necessary files. The uninstall process now provides a detailed list of any files that it fails to remove and advises the user to remove the files manually.


During the installation of a rebranded Run-time Environment using the -v flag (haspdinst.exe -i -v), an internal error would be displayed (message: «An error occurred when the RTE installer attempted to unpack the file sm.cab»). Note that the -v flag is not a documented option, and that the installation would succeed despite the error message.


Given the following circumstances.

  1. A machine is not connected to the network
  2. Run-time Environment v.7.50 is installed on the machine.
  3. The Run-time Environment is removed with a purge command.
  4. You connect a Sentinel HL (HASP configuration) key to the machine.

The Run-time Environment would be automatically reinstalled.

Now, the Run-time Environment is not installed under these circumstances.

Issues Resolved in Version 7.51

Reference Description
LDK-13933 When installing Sentinel LDK Run-time Environment v7.41 or later under Windows 10 (x86), the file hlvdd.dll was not installed. As a result, the protected application would fail.
LDK-16215 Each time the end user would connect a Sentinel HL (Driverless configuration) key to a different USB port on a Windows machine, the Driver Software Installation message box would indicate that a restart was required.

Given the following circumstances:

  • A V2C file was applied to a new SL AdminMode license on a given machine.
  • The same V2C was applied a second time to the license.

Instead of generating an error message and rejecting the update, the License Manager would generate the error message and then remove the original SL AdminMode license from the machine. (The license would be restored when the License Manager was restarted.)

Issues Resolved in Version 7.50

Reference Description
LDK-12479 (RTE GUI Installer only) Given the following circumstances:

  • A file type is registered as “protected” using Version 1 data file protection.
  • A file of the protected type is saved from the protected application using “Save as”.

Under certain circumstances, the saved file was not encrypted.

LDK-12860 (RTE GUI Installer only) When a fully-qualified domain name (FQDN) was provided in the login scope using a character set outside the Windows code page, the login would fail with error code 50 (Scope Result Empty).
LDK-13136 Sentinel Licensing API would identify a Max Micro key as a Max key under certain circumstances.

Given the following circumstances:

  • A license server machine and the recipient machine are in different time zones
  • A detachable license is transferred online from the server to the recipient machine.

The detached license would expire earlier than expected.

LDK-13926 The branded RTE Installer that is generated by Sentinel EMS did not copy the haspvlib correctly to /var/hasplm/. As a result, when hasp_update attempted to apply a V2C file, error 48 was generated.

Given the following circumstances:

  • An SL AdminMode or SL Legacy license is located on a physical machine.
  • From a remote VM, hasp_get_info() is called to fetch values of the «disabled» and «usable» tags for the SL license.

The incorrect values disabled=true and usable= false were returned.

LDK-14280 HASP HL keys are not recognized correctly by the License Manager when keys from two or more vendors are connected to a given machine.
LDK-14805 The Run-time Environment did not support RAID controllers that create symbolic links as \Device\RaidPort.
LDK-15306 On the Diagnostics page of Admin Control Center, the Requests counter would count a request to local licenses as a remote request.

Given the following circumstances:

  1. SL Legacy licenses from two different vendors were present on a machine.
  2. The license from one of the vendors is removed.
  3. The License Manager service is restarted.

The remaining SL Legacy license was no longer visible in Admin Control Center.


(RTE GUI Installer only) Given the following circumstances:

  1. RTE version 6.60 or earlier is installed on a machine with no licenses.
  2. Retrieve the fingerprint of the machine.
  3. Upgrade the RTE to version 7.41
  4. Use the retrieved fingerprint to generate an SL AdminMode license.
  5. Apply the license with the upgraded RTE.

The license would be marked as “cloned”.

LDK-16113 When a V2C file to clear the “cloned” status of an SL Legacy license was applied, The “clear clone” operation was not applied correctly until the user restarted the machine.
LDK-16215 (RTE GUI Installer only) Driver software was reinstalled and the end user was prompted to restart the machine each time an HL (Driverless configuration) key was connected to a differed USB port on the machine.

Issues Resolved in Version 7.41

Reference Description
LDK-12845 Installation of Sentinel Run-time Environment version 7.40 on a machine with an obsolete version (11.5.x) of Intel RAID drivers would cause a Stop error (BSoD).

Enhancements in Revision 7.40

Reference Description
LDK-6938 The Run-time Environment now supports Sentinel HL Drive microSD keys.
LDK-8350 The diagnostic report in Admin Control Center now provides additional information for driverless keys and updated driver versions
LDK-10079 The diagnostic panel in Admin Control Center now displays the version number for the Run-time Environment.
LDK-10107 The Admin Control Center log file now indicates the version number for the Licensing API.
LDK-10279 The button in Admin Control Center for generating C2V files is now blocked for HASP HL keys and Sentinel HL (HASP configuration) keys.
LDK-11034 The Sentinel Keys page in Admin Control Center now displays the capacity of attached Sentinel Drive microSD keys.
LDK-11335 Admin Control Center now displays the module name (in addition to the Feature ID) for Sentinel Master keys and Sentinel Developer keys.

Issues Resolved in Version 7.40

Reference Description
LDK-7237 Under certain circumstances, Admin Control Center would continue to show active sessions for an HL key after all sessions had logged out of the key.
LDK-8866 Under certain circumstances, if SL license information became corrupted, Sentinel LDK License Manager Service would crash instead of issuing an error message. As a result, it was not possible for the vendor to correct the situation by sending a license update.
LDK-9797 The Run-time Environment did not provide a meaningful error message when a given License Manager ID was found on multiple machines in the same network. This situation is typically caused by cloning a VM. As a result, it was difficult to identify the source of the problem when the licenses on these machine were inaccessible. Now an appropriate error message is generated.
LDK-9948  Rehosting of an SL Legacy key to a different machine would fail with the return code HASP_CLONE_DETECTED.
LDK-10273 Admin Control Center would allow a license to be detached even though the termination date for the detach was invalid.
LDK-10564 The Vendor ID for a Master key was not the same in Admin Control Center pages and in the Diagnostics Reports.
LDK-10857 When an iSCSI disk was connected to a Windows physical machine, the License Manager would regard the machine as a virtual machine.
LDK-11478 After Run-time Environment v.7.32 was installed, running an application that was protected with Sentinel HASP Envelope (prior to Sentinel LDK 6.3) would cause a Stop error (BSoD).
LDK-11787 Under certain circumstances, the Licensing API function hasp_get_info would always return a value of 0 as the value for <updateCounter> for an SL license. Now the function returns the correct value for <updateCounter>.
LDK-11825 Admin Control Center was not able to display an invalid HL key. Now such a key is visible in Admin Control Center with an indication that the key is not valid.
LDK-12196 When an SL key is installed on a machine with Run-time Environment 7.32 or 7.3, the Run-time Environment would continually open additional handles.

Enhancements in Version 7.32

Reference Description
LDK-6934 Sentinel LDK Run-time Environment now supports the Sentinel HL Drive microSD key (patent pending). This key has been tested with the following microSD cards:

  • Sandisk: 16 GB, 64 GB
  • Transcend: 16 GB, 64 GB
  • Toshiba: 32 GB
  • Samsung: 64 GB
  • Kingston: 64 GB, 256 GB, 512 GB
LDK-10090 Run-time Environment is now supported under Windows 10 Technical Preview Build 10041.

Issues Resolved in Version 7.32

Reference Description
LDK-9325 Given the following circumstances:

  • An SL key contains a Feature that allows concurrency but does not allow virtual machines.
  • The SL key is installed on a physical machine.

When the SL key is displayed in Admin Control Center on a second physical machine, the Feature is shown as «disabled». However, a protected application that includes that Feature operates correctly.

LDK-8862 When attempting to access a remote License Manager, Sentinel Admin API would return the incorrect error code SNTL_ADMIN_LM_NOT_FOUND (6002).
LDK-7237 Given the following circumstances:

  1. A license with concurrency is installed on a Sentinel protection key. The count criteria is «Per Login».
  2. Protected applications that consume seats from the license are started.
  3. While the applications are active, the license is updated to change the count criteria (for example, from «Per Login» to «Per Process»).
  4. One or more protected applications are closed.

The Login count for the license would no longer match the number of actual applications active.

As part of the resolution for this issue, when the count criteria for a network license is modified, all active sessions are automatically terminated.

Enhancements in Version 6.65

Reference Description

The template for customizing entries for the Access log in Sentinel License Manager has been enhanced.

  • A new log element (functionparams2) is available.
  • Tags for special characters that could not be used in the template until now are provided.
  • Existing elements (sessioncount, logincount, loginlimit) that did not provide reliable results have been corrected.
  • The following events are now logged correctly: session timeout, orphaned session logout, manual disconnect, AdminAPI disconnect.

In addition, the template is now used for log entries generated by Embedded License Managers and External License Managers.

For information on the log template, see the Edit Log Parameters screen and related help screen in Admin Control Center. (Click the Edit Log Parameters button from the Configuration — Basic Settings screen.)


Admin Control Center now enables the user to generate a C2V file without the requirement of installing the RUS utility. This is supported for Windows, Mac and Linux platforms. The following limitations apply:

  • HL Basic keys are not supported.
  • C2V files fetched from HASP HL and Sentinel HL (HASP Configuration) keys will not work with Business Studio.

The C2V file can be generated for locally-connected Sentinel HL, HASP HL, and SL AdminMode keys.

Issues Resolved in Version 6.65

Reference Description
LDK-7893 The License Manager would fail when it attempted to scan more than 128 remote servers. The message “Failed to begin fridge transaction:327683” was displayed.
LDK-7084 The hasp_get_info() function in the Licensing API did not return consistent results for localhost when no IP address set in etc\hosts file for localhost. The function would return either localhost( or IPv4. To resolve this issue, the Licensing API must be upgraded to version 7.3 or later and the Run-time Environment must be upgraded to version 6.65 or later.
LDK-5710 When the real-time clock battery in a Sentinel HL (Driverless configuration) keys is exhausted, the error code returned by the hasp_login or hasp_login_scope function was HASP_INT_ERR instead of HASP_NO_BATTERY_POWER.
LDK-5390 If hasplms.exe is locked at the time the user attempts to upgrade the Run-time Environment, a misleading error message was displayed. The error message now provides an appropriate description of the issue.
LDK-8895 When an activated SL-Legacy license is installed on a machine that contains Products that have clone protection disabled, and a user then attempts to detach a license, error 64 (clone detected) was generated. Now a license can be successfully detached.
LDK-8936 Installation of certain third party tools would cause the removal of a symbolic link from Hardlock drivers. As a result, HL keys would become inaccessible.

>Issues Resolved in Version 6.64

Reference Description
LDK-6857 A compilation error would occur when the RTE 6.62 haspds.msm merge module is used with a WIX-MSI installer.
LDK-7030 A Stop error (BSoD) would occur when the customer applied a V2C on a machine with a dynamic disk.

Issues Resolved in Version 6.63

Reference Description
LDK-6642 A Stop error (BSoD) was reported with certain flash drives (if connected).

Issues Resolved in Version 6.62

Reference Description

After an end user installed Sentinel LDK Run-time Environment v.6.61, applications that are protected using older versions of HASP4 or Hardlock would not start. Applications that are protected using older versions of HASP4 or Hardlock, or that use older versions of HASP4/Hardlock API would display the message: Driver version mismatch.

These issues existed under the following circumstances:

  • These issues existed only with HASP4 API version 8.x or earlier or Hardlock API version 3.83 or earlier.
  • These issues do not exist with the Sentinel LDK API library that also supports the HASP4 and Hardlock API.

Support for legacy HASP4 and Hardlock APIs has been restored in Sentinel LDK Run-time Environment v.6.62.

Enhancements in Version 6.61

Reference Description
LDK-3483 Admin Control Center now correctly displays information regarding Sentinel HL Board
LDK-3366 The Local License Manager is now more resistant to potential sources of corruption, such as power failure.
LDK-2877 Cloned SL-AdminMode keys are now correctly identified by the License Manager and become inaccessible. As soon as the cloned keys or machines are removed, the single remaining key is automatically be re-enabled.
LDK-3129 Support for SL keys under VM live migration solutions is now provided.

Issues Resolved in Version 6.61

Reference Description
LDK-4821 Protected application with encrypted swf would not start under Windows 8.1 32-bit. The message «Error E0025 — unknown error» was returned.
LDK-4787 Documentation has been corrected to state that it is not possible to install vendor-specific SL-UserMode V2C bundled in a branded Run-time Environment.
LDK-4543 When a Feature that is disabled for virtual machines is installed on a virtual machine, the Run-time Environment did not return the usable tag as false.
LDK-4533 Memory leaks in the Sentinel Licensing API have been resolved.
LDK-3970 When a Provisional SL-Legacy license is installed on a machine with Run-time Environment v.6.60, its Product names were not displayed in Admin Control Center.
LDK-3283 The License Manager would require several minutes to load when Flash Media Bay Reader is connected to the system.
LDK-3255 A Stratus server would stop responding during synchronization when the Run-time Environment is installed.
LDK-3092 The Sentinel Admin API function sntl_admin_get would not filter information correctly based on scope template for feature/machine/user tags (Feature ID, computer name or IP address, License Manager user name).
LDK-3005 In Admin Control Center, an inconsistency existed regarding the display of «allow=all» in «Users» and «Access from Remote Clients» restriction tabs of the Configuration page.

Under Windows 8.1 (x86 platform), the Hardlock driver would not detect NtTerminateProcess and NtTerminateThread SST indexes. As a result:

  • When starting a protected application, the Secure Channel Communication error (H0046) would occur.
  • A Stop error (BSoD) would occur.
LDK-2975 When SkyRecon StormShield Agent version 5.6 is present on a computer, installation of the Run-time Environment would cause the operating system to crash.

Enhancements in Version 6.60

Support has been added for Windows XP Embedded and Window 7 Embedded.

Issues Resolved in Version 6.60

Reference Description
LDK-2119 After cancellation of an SL AdminMode license on a machine, Features would disappear from other Products and become unusable.
189473 Under certain circumstances, the License Manager would fail with HTTP scanners.
LDK-1892 For a «6to4» IPv6 address, network licenses would not be available (disconnect from the NetKey) after a short period. Now the License Manager scans the network interfaces to detect local IP addresses, similar to the RuntimelessAPI. The License Manager no longer asks for the DNS.
LDK-1683 Product names displayed in Admin Control Center were different from the names specified at creation time. Product names are now handles as follows:

  • Names provided within a license container (for example, a V2C file) are valid just for that container.
  • Names provided manually in a vendorid.xml file always override those container names, retaining backward compatibility (for examples, for translations)
  • vendorid.xml files are never overwritten by the License Manager, so different names for licenses on different machines are no longer mixed up
LDK-2052 When the login to a Feature would fail, the log file would not contain the username, hostname, FeatureID (and haspid, if specified in scope) .
LDK-2718 Under certain circumstances, Sentinel HL (Driverless configuration) keys did not appear in Admin Control Center.
LDK-1965 Under certain circumstances, a protected application under Windows 7 would cause a «Key not found» error.
LDK-2235 False positive VM detection would occur on a physical machine that had a Hyper-V virtual machine. 
LDK-2107 A reference finger print would not contain the NIC_UID value when the NIC address has an OUI (Organizational Unique Identifier) value of “00:50:56:XX:YY:ZZ” OR “00:05:69:XX:YY:ZZ”. These OUIs (“00:50:56” OR “00:05:69”) are assigned to VMWare, and are used by VMWare when the NIC address for a VM guest m/c is manually generated.
LDK-1175 Intermittent H0043 errors would occur when a USB camera was connected to the machine.
LDK-2564 Under certain circumstances, the bundled RTE installer created using Sentinel EMS would fail.
LDK-1194 Under certain circumstances, termination of a protected application would cause a Stop error.
LDK-2502 When using RTE version 6.56: After logging off and then logging on to the machine, a HASP 4 key was not detected.
LDK-2240 Under Windows XP, when installing haspdinst v.6.51 or 6.55 on an HP 8200 ELITE SFF machine, a stop error would occur.
LDK-2074 The RTE installer would not add the registry entry “HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers» if it was not present. As a result, end users would received Error 16 (Inconsistent Filesystem Structure) errors during RTE installation.
LDK-2034 Licenses that were installed with a bundled RTE were not visible in Admin Control Center if a branded RTE had been first uninstalled and then uninstalled.
LDK-2428 When a proxy server is used, Admin Control Center was not able to obtain language packs automatically.
LDK-3014 When no HL key is connected to a machine, the driver package version was shown as as 0.0.

Issues Resolved in Version 6.56

Reference Description
170463 When the user attempted to install Microsoft Office 2010 on a computer that contains the Run-time Environment, the installation would fail and display an «Error 1046» message.
185897 Run-time Environment v6.55 would not recognize a HASP HL key with Firmware v2.16. The key would not be displayed in Sentinel Admin Control Center.
186197 When an application is protected with «Enable data file encryption» selected in Sentinel LDK Envelope, and file extensions are added in the filter, it was not possible to save the encrypted files to a network location.

Issues Resolved in Version 6.55

Reference Description
MKS177499 Under Windows 7 64-bit, protected application process would not exit from the Task Manager after closing.

A Stop message (BSoD) would occur while running a DataHASP protected application when Norton Internet Security is installed.


A delay would occur in obtaining the current remaining executions count when using the Licensing API hasp_get_sessioninfo() call soon after the hasp_login() call.

MKS177029 The NX flag for hasplms.exe was not enabled.
MKS178460 LM ID content of the LM Server whose information has not been refreshed for a long time would not be shown when more than 512 LM servers exist
MKS168507 If the HL key was changed while a machine was sleeping, then afterwards the License Manager would show that the original HL key is still present. The new HL key would not be recognized and would not work
MKS175770 hasplms.exe would crash and record an Access Violation error in the system log

Issues Resolved in Version 6.50

Reference Description
MKS160209 When installing the Run-time Environment under Windows Server 2008 x32 JP, the system would crash
MKS170889 Irrelevant «func_0» entries have been removed from the Admin Control Center access log
MKS167561 When using «Aggressive Search» in Admin Control Center, if you enter the machine’s own name in the search parameters, the License Manager would fail to detect the local keys.

Issues Resolved in Version 6.27

Reference Description
MKS159048, US159048 SL licenses are now supported on dynamic disk.
MKS153313 Under certain circumstances, when installing the Run-time Environment on a computer connected to a specific Fiber-Channel controller,  a Stop Error (BSOD) would occur.

Issues Resolved in Version 6.25

Reference Description
US157306 Known compatibility issues are now listed in the Run-time Environment readme file.
US126998, CASE1335 When the end user applied an update for one Product, multiple unexpected Products were added in the Admin Control Center. In addition, when the ISV checked in a C2V file from the end user, duplicate Features relating to the Product were added in Business Studio.
US150843, MKS132920 Expired detached licenses would continue to be displayed in Admin Control Center for 7 days. You can now customize Admin Control Center to display these licenses for 0 to 9999 days. In the hasplm.ini file, add or locate the parameter commuter_delete_days = and assign it the number of days to display expired licenses. If you specify 0, an expired detachable license entry is deleted within a few minutes after it expires
US148372, MKS142453 When a computer with an active protected application and attached HL was set to hibernate, and the HL key was then detached, the computer would freeze upon being restarted.
US153304, MKS152843 An error would occur when running an RTE installer that includes a Provisional Product.
MKS154755, 154375, 153944, 152449, US158710 hasplms.exe would fail, sometimes showing an Access Violation error in the system log
MKS147694 When a modification is applied to decrease the concurrency count, it was still possible to extend the duration of detached licenses even though the number of detached licenses exceeded the maximum allowed.
MKS147644 The License Manager would lose track of the number of detached licenses for a given Product when a modification is applied to add a new detachable Feature.
US144668 Under Windows XP, a protected application that is linked with Runtime API v.5.0, and is running in Run-time Environment v.5.95 or later would fail with «Communication Error 33» after several hours of activity
Ref #8033 If you attempted to update the Sentinel HASP Run-time, and your protected application uses DataHASP, it was necessary to close the protected application before running the update. (Resolved in version 6.22
MKS146944, 147038 The License Manager would eventually lose track of the number of detached licenses for a given Product if the number of available licenses for that Product was changed to a value lower than the number of licenses currently detached. (Resolved in version 6.23)

Enhancements in Version 6.23

Reference Description
  The Run-time Environment contains a number of enchancements to support Sentinel LDK (the next generation of Sentinel HASP).
  A number of minor issues reported in the Run-time Environment have been resolved.

Issues Resolved in Version 6.23

Reference Description
Ref #8033 If you attempted to update the Sentinel HASP Run-time, and your protected application uses DataHASP, it was necessary to close the protected application before running the update.
MKS 146944, 147038 The License Manager would eventually lose track of the number of detached licenses for a given Product if the number of available licenses for that Product was changed to a value lower than the number of licenses currently detached.

Enhancements in Version 6.22

Reference Description
  Sentinel LDK Run-time Environment contains a number of enchancements to support the next generation of Sentinel HASP
  A number of minor issues reported in Sentinel HASP Run-time Environment have been resolved.

Issues Resolved in Version 6.22

Reference Description
Ref #8033 If you attempt to update the Sentinel HASP Run-time, and your protected application uses DataHASP, ensure that the protected application is not running before running the update

Issues Resolved in Version 4.02-4.95

Reference Description

V4.95 June 19, 2003

New Features

Signed for Windows Server 2003

Problems Solved

Case TD 966
HASP4 Time ID problem solved.

Case TD 981:
Using devise driver and API with contention enabled, with some printer
drivers, it is not possible to access a key that is connected to the
same port after a print job is executed.

Known Limitations
The -sourcepath installation switch is not supported in this release.
The -sp switch should be used instead.

V4.92 May 2003

New Features

Security enhancements, especially when used in conjunction with API v8.01.

By default parallel port contention handling is enabled.

Enhanced handling of simultaneously connected USB keys having the same

On Windows Server 2003, data protection (DataHASP) is by default

Problems Solved

Case 15940:
The Hinstall added needless registry entries.

Case 3750:
DataHASP applications executed with Norton Antivirus running in the
background crash the system.

V4.85 November 2002

New Features

Support for HL_Server USB

Problems Solved

Case 310669:
WriteBlock on HASP PCMCIA failed sometimes when simultaneously
accessing a second HASP PCMCIA.

Case 310670:
When using a parallel key at a printer port running on 3.3 volts,
the key was occasionally not found, especially multiple keys were daisy-chained.

Case 310671:
Potential deadlock with USB keys when simultaneously using
HL_PORTINF() in different threads.

V4.81 October 30, 2002

Problems Solved

Case 310655:
USB key isn’t found after uninstall and reinstall while no key is

V4.80 October 14, 2002

New Features

Enhanced security

V4.75 May 21, 2002

Problems Solved

Case 310635:
Wrong HDDVersion structure in driver install DLL.
Please make sure to use latest headerfile hiapi.h

Case 310633:
Driver install DLL replaces aksusb.sys even if latest drivers are installed.

Case 310623:
New driver install mechanism fails on Windows 2000.

Case 310634:
HASP-Hardlock interference.
Concurrent usage of HASP and Hardlock parallel keys is blocked.

Case 3744:
HDD 4.70 does not install properly under some Windows 2000 and Windows XP PCs.

Case 310633:
Background checks fail after power mode Standby and Hibernate

V4.70 November 21, 2001

New Features

New WinXP Microsoft signed driver akspccard.sys ver 1.01 to support
PCCard under WinXP.

Problems Solved

Case TD #600:
while accessing the PCCard detaching the card generated a blue screen.

V4.65 November 21, 2001

New Features

The new device driver fully supports Windows XP,
including WHQL driver signature.

Problems Solved

Case 3726:
Dos enveloped application cannot access USB key.

Case 3730:
Some notebook with IrDA port running Win98 can’t find parallel HASP

V4.50 September 2001

Support for Windows XP.
This driver supports Windows XP. It is not signed by MS.
Installation procedure is usual.
When connecting a HASP USB to the computer, XP prompts you with
a warning that the driver is not signed. Click on the NEXT button and
then on the CONTINUE ANYWAY button.

Problems Solved

Case 9357:
DataHASP does not work when all partitions are NTFS, and the PC has no
floppy drive.

V4.35 May 2001

New Features

HASP4 Time USB support:
This driver version includes support for the new HASP4 Time USB keys. Please
note, that you need to unplug all USB keys under Windows 2000 in order to unload
the old driver. The new Aladdin USB driver will be loaded after driver installation
automatically if the first key is plugged.

HASP36 support:
Implemented support for HASP36 keys attached to an IBM compatible PC. Please note,
that HASP36 keys attached to NEC machines are not supported.

Popup on key removal:
The usual message box if a USB device is disconnected under Windows 2000 will
not be displayed anymore,

V4.25 (HASP CD Rel 10.0)

New Features

HASP keys connected to PCI parallel cards registered to the system will
be found on Windows 95/98/ME systems,
because drivers search all LPT ports.

ReadBlock and WriteBlock services on HASP USB keys are handled 40% faster.

Aladdin USB Support for Windows NT4. Since Microsoft Windows NT4 does not
support USB devices, Aladdin provides you this functionality with an
additional set of drivers using a proprietary USB stack.
The stack is available on a separate CD. Please contact your HASP sales

Problems Solved

Case 3713:
Running DOS RUS tools on Windows 98/ME caused reboot.

Case 5402:
Setting LptNum value to a non existing LPT port caused a blue screen.

Case 3692:
HASP PCCARD was not found after Windows 2000 hibernate.

Case 3709:
Application protected with both API function and envelope (using Data HASP)
caused a blue screen after starting it several times.

Case 5677:
USB HASP4 keys without memory were not recognized by HDD 4.12

V4.12 (HASP CD Rel 9.0)

New Features

HASP keys connected to PCI parallel cards registered to the system will
be found on Windows NT4 and Windows 2000 systems,
because drivers search all LPT ports.

Installation switch HI_PORTDELAY is not used anymore, drivers include
automatic speed calibration instead.

NEC type parallel port is not supported anymore. Please use HDD V4.06
in case you are using a NEC type parallel port.

Problems Solved

Driver problems on SMP computers (e.g. dual Pentium) fixed.

Case 3701:
HASP4 Time keys returned incorrect values under some conditions.

Case 3676:
Listed available options for all switches in help window of hinstall.exe.

Case 3697:
InstallShield 5 sample now is correctly recompiled using the latest
driver install DLL.

V4.06 March 25, 2000

new switches for parallel port configuration:

— controlport set control port registers
— ecpdmaint disable ECP-DMA-Interrupt

Problems Solved

HASP not found on Windows 2000.
Printing disturbed on Epson Stylus Pro 9000 after HASP key access

V4.02 (HASP CD Rel 8.0)

New Features

The new device driver fully supports the new HASP4 family of
HASP keys.

We further enhanced support for ECP printers. Please refer to the
descriptions in the HDD.HLP file for:

— ecpretry
— portallocfunctionality
— portallocretrycount

For more about the HASP Device Driver custom API and HINSTALL,
refer to the HDD.HLP file.

Problems Solved

Case 3512:
Calling a HASP key while printing from an HP LaserJet 4050TN and
several HP OfficeJet models caused the printer to be reset or
output garbage. This is resolved in version 3.9x of the HASP Device Driver.



Copyright © 2018 Gemalto. All rights reserved.