Windows 10: Antimalware service executable - high CPU - one solution
Antimalware service executable - high CPU - one solution
In a Windows 10 Pro 32 system, I had25-40% CPU for Antimalware Service Executable and another 25% for Malwarebytes.
In all the CPU was running 100% with other things.
I normally run Widnows Defender and Malwarebytes Premium together on lots of computers. So this is NOT a problem.
And, turning off Windows Defender or Malwarebytes is NOT going to be the solution.
So many posts here go in that direction it seems.
I'm sorry that I can't be more definitive but here is how this was solved:
I had about 6 command line .bat files running continuous pings to various addresses that would log traceroutes should some number of pings be missed in succession. These were originally written for Windows XP and 7 and there were timing differences between the two. Mostly they just run the pings and that caused the timing issues.
Closing the looping .bat files got rid of the Antimalware Service Executable and Malwarebytes heavy loads. Now they are running under 1% each.
It appears there is enough interaction to cause the high loading. So that's where I'd be looking.
I have recently formatted my laptop and within 2 days high memory and cpu consumption is showing in task manager.
every single session since the latest update I inevitably spend half an hour sitting with high cpu usage going to the 'service host unistack service group' and its to the point where I'm curious...what is this? what does it do? is its sole purpose...
How can I end memory hogging of System and Antimalware Service Executable?
This process has started to constantly use about 50% of cpu. I have seen several suggestions on the web but am not sure which apply to Windows 10.
I have not used Windows Media Player since upgrading to Windows 10.
I am not sure which...
lately i have noticed that microsofts antimalware service is taking up too much CPU and ram and makeing my laptop very hot (fans on high) and it stays like thata for the reminander of the usage until reboot on and off. itwas never like that before...