Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. ritchie58

    Mp3Tag Blocked After Renaming Files

    That is also a possibility Zombunny! Immunet 6 does have a exploit/system process protection feature that could have been triggered instead of a malware quarantine response. That's not to say that my extrapolation about possible temp files was way off base. Like I mentioned in the previous thread I have seen this type of quarantine behavior before where no file is present in the Quarantined Files list because it's just a temp file that already got deleted but you may be right about a exploit response instead. Great extrapolation on your part! Cheers, Ritchie...
  3. Yesterday
  4. Zombunny

    Mp3Tag Blocked After Renaming Files

    Apologies for resurrecting a thread after a few weeks, but I think I've had this same issue with another program, and it's not a signature detection. Your mp3 batch tag operation triggered Immunet's rudimentary ransomware protection, so the operation was stopped and the program terminated; however the lack of a signature detection resulted in the program being blocked but not quarantined. It makes sense, if you think about it. What does ransomware do? It locates any document files it can find, and goes through them sequentially. One by one, each file is opened, changes are written, the file is closed, and the next file is opened... What did your mp3 tagging tool do? Go through a folder of data files (mp3s), and one by one, open each file, write a change to it, close it and progress to the next! So in summary, the program's behaviour was blocked, but nothing was probably quarantined.
  5. ritchie58

    How to unlock a file

    Hello pufig, first of all it is very, very important to make sure that what you're attempting to restore is a False Positive and not actually genuine malware. One great way to do this is to check the file with VirusTotal.com's database first. https://www.virustotal.com/#/home/upload After you are "absolutely certain" that the file is not malicious you can click on the History tab -> to the right of View By click on the little downward pointing arrow -> this will open a little drop down menu and click on Quarantined File History -> find the file in question from the list, click on it and choose the "Restore" option. This automatically moves the file from Quarantine to the Exclusion list where it will no longer be scanned.
  6. Last week
  7. Antivirus blocked the file, how to remove the lock from it?
  8. Hey Wookiee, just wanted to get back to you on this subject. Since upgrading to the new 6.2.4 version I've not encountered the same behavior so that's the reason for the diagnostic data not being sent. Like we talked about in our PM's I firmly believe that the exclusion issue and what I saw had to have been directly related. However, if I do encounter iptray not loading properly again then I will expedite the requested data to you. Your friend, Ritchie...
  9. Rob.Turner

    The immunet Service is not running

    I think what's your probably seeing is the Immunet *UI* only supports 1 user at a time. The real time virus protection component does protect all simultaneously connected users, but only the first user to launch the UI ( system tray icon / application with the scan now & settings) will appear to be connected. All other users will have Immunet UI's that appear disconnected. Further if the user who has the connected UI logs off or manually closes the Immunet tray icon, the UI connection will be go to the next user who has had the Immunet UI running the longest; and their disconnected UI will switch to connected. Note when a rdp user disconnects their programs are all left in a running state. Including leaving the the immunet UI running, potentially holding the Immunet UI connection. Given the above limitations, what we usually see when the UI appears disconnected in in multi-user environment is that the one Immunet UI connection has passed to an unknown user who disconnected when they were done without actually logging off. If you think this has happened to you The least disruptive way to reclaim the Immunet UI connection is to: 1) login as an admin user 2)start -> run -> "Services" -> stop the Immunet Service 3) open task manger & enable show processes from all users. Then task kill all the sfc.exe processes ( sfc.exe is Immunet's UI process). Note if you get a message from task manager saying sfc.exe could not be terminated it's probably because the Immunet service hasn't been fully stopped yet. 4) Once all the Immunet UI's are closed restart the Immunet Service and then UI and it should appear connected within 30 seconds after both are started. Another approach is to use the task manager to force log off other users who have the Immunet UI / sfc.exe open and then restart the UI on your own session. This approach doesn't require stopping the immunet service. Note though if you log off someone who is actively using he system you can expect them to immediately re-logon and potentially take the Immunet UI connection token again. The last and easiest approach is to restart the machine and be the first to login - note if the machine is set to auto logon at startup then the auto-login user will be the first to login and get the working Immunet UI session.
  10. Wookiee

    New release v6.2.4

    It fixes the exclusion lists
  11. ritchie58

    Where's My Exclusion List?

    Great news! If you did encounter this exclusion list issue all you have to do is upgrade to the newest 6.2.4.10819 build of Immunet and your Exclusion list will be restored. This build also has some other improvements, bug fixes & with the infrastructure change occurring I would definitely recommend to anyone that's running a earlier version to upgrade ASAP. I got this new build seamlessly installed right through the UI (a re-start is necessary after installation) or you can download the latest 6.2.4.10819 bootstrapper installer package here if you wish to install it manually yourself. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe More info about this new build can be found here at this Announcements topic. http://support.immunet.com/topic/3723-new-release-v624/?_fromLogin=1 Cheers, Ritchie...
  12. ritchie58

    New release v6.2.4

    Hi Andrew, you provided the answers I was curious about. The upgrade got successfully installed through the UI which is a nice touch! Glad you also included a URL for the downloadable installer. Also, really glad to see that the exclusion issue has been rectified with this build and I'm no longer getting numerous pop-ups from the exploit/process protection. That way I no longer need to constantly use Gaming Mode which is not ideal at all of course! "Way to go guys, great upgrade!"
  13. Andrew G.

    New release v6.2.4

    We are happy to announce a new release of Immunet: Version 6.2.4! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Support for Windows Server 2019 RTM Support for Windows 10 October 2018 Update (Version 1809) RTM Fix for Exploit Prevention Engine incompatibility with Office 365 32-bit on Windows 10 October 2018 Update (Version 1809) Fix fordefects found in Exploit Prevention module As always, you can get the new installer at https://www.immunet.com. We strongly recommend existing Immunet user to upgrade to v6.2.4 and start taking advantage of new improvements. If you are running an older version of Immunet, you should be able to upgrade via 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
  14. Earlier
  15. ritchie58

    New release v6.2.4

    Does this build address & fix the recent exclusion issue as well Wookiee, or is that still being worked on? My assumption would be the latter since the fix isn't listed. Also, is a URL link going to be provided for the new build installer when it becomes available or is this build going to be automatically pushed to users through the UI?
  16. Hi all, It has come to our attention that some users may be experiencing a User Interface issue. Some users may see that they are missing the Exclusion list and the portion of the UI where you can add your own Exclusions in Settings. The developers are aware of this issue and are working on a (hopefully) quick fix. We do apologize for any inconvenience this may cause. Regards, Ritchie...
  17. ritchie58

    Logs?

    For my OS the log files are located in the Program Files directory, not the Program Files (x86) directory. For my Win 7 machine the file path is (C:) Win 7 x64\Program Files\Immunet. The log files are in a .db file format so you'd need a program that can read this type of file. However we do recommend you use the UI to view history files instead of using a third-party vendor's product to try and open and view these files which could possibly corrupt the files. BTW - you will have to completely kill Immunet too to view the history files directory's since they're inaccessible while Immunet is running. In regards to the file path for log files there is no way to change that as far as I know. Cheers, Ritchie...
  18. RichieKnight

    Considering Switching From ESET

    OK, thanks for the info Ritchie.
  19. MrEurx

    Logs?

    Where are logs located? I looked program data and program files (x86) I didn't see anything unless it's hidden in another folder? Can I change the location the log files direct to?
  20. ritchie58

    Considering Switching From ESET

    Hi Rich, I'm sorry to say that Windows Server 2019 is not a supported platform at this time however Win 10 is supported. Immunet does have an "enterprise version" that I believe will work with Windows Server 2019 called AMP for Endpoints (AMP is an acronym for Advanced Malware Protection). It's not free but the price is reasonable and actually negotiable depending on the length of your license that you choose and the number of endpoints to be protected. Plus you get much better malware/intrusion protection compared to Immunet in a server environment. So take a look to see it AMP for Endpoints better meets your needs. https://www.cisco.com/c/en/us/products/security/amp-for-endpoints/index.html Cheers, Ritchie...
  21. Hi. I am on the lookout for a new AV solution to use in my home lab. I have been a customer of ESET for quite some time and have been using the ESET Remote Administration appliance in VMWare to manage everything onsite. Given the increasing costs and the fact I am looking to save some hard earned pounds, is Immunet a good alternative? I will be looking to protect the following types of systems... Windows Server 2019 Core Windows Server 2019 with GUI Windows 10 I see that your AV is Cloud based. Do you offer anything that enables you to run a network management platform much like ERA does for ESET? Regards,
  22. Please notify us when they will find a solution :)
  23. Thank you! I'll write back if this change in settings doesn't achieve the desired result.
  24. it sounds like you might have turned on Verbose Tray Notifications. Open the immunet interface and check Settings -> Notification Settings -> Verbose Tray Notifications. When turned on Immunet will popup the message you're seeing whenever it detects a new file on the system, regardless of if the file is clean or malicious.
  25. For the last ~2 weeks, Immunet v. 6.2.0.10768 has been displaying "Notices" of new files being installed on my Win10 PC x64. Not sure if they are updates to Immunet itself, other programs, or not related to software updates at all. The notices (see screenshot below) typically say "Notice! Trusted file xxxxxx.xxx has been installed on this machine." Immunet is tallying several, sometimes dozens, of these notices per day. Does anyone know what these notices are? And how can I shut off the notices if they are not indicating something harmful? I searched and didn't come across other forum postings like this, so am posting this new one myself.
  26. Hello guys, if Immunet is to be used as a stand-alone antivirus solution I would "definitely recommend" that the ClamAV module is utilized for the extra protection it provides. Cheers, Ritchie...
  27. Really depends on what is on the boxes etc. The design does have an 'old' feeling to it, and we (development team) have talked many times of redesigning it in the future. I would say, do a fullscan first and if you want to exclude file paths or certain files...add the exclusions in the settings option.
  1. Load more activity
×