Windows Patch Notes for CTE v7.5.0

Resolved Issues

• AGT-45257 [CS1472032]: Server gets rebooted when user tries to access/perform exports when accessing GuardPoint

  The issue was caused by the CTE agent passing the wrong length while copying the data. The CTE agent accessed invalid memory which caused the crash. The string was not NULL terminated and CTE did not ensure that it had enough memory allocated. This has been fixed.

• AGT-46299 [CS1475860| CS1488372]: CTE Server hangs

  The issue was due to a synchronization issue on CTE. The CTE threads were waiting for certain locks to be released. They were stuck because another APC (Advanced process control) level task interrupted the CTE thread progress. This has been fixed.

• AGT-48355 [CS1477380]: Agenthealth script failed to run on Japanese OS

  The agenthealth feature is not supported with the Japanese OS. This issue is fixed in the latest CTE version, where the script does not depend on the OS language pack.

• AGT-48413 [CS1496864]: Failed to start VMD service after system reboot

  VMD service depends on, and fails to start, if all of the system network services are not up and running. The CTE team observed that intermittently, the networking services were not starting before VMD started. This has been fixed.

• AGT-48492 [CS1503921]: Failed to query the guardpoint directory when the username is Korean

  This issue was caused by a deadlock. It has been fixed.

• AGT-48579 [CS1508083|CS1508054] Documentum Server Crashes with Blue Screen

  Previously, the work-around for this issue was to change the registry entry. This has been fixed. Now, when CipherTrust Transparent Encryption detects metadata that is not correct, CipherTrust Transparent Encryption automatically corrects it. Metadata correction is no longer dependent on the registry entry.

• AGT-48869: Key mismatch error after reboot

  To avoid potential complications when re-registering to different key managers, Thales advises to not re-use key names for different keys across different key managers. If different keys are created on separate key managers, yet have the same exact key name, then re-registering from one such key manager to the other produces unpredictable results as the agent may still continue using the old key until reboot.

• AGT-49848 [CS1514312]: CTE overwriting the NTFS permission

  The VMLFS driver was not properly abiding by the set NTFS permissions. This has been fixed.

• AGT-50412 | 50641 [CS1520559 | CS1516858]: Customer seeing high levels of non-paged pool memory usage due to CTE agent

  The memory leak was due to an improper reference count on process records when using the VMLFS driver. This has been fixed.