Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/14/2020 in all areas

  1. 2 points
    Oh yes Ritchie, you are doing an excellent job.
  2. 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.
  3. 2 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
  4. 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.
  5. 1 point
    I'd like to wish everyone a safe & happy July 4th weekend! I know that many cities & municipalities across the country have canceled their fireworks display because of the pandemic. If you're lucky enough to live in or near a location that will have a display just remember to follow the CDC's guidelines. If you go out wear a face mask & continue to practice social distancing! Some health experts are worried that if people congregate in large crowds (like what happened Memorial Day) it could cause another spike in covid-19 cases. Cheers, Ritchie...
  6. 1 point
    Thanks for the encouraging words guys! "I do really appreciate it!" It is rather obvious by now that Immunet is not getting the priority it once did by the Cisco/Sourcefire management. I guess one can only hope that things will eventually improve and there is more input from the support staff. Best wishes, Ritchie...
  7. 1 point
    Are you getting paid for this job? I've been reading from your comments for some time that it frustrates you. If you don't get paid, you would quit as a moderator before it affects your health. Otherwise, it may be time to think about further training to expand your professional future. Have a nice day Frank
  8. 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!!"
  9. 1 point
    @zombunny2: Since my version was already up to date, your solution did not work for me. Thank you for the suggestion though. @ritchie58: Thank you. The complete uninstall did the trick. I hope the future updates don't need that workaround.
  10. 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.
  11. 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.
  12. 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/
  13. 1 point
    failed after a week
  14. 1 point
    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.
×
×
  • Create New...