50m30n3

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!

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.