Jump to content

Wookiee

Administrators
  • Content Count

    267
  • Joined

  • Last visited

  • Days Won

    22

Everything posted by Wookiee

  1. I edited my previous response hopefully to make more sense and to correct what I previous said. As far as ClamAV, you should report the file in question to clamav.net and select contact, for FP submissions so we can correct that.
  2. if it's a known sha and is reporting malicious, clamav and immunet both should detect it based on the SHA. Immunet doesn't rely on talos intelligence file rep but the same hashes searched for should be convicted on immunet. If that makes sense. It should still flag.
  3. Yeah, like Rob said. We had an issue with a signature but all should be fixed now. Let us know if you have anymore issues.
  4. I am glad you fixed it, I am not sure exactly what might of happened- if you see it again, send me a screenshot
  5. it might be an issue with a signature, I am looking into it.
  6. you can submit the file to immunet.com and click on the false positive section for the file to be reviewed.
  7. i mean, you should be able to delete the 'internet gateway' and 're-create' it with the correct permissions, as well as disabling it. That might be a permissions issue.
  8. The only thing I can think of, off the top of my head is that you might run a "content delivery" service, or platform? Maybe a mirror of a product you like? where people can install updates from etc? HCDN is a 'hybrid content distribution network" Either that or one of your devices (routers) is what is causing the connection. IF you take one router away, and connect directly to the modem what happens?
  9. do you use a product like limewire, or any p2p software for sharing?
  10. Wookiee

    FULL SCAN TAKING TOO LONG

    Hello, is it getting stuck on the same file each time? what kind of file is it? Can you send me a support dump? I'll private message you instructions. Just to cover all bases, does this seem to happen on the same hard drive (if it's the same file, then most likely yes), I am wondering if it could be a bad sector on that Hard drive, You could try running the following overnight (as it will take awhile) 1) open windows explorer, find the drive causing issues (C drive) most likely 2) right click the Drive and select properties 3) Click on the "tool" tab and click "check now (verify "automatically fix errors" and " scan for and attempt recovery of bad sectors" is checked. 4) start.
  11. 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.
  12. 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
  13. Wookiee

    OFFLINE INSTALLER

    It requires an active internet connection
  14. if you have a second anti-virus, just exclude them from eachother so it doesn't cause any issues and you should be fine.
  15. Cisco did take over this project and we are working on improving everything (the software, the forums etc). Glad you like it !
  16. Windows XP isn't even supported by Windows...
  17. 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.
  18. what is the bios name? or what is the character that is in the bios name?
  19. Also, you saved the bios once you removed the character in the name? safe mode with networking would be best to try and install it with, (with full admin rights) IF you did make the name change, are you getting the same error ?
  20. 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.
  21. i will put a feature request in then.
  22. Not at the moment, I can put a feature request in to the developers to see if they can't have a whitelist with anything that starts with "UTW" or whatever you want (wildcard characters) , and such. Is there anyway in the software to have the local/TEMP files be created in another location? If so, point it to a generic folder that you create, and then whitelist that folder so it wouldn't matter the name changes
  23. If you just exclude the exe file or application path on the share, it should work without crashing while being able to access the other files. unless it is creating temp files, that it needs each time the application is launched - where knowing the exact file name could be difficult.
  24. Any version 6.2.0 and greater should have 64 bit support
×
×
  • Create New...