Sophos Central Endpoint and SEC: Computers fail/hang on boot after the Microsoft Windows April 9, 2019 update. Please follow knowledge base article 133945
Learn about the Benefits of Multi-Factor Authentication (MFA). Turn your MFA on now!
We'd love to hear about it! Click here to go to the product suggestion community
On a new software build of windows 10 on a T450 Lenovo, we found that at the end we installed Sophos Endpoint Intercept X 2.0 and it significantly slowed down the computer. All aspects of the computer became slow. On first bootup, connecting the Wifi - slow. On login, the CPU would pin at 100% for long periods of time with high memory usage. All applications would be slow to open, printing would be very slow. This is a new laptop i5, 8 GB RAM, 256 SSD.
We would remove the Intercept X and the computer would return to normal operation. Fast bootup, fast login, apps, etc...
Now for this customer, then use Trend Micro as their primary AV. We have Sophos Intercept X added on for the extra protection. We did not have issues previously until the Intercept X Version went up to 2.0. Has anyone else noticed a large performance hit with Intercept X 2.0?
I have also experienced this on some of our company's computers.
Was running into an issue with Windows 8.1 users and slow performance with spinning HD. Disk was showing 100% at login and would stay high causing other software to run slow.
I had been running Sophos for a while and auto updates were up to the latest agent version of 2.2.2 and latest version of Intercept X. I figured after monitoring task manager I observed that the majority of disk usage was caused by the Sophos software suite. I decided to completely remove and install again.
I started by disabling taper protection in Sophos central for the workstations having the issue. This allowed me to completely uninstall Sophos.
I downloaded the current installer from the central website and installed the Intercept X and Endpoint software. Once completed I enabled the tamper protection again.
After reboot the end result was what I was looking for. Everything went back to normal acceptable disk usage.
We always advise to please create a new thread for your specific issue so that other community users can properly track your issue.
In regards to this thread and useful tips for troubleshooting your Intercept X issues, please note the following:
If you require immediate assistance or assistance troubleshooting, we would advise to please raise a support case so that further investigation can be performed for your situation.