Traps Agent Known Issues

Known issues with the Traps agent 5.0.
The following table includes known issues in Traps 5.0.
Issue ID
Description
CPA-3352
This issue is now resolved. See Traps Agent 5.0.6 Addressed Issues.
On endpoints running Windows 10 Insider Preview, the Windows Defender Security Center displays Virus & threat protection as Unknown and displays Status unavailable for Traps even though Traps successfully registers with the Security Center and is available.
CPA-2814
This issue is now resolved. See Traps Agent 5.0.3 Addressed Issues.
When you install Traps on a Linux endpoint and multiple OpenSSL Red-hat Package Manager (RPM) packages are installed, installation fails.
Workaround: Remove any extra OpenSSL packages from the Linux server.
CPA-2681
This issue is now resolved. See Traps Agent 5.0.1 Addressed Issues.
Clicking Check In Now in the Traps agent console disconnects the agent from the Traps management service after you configure a malware profile with a Parent Process Name that exceeds 250 characters (ProfilesWindows<malware_profile>).
CPA-1942
This issue is now resolved. See Traps Agent 5.0.1 Addressed Issues.
When you first install the Traps agent, the Traps management service can take up to one hour to display the associated content and agent version. As a result, the Dashboard can misreport the content version as outdated.
CPA-1861
This issue is now resolved. See Traps Agent 5.0.4 Addressed Issues.
When device details such as username, user domain, and hostname change on an endpoint, the Traps management service can take up to five minutes to display the updated details after the endpoint restarts.
CPA-1768
This issue is now resolved. See Traps Agent 5.0.4 Addressed Issues.
When a remote user logs into a Remote Desktop Server, the Traps does not capture the name of the remote user. As a result, when a security event occurs, the user is identified in logs as undefined.
CPA-1278
When you configure a hash exception for a file that local analysis reported as malware, the Traps agent overrides the WildFire verdict of Unknown with Benign in the local cache instead of waiting for the official WildFire verdict.

Related Documentation