During the update to ver 55.00 / 55.0.1 svchost.exe NETWORK which is a Host process for windows services, is now using 51% of cpu all the time.
Is there any way to shut down the svchost.exe processes. that best I can do is give them low priority.
All Replies (5)
Wait a minute. Make sure your svchost.exe process is located under C:\Windows\System32 (or WOW64, depending on your system architecture).
If it's located elsewhere, it's not a Windows process but very likely a form of malware trying to disguise itself as a system file.
Go to Safe Mode and remove it, after performing a full backup of your system.
Modified
mattcamp said
Wait a minute. Make sure your svchost.exe process is located under C:\Windows\System32 (or WOW64, depending on your system architecture). If it's located elsewhere, it's not a Windows process but very likely a form of malware trying to disguise itself as a system file. Go to Safe Mode and remove it, after performing a full backup of your system.
Thank you for the information on that tidbit. I just checked ALL host processes and they are all located in the proper windows folder.
However, I will update by saying that on my 8th restart since this update has occurred the CPU and Memory hungry process seems to have cleaned itself up for the most part. But I still dont know why ver 55 activated this problem in the first place.
svchost.exe is a main Windows process forking a bunch of related Windows services (Windows Firewall, for example).
If you want to dig deeper, you can try investigating why it happens with Process Explorer.
Modified
GOODBYE Firefox
Well, Mozilla Foundation, Thanks for the trip. I have enjoyed your product for many years. Unfortunately, ver 55. just is not compatible with my system it would seem. No Bookmarks, or No Private Window. Plus, something activated my widows Svchost.exe to a point where it is now 51% of my cpu processes most of the time. Essentially, my computer is dead now. more than a minute to just load FF.
Good luck and I wish you all the best.
I think it's a Windows problem, more than a Firefox issue, but of course it's your call.