Bug fixes 2022.2

Certificate checking for predictive whitelisting has been improved.

Fixed an error when importing BitLocker management certificates into a policy.

When taking over existing BitLocker environments, it was possible that each time a policy update occurred, the BitLocker password was re-quested and re-set. This behavior was associated with the number of recovery keys that were entered for the system drive that was being being taken over.

When merging policies, string lists in the Defender configuration sometimes did not correctly overwrite string lists from other policies. If this behavior was desired, you must now set the "Append values" option in the string list.

Some external drives experienced a timing issue that resulted in a Blue Screen of Death (BSOD) error.

Fixed an error that caused device collections to stop working under certain circumstances in conjunction with old db3 CSP policies.

Fixed an error that the datAshur stick triggered at system startup.

The status of the hard disk self-monitoring (S.M.A.R.T.) is now read out correctly again.

Fixed an error where the agent crashed when an extremely long serial number was present in a drive collection.

During an update, the Windows Installer may not have replaced all DriveLock files, resulting in an inconsistent installation.

For file access events, the process was truncated at 128 characters.

Fixed an error where the agent crashed when there were multiple remote connections.

The character combination "\n" (e.g. C:\windows\system32\notepad.exe) is now displayed correctly in message texts instead of replacing it with a line break.

For some remote control events, the agent now sends error information.

The agent no longer crashes when the registration of the agent fails.

In some cases, the DriveLock service took a long time to start when no user was logged in.

Changes to ports in the Windows Firewall policy are now transmitted to the agent computer.

The Device Scanner Database tab is now only displayed if there is matching content.

Note: For new installations of DriveLock, this tab no longer exists.

When creating a new SB group, an endless progress bar came up, if there were no DriveLock groups in the environment at all.

In the RSOP, in "Policies applied", the DMC tried to open the Centrally Stored Policies in the GPO Editor instead of the Policy Editor, resulting in an error message.

The definition of dynamic groups can no longer be edited in the DMC starting with version 22.1. In spite of this, the definitions were deleted when you viewed the group properties, which made the group unusable.

The number of conditional setting nodes per node was limited to 15. However, it was still possible to add as many as you wanted per node in the DMC, but after that the policy could not be opened in the DMC anymore - it crashed. The limit has now been increased to 50, you cannot add more than 50, and if you open a policy (unlikely) that contains more anyway, it will no longer crash.

After updating to 21.2 or newer, it was not possible to customize the agent configuration via DMC for agents older than 21.2.

Requesting the agent's local whitelist in the DMC now also works if the process takes up to 2 minutes. Previously, an error was displayed after 15 seconds.

If you modify a widget after creating it or create a custom widget, some properties that are no longer supported will be displayed as obsolete when you refresh them.

Entering an incorrect password in the DOC login screen no longer results in multiple incorrect login attempts being registered in the AD. This could lead to a temporary account suspension.

Fixed an error when displaying the application control license for agents older than 21.2.

When creating a filter for the Windows/DriveLock version for dynamic groups in the DOC, you are now also given a drop-down list with predefined values.

When grouping by text or event ID, the ID or text displayed for third-party events sometimes did not match that of the event.

The drive list did not show any drives when the policy was opened with DOC Companion.

Information about the fact that a PBA that had previously been deactivated was active again was displayed repeatedly.

DriveLock Support Companion no longer crashes when collecting system information on Windows XP.

The user is now displayed in third-party events.

Some remote control events were missing parameters.

File Protection decryption did not always work on network shares when the folder was mounted and the encrypted folder was directly in the share.

An incorrect subscription end date was displayed when no Device Control license was present.

The settings for very detailed logging were not removed correctly.

After setting the remote ports of a firewall rule, they were correctly saved in the policy. However, after reopening the rule's properties dialog, it looked as if the ports had not been saved.

Portable media devices (e.g. cameras, media players) are now managed in terminal service environments when connected via a terminal session (in ICA or RDP protocol).