I've been having a similar problem for upwards of a year and I do not have Webroot installed. I use Google Chrome and Windows Defender. However, closing Chrome does not seem to fix the issue either.
Opening Task Manager Slows PC to Crawl - Windows 10 Pro 1709
Hi all,
I've had an issue with Windows 10 Pro really freezing up and not being responsive after opening up Task Manager. The numbers shown for performance and CPU utilization are not pegged at all.
This is on a Dell T3500 with a SSD OS drive, W3580 cpu, 24GB RAM, and an AMD Radeon Pro WX7100.
The computer is on a Domain with Webroot installed as AV. I usually have Solidworks and a couple of other programs open. I do not have any hardware bottlenecks as far as I can see. I also looked at the Event Viewer, and apart from a couple Group Policy warnings, nothing out of the ordinary, and no system events registered at the time of opening Task Manager.
Thanks for the insights, gents n ladies.
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
78 answers
Sort by: Newest
-
Anonymous
2018-07-18T19:25:15+00:00 -
Anonymous
2018-05-17T10:01:10+00:00 It seems to just be a delay rolling out. I'm an MSP also and yesterday all our endpoints were on 9.0.19.43, but as of this morning a few are starting to move over to 9.0.20.31
I haven't tested the issue since updating my Webroot so we'll see how it goes
-
Anonymous
2018-05-16T15:10:43+00:00 I wonder why you're not on Webroot 9.0.20.31. It was released a few weeks ago and fixes the problem.
I'm an MSP, perhaps they are holding us one version back. I'll check with them.
-
Anonymous
2018-05-16T12:33:11+00:00 I'm also still on 9.0.19.43 not sure why 9.0.20.31 hasn't been pushed out to us yet. I would really like to have this fixed.
-
Anonymous
2018-05-16T10:57:47+00:00 Logged in to subscribe to this thread and to thank the folks that discovered this interaction. It's been driving me crazy for weeks! I'm still seeing this issue with Webroot SecureAnywhere 9.0.19.43.
I wonder why you're not on Webroot 9.0.20.31. It was released a few weeks ago and fixes the problem.