Resolved Issues
Service Pack: 10.0.300
The following issues that were reported by vendors were resolved in this service pack.
Reference | Resolved Issue | Components |
---|---|---|
SM-158283 | It was not possible to clear the cloned status successfully more than once for same SL key. | LDK-EMS |
SM-177036 | After a login logo was uploaded in the UI Branding section of Sentinel LDK-EMS: The login logo was displayed in the Customer Portal instead of the application logo. | LDK-EMS |
SM-179528 | Vendor Key License Transfer Tool UI displayed "Gemalto" instead of "Thales". | Vendor Tools |
SM-184671 | A protected MP4 file could not be played due to the failure of a sequential read for encrypted data files. | Envelope |
SM-185101 | An Issue would occur when fetching local license data when the Internet is disconnected. | LIcensing API |
SM-186342 | Sentinel LDK-EMS was not able to send e-mails with Mdaemon on a Windows server. | LDK-EMS |
SM-187375 | Performance would deteriorate when trying to retrieve certain combinations of data. | LDK-EMS |
SM-188969 | Script Envelope was not able to find imports in a subfolder. | Envelope |
SM-190032 | In RTE 10.13, ACC web pages were unusable after invalid "user restrictions" input. | Run-time Environment |
SM-190046 |
Enforcement data was not encrypted. |
Envelope |
SM-190097 | Certain .NET applications would fail with no error message when background check was enabled. | Envelope |
SM-190492 | Certain .NET standard applications were obfuscated incorrectly. | Envelope |
SM-190748 | Under certain circumstances, protected .NET8 applications would fail without trace at runtime. | Envelope |
SM-190801 | Retrieving all configuration settings, did not return the multiple_session_per_identity and multiple_detach_per_identity. | Licensing API |
SM-191025 | Data file protection hooks would not cover functionality implemented directly in ntdll such as IO thread pools. | Envelope |
SM-191388 | Under certain circumstances, access violations were generated on protected applications. | Envelope |
SM-191673 | Under certain circumstances, the wrong CLR version was bound to Envelope after a .NET program was protected by Windows shell. | Envelope |
SM-191764 | A detach operation succeeded, but the client machine was not listed in the Registered machines list. | Run-time Environment |
SM-191911 |
Given the following circumstances: >You are protected a program with dynamic runtime. >The user's API path (in the Documents folder) contains multibyte characters. Envelope would fail to generate dynamic runtime in Chinese-Traditional systems with a Microsoft account. |
Envelope |
SM-192364 | Incorrect product names were shown in Admin Control Center when accessing remote licenses | Run-time Environment |
SM-192720 | Envelope would fail and input files' names would be changed due to incorrect handling of a Qt event. | Envelope |
SM-192948 | Envelope for Linux documentation stated "applications using the Spring Framework" when discussing Java applications that use reflection APIs. This has been changed to "applications running inside a web server (for example, tomcat)". | Envelope for Linux |
SM-193003 | A session with DieAtExpiration = true was not terminated at expiration. | Run-Time Environment/LMS |
SM-194472 | A misleading error message was generated when trying to create a Product/Entitlement with an invalid expiration date in LDK-EMS Web Services. | LDK-EMS |
SM-197801 | Relocation RVA was overlapped by both the TLS dir area and the TLS RawData area. | Envelope |
Service Pack: 10.0.200
The following issues that were reported by vendors were resolved in this service pack.
Reference | Resolved Issue | Components |
---|---|---|
SM-164976 |
Under certain circumstances, an application would fail when attempting to log in to a feature on an HL Net key. |
Envelope |
SM-171980 |
Relocation issue of TLS data by LDR in Windows V3 Envelope. |
Envelope |
SM-172025 |
Issue with exception handling in an imported function by Windows V3 Envelope |
Envelope |
SM-174142 |
Launch issue with Springboot JAR (version > 2.7) on Linux x86 by Envelope Java-Class |
Envelope |
SM-176031 |
Protection engines V3 and WinNG did not support x86 PE files with the latest VS CFG /guard:cf. |
Envelope |
SM-176205 |
A false pending update was returned to Sentinel LDK for newly-activated SL keys. |
LDK-EMS |
SM-176205 |
In Sentinel LDK 10.0, a change in LDK EMS web service behavior would occur , indicating that a license update was pending when no update was available. |
Envelope |
SM-176327 |
Java method-level protection and background checks did not work with JDK 20 and JDK 21. |
Envelope |
SM-176389 |
Incompatibility of API/Envelope and API/EnvelopeRuntime samples in x86 mode |
Envelope |
SM-177549 |
A protected application with data file protection would show significant delays during initialization with video playback when using MapView. |
Envelope |
SM-179402 |
Issue where Windows Shell protected application could not be executed when located on a network drive. |
Envelope |
SM-179660 |
Under certain circumstances, a Python script protected with Script Envelope would fail to run. |
Envelope |
SM-179936 |
A protected application would become unresponsive when operating on non-regular files (for example, FIFO files) after applying protection with the Data File Protection option enabled. |
Envelope |
SM-180573 |
ByRef-like parameters should be excluded by .NET Envelope. |
Envelope |
SM-180622 |
Issue with encryption of newly-created .py files by Script Envelope. |
Envelope |
SM-182015 |
Import failure for encrypted libraries after fork. |
Envelope |
SM-182131 |
An application with V2 data file protection would, under certain circumstances, generated an unencrypted file when copying an encrypted file. |
Envelope |
SM-182801 |
Debug directory pointer issue by Windows V3 Envelope |
Envelope |
SM-183854 |
Envelope KEEP_DEBUG_INFO was not enabled for mixed (x86 and x64) .NET executable files. |
Envelope |
SM-184671 |
A protected MP4 file could not be played due to a failure of sequential read for the encrypted data file. |
Envelope |
SM-185023 |
Overriding generic methods in generic tem plates would emit incorrect member references. |
Envelope |
SM-185043 |
An issue would occur with refreshing when loading and protecting several .NET dlls from an Envelope project. |
Envelope |
SM-185883 |
When an application has a large number of protected modules and threads, then threads * modules was able to exceed the number of total TLS slots (which is 1088). This would cause numerous problems, especially in COM. |
Envelope |
SM-186209 |
In LDK 9.0, a .NET application using a DLL protected with Envelope using the V3 engine was unable to catch an unhandled exception. |
Envelope |
SM-186211 |
A binary that was protected using Envelope with the V3 engine would randomly failed with the message "Integrity Check failed!". |
Envelope |
SM-188034 |
The message "Internal error 0x7102 occurred!" would occur when running a protected Windows native exe that has been signed. |
Envelope |
The following issues that were reported by vendors were resolved in this release.
Reference | Resolved Issue | Components |
---|---|---|
SM-158582 |
Under certain circumstances, an application that was protected with AppOnChip and that has access to both a local key and a network key would generate the error message: "A Sentinel key error occurred. Error 40". The application would then fail instead of continuing to operate using only the local key. |
Envelope |
SM-158980 | Windows V3 protection engine - The protected startup performance was significantly impacted by the protection key disabling feature. | Envelope |
SM-160265 | Scanning .NET methods for AppOnChip would sometimes cause Envelope to fail. | Envelope-.NET |
SM-160693 | When an application that was protected using the Windows NG protection engine runs under Windows 11, the application was not able to run in administrator mode. | Envelope |
SM-160897 | The title in the error message window for a grace period message was "Unknown error". | Envelope-.NET |
SM-161581 | The "Key not found" message was not shown when a license was not available during startup of the protected application. | Envelope-.NET |
SM-161827 | The character ";" would truncate the string of a proxy_password. | LDK Run-time/API |
SM-162414 |
Exclude local network addresses from using the proxy. Now the proxy configuration is not used if the destination address is a local one. |
LDK Run-time/API |
SM-162897 | [AoC] <APPONCHIP_MAPFILE> path should be relative to the prjx file. | Envelope-AppOnChip |
SM-164981 | The Entitlements grid was not sorted correctly after performing a search for entitlements. | Sentinel LDK-EMS |
SM-165522 | When a .NET executable was protected with Windows shell protection using the Windows NG engine: During execution, the executable would sometimes fail with "AccessViolationException". | Envelope-.NET |
SM-165536 | An exception occur when a protected mixed mode assembly(debug version) with method protection was executed. | Envelope-.NET |
SM-166961 | V3 Envelope runtime code did not execute hasp_dllmain() from its DLLMain function. | Envelope |
SM-167184 | When an application protected with the Windows V3 engine contained malformed Delphi export table entries, they were not handled correctly. | Envelope |
SM-167450 | Incorrect handling of type modifiers on .NET void return type would result in incorrect code generation. | Envelope-.NET |
SM-168845 | On the Edit Product page for Unlocked products, the Add feature option was removed. This has been restored. | Sentinel LDK-EMS |
SM-169115 | Java Envelope did not copy Linux and ARM-dependent files with the protected binary. | Envelope-Java |
SM-170106 | Rare compiler-generated, toplevel exported Types could not be imported. | Envelope-.NET |