- Apr 21, 2016
Do you mean that the opened GUI takes 100% of the processor power? This is definitely not the case for me. On the other hand, I notice that when updating signatures etc., other programs, especially the Internet browser, are slowed down or stopped completely for a few seconds.In past I had to use "a2start /warp" command to prevent GUI process from using 100% CPU when idle.
Does anybody know if this workaround still needs to be applied or was problem fixed with one of later updates?
No the problem was after one of their updates caused 100% CPU usage even when GUI was closed. As I remember it was a problem with some GPUs and hardware acceleration? Their workaround was to run a2start with /warp switch which disabled HW acceleration and solved the problem. Since there was never any info on their (now deleted) forum that this problem was solved, I always enabled that workaround - just to be safe.Do you mean that the opened GUI takes 100% of the processor power? This is definitely not the case for me.
Same here. I tried the new version and did not notice significant improvement in terms of performance. Not sure how Emsisoft came to the conclusion that performance improved by 50%.I tested EAM yesterday and on my system service was using around 600 MB of RAM (same as with previous versions). Application startup also wasn't noticeably faster than before on my computer. First application startup is - same as before - still slower (probably because of online check that is performed).
Web browsing is slower than browsing when I use Eset. Eset scans all http(s) traffic and is still faster than EAM, which performs only DNS level check against a list of bad web addresses.
There was no CPU hogging by a2start.exe even without / warp switch.
That just experience I had on my system.