If disabling Endpoint Standard resolves the issue, proceed to step 5.
If disabling Endpoint Standard does not resolve the issue or if Endpoint Standard is disabled proceed to step 6.
Create a path based Permission rule that allows the relevant application paths to run. If this issue is happening due to an interoperability issue between VMware Carbon Black and the Operating System / Third Party Software, then likely an API Bypass or Full Bypass rule will be required.
If any relevant hash(es) do not have a definite reputation (Anything other than NOT_LISTED or UNKNOWN) or a trusted reputation then the hashes may need to be added to the CBC Company Approved List if your organization determines that the hash(s) should be trusted. If not or if this does not resolve the issue, go to step 7.
Uninstall the Sensor to confirm if the issue persists when the sensor is uninstalled. If yes, then likely this is not a CB issue. If not, please create a Support Case with the following details:
Information Required for Performance Support Case
Define the problem
Is there high disk usage / CPU / Memory, device crash, processes hanging?
If processes are handing, is it just a few processes or the whole system, e.g. general system sluggishness?
Would it be possible to provide a video recording demonstrating the issue?
Background information
The Device ID or Name of the impacted device.
When the issue started occurring and if there were any changes that led up to it
Any Applicable application names and the paths/processes involved when the impact occurs.
Are there other 3rd party security applications installed? Have exclusions been configured?
Are there other resource issues besides CPU / Memory? What is the overall resource usage? Use the utility applicable for your OS
Linux: Use the ps command. Check the relevant documentation for your specific OS for usage instructions
This tool can be used to get CPU performance logging for Linux
Are there any specific behaviors or steps that trigger the issue? (For example, launching an application, selecting a tab / link / process, executing a specific function, etc...?)
Windows: If the operation can be performed from command line, run from powershell shell and use measure-command utility to get precise times.
What is the expected behavior vs the current behavior?
When did the performance issue start? What changes occurred?
New sensor install or upgrade?
Windows update?
Other security software install or updated?
Does this issue happen when sensor is in bypass, uninstalled, when relevant applications are allowed in a permission rule or added to the Company Approved List?