Bug fixes

DriveLock 2024.2 Patch 2 is a patch version.

This chapter contains information on errors that have been fixed with DriveLock version 2024.2 Patch 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

Reference	Application Control
EI-2889	If querying detailed information was necessary when starting a binary (.exe or .dll) and this failed, this error was also cached for future program starts. Now, this is not the case anymore, so that a new execution of the file usually works.
	Start times for processes in the process tree are now displayed correctly.

Reference	Device Control
EI-2885	The "Disable locked devices in device manager" setting works correctly again.
EI-2885	Under certain unknown circumstances, Windows failed to load the device control driver on some systems, even though it had been loaded successfully several times before. The issue has been fixed for some of these cases, but not all. In some cases, changing the setting to disable devices instead of blocking them may also help.
	Extraction of allowed files from Zip Archives may have been incorrectly blocked in previous versions. In these cases, empty files were created in the target folder. Generally speaking, all writes under Content Scan Control may have produced problems if they were paging I/O (with size and buffer adjusted to disk access and not to real file sizes). This bug is fixed.

Reference

Device Control

EI-2885

The "Disable locked devices in device manager" setting works correctly again.

EI-2885

Under certain unknown circumstances, Windows failed to load the device control driver on some systems, even though it had been loaded successfully several times before. The issue has been fixed for some of these cases, but not all. In some cases, changing the setting to disable devices instead of blocking them may also help.

Extraction of allowed files from Zip Archives may have been incorrectly blocked in previous versions. In these cases, empty files were created in the target folder.

Generally speaking, all writes under Content Scan Control may have produced problems if they were paging I/O (with size and buffer adjusted to disk access and not to real file sizes). This bug is fixed.

Reference	DriveLock Agent
EI-2882	Drivelock drivers now work again under Windows 7.