Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/28/2010 in all areas

  1. 3 points
    Hello all, We are happy to announce a new release of Immunet: Version 6.3.0! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Improved detection coverage Windows 10 RedStone 6 support Update ClamAV to version 0.101.2 Improved status in Windows Security Center Bug fix to exploit prevention engine Immunet installer now handles all legal windows characters that can be in a Windows file path for default install Fixes to mitigate high CPU/Memory issue some users are seeing on Windows 10 during Windows updates. As always, you can get the new installer at https://www.immunet.com. We strongly recommend existing Immunet user to upgrade to v6.3.0 and start taking advantage of new improvements. 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 If you do encounter problems with the new version of Immunet Protect, please let us know via forums at http://support.immunet.com Thank you for your continued support! The Immunet Protect Team
  2. 2 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.0.2! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes NoReboot upgrade beta. The Immunet Windows Connector often requires a reboot to complete the upgrade. This can be problematic for end users who have to time reboots, if they are in middle of critical updates or working on some important project, in order to upgrade the Connector, raising barriers to upgrading more regularly. This feature is to remove the requirement for reboots when upgrading the Windows Connector for good. Expected upgrade behaviour for Immunet users: * Upgrades from Connector versions < 7.0.0 to 7.0.0+ require a reboot to complete * Upgrades from Connector versions 7.0.0+ to any higher version do not require a reboot to complete Looking forward for your participation and help in cases of upgrade reboot failures issues, if encountered any. We would appreciate if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for reboot on upgrade. You can get the new installer here. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe 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 http://www.immunet.com/index Changes in 7.0.2 Improvements and updates: No Reboot upgrades No Reboot uninstalls New kernel logs for Connector upgrades and uninstalls Installer improvements to handle NoReboot upgrades and uninstall Fixes: Stability Improvements in the Immunet SelfProtect driver Fixed reference leak in asynchronous kernel exclusions Stability Improvements on Immunet Protect driver
  3. 2 points
    Hi all, The newest 6.3.0.10988 build of Immunet has a new running process called cscm. Microsoft made some improvements as to how antivirus solutions can better protect their software from unauthorized intrusion. It's a fact that some malware has the capacity to disable the installed AV, usually through unauthorized code-injection methods. This added security protocol will make it much harder for malware to disable Immunet. For anyone that wants to read this Windows Dev Center article (thanks Wookiee) regarding this added security protocol click on this link. https://docs.microsoft.com/en-us/windows/desktop/services/protecting-anti-malware-services- Regards, Ritchie...
  4. 2 points
    Yup, this is the right place for your questions. Sorry, Immunet doesn't offer spam or phishing protection, Interestingly , older versions of Immunet could scan local Outlook.pst email databases for malicious email attachments, but we shelved this feature for a couple reasons: 1) the average user moved to cloud email services (gmail, Hotmail, outlook.com / etc), most of which provide absolutely minimal span and phishing protection, making local emal scanning redundant 2) Microsoft changed their outlook.pst format and libraries a couple times resulting in Immunet failing to quarantine just the attachment from within the outlook.pst database file; and instead quarantined the entire email database.
  5. 2 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.0.0! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Credo and AMSI. Credo is a ML engine that allows endpoint connector to extract feature print of a PE file and send to the cloud to see whether the file is malware or not. ScriptID engine allows AMP connector to analyze scripts prior to execution. It is based on the Windows Antimalware Scan Interface (AMSI). In 7.0.0 version of connector only PowerShell scripts are analyzed. You can get the new installer here. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe 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 http://www.immunet.com/index Changes in 7.0.0 Improvements and updates: New Credo engine New ScriptID engine for AMSI Query improvements in Immunet Protect driver Improvement in preforming Immunet registration Improvements in Connectivity test tool Curl version update ImmunetSCMS service now handle crash reporting Driver updates to support No Reboot upgrades New certificate for the ELAM driver Improvements on the Malicious Activity Protection (MAP) to reduce false positive Fixes: Stability Improvements in the Immunet Protect driver Stability Improvements in the SPP Stability Improvement on Immunet Protect shutdown Stability Improvements in the Exploit prevention
  6. 2 points
    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
  7. 2 points
    I've sent it to Clam so guess we'll see what they say. Thanks for your help!
  8. 2 points
    I would venture to guess that the ClamAV module is scanning files at the same time as they're being created by Visual Studio. Try creating a custom Immunet Exclusion rule for Visual Studio's entire Program Files folder in Settings. Then turn ClamAV back on, restart your computer and see if the same behavior persists. You can also directly contact the ClamAV developers to inform them of this issue if you wish. https://www.clamav.net/contact Best wishes, Ritchie...
  9. 2 points
    Try a restart of your PC and also press several times the update button!
  10. 2 points
    First of all that is an "out-dated build" of Immunet (seen it, this vid is old). The current version is 6.2.4.10819. This video has absolutely no current validity since it doesn't relate to the newest build. Secondly, there have also been some recent infrastructure changes that will help in defeating the spread of such malware more aggressively within the Immunet cloud community.
  11. 2 points
    You can try to upload the two files on Virustotal and check the results from different AVs https://www.virustotal.com/#/home/upload
  12. 2 points
    I am running Windows 7 Pro on an older desk top and during the last few days have been getting a Virus detected and quarantined message on virtually every application that I use. I have been using some of these sights for 10 plus years and never had this issue previously. It persists even when I switch from Firefox to Chrome. I just ran a full scan of the entire computer and get reports of no virus found and have verified that the latest update is installed (as of 2/2/19). When I go to manually initialize Immunet, I see a note that the computer has never been scanned and is not secure even when I have just run a full scan. A typical warning is that f_0001f3 has been detected as Clam.Txt.Trojan.Generic-6840302-0. Quarantine was successful. I even got a message that Firefox Installer was a Trojan. This is very annoying and I would like some suggestions to resolve this issue. Nelson
  13. 2 points
    confirmed, is defiantly a Clam false positive. Thanks to everyone who reported this. we're reprod it internally and are working on a fix. In the mean time, if you turn off the clam AV engine in Immunet's settings that'll prevent the constant FP notifications and still keep your computer protected with the immunet cloud engine. We'll notify the thread to turn clam back on as soon as the fp is fixed.
  14. 2 points
    it might be an issue with a signature, I am looking into it.
  15. 2 points
    it looks like you are using clamav, not immunet. ClamAV gives you the ability to run commands- immunet does not. As far as multi-threaded scans in ClamAV, you could just do a clamd scan with multithreaded- should work
  16. 2 points
    Why not brother.. You can download Avast offline installer from here and Know how to uninstall avast step by step here.. The step by step guide also has a link to the avast removal tool
  17. 2 points
    Hello everyone, I see a lot of future in this software, its interface is destined to "the end", compared to other interfaces today ... But instead of just talking, I made a new design for Immunet AntiVirus .. .I only did the basic part, in case I get you back, I can go back to work on the interface and finish for a new look to the software. Here are the images: I look forward to the feedback from the developers, and also from the community. Att: Lucas Lks
  18. 1 point
    Hi, I just have some free time to play with UI concepts - so I came up with these artistic prototypes. What do You Guys think? Any thoughts? My goal was to keep current functionality -> development, not a revolution. Regards, Marcin Full View: https://imgur.com/a/im7fywl
  19. 1 point
    Will be nice can protect the program with password so cannot be edited or deactivated by other PC users.
  20. 1 point
    To include the ability to lock the UI with a password is not a bad idea in my view! If the computer is used by multiple people (especially if kids are present) in the household that could prove to be beneficial. Actually Immunet's enterprise version called Amp for Endpoints uses an on-line console instead of a traditional UI. This ensures that no unauthorized personal can make any changes unless one knows the user name & password to the console.
  21. 1 point
    Because of version 7's excellent improvements to Immunet, I am once again a user and fan of this AV. I have a few comments concerning Immunet's Clam component: 1) I *think* Clam is included with Immunet primarily to enable a user to do a scan without needing an internet connection... correct??? 2) Some folks (I am one of them) do not need Clam because they use some other on-demand AV scanner (such as HitmanPro, McAfee Stinger, Dr.Web CureIt, Emsisoft EEK, & Trend Micro Housecall). I *suppose* this is the reason why Immunet's GUI offers the option of disabling Clam... correct??? 3) However, although Clam can be disabled by using the GUI, Clam is nevertheless resident on one's computer, unnecessarily taking up disk space. It would be nice if the option to NOT use Clam were instead included as an option in Immunet's install routine, so that it would not be loaded onto one's computer at all. By the way, my favorite computer loves immunet because it is VERY easy on RAM & CPU, and it scans really really fast. A beautiful job of programming! Aloha from Hawaii, bellgamin
  22. 1 point
    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
  23. 1 point
    @Rob.Turner I can confirm that I can either see text or get a download prompt for every one of those links supplied. @ritchie58 Don't worry, I of course still allow Windows updates on my internet-connected machine. I have Pro so am fortunately able to defer any non-security updates for up to a year, which I recommend everyone should do before their PC gets bricked. It gives Microsoft a good chance at fixing the worst of their problems before their "improvements" reach your machine - unless the next broken update they release without testing just happens to be a security one... As a side note, When your Windows 7 reaches end-of-life, one option would be to just have a dual-boot scenario: Switch to GNU/Linux for anything that requires the internet, and keep your unsupported Win7 installation as-is, unpatched, for any obscure software you might still need to run occasionally, but can't get on GNU/Linux. You'd just need to keep the Windows 7 installation offline, for instance by disabling your network interfaces in the device-manager, or unplugging your network cables. I'm aware there's a learning-curve, it's a matter of personal taste, and It's not possible for everyone, but I'm about 90% of the way there. I used to dual-boot and value both OSs for their respective qualities, but I'm rapidly getting to the point where I just need to get the work done and Windows now gets in the way of that for me.
  24. 1 point
    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.
  25. 1 point
    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. 1 point
    Cool, thanks for taking the time to report this to the ClamAV team! Much appreciated Macbeth!
  27. 1 point
  28. 1 point
    Hi Bitsomper, I'm sure you've read the previous threads to this topic so the devs are definitely aware of the situation. Unfortunately the newest 6.3.0.10988 build did not address this known issue. Thanks for adding this thread! Maybe the devs will see this issue is still causing problems for users and "eventually" do something about it. Immunet really needs to incorporate a way to upscale the UI for 4k screens! That is a obviously needed upgrade, that seems to be continually overlooked, that should be implemented with some new code in some future build. The sooner the better in my opinion.
  29. 1 point
    Instead of downloading an online installer, try the same with the offline installer. You can download it here. Also, ClamAV detects a lot of false positives, so no need to worry.
  30. 1 point
    Problem solved. I used Immunet installer (found in the \Temp folder) in a Windows 10 virtual machine, then I monitored the uninstaller process handlers while I used Revo Uninstaller. Then I erased (on my real, affected PC) all of the files the Uninstaller modified/erased (Cleanup agent included) and that Revo had to erase too (I used a Linux LiveCD as some files/registry entries were blocked). It looks like Immunet uses Cisco's AMP, (Self Protect, Policy files...) and all of those files are kind of hidden and well protected. After all that was done, Immunet installed correctly. If someone's having this problem, please don't do as I did, as this process is very, very risky and Windows will most certainly get damaged. Just disable your antivirus before installing KB4503293 update. It seems like this problem could happen with any antivirus, but Immunet has no Removal Tool and so the only fix is to reinstall (a system restore point won't do the trick) Windows. Anyway, this is a really unique problem so I don't think someone will ever run into this issue where Windows removes Immunet files (and uninstallers). Still, Cisco should offer a Removal Tool to avoid these situations. Thanks for all the help you've given to me, ritchie58.
  31. 1 point
    Sorry to hear Revo wasn't much help to you Chame. Usually that software is great at dealing with uninstalling stubborn programs or finding left over files from a botched uninstall. Since no other user, thus far, has reported the same issue I believe this to be an isolated, anomalous occurrence. I think it really wasn't a good idea at all to just start manually deleting stuff, especially in the registry. Do you use any type of system imaging or did you, by any chance, create a bootable Win 10 emergency recovery CD or USB device that will write over any corrupted Windows Operating System files or re-install any missing ones? If not, I'm at a loss as to what to try next. Maybe it might be that you'll have to re-format your OS unfortunately.
  32. 1 point
    It's a hell wonderful idea! I promise I will share this great news when new Immunet will be in use with all my friends and tell them what to do to be secure and safe. You are really cool, guys! Are you going to create several VPN servers or only one?
  33. 1 point
    It should be fixed now, you will want to update your signature set. It was a ClamAV signature that caused the issue.
  34. 1 point
    I think what Kirav is talking about is the Metro theme configuration you can use with Win 8 & 8.1. To make the UI look similar to this I would conjecture. I have to agree with Kirav, it really has been a while since the UI got updated to "something" newer/different looking. Folks keep pointing that fact out!
  35. 1 point
    You could use ClamAV for Windows, which is still opensourced. I've not been with the project long enough to know of the complaints for years on logging. For me , I was not aware people cared about this until this thread. I do think the product SHOULD be more user-friendly- I am working with the dev team to make that possible in the future.
  36. 1 point
    Thank you Richie a VPN in Immunet is a great suggestion, and thanks Cyrille for the +1 and being willing to pay for it. I've escalated the suggestion and can only wait and see what comes of it.
  37. 1 point
    The difference between http and https is that with https any server page requests from your computer are automatically encrypted then decrypted by your browser using Hypertext Transfer over Secure Sockets Layer protocol. This means that any data sent to the server is encrypted so log in data, for instance, is much more secure from unauthorized access. There are plenty of http sites on the web still but more and more of them are switching to the https protocol as time goes by. If you are on a http site just be careful what personal information you divulge because hackers can more easily infiltrate and steal personal information from non-encrypted sites. That's why I was so glad to see this site "finally" start using the https protocol. Something I was advocating for in the past.
  38. 1 point
    it only happens if you use f-secure products with Immunet.
  39. 1 point
    You can submit the files to us for review on immunet.com. If they are found to be malicious, we will write detection for them If you can provide the SHA's of the files, I can look at them quicker,- though not necessarily.
  40. 1 point
    Immunet is undergoing major changes. For a long time, the AMP infrastructure and Immunet infrastructure have been the same. But, we are changing that now to separate the customers of AMP and Immunet into their own cloud infrastructures. As of right now, any Immunet user who is not on version 6.2.0 is on the old infrastructure and will need to upgrade to the latest version as soon as possible. We plan on decommissioning the old infrastructure (that means any versions prior to 6.2.0) on Feb. 4, 2019. What does this mean? This means that all users who aren’t already, need to be on version 6.2.0. If you are on 6.2.0 now, you will not see any changes and do not need to worry. If you are on the older version, you need to upgrade immediately. If you do not upgrade before Feb. 4, you may experience service interruptions and may not be able to upgrade Immunet or receive protection. What happens if you do not upgrade before the decommission? You will need to uninstall and reinstall the software once the old infrastructure is decommissioned. We urge everyone on a version prior to 6.2.0 to upgrade Immediately. If you have any questions or concerns, please contact us via the support forums or posting below.
  41. 1 point
    What is your Immunet version? It should look like this: The copy fail should be fixed in the later versions of Immunet. Though, sometimes it happens because it is not handling a odd character in the BIOs name such as a tilde key, or something similar. You could attempt to boot into safemode and try that, but if it is the bios name triggering the copyfail, then that wouldn't work without a bios change.
  42. 1 point
    Immunet is undergoing major changes. For a long time, the AMP infrastructure and Immunet infrastructure have been the same. But, we are changing that now to separate the customers of AMP and Immunet into their own cloud infrastructures. As of right now, any Immunet user who is not on version 6.2.0 is on the old infrastructure and will need to upgrade to the latest version as soon as possible. We plan on decommissioning the old infrastructure (that means any versions prior to 6.2.0) on Feb. 4, 2019. What does this mean? This means that all users who aren’t already, need to be on version 6.2.0. If you are on 6.2.0 now, you will not see any changes and do not need to worry. If you are on the older version, you need to upgrade immediately. If you do not upgrade before Feb. 4, you may experience service interruptions and may not be able to upgrade Immunet or receive protection. What happens if you do not upgrade before the decommission? You will need to uninstall and reinstall the software once the old infrastructure is decommissioned. We urge everyone on a version prior to 6.2.0 to upgrade Immediately. If you have any questions or concerns, please contact us via the support forums or posting below.
  43. 1 point
    Yes, it will have the same level of protection
  44. 1 point
    The cloud stats message, shouldn't have anything to do with you having the latest signatures. It should not leave you unprotected. You will need to make sure you are running the same signature set on both versions.
  45. 1 point
    Hello all, We are happy to announce a new release of Immunet: Version 6.2.0! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Malicious Activity Protection (MAP) engine for detecting ransomware, System process protection detection notifications, Connector UI improvement, Performance improvements, Support for Windows Server 2016 and other bug fixes. As always, you can get the new installer at https://www.immunet.com. We strongly recommend existing Immunet user to upgrade to v6.2.0 and start taking advantage of new features and improvements. 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, you can always download the latest installer from https://www.immunet.com and execute it to get the upgrade. If you do encounter problems with the new version of Immunet Protect, please let us know via forums at http://support.immunet.com Thank you for your continued support! The Immunet Protect Team
  46. 1 point
    We are aware of the issue and should be releasing a fix 'soon'
  47. 1 point
    Hi Art, what version of Win 10 are you using? In the mean time here's a few things you can look into. Make sure there isn't a program you use that may interfere with Immunet's installation such as your firewall of choice, another AV, sandboxing software, behavior blocker, etc... Since Immunet uses a bootstrapper installer an "uninterrupted internet connection" is also required when the files are being downloaded & during installation. You could also try a new installer package in case the one you downloaded got corrupted some how. Here's a link to download the newest installer. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe Best wishes, Ritchie...
  48. 1 point
    Every software has bugs, the point of reporting these issues is so that we can fix them. Immunet bugs go through ME now, I have only been on this project for a short time. I am trying to FIX any and all problems reported. Though, this will obviously take time to find WHY something is not working right. Now, if you want to enable debugging, and wait for the scheduled scan to not kick off again- then generate a support dump, and send it in- I can look at fixing it.
  49. 1 point
    Hi Valnat, Immunet & Amp for Endpoints do share the ETHOS, SPERO and the ClamAV engines & sigs. AMP also has the TETRA module that was only available to the Plus (paid) version of Immunet when it was still being supported. TETRA has the ability to detect threats that other AV engines may have trouble with. For instance, encrypted rootkits to name just one. I hope that answered your question. Regards, Ritchie...
  50. 1 point
    Hey everyone! Yes, more can be done with the overall design, and I can bring it up to the rest of the developers for a potential future release. @lucasLKs, you must know I am a sucker for anything dark themed because I dislike bright, bright colors in software. I actually really dig the design, though- I would probably tweak somethings. personally- interfaces are important for people to understand and use, and command-line only is more outdated than anything ( depending on who's actually using it, skill level, etc). I am simply saying, you all ARE being heard, and I will bring it up to the rest of the team.
×
×
  • Create New...