You can "ungrey" enable it by clicking on the Properties link located at the right hand panel. The properties window will appear where you can do your change.
Can one prevent Antimalware Executable to start hogging CPU for extended periods each time some network adapter gets active?
One of the most annoying habits in Windows 8 is, that the built-in "Antimalware Service Executable" (part of "Windows Defender") starts hogging my device's CPU with 60-70% (and 100% disk) for extended periods EACH AND EVERY time after I wake it up.
I wouldn't mind if it starts doing its business IN THE BACKGROUND but when I wake my device up from standby it's usually to get something done NOW and thus I find it increasingly unacceptable, that the system is always taken over by Window's defender exactly then and for up to several minutes! If I don't find a solution soon to throttle this beast, then I will disable Defender altogether!
What I noticed is, that this process seems to be actually triggered not by the system waking up, but by the network adapter becoming active. And actually, this happens each and every time ANY network adapter gets active! E.g. if my system has NO network connection at all and I plugin the network cable the Antimalware Service Executable starts. When - after it has settled again - I additionally enable Bluetooth then the Antimalware Service Executable starts its hogging business again. And if I then additionally enable the WLAN a few minutes later, it will AGAIN start to consume CPU!
So: can one decouple this? Running a scan ONCE after (re-)starting it is definitely enough, especially if Defender hasn't downloaded any new signatures since the last run! And, second, can one make Defender convince to strictly run in the background ONLY?
Michael
[Moved from Windows]
Windows for home | Previous Windows versions | Security and privacy
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.
146 answers
Sort by: Most helpful
-
Anonymous
2014-12-02T22:27:53+00:00 -
Anonymous
2014-11-25T14:42:28+00:00 Well issue I had both processes hogging CPU and disc, but windows module installer worker was worse of two. It was not pulling 18%, but rather 40% and up. Until I went in and stopped the " windows module installer worker" service I could not do anything. Period. Hopefully this was just case of an update gone wrong or corrupted.
-
Anonymous
2014-11-25T13:57:11+00:00 Wow, is this problem still not fixed? It's been like a year and a half and still nothing but angry costumers? Pathetic. Guess I won't be restarting this service any time soon...
-
Anonymous
2014-11-25T00:41:35+00:00 Another BS service that will eat up your CPU & disc is "windows module installer worker". So it also may be cause of CPU hogging.
-
Anonymous
2014-11-25T00:36:08+00:00 What's even worse then that.... is u have apple users as friends... lol. How many people u think don't have ability or time for all this BS??. They just take into repair store, pay money to fix that they shouldn't have to.. or they just go buy another laptop, thinking theirs is slow because of age or whatever and again more money for Microsoft and all manufactures...BS. Do they not beta test this **** before they release (force) on the public??