Online Armor permanently using 30% of my CPU

~Link removed. Post your screenshot as an attachment here instead.~

Why is Online Armor using so much of my CPU all the time ?

 

What OS are you using? What other real-time security applications are you using? You may have to submit a bug report at Emsisoft's Official forum. http://support.emsisoft.com/

 

There is an app called Process Explorer from System Internals which will also give a clue
which process makes Online Armor gives the CPU hike. Once that process is identified , you
can exclude it from OA 's option.


Posted on: support.emsisoft.com forum

 

I experienced very similar results when I tried it on an XP machine. Had to abandon it for something else.

 

I'm using Windows 8.1 64bit together with Emsisoft Antimalware and Online Armor. Even when I switch off all the components of Online Armor it still uses the same 30% of my CPU all the time.

 

Tom, fwiw, I'm on XP and OA Premium is using 0% CPU on my system.

(I did have some CPU issues with it a good while back and that was when I used alternatives such as PF and Comodo. However, once I tested and found the issue resolved I was able to return. It's always been the firewall that made the most intuitive sense to me and has given me the most satisfactory results. Others may have differing experiences.)

 

As others said, report it on the Emsisoft forums. There are a number of posts there by users experiencing similar issues (myself included). The more data they have, the better.

 

So did you report it on the Emsisoft forums?

 

Ye I did. However, after I received the first answer the problem was already gone (the response was very fast!)Works like a charm now


Im seriously thinking about switching from Avira to Emsisoft. EAM found many malware traces that neither avira nor mbam found.

 

You can get the free Emsisoft Emergency Kit, which does on-demand scan only (not real-time) to scan your PC.
I don't want to deter you from buying EAM, just suggesting a free solution to benefit from Emsisoft detection engines.

 

Was there a fix for it or did it correct itself?

 

This sounds interesting, too, but the installation file alone is huge -- well over 200MB. Can't even imagine what the installed size would be.

 

because the signatures; EAM folder after updates = 264mb

 

It fixed itself. However, they gave me a variety of other solutions I may try out, just in case.