# Sentinel® LDK and Sentinel HASP® Run-time Environment Installer GUI for Windows: Readme

## Version 7.41

### October 2015

This document provides information regarding the Run-time Environment Installer GUI for Sentinel LDK and Sentinel HASP, including supported operating systems, enhancements, known compatibility issue, and issues resolved. ("Sentinel LDK" is the next generation of Sentinel HASP.)

The following topics are discussed:

- Operating Systems Supported
- Upgrading the Run-time Environment
- Installing the Run-time Environment
- Issues Resolved in This Release
- Revision History
- Known Issues - Run-time Environment

## Operating Systems Supported

- Windows XP (X86) SP3
- Windows XP (X64) SP2
- Windows Vista SP2
- Windows 7 SP1
- Windows 8.1 SP1
- Windows 10
- Windows Server 2003 SP2
- Windows Server 2008 SP2
- Windows Server 2008 R2 SP1
- Windows Server 2012 R2
- Windows 7 SP1 Embedded standard (x86)

The operating system versions listed in this section were tested by SafeNet and verified to be fully compatible with Sentinel LDK. Older operating system versions are likely to be fully compatible as well, but are not guaranteed. For reasons of compatibility and security, SafeNet recommends that you always keep your operating system up to date with the latest fixes and service packs.

Back to Topics

## Upgrading the Run-time Environment

When using the Installer GUI to upgrade the Run-time Environment, ensure that:

- No other Run-time Environment Installer is active.
- No other Run-time Environment components are active. Although the installation program terminates applications that are accessing the Run-time, it does not terminate running services. For example, if the Sentinel License Manager is running as a service, you must stop the service before upgrading the Run-time Environment.

Back to Topics

## Installing the Run-time Environment

- The Installer GUI detects the version of the operating system during Run-time Environment installation, before installing the relevant drivers.
- By default, Windows Vista (and later) operating systems display a User Account Control message during driver installation. The user must click Continue to continue the installation. Alternatively, the user can change the default setting from the Control Panel of their operating system.
- A log file of the installation process is written to aksdrvsetup.log in the Windows directory.

Back to Topics

## Issues Resolved in This Release

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).

Back to Topics

## Revision History

### 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: A license with concurrency is installed on a Sentinel protection key. The count criteria is "Per Login". Protected applications that consume seats from the license are started. While the applications are active, the license is updated to change the count criteria (for example, from "Per Login" to "Per Process"). 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
--- | ---
LDK-4468 | 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.)
LDK-735 | 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-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(127.0.0.1) 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.

Back to Topics

## Known Issues - Run-time Environment

Reference | Description
--- | ---
12506 | Sentinel LDK communicates via TCP and UDP on port 1947. This port is IANA-registered exclusively for this purpose. At the end user site, the firewall must be configured so that communication via this port is not blocked.
180256 | When a computer names contains UTF-16 characters, Admin Control Center displays the short name for the computer (similar to Windows Explorer). Similarly, the sntl_admin_get function in Admin API returns the short name.
182646 | After Windows 7 is upgraded to Windows 8, the user is not able to use existing SL licenses or to install new SL licenses. Workaround: After you upgrade from Windows 7 to Windows 8, reinstall the Run-time Environment.
LDK-2471 | Sentinel Licensing API: On a computer with the Nvidia chip set GeForce 7025/nForce 630a, and where the CPU is AMD Athlon 64 X2, the hasp_read and hasp_encrypt functions may fail with error 39, HASP_BROKEN_SESSION. This problem only exists with HASP HL keys with Firmware version 3.25. Workaround 1: On the computer described above, when error 39 is returned, call the hasp_read or hasp_encrypt function again. It is not necessary to call hasp_login again. Workaround 2: Use Sentinel HL keys with Firmware version 4.2x.
LDK-8480 | With some new USB chipsets, it is possible that the API hasp_update() call, used to update the firmware of Sentinel HL keys to version 3.25, will generate the HASP_BROKEN_SESSION return code, even if the firmware is correctly updated. (This issue does not occur with Sentinel HL Driverless keys with firmware version 4.x.) Workaround: Install the latest Run-time Environment. The automatic firmware update feature of the License Manager will automatically update the firmware of the key the first time that the key is connected, without the need to call hasp_update().
LDK-11418 | For a Java 7 or Java 8 application that is protected with Envelope, the end user must use the following flag when launching the protected application: For Java 7: Specify -usesplitverifier For Java 8: Specify -noverify If the appropriate flag is not specified, the application may throw java.verifyerror when launched.
LDK-12145 | 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 is not able to decrypt the protected data file, no error message is generated to explain why the file cannot be opened.

Back to Topics

Copyright © 2015 SafeNet, Inc. All rights reserved.

DocID 118r Revision 1509-1