# Revision History

This section describes enhancements implemented and issues resolved in the last three major releases of Sentinel Run-time Environment.

The revision history for earlier versions of Sentinel Run-time Environment is available at: https://docs.sentinel.thalesgroup.com/ldk/LDKdocs/RTE_History/Default.htm

### Enhancements in Version 9.12

Reference | Description
--- | ---
SM-137293 | Sentinel LDK Run-time Environment and protected applications are both supported under Windows 11 ARM 22H2.
SM-137232 | Maximum idle timeout for sessions has been increased to 72 hours.
SM-134021 | Access to Sentinel Admin API can now be restricted so that it is only available for users from the local network. This can be enforced using firewall rules. Administrator-level requests would be allowed only on a specific port or network interface (or both).
SM-105690 | The License Manager now supports the new Sentinel Licensing REST API.
SM-104883 | The License Manager now accepts a V2C file to clear the the time-tampered status for an SL key.

### Issues Resolved in Version 9.12

Reference | Description
--- | ---
SM-134020 | Under certain circumstances, UDP packets may be lost. Broadcast search now repeats the UDP transmission multiple times to overcome the loss of UDP packets.
SM-136775 | The License Manager was not able to keep track of more than 2,000 clients' LM identifiers. This could result in incomplete information when listing detached licenses in the server Admin Control Center pages. The limitation of 2,000 LM identifiers has been removed.
SM-139869 | Previously, when a proxy was configured in ACC, the LM would attempt to resolve DNS names, even if they were not resolvable in the local network. This resulted in connection failures. Now, when a proxy is defined in ACC, the LM no longer attempts to resolve DNS names. Instead, it allows the proxy to handle DNS resolution.
SM-139963 | When a seat was detached from a license with no vendor name defined, the H2R file would contain invalid information in the vendor name field.
SM-140200 | Sentinel Admin API was not able to retrieve client identity information when the client identity was defined with multiple key IDs and admin_get was called using a specific key ID in the scope.
SM-141007 | If the session username contains the "&" character, the GetInfo function would report the value in the XML structure as specified, resulting in an invalid XML file. For example: `<session username="G&D" />` Now, the character is reported back as an XML entity. For example: `<session username="G&amp;D" />`

### Enhancements in Version 8.53

Reference | Description
--- | ---
SM-134244 | Sentinel LDK Run-time Environment and protected applications are both supported under Windows 10 22H2.

### Issues Resolved in Version 8.53

Reference | Description
--- | ---
SM-134170 | Given the following circumstances: 1.The vendor asssigned multiple key IDs in the Limit to Key ID field for a client identity on the license server. 2.The vendor sends the identity string for the client identity to the licensed user. After the licensed user applies the identity string on their machine, only one key ID is shown on the user's machine.

### Enhancements in Version 8.51

Reference | Description
--- | ---
SM-98674 | Sentinel License Manager now supports client identity registration on a user's machine when the user click a provided link. The License Manager Service can parse and decode the URL to copy the identity string to the local INI file.
SM-128094 | Sentinel Admin API can now be used to obtain a C2V file or fingerprint file from a user's machine.

### Issues Resolved in Version 8.51

Reference | Description
--- | ---
SM-122150 | The License Manager would fail on machines with a CPU from before 2010.
SM-123325 | The recipient list of detaches was incomplete when working with secure storage. (The list is complete when working with trusted storage.) Note: This issue did not affect functionality - it only affected the user interface.
SM-123370 | Certain errors would occur in the detection of Parallels VMs.
SM-124009 SM-130468 | The PMType2 clone detection scheme did not work correctly under certain unusual circumstances.
SM-126115 | The Admin License Manager would always checks the idle timeout, while the Runtimeless API never checks it. As a result, when installing or uninstall the RTE, conflicting behavior might occur for an HL Driverless key. Now, if the logged-in Feature on the key is not enabled for network access, idle timeout is skipped.
SM-127056 | The listing in Admin Control Center of products with detachable features did not paginate correctly.
SM-128810 | For Sentinel Licensing API, when a call to hasp_login_scope() fails, the event is now logged with the related feature_id, as was already occuring with hasp_login(). Until now, the behavior for the two functions was inconsistent.
SM-130023 | Errors in DNS resolution with client identity are now handled better.
SM-130889 | The License Manager Service was not able to access a cloud license manager hosted by Google Cloud Platform with proxy settings.
SM-131117 | In Admin Control Center, automatic detach was not taking friendly names for Feature and Product names.

### Enhancements in Version 8.43

No enhancements are included in this release.

### Issues Resolved in Version 8.43

Reference | Description
--- | ---
SM-120179 | The zlib library has been upgraded to version 1.2.12.
SM-121566 | During installation of Run-time Environment 8.41 on a machine with an old CPU, installation would fail with a message similar to: Error when starting the Sentinel License Manager service with parameters 1280 0 0. This is an internal error.
SM-123325 | In Admin Control Center, the displayed recipient list of detached licenses was incomplete when the Sentinel License Manager worked with Secure Storage. This issue would not occur when working with Trusted Storage. This issue did not affect functionality of the License Manager.

### Enhancements in Version 8.31

Reference | Description
--- | ---
SM-108300 | Admin Control Center help system now describes how to set a user name for the ACC administrator. Setting a user name helps to improve security for Admin Control Center. For details, open the Admin Control Center help. From the list of links at the bottom of the pages, click Configuration > Managing User Access to Admin License Manager Information > Setting a User Name for the ACC Administrator.

### Issues Resolved in Version 8.31

Reference | Description
--- | ---
SM-104739 | When the Windows user names includes non-unicode characters as in Korean and Chinese names, installing a rebranded RTE returns "EMSUrl.properties processing" error.
SM-102367 | In some cases, RTE installation would fail with error -536870329.