-
Content Count
16 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout tm-107
-
Rank
Member
Profile Information
-
Gender
Male
-
Location
Berlin, Germany
Recent Profile Visitors
456 profile views
-
Same problem here when scanning ... 100% CPU and after a few minutes, the computer stops responding. I had to stop the Immunet-Service to do a scan.
-
No good advertising for Cisco ... Today, Immunet (sfc.exe) uses again and again for several minutes 50-99% CPU without a recognizable reason. During that time, the whole computer is only difficult to use. Stopping and restarting the Immunet service will remove the problem for some time but not permanently. Is there any way to download and reinstall Immunet v5.x till the problems with v6.x are fixed? Currently I have terminated the Immunet service manually, since otherwise no reasonable use is possible.
-
Yesterday i installed the update to v6.0.6 und since then, the cloud-protection seems to be not working. Both (ETHOS & SPERO) are enabled in the settings and i did more than one reboot. The problem is the same on my desktop and laptop. Both running Win 7 Pro x64. Any idea what's the reason for that? P.S: When opening https://www.immunet.com, it says 0 Members & 0 Threats. But on http://www.immunet.com(unsecured) everything is fine.
-
You can also use a linux-live-cd (Knoppix) to delete the old files. edit: the method from ebloch (next post) is much more easy ;-)
-
Too Many Log Files & No Clamav Updates
tm-107 replied to tm-107's topic in Immunet Support (Issues/Defects)
Of course, there isn't a new signature every hour. But my daily.cld is from 02 August 2016 ... today we have August the 5th and my computer is online since more than 5 hours. On another machine, i'm using ClamAV as standalone-service (for mail-scanning). So I can see, that there are updates every 1-6 hours. Since Friday, there are almost 16 updates for the daily.cld. edit: Immunet also says, that there are updates available. But they couldn't be installed: -
Too Many Log Files & No Clamav Updates
tm-107 replied to tm-107's topic in Immunet Support (Issues/Defects)
Yes, the "Exception Rule" was already created. It looks like it is sometimes working (22:15): 2016-09-02 15:11:03 - Log file initialized 2016-09-02 15:11:03 - INFO: custom freshclam return code: 56 2016-09-02 15:11:33 - ERROR: freshclam exit code 59 2016-09-02 15:11:33 - ERROR: failed to read stop event from pipe 2016-09-02 15:11:33 - Log file closed 2016-09-02 16:11:36 - Log file initialized 2016-09-02 16:11:36 - INFO: custom freshclam return code: 56 2016-09-02 16:12:06 - ERROR: freshclam exit code 58 2016-09-02 16:12:06 - ERROR: failed to read stop event from pipe 2016-09-02 16:12:06 - Log file closed 2016-09-02 17:12:09 - Log file initialized 2016-09-02 17:12:09 - INFO: custom freshclam return code: 56 2016-09-02 17:12:38 - ERROR: freshclam exit code 58 2016-09-02 17:12:38 - ERROR: failed to read stop event from pipe 2016-09-02 17:12:38 - Log file closed 2016-09-02 18:12:41 - Log file initialized 2016-09-02 18:12:41 - INFO: custom freshclam return code: 56 2016-09-02 18:13:10 - ERROR: freshclam exit code 58 2016-09-02 18:13:10 - ERROR: failed to read stop event from pipe 2016-09-02 18:13:10 - Log file closed 2016-09-02 19:13:13 - Log file initialized 2016-09-02 19:13:13 - INFO: custom freshclam return code: 56 2016-09-02 19:13:45 - ERROR: freshclam exit code 59 2016-09-02 19:13:45 - Log file closed 2016-09-02 20:13:48 - Log file initialized 2016-09-02 20:13:48 - INFO: custom freshclam return code: 56 2016-09-02 20:14:20 - ERROR: freshclam exit code 58 2016-09-02 20:14:20 - ERROR: failed to read stop event from pipe 2016-09-02 20:14:20 - Log file closed 2016-09-02 21:14:23 - Log file initialized 2016-09-02 21:14:23 - INFO: custom freshclam return code: 56 2016-09-02 21:14:57 - ERROR: freshclam exit code 58 2016-09-02 21:14:57 - ERROR: failed to read stop event from pipe 2016-09-02 21:14:57 - Log file closed 2016-09-02 22:15:00 - Log file initialized 2016-09-02 22:15:00 - INFO: custom freshclam return code: 56 2016-09-02 22:16:03 - Log file closed 2016-09-02 23:16:21 - Log file initialized 2016-09-02 23:16:21 - INFO: custom freshclam return code: 56 2016-09-02 23:17:54 - ERROR: freshclam exit code 58 2016-09-02 23:17:54 - ERROR: failed to read stop event from pipe 2016-09-02 23:17:54 - Log file closed But once a day is not what i want -
Too Many Log Files & No Clamav Updates
tm-107 replied to tm-107's topic in Immunet Support (Issues/Defects)
Sometimes it is another exit code: 2016-09-01 17:53:40 - Log file initialized 2016-09-01 17:53:40 - INFO: custom freshclam return code: 56 2016-09-01 17:54:09 - ERROR: freshclam exit code 59 2016-09-01 17:54:09 - ERROR: failed to read stop event from pipe 2016-09-01 17:54:09 - Log file closed Have it now also tested on another computer -> there the updates do without error. So i deinstalled and reinstalled Immunet 5 -> same problem -
The Knowledge Base article describes the use of SigUI.exe, which ist not included in Immunet 5 ... I couldn't find out how to use own signatures in ClamAV with Immunet 5.