Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. How do you view what Immunet is scanning causing high CPU? I noticed the other day it was high yet I couldn't find out why. I may need to add an exclusion, but for what? Thanks
  3. Since this was reported back in February 2019 I have upgraded Immunet twice that I can remember, the latest was today to version 6.5.0.11255. There is no change over the last 6 months and I still have to stop Immunet to launch anything in MS Office suite. Can this be fixed or am I wasting my time waiting?
  4. I do have some questions. Is this new Orbital code associated with the folks at IronOrbit & their Orbital Security software? Since you did mention that version 6.5.0 is a beta build, I have to assume that this is a open to the general public beta testing program that's being implemented, is that correct? If any code is included with Immunet that makes it's efficacy that much better is definitely a good thing, that's if it doesn't impact system resources to a negative degree. Also, a "complete change log" would be very beneficial. Just wondering if the most recent issue with scans not completing with some users were looked into & (hopefully) rectified. Best wishes, Ritchie...
  5. Last week
  6. Hello all, We are happy to announce a new release of Immunet: Version 6.5.0! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Orbital. Orbital uses cloud technology similar to Immunet to look for complex indicators of compromise on the machine. Over the next couple of months, the Orbital service will be periodically scanning your device in an attempt to fine-tune our Indicators of Compromise and generate useful feedback to the Immunet users. If you choose to install 6.5.0 Beta, you will see an additional install in "C:\Program Files\Orbital." You will also see intermittent traffic from the Orbital service as it looks for other patterns we associate with compromised machines. As always, you can get the new installer at https://www.immunet.com. If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from https://www.immunet.com.
  7. Earlier
  8. These occurrences are very similar to (if not the same issue) to this previous topic. https://support.immunet.com/topic/4584-last-scan-never/?tab=comments#comment-15890 Obviously this issue goes unresolved since it has been already reported. This is something the devs need to (further?) investigate in my opinion.
  9. Hi, I have the same issue with Immunet on Windows server 2016 operating system. Immunet version 6.3.0.10988. Any advise is appreciated.
  10. Immunet should remember the date and what type of scan was performed and you shouldn't see a yellow warning on the UI. This can be caused by a connectivity issue or perhaps some corrupted history files. Could you open the UI, first click on the History tab then next to "View By" click on the little downward pointing arrow. This will open a small drop down menu, choose Scan History and see if your scan has been remembered there. Let us know if it's not present in this list as well.
  11. Ok, so I use Immunet, and whenever I open it for the first time after firing my computer up in the morning (since I turn it off at night), it shows the last scanned as "Never" https://i.imgur.com/2j6PJLa.png I'm pretty sure this isn't anything major, but it is mildly weird, especially when I ran a scan the other day. I get that this may be intentional, like for use of stuff that never really gets restarted, and to save a few bytes of space, but for home users, it would be nice if Immunet remembered that we scanned it prior to rebooting.
  12. Hello Pedro, I would suggest you send the Administrator bcouncil a Private Message and perhaps she can further assist you in this matter. Here's a link to her Profile page. Just click on the Message button to send her a PM. https://support.immunet.com/profile/33373-bcouncil/
  13. What is your Operating System and what version of Immunet are you using? Are all the scan options (Flash Scan or a Custom Scan) not functioning as well?
  14. Hi, I'm also having this problem in a windows server 2012 r2, sfc.exe consumes too much cpu. The same happened in another windows 10 pc, in that case the pc completly freezed, I had to disable Immunet from that pc. I'm using the last version 6.3.10988. Is any new release coming that solves this problem?
  15. Immunet is not running a full scan and remains as if the scan did not started. Anyone faced this issue before?
  16. Great idea to include some screenshots qwerty123, much appreciated! Those are defiantly ClamAV update files being quarantined. Have you created an exclusion rule for Immunet's "entire Program Files folder" with Windows Defender yet? If not, give that a try. If you're using Win 10 & you're not sure how to create custom exclusion rules with WD here's a URL that may be helpful. https://www.windowscentral.com/how-exclude-files-and-folders-windows-defender-antivirus-scans
  17. You may be interested to know that Windows Defender is detecting some immunet temp files as Trojan: JS/Foretype.A!ml This started happening 2 days ago, and has happened daily to me since. Their "more info" link, if useful: https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aJS%2fForetype.A!ml&threatid=2147724342&enterprise=0 Edit: Uh, pasting images to your forum is terrible, they lose a ton of quality in the process, practically unreadable. Here: https://imgur.com/15VhZ3Y
  18. That fixed it, altough the memory usage has now doubled and randomly spikes to 300 megabytes along with the cpu spiking to 25% sometimes
  19. Hello EmanuelJac, One of our most knowledgeable Administrators, Rob. Turner, just commented on why ClamAV might temporarily cause system resources to increase, here's what he had to say on the subject. The clam av engine loads it's full virus definitions signature set into memory: which takes from 100 to 600mb. add to that the clam scanning engine and virus definitions updater and clam alone can in a worst case scenario use in the the 700mb of memory range. Currently we have extra experimental blue keep preventative signatures out for a worm we're expecting that are inflating the usual virus definitions set size. You can try updating the clam av definitions set via the update button in the gui and running a full scan overnight. That might get you a smaller more concise set of definitions that'll take less memory and get you over the initial performance hump of building the local cache up.
  20. Immunet doesn't have any know issues running in virtualized environments and has been thoroughly tested in vmware workstation, vmware server and virtual box. and once even in Microsoft's cloud. Complaints we've gotten about running in visualized environments usually stem from unrealistic expectations of performance on non-dedicated hardware (i.e. cloud hardware thats randomly shared with strangers (e.g. the free trial and budget tier's of google, amazon and Microsoft clouds). There is just too high a chance someone like me is sharing hardware time and already pushing the machine to it' s limits (see paragraph below:) To set some hardware expectations, I test Immunet on a local desktop running dual xenon e506 2.13Ghz CPU's +12 gb ram (ouch), and 2 independent scsi 1TB drives ( one dedicated to my os & apps, the other dedicated to vmware images) and it easily simultaneously powers my win10 working desktop (chrome, waterfox, and IE browsers, email, visual studio, and an Android Virtual device) plus 3 copies of immunet running on vmware workstation images for win7x32, win7x64, & xpx32. It can also power an additional win 10x64, but at this point the images start to chug ( I think disk bandwidth is the bottleneck). I can easily run this same level of compute (dektop + 4 images) + an additional win10_x64 image on a single more modern Intel i-core 7 + 64gb of ram and 2 sata disks (one flash drive for the OS & apps an a 1tb 7200 rpm disk for the images). Getting back to your original problem, yochenhsieh you nailed it figuring out clamAV, I've seen similar stats with my benchmarking too. The clam av engine loads it's full virus definitions signature set into memory: which takes from 100 to 600mb. add to that the clam scanning engine and virus definitions updater and clam alone can in a worst case scenario use in the the 700mb of memory range. Currently we have extra experimental blue keep preventative signatures out for a worm we're expecting that are inflating the usual virus definitions set size. You can try updating the clam av definitions set via the update button in the gui and running a full scan overnight. That might get you a smaller more concise set of definitions that'll take less memory and get you over the initial performance hump of building the local cache up.
  21. 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.
  22. Just to be sure you were actually clicking the save settings button at the bottom of the config page after changing settings right? Immunet does save settings but changes don't take effect & aren't retained until you intentionally save them. Many web and mobile interfaces are designed around the paradigm of instant and pregnant effect "immediately on change", But most desktop & security software is still designed around the paradigm of one last confirmation of changes before taking effect. The idea, at least with security software is to give the user one last chance to fully think through the implications of their changes, and also to save users who mis-click/type a wrong setting by accident. E.g. in any security software you wouldn't' want to accidentally add a partially typed exclusion for c:\ even for a moment.
  23. Glad I could help! Immunet is a great product in my view too considering it's been developed to be used as a companion AV to a good number of major player's products. That gives users an added layer of protection if they so desire! I have it running compatible & stable (ClamAV module disabled) as a companion AV alongside Panda Dome Pro at this time as an example. If Immunet is to be used as a stand-alone AV then it is recommended that the ClamAV module & updates for it be enabled. If Immunet is used as a companion AV to a paid AV product it is also recommended that you turn off the ClamAV module.
  24. Ritchie, As soon and you mentioned AMP I fully remembered that I selected YES on both of those systems. I uninstalled Immunet and selected NO, rebooted and all is good now!! I agree that I will stay with AMP, but this is a GREAT free product for home users. Grant
  25. Sorry for the delay in responding & thanks for the added info. What it sounds like to me is that your copy of Immunet has some corrupted .db files if it's not remembering the previous settings configuration. I would suggest you try and do a clean uninstall. First uninstall Immunet, when asked by the uninstaller if you plan to reinstall Immunet again choose the "NO" option, this will delete all .db history files. Then reinstall Immunet but you will have to reconfigure the Settings and add any custom Exclusions you were using again. Let us know if this corrects the issue. I was given a free one year license for AMP a while back just to check it out myself so I am familiar with the software. It can be configured for home/personal use too. Having to use an on-line console to effect changes instead of a traditional UI did take a bit of getting use to I remember. This is a security feature since no unauthorized personal can make any changes to the software without the proper log in credentials to the console. Although not free like Immunet, AMP for Endpoints really is the better choice if you're using a multiple endpoint server environment for the simple fact that you can customize this software to your specific needs. Also with AMP you have the option of using the TETRA detection engine (which was part of the no longer available Immunet Plus). Originally based on Bitdefender's detection engine this now highly customized engine can sniff out usually hard to detect malware like root-kits, keyloggers, encrypted Trojan downloaders, etc... One more nice thing with AMP (compared to Immunet) is that you can configure it to automatically scan all in-coming email data packets for malware. A still prevalent attack vector. Compared to AMP, Immunet doesn't have no way near the customization options. I would suggest you stick with using AMP for Endpoints at least with your server! Something else I should mention is that Immunet is not licensed to be used in any "for profit" business, service, product or organization. If it's discovered Immunet is being used in this manner no further support will be offered. This info is included in the End User License Agreement (EULA) when you first install Immunet. Best wishes, Ritchie...
  26. Windows 10, Windows server 2016 and the latest version I guess. I downloaded from the main site. I am reviewing this product to see what all it offers compared to AMP. I know that it will not have all of the features, but I would assume I would be able to modify the settings.
  27. To be specific, since there is so much about this product, I am talking about customizing the settings. I am familiar with AMP which this product is very similar but you have to manage the setting locally and not over the cloud. So if I want to change the following setting to on. How is this done? Every time I make changes it reverts back. I have even tried this from the admin account with no luck.
  1. Load more activity
×
×
  • Create New...