Corrupted Immunet Auto Update

[ritchie58]

I booted up my machine today and it was running "mind numbingly slow!" So I rebooted and let everything load again and discovered that Immunet's agent was not launching correctly although agent showed up as an active process. The GUI Scan Now and Settings tabs were greyed out. I tried several manual kills & restarts using CMD to no avail. Then I checked Settings and discovered that Blocking Mode, ClamAV & auto updates for it, Scan Archive Files and Scan Packed Files were disabled. These setting were enabled. Also "all" the exclusions disappeared and the Scheduled Scan I had set. I went ahead and did a complete uninstall and reinstalled. Reconfigured all settings and exclusions after that. I did create a SDT zip file before unistalling and plan to send that in to Support. After reinstalling I did notice I got the newest 3.0.13.9411 version from the bootstrapper so I'm venturing to guess that something went wrong while that update was being pushed through the GUI or is it that the Local.xml file got corrupted instead maybe?

 

One last thing, I'm getting an unexpected error message while trying to log into My Community. Other than that everything seems to be functioning properly now.

 

Regards, Ritchie...

[Jose]

Hi Ritchie,

 

I believe you are right with regards to the local.xml (and I think policy.xml) being corrupted.

 

With regards to My Community, it is a feature that we are trying to phase out, so I wouldn't be overly concerned if it is not working (it's function has been covered by other aspects of the program, so security wise the protection is equivalent).

 

It worries me that it was running "mind numbingly slow" however, can you perhaps send us the SDT for it?

 

Thanks,

 

-Jose

[ritchie58]

Yup, just sent the SDT report in Jose. Since reinstalling my machine seems to be running normally now thankfully! It's no big deal if I can't log into My Community. I know it's going to get phased out eventually anyway.

[Jose]

Me or Tom will take a look at it tomorrow. Your post caught me as I was leaving work for today.

 

Thanks

 

-Jose

[ritchie58]

That would be great, thanks!

 

Cheers, Ritchie...

[ritchie58]

Don't know if this is relevent or not but I did notice a slow down in bootup time that seemed to be getting progressively worse leading up to the event. That did have me a little worried because I thought It might be hardware related. Since I've reinstalled with 3.0.13 I'm seeing a much better bootup time now!

[Jose]

Hi Ritchie,

 

I gave it a look, and it does seem to be a corrupted Local.xml.

 

Since it was solved by a re-install, I am going to shelve this issue for the time being, unless it comes up again.

 

Thanks,

 

-Jose

[ritchie58]

Thanks Jose. well, I was definetly, completely wrong on the auto update thing but my second guess proved to be correct then. Since reinstalling everything is ok so far. I'll report to this topic if it happens again. Since I run my Puran Defragger 7.6 on a daily basis I have noticed that the Local.xml file seems to get "really fragmented" more often than not. I'm sure this is due to the file being written to on a daily basis too but I was wondering if that might have something to do with the corruption problem, the file's data being constantly shuffled around the HDD. Don't know, maybe it has nothing to do with the issue at all. Just thought I'd mention this fact though.