Resolved Issues
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 |