Resolved Issues

Under certain circumstances, an application would fail when attempting to log in to a feature on an HL Net key.

Relocation issue of TLS data by LDR in Windows V3 Envelope.

Issue with exception handling in an imported function by Windows V3 Envelope

Launch issue with Springboot JAR (version > 2.7) on Linux x86 by Envelope Java-Class

Protection engines V3 and WinNG did not support x86 PE files with the latest VS CFG /guard:cf.

A false pending update was returned to Sentinel LDK for newly-activated SL keys.

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.

Java method-level protection and background checks did not work with JDK 20 and JDK 21.

Incompatibility of API/Envelope and API/EnvelopeRuntime samples in x86 mode

A protected application with data file protection would show significant delays during initialization with video playback when using MapView.

Issue where Windows Shell protected application could not be executed when located on a network drive.

Under certain circumstances, a Python script protected with Script Envelope would fail to run.

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.

ByRef-like parameters should be excluded by .NET Envelope.

Issue with encryption of newly-created .py files by Script Envelope.

Import failure for encrypted libraries after fork.

An application with V2 data file protection would, under certain circumstances, generated an unencrypted file when copying an encrypted file.

Debug directory pointer issue by Windows V3 Envelope

Envelope KEEP_DEBUG_INFO was not enabled for mixed (x86 and x64) .NET executable files.

A protected MP4 file could not be played due to a failure of sequential read for the encrypted data file.

Overriding generic methods in generic tem

plates would emit incorrect member references.

An issue would occur with refreshing when loading and protecting several .NET dlls from an Envelope project.

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.

In LDK 9.0, a .NET application using a DLL protected with Envelope using the V3 engine was unable to catch an unhandled exception.

A binary that was protected using Envelope with the V3 engine would randomly failed with the message "Integrity Check failed!".

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.

Exclude local network addresses from using the proxy.

Now the proxy configuration is not used if the destination address is a local one.