Jump to content


Popular Content

Showing content with the highest reputation since 04/22/2020 in all areas

  1. 4 points
    What a "great idea" for Immunet users to voice their likes & dislikes Barbara! I completed the survey although, if chosen, I wouldn't be able to participate in the video conference since my computer has no web cam. "I would 'strongly urge any & all Immunet users' to complete this survey!" It really does only take a few minutes & that will give the devs much more insight into what Immunet users want in a new build. Best wishes, Ritchie...
  2. 3 points
    A couple of times this month I received a recorded phone call allegedly from an Amazon employee stating that they have detected possibly fraudulent activity with my account. I was then prompted to press 1 for more info. "I immediately knew this was a 'scam call' for the simple reason that I don't have an Amazon account!" After that I decided to do some investigation into this. "Amazon is aware of this scam and is advising it's customers if you do receive one of these scam calls don't fall for it, just hang up & 'definitely don't press any numbers' when prompted!" You can always check your Amazon on-line account yourself if you have any concerns and then contact Amazon customer service directly if you have questions. These Amazon scammers have also been using hacked email accounts. If you receive an email with similar content just delete it without clicking on any links or attachments included. You're also encouraged to report these calls or email to the Better Business Bureau, https://www.bbb.org/ and the Federal Trade Commission. https://reportfraud.ftc.gov/ Not a bad idea to also report this activity to your state's Attorneys General office. Regards, Ritchie...
  3. 3 points
    Hi Immunet Users, The development team working on Immunet (by Cisco) is looking for your feedback. Do you have 5 minutes to fill out a survey telling us more about how you use Immunet and how you think it could improve? Here is the link to the survey: https://www.ciscofeedback.vovici.com/se/6A5348A7201B0385 We know there is a lot of misinformation on the internet these days. If you would like to verify that this is real Cisco-sponsored research, email Barbara Shain, Cisco User Researcher, at bshain@cisco.com Thanks, Immunet UX
  4. 3 points
    I think this is an awesome thing!! I have filled out the survey and left my feedback. I really like that the platform is getting more support from cisco! As you said ritchie I would also encourage all users to fill out the survey, this will give us a chance to give feedback to the devs on how to improve the AV. The more of us that fill it out the better it will be. I can't wait to see how the survey helps and how it will help improve Immunet as a whole:) Stay safe everyone
  5. 3 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.3.0! This latest version of Immunet provides the same great protection against malware and viruses as before but also includes some new features, enhancements and bug fixes as below. Changes in 7.3.0 New & Enhancements: New endpoint threat activity detection engine New Immunet UI cloud connect status message replacing cloud stats message Bug Fixes: Connector cloud registration issue fix related to long network interface names Fixed an issue related to support package Mitigating fixes related to no-reboot upgrade and uninstall failures Immunet Installer bug fixes Other bug fixes You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe 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 to your participation in using our new detection engine and some help in cases of upgrade reboot failures issues, if encountered any. We would appreciate it if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for a reboot on upgrade. 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
  6. 2 points
    Oh, and by the way, I forgot to mention Ritchie, it goes without saying that all the work you do on these forums is really appreciated. It must be pretty hard as it's probably quite a frustrating and thankless task, but the fact you haven't given up is an absolute godsend to the remaining loyal users! I try my best to help too, but you seem to have super-powers and have usually already solved someone's issue before I've even read their post!
  7. 2 points
    Hmm, restore from quarantine seems fine now. I suspect this might just be related to system load. If the system is under stress when an attempt is made to restore from quarantine, it probably takes slightly too long for the GUI to communicate properly with the Immunet service, so the GUI assumes that the service isn't running, and/or the operation has failed. Intermittent error are the worst to diagnose and fix!
  8. 2 points
    Hello all We are happy to announce a new release of Immunet: Version 7.3.2! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes some new features, enhancements and bug fixes as below. Changes in 7.3.2 New: Exploit Prevention engine with Script Control support Bugfixes/Enhancements Improvements to endpoint threat activity detection engine Increased the number of process exclusions honoured by the Connector to 500. Improved stability of local UI notifications. Addressed an issue where System Process Protection exclusions would not work for processes that start before the Connector. Changed Connector driver altitudes to officially registered altitudes. Removed Connector-related events and logs from a computer when the Connector is uninstalled Addressed issues with file exclusions. General performance and stability improvements for Exploit Prevention engine Fix for the vulnerability described in CVE-2019-0708. Fixed Exploit Prevention engine compatibility issues with the following applications: APTA Connect MS PowerPoint 2016/2013 FSLogix Internet Explorer and different plugins CIG ACG MS Office Appv applications Visual Studio debugger Vizient and Open Text IRM Black Knight You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe 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 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
  9. 2 points
    I thought of yet another Idea that some users might appreciate. Add a dedicated CMD Command-line scanner to Immunet. That would be something useful for power users & IT technicians. Cheers, Ritchie...
  10. 2 points
    I support that 99,999% Jasen Dear Immunet_UX, please read the forum! please support your forum moderator! please tell the support that you are welcome to reply to e-mails! The Form is fillet out with my informations but please ask to ritchie because ritchie knows all important things and is our hero. I don't have high hopes, because Windows 7 ...
  11. 2 points
    Done! It's nice to see this project getting the care it needs. I'm eager to see what it's coming from this!
  12. 2 points
    Oh yes Ritchie, you are doing an excellent job.
  13. 2 points
    You made a great Job here Ritchie, you help a lot this community. Perhaps cisco doesn't have someone managing support of immunet. It seems when they have a free time they visit here to see what is going on.
  14. 2 points
    Hey all, For a more "generic" way to start/stop Immunet, you can do the following (possibly only works in Windows 10, I haven't tried on earlier versions * ) : Stopping Immunet From the command line: wmic service where "name like 'Immunet%'" call stopservice or from a batch file: wmic service where "name like 'Immunet%%'" call stopservice (Re-)Starting Immunet From the command line: wmic service where "name like 'Immunet%'" call startservice or from a batch file: wmic service where "name like 'Immunet%%'" call startservice The advantage of these is you don't need to know what version of Immunet you're using, so you don't need to work out the new service name after upgrades or edit any scripts you have. I have a custom script that downloads some of the Securiteinfo, Sanesecurity and RFXN custom databases, stops Immunet, copies them to Immunet's "ClamAV" dir, and restarts Immunet. By identifying the "newest" ClamAV dir and using the more-generic way of stopping the service, my script doesn't need editing every time Immunet upgrades. For my case, this increases Immunet's static file detection rate from about ~75% to >95%. I originally worked this out a while ago because I did a couple of upgrades where the Immunet service changed name from something like "ImmunetProtect" to "Immunet 6.0.4" --- * I don't know much about Windows as I've been primarily a Unix/Solaris/GNU-Linux user for both work and play since the late 1990s. I only maintain a Windows installation for the tuning software that allows me to flash custom maps to my car's ECU.
  15. 2 points
    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
  16. 2 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.2.8! This latest version of Immunet provides the same great protection against malware and viruses as before but also includes some new features, enchantments and bug fixes as below. Changes in 7.2.8 New & Enhancements: Added support for the Windows 10 November 2019 Update (version 1909) Added support for Windows 10 20H1 (Version 2004) (RTM Preview build: 19041) Improved visibility and enhanced protection against script-based attacks System Process Protection Improvements Improved Malicious Activity Protection engine to no longer detect on Google Chrome Stability Improvements in the Exploit Prevention engine Installer improvements to handle NoReboot upgrades and uninstall Stability Improvements in the Immunet SelfProtect driver Bug Fixes: Resolved Windows Connector service freeze issue on startup, under certain circumstances Improved the Windows connector process of gathering BIOS serial number, when needed, to properly detect hardware changes for registration with AMP Cloud Fixed a crash that could be encountered on shutdown Addressed issue where Windows Connector would fail to upgrade when installed alongside BitDefender AV Made stability improvements in the Connector installer Fixed an issue where ClamAV was taking a long time in scanning PDF files resulting into longer high CPU usage Updated ClamAV to 0.102.1, including changes related to the vulnerability described in CVE-2019-15961 Fixed an Exploit Prevention engine issue that could cause Google Chrome v78 and later to crash or display a renderer code integrity error This version also addresses the following vulnerabilities: CVE-2019-1010305 CVE-2019-12625 CVE-2019-12900 You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe 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 to your participation and help in cases of upgrade reboot failures issues, if encountered any. We would appreciate it if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for a reboot on upgrade. 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
  17. 2 points
    I'd like to report that the 7.2.8 upgrade through the UI took place with no problems. No reboot necessary! Great job on that guys! I did have to create a new allow rule with my firewall for sfc.exe but that's not uncommon behavior when a new build is installed. Some impressive changes have been made! A personal thanks to nirmeshptl for including a detailed change log with this announcement! Something I've been suggesting in the past when a new build is publicly rolled out. Best wishes, Ritchie...
  18. 1 point
    Hi folks, Sorry for the delay in responding. I took some needed time off. That is indeed a False Positive by the ClamAV module. I would suggest you report this at Immunet's FP reporting site. https://www.immunet.com/false_positive Also, since it is a ClamAV detection you can report this directly to the ClamAV support team as well. https://www.clamav.net/reports/fp Cheers, Ritchie...
  19. 1 point
    If you are running Immunet in parallel with another AV like Norton, you can safely disable the ClamAV module in Immunet. ClamAV is very CPU-intensive, and you may find that this is the component that's causing the CPU-spike. I personally leave ClamAV enabled, because I often add custom signatures to it - but it does really hammer that CPU. You should also make sure you've gone into Immunet's settings and excluded Symantec/Norton's directories under %programfiles%, %programfiles(x86)% and %programdata% as relevant/necessary. You may also want to add Immunet's folders to Norton's exclusions (these are %programfiles%\Cisco\Immunet, %programfiles%\Immunet, %programdata%\Cisco\Immunet, %programdata%\Immunet if you are running 64-bit). I'd be willing to bet a lot of your trouble is Norton and Immunet scanning each other whenever they do anything. As WilliamKing321 states, updates and things also cause this behaviour. I know when my W10 is running an update because Immunet in particular starts consuming massive resources scanning it all. And seeing as I'm a fairly infrequent Windows user, this is very noticeable every time I have the misfortune of needing to boot that operating-system.
  20. 1 point
    Ok, my bad! Sorry about the lapse in memory! The topic is pinned so that means only admins, devs or myself have the proper permission to post there. I'll add another thread there myself regarding your recent findings! Maybe not tonight but I'll get 'er done! As you pointed out it does seem to me too that Cisco has made the Immunet project an extremely low priority with (no doubt) minimal funding. You can't actually call it abandonware though since new builds are rolled-out from time to time, so it's still getting 'some' development. As far as responding to users support issues there have been 'no technical input' from any admins or devs since early April of last year when the admin RobT abandoned ship. It's just been little ol' me for over 10 months doing what I can to fill in as a support person. So in that regard I'm just as frustrated as you are zom. Believe me I've contemplated just leaving the project on more than one occasion. Being the forum's moderator for a number of years I can tell that Immunet's user base has already significantly diminished just by the amount of traffic the forum gets now. Especially before the Plus (paid) version of Immunet was completely scrapped in favor of developing an enterprise version of Immunet called FireAMP Connector (now called AMP for Endpoints) this forum was actually quite busy & interactive between users, admins, devs & mods. Besides myself there actually was more than one moderator for this site in the past! Oh, the good ol' days! If you too decide to leave the project I would like to say that, by your posts, I've always found you an intelligent & articulate fellow. If no one else, I've appreciated your input on the forum bro! You've got 14 'likes' which makes your community reputation good. Who do you think gave you most of those? I'll give you three guesses & the first two don't count, lol! Best wishes, Ritchie...
  21. 1 point
    ritchie58 Thanks for the research. Yes I was aware of these settings and tried to add the files you mentioned, but ZA refused to allow me to. Thinking that there must be a special way to do it in ZA was the reason for my post. I've decided that I'd had enough of ZA. (I'd had other issues in the past), I just uninstalled it completely and installed a new and different Firewall program. So far everything is working well with Immunet. Thanks again for your expert help. SG
  22. 1 point
    Ok, I sent out emails to a couple of Admins regarding this and a few other issues that go unresolved. Let's see what happens.
  23. 1 point
    I receive enough suspicious calls that I don't believe anyone. 2 days ago I got called from "Discover Bank support". I hang up and called the actual Discover, and they didn't recognize the number, and they had no record of anyone calling me. In the past, I got calls from "IRS" about "tax fraud", I won multiple cruises, ... Unless I initiate the call, I do NOT give any information.
  24. 1 point
    I watched the whole video. Great idea to add the screen grab video for documentation! There definitely is some sort of 'continuing' serious conflict between the game & Immunet. "Yeah, that process 'normally' does not continue to use up that much system resources for that length of time!" Weird! Have you tried to contact the game's developers to see if Path Of Exile has caused problems with other AV's & if there's a fix/workaround for that? This just a guess on my part but some games do use one or more Windows Temp file directories that might also need excluded. That's something else you could ask the game's developers. One more thing you could try is also disable 'Monitor Program Start' in Settings to see if that makes any difference. You will lose some of Immunet's efficacy by turning off this important setting however. Like I mentioned before, I do wish a support technician would get involved with this issue but I'm not going to hold my breath on that happening! Best wishes, Ritchie...
  25. 1 point
    Original article by Katherian - cybersecurity expert & Emsisoft blog contributor Who would have thought that holiday 2019 would be the “last” of the traditional holidays we’ve enjoyed for so long (at least for some time)? This year, there are no carolers, no shopping in packed malls, no ice skating in public rinks, and very little of all the other holiday fanfare we’re used to. Instead, many of us are home—in front of the computer for several hours per day—studying or working remotely. There’s also shopping, gaming, and watching, all done online as well. (Quick shoutout to the front liners and essential workers! Thank you!) Suffice it to say, holiday season 2020 is unlike any we’ve had in recent memory. And cybercriminals are having the profit of their lives. As the holidays approach, we start to let our guard down. Many people are on vacation and trying to relax. Cybercriminals, on the other hand, are hard at work. They’re busy breaking and hacking networks, planting malware, or sending out phishing emails. The attacks never end. And as if the holidays (and pandemic) were not burning enough holes in our pockets, a cyber attack can happen at any time, too. We’re pretty sure the last thing you need right now is paying hackers thousands of dollars of ransom to decrypt your personal and work files. So to help you avoid more headaches, here are four easy things you can do to stay safe online during this holiday season (and beyond): 1. Create a separate guest wifi If you have a few friends and family coming over, you absolutely need to create separate guest wifi. Particularly if you work from home since your business files could be accessible in your home network. Having separate wifi helps keep your home network separate and secure from your guests. That way, you feel comfortable giving out the password and not worrying about having to remember to change it after your guests leave. Yes, we still recommend you create guest wifi even if you trust your friends and family with your life. The folks at LifeWire wrote a great post on how to create guest wifi. 2. New year, new password Update your passwords, or better yet, get yourself a password manager. It will save you a lot of time and potentially a lot of headaches down the line. Hackers are busy breaking through accounts using publicly leaked passwords. Don’t make it too easy for them. Depending on how many online accounts you have, this could take a few minutes to an hour or two of your time. So think of this as an investment—you’re actually saving yourself hundreds, if not thousands, of dollars from avoiding a cyber-attack. Not to mention setting yourself up for security success. We have a winning guide on password management here. 3. Shop securely Found a unique gift from an eCommerce store? Doing more last-minute shopping (even if it’s just gift cards)? Before you checkout and provide your card info, make sure you’re on a secure site. First, try to only go to online stores you know and trust. Second, check the site’s URL and make sure there’s “https://” at the beginning, and the URL is what you expect it to be. For example, if you’re on Paypal, make sure the URL says “paypal.com” not a misspelled variant like “paypaal.com,” or any other unrecognized URL. Third, consider using a disposable or virtual credit card, especially for one-off purchases. Doing this helps further secure your information. To learn more about how to get one, go to Wallet Hub‘s guide to virtual cards. 4. Keep your security apps running Your antivirus, VPN, etc., are some of your most vital defense against hackers. Keep them running. Cybercriminals are going all out and will try to catch you everywhere on the web. Whether by downloading an app or file, clicking on an email, or visiting an innocent-looking website, you can fall prey to malware within seconds.
  26. 1 point
    I found a way to manually update clamav (from http://www.clamwin.com/content/view/58/27/), by creating a folder [C:\Users\All Users\.clamwin\db] then put daily.cvd and main.cvd into the folder. After that immunet main view will show updated version number at next launch. I am not sure if this was the root cause in my case but 2 issues I found: By default my C:\Users\All Users\ folder is inaccessible. I had to change the security permission by removing all users deny all permission. Creating folder starting with "." requires use of command prompt. However this does not enable auto update, albeit settings is, I still have to download the files myself. The immunet updater show downloading daily.cvd (7%, 15%, 22%) then always fails, saying 'unable to install updates, please try again later.'
  27. 1 point
    Here is something I would recommend you try. First uninstall the old build first. When asked by the uninstaller if you plan to reinstall Immunet again choose the "NO" option and proceed with the remainder of the uninstall. Then download this bootstrapper installer package & run it. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe This will install the newest build of Immunet. You will have to reconfigure your settings to way you had them & add any custom exclusions & automatic scan(s) you may have been using again. Please note: Some users have reported issues with updating the ClamAV module after installation with build 7.3.2 unfortunately. I hope this info helps. Regards, Ritchie...
  28. 1 point
    Dr. Franken...: What a filthy job. Igor: Could be worse. Dr. Franken...: How? Igor: Could be raining.
  29. 1 point
    Hi qwerty123, Have you tried to add a custom Exclusion rule for the autohotkey app(s) with Immunet? If not, give that a try and see if that fixes the issue. Just make sure you exclude the correct file path(s) for the app(s).
  30. 1 point
    Did you overwrite the old files in the folder %programfiles%\Immunet\clamav\[version] ??? Immunet use the old engine if you create a new folder with the new version of the engine in %programfiles%\Immunet\clamav\. This folder is set in the configuration files of Immunet and you cant edit this cofiguration file about protection functions of Immunet. (If you edit the file, Immunet cant start and stop protection od the system) So you have to stop the Immunet service and overwrite the old files i. e. in ...\Immunet\clamav\ Start the Immunet service and try again the update 2-3 times. This is not a Problem or Bug. ClamAV doesent Update the CVD Files if Engine is outdated. This is not a bug, it is a security feature. The update Button in Immunet only check for a Update of Immunet it self and runs freshclam.exe (from ClamAV) to update the CVD files. Thats all. So if the Engine is outdated freshclam.exe cancel the update. You can check this also if you run freshclam.exe in CMD.
  31. 1 point
    Hello Ritchie, the machine that started working experienced multiple failures updating the database after this first initial update - and then I think might have subsequently updated successfully. --- As an additional test...: I have tried Immunet on a second machine and nothing works to make the ClamAV module update on the second machine: I tried editing freshclam.conf to change the timeouts to much larger values. Update still fails. I tried booting from GNU/Linux and manually copying recent (a couple of days old) clamav cvd files to Immunet\clamav\[version] folder. Update seems to have been attempted once and failed. No further updates are attempted when clicking "update" in the Immunet GUI. I tried uncompressing the latest windows 64-bit clamav portable zip file from the ClamAV official website, overwriting the files in Immunet's %programfiles%\Immunet\clamav\[version] folder. No updates are attempted when clicking "update" in the Immunet GUI. I'm not sure what the difference is between the two machines. They're both 64-bit Windows 10 and Immunet was a fresh install (i.e. any previous installation had been removed with the "save settings: no" option). There is a log file in Immunet's ClamAV dir, which indicates that the ClamAV engine itself loads into memory, but I've not found any log file detailing what happens during an update attempt. It's a shame, as ClamAV can actually have a really good detection rate if you supplement it with the Securiteinfo and Sane Security custom databases. While attempting to diagnose it, I'm reluctant to customise my installation beyond anything required for the diagnostic effort, though.
  32. 1 point
    I am guessing you didn't read my post? I said that the link https://www.immunet.com/false_positive shows an error when posting it, from what I have heard it has been broken for months now. Guess the Devs can't keep up with all the bugs, not sure how many there are working on Immunet?
  33. 1 point
    It seems like there might be another issue in build 7.3.2, although I think it's an exacerbation of a long-standing one. I was running a full scan as a test in 7.3.2 and a few items (all false-positives so far) have been quarantined. Attempting to restore from quarantine results in "Restore from quarantine failed. Check agent is online". The agent is definitely online because I can still run more scans and quarantine (well, permanently lose) even more items. The unfortunate thing is, once a restoration attempt has failed once, Immunet won't let you even try to restore the item from quarantine again. This means that any files that have been quarantined and not restored are lost forever (subject to having adequate backups). This was always an intermittent (but rare issue) in Immunet, but in this latest build, it has happened on all but 1 of the detections in my initial test scan. This is why the "ask me" option in the settings should ask the question *before* quarantining, not after like it currently does.
  34. 1 point
    Would be nice to have false positive reporter in the Immunet program possibly in quarantine maybe in new UI update?
  35. 1 point
    Wow, that's strange! I've just reinstalled Immunet (I had uninstalled it, selecting "no", so that all data and settings would be deleted). The first thing it did was update the ClamAV databases successfully! I hope this was just a temporary glitch. Fingers crossed it's now fixed...
  36. 1 point
    Sorry to have been the harbinger of doom! I agree with lavamagma in that it is probably some sort of timeout issue. A while back I started experiencing update timeouts with both Freshclam and the "clamav-unofficial-sigs" scripts on my GNU/Linux boxes. It was basically caused by a time-out value that was too low in freshclam.conf (or wget/curl's default settings, in the case of the unofficial signatures script). Once the database had grown to a certain size, it was impossible to download it quickly-enough for the entire file to be complete before the timeout was reached. This was initially noticeable with the unofficial signatures script, because the SecuriteInfo "old" database is extremely large (~300MB), and SecuriteInfo restricts download-speeds for free users to circa 384KB/s. I believe a change to the default freshclam.conf fixed this in one of the recent versions. I suspect that you won't see this issue if you've already downloaded all the ClamAV databases once, because subsequent updates only require downloading the latest .cld patches. One way to test this would be to manually download the ClamAV databases from the web site, stop Immunet's service, copy them to Immunet's ClamAV dir, and then restart Immunet. Another option, if Immunet honours freshclam.conf settings, is to look to see if freshclam.conf is present in the folder, and set the ConnectTimeout and ReceiveTimeout settings to something like 300 (5 minutes) and 3600 (1 hour) respectively. I may have a quick look at these two options when I am next back in Windows.
  37. 1 point
    Immunet causes a RESULT_CODE_KILLED error in chrome 81-83, occurs randomly on some pages with YouTube. Disabling extensions does not help, only removing immunet fixes the problem. In the browser, on the chrome: // conflicts # R tab ETP Protecto Morphisec Information Security 2014 Ltd v4. 5EAAD359b6000 BR C :\ program files \ immunet \ exprev \ protector32.dll description link https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/
  38. 1 point
    I'm sorry, but I find the survey very disturbing. I cannot get the Immunet 7 service to stay running and development wants to ask how I feel about the importance of "history" and if I like the idea of moving history to the Windows Event Viewer. Are they serious? The location of "history" is the biggest thing they are worried about? How about they fix what they have before they rip away or add new features? How about leaning on your support forum for actual customer feedback? BTW, Windows Event Viewer interface is old and outdated. Why Microsoft has not changed the MMC interface is beyond me. I have to resort to LDAP queries and other scripts to properly search/filter event viewer at work and now Immunet wants to know if I'm ok with that on my home computer? No thank you. I would rather see some Cisco AMP for Endpoint features making their way into Immunet. I would like to know what my family members were doing on a computer when an incident occurs. AMP makes this very nice. This is a step forward. Windows Event Viewer is a step backwards. If Cisco is not willing to resolve the issues with Immunet and properly support the consumer base, then pull the plug and let it die. I really hope Immunet development continues and improves. Jasen
  39. 1 point
    Hi Gordon, You're just one of many that have run into this same update/connection bug with the 7.3.0 build unfortunately. I use Immunet as a companion AV to another paid AV product. For that reason I didn't use the ClamAV module so that's never been a problem for me. However I did like the added security that the ETHOS & SPERO cloud engines provided. After I noticed that cloud lookups were not taking place I had no other choice but to uninstall Immunet for now. I mean, why keep an app installed that is essentially useless! So now I'm waiting for the developers to fix this issue before I reinstall Immunet again. What's particularly disconcerting for me is that no admin or dev seems to want to even take the time to look into this or let users know they're working on it. "I hate to sound so pessimistic but your guess is as good as mine when/if this bug will be adequately resolved regrettably!" I know Cisco has made Immunet a "Low Priory" project but this is getting absolutely ridicules how long it's taking in my honest opinion! Has Immunet become complete ABANDONWARE? I'm starting to have my suspicions and this ongoing scenario is really starting to bum me out! I've been involved with this project for over 10 years now and "this is the worst situation I've encountered in all that time!" If things don't improve soon I'm not sure how much longer I will wish to stay involved with this software. What's the point of helping to support abandonware that no longer even works properly? Frustratingly, Ritchie...
  40. 1 point
    Tried virus samples from https://www.eicar.org/?page_id=3950 and online scaner did not work!
  41. 1 point
    I have version 7.3.011792. It works fine for a week or two after a complete uninstall telling immunet I will not re-install - remove all files I also go into the directory to be sure every thing is gone and delete completely anything left and restart.. It works fine a week or two, the it is back to the same thing - immunet up to date but it indicates a problem. I poked around a little trying to narrow down the problem. If you turn off "Enable ClamAV Engine" in settings (leave update definitions on), it IMMEDIATELY fixes the problem. Apparently the newest version is unable to always use the ClamAV engine and returns the error. Virus definitions and Immenet interface are up to date, but ClamAV is not enabled. It looks as if Immunet does not patch problems. I don't know that ClamAV can be successfully updated manually, but since the virus definitions update, turn off update ClamAVEngine in settings to avoid the error message. Maybe Immunet will fix the problem in the next big release. If the error message does not go off when you turn off enable ClamAV engine, ClamAV may not be the problem. Keep looking.
  42. 1 point
    Everyone is entitled to there opinion Frank. What I would like to see is more input from some knowledgeable support staff helping users with there technical issues. I'm the forum moderator for this site but I've been thrust into the role of doing the duties of a support person to the best of my abilities. I've been getting almost no help for over several months now! I have no clue as to why that's happening! The admin Rob T was a great help on the site but he's been M.I.A. since April. That certainly isn't the first time this has happened in the years I've been doing this. "It does get 'rather frustrating' when I get no assistance at all on the site!!"
  43. 1 point
    I noticed that I get the "not updated" status on a fresh install until I manually perform a scan (even just a "flash scan" will do - and it only takes a minute or two). Even after manually updating Immunet, I noticed that closing and re-opening the GUI (or restarting the computer) resulted in the "not updated" status. The only way to fix it was to update then scan. On every machine I've tried so far (all some variant of Windows 10), the following seems to fix it: 1. Open Immunet GUI 2. Manually check for updates. Wait a few minutes, to give the ClamAV database a chance to update, then close the update dialog. 3. Now run a flash scan (or full scan, but beware a full scan can take hours whereas a flash scan only takes minutes). It seems as if forcing an update then forcing a scan resets Immunet's indicators and it all works again.
  44. 1 point
    Ritchie - I've added the three products to the firewall allow rules - no change. Rebooted, the device, double checked to make sure the firewall rules were still in place - they were. The application keeps telling me I need to update and there's no update available.
  45. 1 point
    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.
  46. 1 point
    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
  47. 1 point
    @gogos888 Thanks for pointing out the issue. As @ritchie explained above, its just a stats issue on our backend side. Immunet is still connected to our servers and does not affect protection Immunet provide in any ways. We will try to git it fixed soon. Thanks @ritchie58 for your response.
  48. 1 point
    I'm sorry to say that the Orbital code can't be disabled or deleted once it's installed. It's now an integral part of how Immunet's protection works for you. Not everyone gets the Orbital code actually. I never got the code installed on my PC. A person gets the Orbital code if Immunet detects one or more security weaknesses with your Operating System. That fills the gap for those possible vulnerabilities so to speak. Interesting idea to let the user decide if he/she wants to use it though. You could start a new topic in the "Ideas" section of the forum regarding the subject. That's not a bad idea! Regards, Ritchie...
  49. 1 point
    Thanks Ritchie! I should have been a bit more specific with "low power" like HTPCs and basic builds I have been a fan of Immunets cloud ability's for a while. Yeah my personal build is a bit overkill Donavyn, I set up a VM to test Sophos with immunet and my results are pretty good like yours. I did run in to a bit of slow down with opening larger programs, but turning off monitor program start seemed have fixed it. Have you run in to that? Could have just been me as I only allocated 4 gigs ram to it. I usually keep that setting on though. Other then that it seems to work very well with both AVs running. I'll keep testing it for a bit to see if anything under different scenarios else come up.
  50. 1 point
    Fixed on the latest version until eventually it comes back. Every version I've ever used has ended up at high CPU utilization for long periods of time (just for sitting idle on active scan, not doing any actual scans), 90% to the point I have to kill it. Debugging is not enabled (and I never enable it). The log file thing was just an older issue I was describing. I don't think I will go to any future version but I recommend that the false positive thing happens way too often. Do reach-out to major vendors like Microsoft & Adobe and see if they are willing to do testing on your newer versions before they get rolled out. I am sure they are just as keen to not have a 3rd party AV kill their users' installs as much as you. My conclusion is that I have spent a significant amount of time dealing with Immunet issues that actually getting a virus would take less time to deal with. It should be a set-it-and-forget it type of thing.
  • Create New...