Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. As far as I can understand now, freshclam.exe has connection problems or a bug when downloading. At first I had the problem that the download worked but the downloaded file could not be imported. This problem does not occur with the new version. I also tried to instruct the updater in "freshclam.conf" to use uncompressed DB files. But unfortunately this entry is ignored by Immunet. It would be nice if the configuration file could be used fully, then it would be possible to create notifications with OnUpdateExecute, OnOutdatedExecute and OnErrorExecute. CompressLocalDatabase BOOL By default freshclam will keep the local databases (.cld) uncompressed to make their handling faster. With this option you can enable the compression; the change will take effect with the next database update. Default: no Source: https://www.systutorials.com/docs/linux/man/5-freshclam.conf/ Slowly I am becoming more and more convinced that ClamAV is a nice and very useful tool, but its development at Immunet has been very limited I doubt that I'm really well protected with Immunet right now. I am seriously considering switching to something else that is too bloated for me.
  3. Not sure what is needed in the tags box, just want to report a fault with my immunet security download as it isn't working properly, i,e it wont download new updates and is showing that latest updates are installed. it hasn't updated since the 3rd of May and usually does every day
  4. Thanks for the feedback regarding your OS Rosetta. Much appreciated! Here's a few suggestions that may help with the slowdown. You could experiment a bit with the settings. Especially if you're using some other security products other than Immunet try disabling Monitor Program Start. If you don't regularly install new software on your computer you could also try disabling Blocking Mode. If you're running Immunet as a companion AV to another "paid" AV product then disable the ClamAV module & updates for it. Also create Exclusion rules for both respective AV's Program Files folder. Immunet has a number of major players AV's excluded by default already so check that list first. Regardless which settings you use or don't use it's always best to leave the ETHOS & SPERO cloud engines enabled! Best wishes, Ritchie...
  5. Richie! Thanks for the link for the new release. I currently has Windows 10 Pro, Version 1903, O.S. Build 18362.836 which was installed on my PC 1/16/20. Since the update though, the pc is running slow. I'll have to check the settings to see what I need turned on or off. Stay Safe.
  6. Hi Rosetta, I'm glad a reinstall worked for you but that is still strange that happened! I was pretty sure that your internal computer clock was messed up and that was the cause but perhaps that wasn't the case after all. What is your Operating System in case someone else reports a similar incident? That could be useful. Still not a bad idea to check your BIOS clock to make absolutely sure it's synchronized to the correct time/date for your area I think. If that happened to me that's the "first" thing I would have checked. The cloud stats not displaying correctly is known by the devs. There is supposed to be a new build rolled-out sometime in June that will (hopefully) address that issue. Here's a link to the Announcements section that has the 7.2.8 change log you were interested in. https://support.immunet.com/topic/7436-new-release-immunet-728/ Regards, Ritchie...
  7. Yesterday
  8. I just tried the above on two computers here in the office, SUCCESS! I also noticed that both computers had two versions of ClamAV installed, I used rmdir to kill the oldest. I had almost forgotten about using xcopy, my buddy and I wrote and EARLY version of that back in the MS-DOS on floppy days. I wonder if it's still our code? Glad my work computer is Linux, there's some crazy things in there but nothing compared to Windows.
  9. Ok, after un-istalling, re-installing and re-booting 2 times - the screen shows Install 5/29/2020 9:53 pm. I have a scheduled scan that completed at 3:01 am, supposedly with no threats found. This is a single user desktop PC, no multiple servers here. BUT, when I look at the main screen - you know how you see 114,389.302 people and 407,719.083 protected - don't have that anymore. In the top right I have Cloud Stats from 0 threats. Did something change with this newest version version 7.2811723? I've about had it with this software. Thank you. Can you re-direct me to the release notes for this version. Maybe I need to change some settings?
  10. Guess it's time to try the manual ClamAV update. All computers here stop at 22% downloaded, they try again but never get past 22% What's bad is I've also got this on computers at a remote location, it's a financial office so I have to travel there and get people off each workstation to make updates.
  11. Speaking of time. Here's a "free app" I like to use called Atomic TimeSync. If used correctly, it will keep your computer clock accurately synchronized. https://www.softpedia.com/get/Desktop-Enhancements/Clocks-Time-Management/Atomic-TimeSync.shtml I have it configured to access one of the servers for the National Institute of Standards and Technology atomic clocks. Nothing's more accurate than an atomic clock. Of course there will be a few seconds of discrepancy as the NIST server & your ISP server shake hands and relay the data to your computer.
  12. You might want to access & check your motherboard's BIOS settings to make sure that the BIOS clock is reading the correct time & date. If that's incorrect that can cause the date & time to be also displayed incorrectly with Windows & other third-party programs.
  13. The devs are aware that some users are encountering update issues. Supposedly a new build will be rolled-out sometime in June that will (hopefully) address this issue and the cloud stats not displaying properly too. So I guess we'll all have to wait and see what the next build has as far as fixing these bugs.
  14. Personally I don't use that setting enabled myself either. I seems to interfere with some of my other security start-up programs at boot-up.
  15. Last week
  16. Yes my system date is 5/29/20 and my current time is 11:29 am.
  17. Yes, i know... old post... SFC.EXE -s and SFC.exe -k are working to start and stop Immunet Protect. (You can do the same with NET Start/Stop command) Other commands i've not tested. https://www.cisco.com/c/en/us/support/docs/security/amp-endpoints/213690-amp-for-endpoint-command-line-switches.html
  18. I just updated the Immunet program per the update now screen. It took an exceptionally long time. When I now look at the screen it say update 1/15/2034 at 4:19:21 pm. Kind of scary for me. when I go to the about tab it does show version 7.2811723. Should I uninstall and re-install immunet? thank you.
  19. I use Immunet on several of my computers as I'm pretty fond of the ClamAV service in Linux, thus, extended it to Windows. Recently, however, on both main Windows machines, the Immunet software reports needing to be updated (definitions, not software) and, when I try to update, the Immunet Updater gets stuck on "Initializing Updater." See attached screenshot. This is occurring on both Windows machines. I did some packet sniffing and did not identify unusual network activity from Immunet so, I would guess that it's not a network issue. I do run a pretty interesting DNS-based firewall, but, again, I didn't see DNS calls being made on immunet's behalf when I did the packet analysis (thus, it shouldn't have an issue with being blocked at the DNS level). Any thoughts? Do I need to try uninstalling and reinstalling? Thanks!
  20. Hi VanPrat, I was having the same problem until I discovered the "monitor program start" was enabled by default. I found that, especially when trying to start programs or intensely use programs, CPU usage was insane and rendered the computer almost unusable. Since then, I turned off the setting and CPU usage went back down to normal. I would take an educated guess that, when you have "monitor program start" enabled in the Immunet settings, it applies to any time a new process gets started on your computer. This could even be triggered by loading several tabs in your browser as, the more tabs loaded, the more processes get started by the browser. Please also note that when a scan is taking place, the load is pretty high on the CPU. I think putting it in gaming mode should lessen it's load a little bit during a scan. You might also check your scan schedule and make sure your scheduled scans are for off-hours when your computer will be on, but not being used. Hope that helps a little.
  21. Here the solution i found last hour. Immunet need to update to new version of clamav, clamav stop updating database files with old ClamAv version.
  22. This Problem is a error of Immunet and not a server Problem. The ClamAV 0.102.1 provided by Immunet is outdated and the current version is 0.102.3. This is also reportet by C:\Program Files\Immunet\clamav\\freshclam.exe and freshclam.exe cancel the update after the download of the first "cvd" it get. ClamAV do that to prevent using a old engine with new Database files. Freshclam.exe have problems to download and also cant update complete downloaded files. Solution 1 Download clamav-0.102.3-win-x64-portable.zip from https://www.clamav.net/downloads#otherversions Stop the Immunet Service --> net stop ImmunetProtect_7.2.8 Delete old Database files bytecode.c*, daily.c*, main.c*, lastupd and update.log Extract the files to C:\Program Files\Immunet\clamav\ Start the Immunet Service --> net start ImmunetProtect_7.2.8 Start Immunet, Click on Update Now and wait a moment (if Update does not start repead it after a min.) The download location is configuratet in the file freshclam.conf, if you need to use a other mirror change it in this file. Solution 2 Immunet need a Update to new ClamAV version 0.102.3.x What a disgrace from Immunet
  23. Thanks, worth a try. I don't worry too much about ClamAV as the cloud-based AV engines are working.
  24. Hi 4tygrit i've the same update problem with the main.cvd file in a other post. To update immunet i've download ClamAV Portable (doant forget to get Updates in ClamAV). Stop the Immunet Service Delete in "C:\Program Files\Immunet\clamav\0.1......" the file main.cvd and daily.cvd copy the main.cld and daily.cvd files from "...\PortableApps\ClamWinPortable\Data\db" to "C:\Program Files\Immunet\clamav\0.1......" Start the Immunet Service again
  25. I have to say that I'm happy that the quarantine response settings & the cloud stats will be functionally restored "eventually!" I guess we'll all have to use a little more patience until the new build is rolled-out. I do hope the update issue that users are encountering is addressed also. With the absence of an answer to my question, I have to assume Rob T. is no longer involved with the project would be a logical assumption on my part I think. If that's the case then his expert involvement will be sorely missed by me anyway. Best wishes, Ritchie...
  26. Reg. quarantine/suspicious file behaviour settings - We have identified the bug and will be fixed soon. Reg. Cloud Stats server issue - Again it's a connector issue which will be fixed soon. Reg. product update issues - We are not aware of any issue in this space. Will follow up with the user who is reporting this issue. If you have more details please let us know. New release is coming out by mid June. Stay Tuned!
  27. Why has support for Immunet seemed to have come to a screeching halt after this build was rolled-out? This is really becoming increasingly frustrating! Why is Rob T. no longer providing support?
  1. Load more activity
  • Create New...