Ah, so it is a Task Manager issue perhaps more than a Chrome or Firefox issue. Perhaps those browsers trigger something weird that Task Manager can't quite handle?
I work in IT as well and have seen it on a small handful of pc's here at the office.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
Ah, so it is a Task Manager issue perhaps more than a Chrome or Firefox issue. Perhaps those browsers trigger something weird that Task Manager can't quite handle?
I work in IT as well and have seen it on a small handful of pc's here at the office.
I work in IT. This problem is present on a lot of PCs with the Fall Creator's update, regardless of the presence of Fx. Opening task manager KILLS Windows.
Need a fix ASAP.
Hmmm, I haven't at least in a simple google search. I'm not a member of the Mozilla forums though, so I'm not sure.
Agreed! Hardware isn't an issue for me either. I am not using the machine in my original post, although that was no slouch. I am now on a Dell Precision T7600 with dual Xeon 6-core 2267 cpu's and 64GB of DDR3 1600mhz ECC ram. Still with my Samsung EVO 850 OS drive and a couple secondary drives.
Have you seen this issue posted anywhere other than here? I can't imagine that they don't know about it, but wondering why it's not viewed as being important enough to fix it.
Agreed! Hardware isn't an issue for me either. I am not using the machine in my original post, although that was no slouch. I am now on a Dell Precision T7600 with dual Xeon 6-core 2267 cpu's and 64GB of DDR3 1600mhz ECC ram. Still with my Samsung EVO 850 OS drive and a couple secondary drives.