Jump to content

'last Scanned'


Phil.h.Collins

Recommended Posts

Hi Phil, no, that's not normal behavior. It sounds like agent.exe is either not starting or has no connection to the Immunet severs. Open Task Manager (press Crtl, Alt, Delete) and click on Processes for all Users and check to see if that process is running. If agent.exe isn't running try to start it manually by first closing the GUI if you have it open, right click on the Immunet System Tray Icon, click on Hide Tray Icon, wait a few seconds then click on Immunet's Desktop Icon or go to Immunet's All Programs folder and click on the Immunet 3.0 Icon to relaunch the GUI. If you do see agent.exe running then it's probably a connection issue. Make sure that nothing is blocking agent.exe and iptray.exe from connecting to the internet such as your firewall or other software. There's some support articles concerning firewall configurations at this link you may find helpful. Regards, Ritchie...

Link to comment
Share on other sites

I seem to be having the same problem on a regular basis. I'll do a manual flash scan and I do get the green check mark. Immunet later seems to reset it's scan history, perhaps each time I reboot my laptop. I just checked history and noticed it only shows one scan being done and that was on 3/18.

 

I am not griping here! I wanted to add my experience and then ask if anyone thinks that regular use of something like CCleaner could be deleting log files and causing the reset.

Link to comment
Share on other sites

The history of Immunet is stored for one week of activity and then is automatically reset to avoid this file getting too large and taking up valuable HD space. I too use CCleaner on a daily basis and there is no definition to clean Immunet's history.DB file included with CCleaner, even if you use CCEnhancer. That's not to say that some other disk cleaner might have the ability to wipe this file clean, perhaps on reboot since this file cannot be accessed by another process while Immunet is running. If the history is resetting every time you reboot, and I'm assuming you hit the power button more than once a week, that is not normal behavior iTrendsNET. What Operating System do you have on your laptop and do you use some other cleaner(s) besides CCleaner?

Link to comment
Share on other sites

Hi, another thing that might cause this type of behavior is if you switch user accounts without doing a restart. Here is what Millard had to say from a previous thread about user switching: Do you share this computer with multiple users? I mean do you do user switching where you don't log out a previous user? One of the design flaws in Immunet is that only one UI or IPTray.exe instance can talk to only one agent.exe instance. If you open your Task Manager and view processes for all users, it's possible that you might see two iptray.exe instances running. If you do, kill both of them and restart the iptray.exe in the instance that you are using. Regards, Ritchie...

Link to comment
Share on other sites

My laptop is running Win 7 64-bit. It only gets an actual reboot if I need to take in on the road with me for the day, otherwise it stays running at home. Other "cleaners" that I use on occasion are Glary Utilities Pro and PC Pitstop. However, I can say that lately I am not running any of the cleaners on a regular basis or more often than about once every two weeks.

 

So on the 19th it showed one previous scan in history. Today it again shows "Not Secure - Fit it" and no scans shown in history. Since I am adding this replay at 06:04 I guess my scheduled flash scan for 0300 each day also is not working.

Link to comment
Share on other sites

Hi iTrendsNET, That is strange. I wonder if it has something to do with the fact you normally keep your laptop running 24/7? Perhaps the DB file is reaching it's maximum size limit quicker than most users and resetting because of that. You could send in a SDT report. I'm sure support would like to take a look at this. This is just a guess on my part but it's also possible some registry components could be corrupted. You could try installing the new 3.0.6 beta over top your current version to see if that has any effect or you could completely try uninstalling and reinstalling, which is something I normally don't recommend. If you try installing the beta or do a complete uninstall and reinstall could you send in that SDT report first? Best wishes, Ritchie...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...