Bug fixes 2023.1 HF1
DriveLock 2023.1 HF1 is a hotfix version.
This chapter contains information about issues that are fixed with DriveLock version 2023.1 HF1. Our External Issue numbers (EI) serve as references, where applicable.
Reference |
Defender Management |
---|---|
EI-2514 |
If the "Save events with e-mail" option was enabled for DriveLock events 684 and 697, neither events were generated nor e-mails were sent for detected threats under some circumstances. |
Reference |
Device Control |
---|---|
EI-2513 |
If no connection to the AD controller was available, event processing could become very slow and cause timeouts when checking if files matched the file filter. |
Reference |
Disk Protection |
---|---|
EI-2491 |
Windows boot would hang when a Disk Protection decryption with network pre-boot enabled was interrupted by a reboot. |
Reference |
DriveLock Agent |
---|---|
EI-2506 |
After updating the agent, some composite devices were sometimes disabled depending on the device control configuration. |
Reference |
DriveLock Operations Center (DOC) |
---|---|
The functionality to display the passwords of local users did not work if you did not enter a 'full name' in the policy for the users. |
|
When trying to create a drive rule from an event, the dialog boxes (Vendor ID, Product ID, Hardware ID, Serial Number) were not filled with the appropriate values from the given event. |
Reference |
DriveLock policies |
---|---|
In some circumstances it was possible that the application/drive rules created in the DOC disappeared. This occurred when the default policy was published in the DMC and there was a | in the name or comment of a rule, for example. |
Reference |
Self-service groups |
---|---|
During self-service unlock, the wizard for enforced encryption was displayed. This issue is now fixed. |