Bug fixes

DriveLock 2024.2 is a major version.

This chapter contains information on errors that have been fixed with DriveLock version 2024.2. Our External Issues (EI) numbers, if available, serve as a reference.

Please note that some issues may cause a change in product behavior when you install the update. Before updating, make sure to check your settings to see if your existing environment is affected. The issues are labeled with the following icon

	Application Control (AC)
	Filters for application behavior control and application lists ending with a backslash, followed by wildcards, incorrectly matched files in child directories. For example, c:\test\* matched c:\test\subdir\readme.txt. To match all files in all child directories, the filter must be c:\test\ or c:\test\*\. This is a behavior change: filters are now evaluated correctly!
	If application behavior rules were saved in the DMC without selecting the 'Filters' tab, command line parameters were not saved, and changes to the target were not applied.
	The timing of rule evaluations has been improved to prevent longer-running checks from slowing down others.

Application Control (AC)

Filters for application behavior control and application lists ending with a backslash, followed by wildcards, incorrectly matched files in child directories. For example, c:\test\* matched c:\test\subdir\readme.txt. To match all files in all child directories, the filter must be c:\test\ or c:\test\**\*.

This is a behavior change: filters are now evaluated correctly!

If application behavior rules were saved in the DMC without selecting the 'Filters' tab, command line parameters were not saved, and changes to the target were not applied.

The timing of rule evaluations has been improved to prevent longer-running checks from slowing down others.

	BitLocker Management (BLM)
	When decrypting BitLocker-encrypted partitions, events were sent without specifying any data. This resulted in an error message in the DES log file.
	The menu item "Encryption" in the DOC Security Controls was not displayed if you only had BitLocker licensed.
EI-2787	When restricting the BitLocker password to numbers or numbers and Latin letters, dictionary files could not be used because the option was grayed out.
	After resuming a delayed encryption, it was possible that external hard disks were also encrypted.
EI-1611	The uninstallation of the DL-PBA was incomplete under certain circumstances, despite the corresponding assigned policy, making it impossible to uninstall the DriveLock Agent.

	Defender Management
EI-2790	Fixed an issue with transmitting the detected threats to the DES.

	Device Control
	Fixed an issue that made the content search for files in rar archives unreliable.
	If the 'Allow authorized user login' option is enabled for a usage policy, the currently logged in user can only accept the usage policy (without specifying another account) if they are also listed in the list of authorized users. This is a change in behavior. If the logged-in user is to be able to accept the usage policy, they must be entered in the list via the 'Authorized users' option.
	If the usage policy is configured with the option 'Launch self-service unlock after accepting usage policy', but the accepting user does not have authorization for self-service unlock, the usage policy can now simply be accepted without starting the self-service unlock. This is a change in behavior. If you want to specify users who are allowed to accept the usage policy, you can enter them in the list using the 'Authorized users' option.
EI-2682	In the DMC, when browsing for COM ports (Devices -> Device class locking -> Serial ports (COM) -> Ignored port devices), the ports available locally (or on an agent connected via remote control) were not listed. PCMCIA adapters would have been displayed instead, if available.
	The Linux agent can now be installed on the SUSE Enterprise desktop.
	The Linux Agent now reports composite devices with the correct hardware ID for all interfaces. Please check your already configured device rules and use wildcards ('') to map all interfaces of a device, e.g.: USB\VID_1234&PID_1234&REV_0001.

Reference	Disk Protection
	Fixed an issue in the user-related agent settings where the display of Disk Protection logon notifications did not work correctly.
	A successful emergency pre-boot logon (event 503) was not logged.

Reference	DriveLock Agent
	The settings for the push installation of the agent via a linked DES were read from the central DES.
EI-2779	The content scanner has blocked some valid DOCX files.
EI-2768	It was not possible to control external drives with serial numbers on the macOS Agent.
	In some configurations, the agent sometimes tried to start a blocked device, which led to unnecessary events.

Reference	DriveLock Enterprise Service (DES)
	The maintenance settings of clients are now correctly evaluated per client.
EI-2678	A scheduling problem in connection with summer time has been fixed.

Reference	DriveLock Management Console (DMC)
EI-2726	Events 704-706 have been moved to a more appropriate event category (Device events instead of Temporary unlock).
EI-2709	The option to select a file from the application inventory was also offered if no application inventory was available.
	If a policy in the new format was created with a policy in the old format as a template, the new policy was empty.
	Removing the default restore settings from a policy did not work.

Reference	DriveLock Operations Center (DOC)
EI-2777	In the DOC, any duplicate spaces in the event properties were replaced with a single space in the parameters, so that after copying and pasting, for example, ProductIDs, they could not be used correctly in rules.
EI-2720	In the detail view of computers, the "Definition" tab in the "Group memberships" window has been renamed "Static group definitions" to avoid confusion.
EI-2772	An error in the listing and correct counting of objects has been fixed. This error could occur with restricted DOC user authorizations (for OUs or groups).
	Under certain circumstances, taking over a report from another user could lead to a loss of the report settings.
EI-2750	Notifications in the DOC did not work for third-party events, although they could be configured.

Reference	DriveLock Setup
EI-2640	On Windows servers, some Windows files remained changed after uninstalling the DriveLock Agent when MTP device control was enabled.

Reference	Encryption 2-Go
EI-2714	The length of the entered drive label for enforced encryption was not checked. As a result, the encryption process could not be completed when more than 11 characters were assigned.

Reference	File Protection (FFE)
	Compatibility problems occurred when locking regions of files on network shares. For more information, see the known issues and notes for File Protection.