Anyone had this issue in Build 1803?
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: Most helpful
-
Anonymous
2018-05-07T13:15:16+00:00 -
Anonymous
2018-04-20T11:23:45+00:00 So I got the following response from Webroot:
"The issue you are reporting is most likely a known issue related to the Identity Shield protection layer. The Webroot Development team has been notified of this issue and is currently working on a resolution. We expect to address this issue in an upcoming software version release, which will be downloaded automatically to your computer and installed when it is available
In the meantime may you please try allowing Task Manager (taskmgr.exe) and Chrome and/or Firefox (chrome.exe and/or firefox.exe) on Identity Shield by sending an 'Identity Shield Allow application' agent command following the instructions below
[...]
Finally, please reboot the machine for it to take effect."
Previously I had allowed both Firefox and Task Manager in Webroot, but it didn't work. They essentially suggested the steps I had already taken, with the caveat that I should reboot my machine for them to take effect. In my case, at least, a reboot following these changes has worked and I can now access my Task Manager as normal with no lag, even with Firefox open and full Webroot protection enabled (with the new exceptions of course)
I'll monitor over time and report back any changes
I am a Webroot Beta tester, and I can confirm that beta version 9.0.20.31 seems to have solved the problem (you are probably running 9.0.19). Also, you can do the "allow" fix without rebooting. All you have to do is shut down Webroot protection and the re-enable it. At least that was the case for me. You would need to do the same once Webroot is updated to 9.0.20, I think. Though I'm not quite sure why, but I had to do it once by beta version was updated.
-
Anonymous
2018-04-20T10:25:28+00:00 So I got the following response from Webroot:
"The issue you are reporting is most likely a known issue related to the Identity Shield protection layer. The Webroot Development team has been notified of this issue and is currently working on a resolution. We expect to address this issue in an upcoming software version release, which will be downloaded automatically to your computer and installed when it is available
In the meantime may you please try allowing Task Manager (taskmgr.exe) and Chrome and/or Firefox (chrome.exe and/or firefox.exe) on Identity Shield by sending an 'Identity Shield Allow application' agent command following the instructions below
[...]
Finally, please reboot the machine for it to take effect."
Previously I had allowed both Firefox and Task Manager in Webroot, but it didn't work. They essentially suggested the steps I had already taken, with the caveat that I should reboot my machine for them to take effect. In my case, at least, a reboot following these changes has worked and I can now access my Task Manager as normal with no lag, even with Firefox open and full Webroot protection enabled (with the new exceptions of course)
I'll monitor over time and report back any changes
-
Anonymous
2018-04-17T17:26:13+00:00 Webroot was definitely the issue for me. Here are the changes I made in the Webroot UI. After this was set, Task Manager played along fine with Windows/Chrome/Firefox.
It would be great if anyone has any contacts at Webroot and could point them to this thread so they could optimize the application to play nicely with the OS instead of the admins having to push out workarounds and fixes for client machines.
I had to "allow" Firefox. Unfortunately, every time there's a Firefox update, Webroot detects it as something different and I have to allow it again. My wife's work laptop has Webroot but making changes to it is administratively blocked out, so having to live with the problem on that one.
-
Anonymous
2017-12-19T14:23:35+00:00 Yes! Excellent diagnosis! Task Manager freezes up when Firefox is open. I confirmed that I can use Task Manager fine when Firefox is closed. Has Mozilla been made aware of the issue?