rsvelankar Posted November 25, 2011 Report Share Posted November 25, 2011 After updating to Immunet 3.0.5 It started using 50 to 60 % of my cpu On searching through Windows Task Manager 'Agent.exe' process related to Immunet was causing high usage. I am using Microsoft Security Essentials as my Live installed Antivirus O.S. - Windows Vista Home Basic And apart from MSE, My System has installed with Malwarebyte's AntiMalware (MBAM)free edition, Super Antispyware (SAS)free edition, Malwareblaster for on demand scanning Can any one suggest how to stop the process or to bring down high cpu usage or Is it conflicting with my Antivirus. Link to comment Share on other sites More sharing options...
jgroep Posted November 25, 2011 Report Share Posted November 25, 2011 Are you using the lastest Immunet? which is 3.0.5.7552 Try the following settings/setup: 1. [Windows Firewall] Allow a program through Windows Firewall ---------------------------------------- C:\Program Files\Immunet\3.0.5\agent.exe C:\Program Files\Immunet\3.0.5\iptray.exe C:\Program Files\Immunet\3.0.5\updater.exe 2. [Microsoft Security Essentials] Excluded files & locations -------------------------- C:\Program Files\Immunet C:\Program Files\Microsoft Security Client C:\ProgramData\Microsoft\Microsoft Antimalware C:\ProgramData\Microsoft\Microsoft Security Client Process Exclusion ----------------- C:\Program Files\Immunet\3.0.5\agent.exe C:\Program Files\Immunet\3.0.5\iptray.exe C:\Program Files\Immunet\3.0.5\updater.exe C:\Program Files\Microsoft Security Client\msseces.exe 3. [immunet Settings] Protection Blocking Mode: Off (I also got ClamAV Detection Engine: Off) And delete all entries for File Exclusions for programs you didn't install. Since you use MSE, keep (and add): File Exclusions --------------- C:\Program Files\Immunet C:\Program Files\Microsoft Security Client C:\ProgramData\Microsoft\Microsoft Antimalware C:\ProgramData\Microsoft\Microsoft Security Client C:\Windows\Prefetch C:\Windows\System32\catroot2 This should help. Greetz, Jochem. Link to comment Share on other sites More sharing options...
rsvelankar Posted November 26, 2011 Author Report Share Posted November 26, 2011 Thank you JGROEP for your valuable advise, However I, after posting on this thread, tried to uninstall Immunet with uninstall application within "c:\Program files\Immunet\..." where I found earlier version directory ie "c:\Program files\Immunet\3.0.4" and "c:\Program files\Immunet\3.0.5" exist and where both directories were containing Agent.exe file. It seems that since I updated this version over 3.0.4.7241 where the old version files were still remain active ( Don't know whether in my system Updating went wrong or it is mistake of Immunet updating installer). So, I completely uninstalled Immunet and reinstalled with new version Installer and now I have no heavy CPU usage problem. Also I will exclude files as you have mention in MSE and Immunet and settings to have better efficiency. Link to comment Share on other sites More sharing options...
jgroep Posted November 26, 2011 Report Share Posted November 26, 2011 Indeed, the 3.0.4 and 3.0.5 directory is troublesome. Maybe Immunet could change the program to use a tree which never changes, so you also never have to change the "Allow a program through Windows Firewall" and exclusion list(s). Link to comment Share on other sites More sharing options...
ritchie58 Posted October 15, 2012 Report Share Posted October 15, 2012 I have noticed that this old topic still gets some views by members and guests alike. If you haven't already I would encourage everyone to install or update to the newest 3.0.8.9025 version. This newest version has "eliminated" the problem of excessive CPU and/or disk I/O activity that some users encountered with older versions. Plus the scan speed has been "greatly improved" and some other minor bugs have been fixed! https://sourcefire-apps.s3.amazonaws.com/av/protect/3.0.8.9015/protectbootstrap_url.exe Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.