# Enhancements and Issues Resolved in This Release

This section describes enhancements introduced and issues resolved in this release of the Sentinel LDK Run-time Environment.

### 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" />`