There have been reports of issues on the User Exchange and via support cases related to performance issues after installing the 3.2 sensor release. These performance issues have resulted in behavior such as:
Microsoft Management Console (mmc) panels loading objects slowly
Certain applications observing delays between keystroke and the text appearing on screen
Reported applications: Internet Explorer and Outlook
Carbon Black has identified a root cause for these performance issues and is currently working to resolve the behavior. A hotfix build will be made available to resolve the identified issues.
If you are experiencing performance issues in specific applications, please open a case with our technical support team. Please provide the following information when opening a support case so that we can confirm whether the hotfix will resolve the reported issue:
Sensor logs from an impacted system
Technical support can capture these logs remotely if needed, but the device name will be required
The last command should be used: procdump.exe -ma -s 5 -n 5 "PID of the process"
We will continue to keep this post up to date as more information becomes available.
July 11th, 2018 1:18 PM Pacific -- We are currently performing QA validation on the hotfix build. Once QA validation occurs, we will get the build WHQL signed (which allows installation on Windows 10). We'll continue to provide updates as we have them.
July 12th, 2018 9:30 AM Pacific -- Testing is ongoing with the hotfix build. Our internal testing indicates that the hotfix does resolve the performance issues. Historically, we prefer to deliver hotfixes to individual customers as they report problems. To help expedite delivery of the hotfix, we will be publishing the hotfix on the User Exchange when it becomes available. Support will be publishing a Knowledgebase article with the build and some information about what we mean when we create a hotfix. Thank you for your patience on this.
July 13th, 2018 12:15 PM Pacific -- The build has finished WHQL signing and QA validation. We are performing some additional validations currently. Once we receive feedback from that validation, we will be making the hotfix available on the UEX to all impacted customers.