Search the Community
Showing results for tags 'issues'.
Found 4 results
I sat down to my computer this morning and found immunet utilizing 100% of the CPU. Although I sat up a scan schedule (daily full scan 0300), it states it has never run a scan. I see that it updated today at 11:12:44 AM. As I am typing it just dropped to a reasonable CPU usage, but it still states a scan has never been run. HA! CPU is back to 98% utilization. I was super excited to find this product because we use the commercial version (AMP) at work and client locations. But not being able to use my computer is going to be an issue. Dell 8920 i7-7700K 4.20GHZ 48 GB RAM Windows 10 Home v1909 Any recommendations? Thanks!!
Hello all, I installed yesterday Immunet 7.0.0 11362 on Windows 10 x64. Windows Does have an automate proxy settings throught a pac file and a manual settings activated as you can see with the screenshot. Wouldn't it be best to have an always active manual settings for the proxy in case the automate detection fails? Aside that I'm new to Immunet and I do love the idea behind it! I hope I could help you all to fix this issue to make Immunet better!
Im not sure if its supposed to be like this, but enabling the clamav engine spikes the CPU and resource usage to 25% CPU and 350 megabytes of memory from 0-1% CPU and 50 megabytes of memory, is it always like this? the update button always says "up to date" even after reinstalling the product a lot of times and I have no folder that contains error logs.
I have used Immunet free for a long time with no real problems. Recently it started preventing all programs within my office 2013 suite from launching. In Task Manager it will show MS Word Or Outlook running but the icon fails to open the program. I know this because I can close Immunet protect in Task Manager and the programs work again. (I leave Immunet Protect Tray Client running.) I use WIN 8.1 64 bit and it is up to date. Immunet is also current (18.104.22.16819) Right now it is a trial version of Plus but the problem started before I updated. Anyone have any clue why this might be happening?