Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 04/25/2020 in Posts

  1. 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...
  2. 1 point
    works fine ran few tests of crap detectionS went OK
  3. 1 point
    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
  4. 1 point
    Personally, I've never seen the cloud stat issue go unresolved this long after a new build is released. Now users are reporting update issues too. Are these related or what? "Hello, is there anybody out there!!!"
  5. 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.
  6. 1 point
    Hi, Can we please add an option to prompt the user if Cisco Orbital and osquery should be installed and/or enabled, before this happens? Maybe at installation time then as an option in the "Scan Settings" ? From Cisco: https://orbital.amp.cisco.com/help/what-is-orbital/ " Cisco Orbital is a service that uses Osquery to provide you and your applications with information about your hosts. Osquery exposes an entire operating system as a relational database that you can query with SQL to gather information about the host. Orbital can be used by both Cisco customers and their applications to query their computers wherever Orbital has been deployed. " Orbital, in the context of a privately owned endpoint, is a very intrusive tool and should not be enabled by default. Thank you.
  7. 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...
  8. 1 point
    I used Immunet alongside Sophos Home for maybe a year on a Windows 10 rig. It was probably the most stable and quick combination I've ever used - and that was with the ClamAV engine enabled as well! They never clashed once, even on files they could both detect. For ages I never bothered adding each to the other's exclusion list, and they played fine together. I eventually added each one's "program files" folders to the other's exclusion-list, when Sophos eventually got a false positive on one of Immunet's temporary files (I had ClamAV enabled). I think I also had to add another Sophos folder (somewhere inside "c:\programdata") to Immunet's exclusions. The combo was great and never gave me an issue once. Speed was similar to running just Windows Defender. The only way I could get quicker performance was to turn off ClamAV or switch to running just Kaspersky or F-Secure on its own.
  9. 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.
  10. 1 point
    Thanks everyone for their input. In my test environment I'm seeing no issues between the two applications as of yet. Sophos Home Pro and Immunet are functioning without any added configuration to quell any false positives. So far so good!
×
×
  • Create New...