Jump to content

Wookiee

Members
  • Content Count

    281
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by Wookiee

  1. It's a known issue that Immunet UI doesn't adapt or change sizes with bigger resolutions (we hope to fix it in the future)
  2. Let me look into this, and see if I can replicate it. what OS are you using? Was this an upgraded from another version of Immunet or a fresh install of 6.2?
  3. You will want to contact AMP support for this. This forum is more for Immunet (free version)
  4. Immunet packages with ClamAV, So. If a new version of ClamAV comes out, you can't update it without Immunet releasing a new version. Now, if you are JUST using ClamAV. Just download the new copy, (if installed from source), or wait for a package maintainer to release it
  5. Can someone enable 'debugging' and send me a support log after a scan so I can look into the .db history files.
  6. Yeah, The devs are looking into finding a better solution for this.
  7. The process blocked *should* only block the process when it's trying to access protected services on the computer. It shouldn't hinder your use of using the process at all. The annoying pop-ups will hopefully be addressed 'soon', the pop-ups are a feature that was added, but it's always had the 'process blocked' but it was in the background. Now, it tells you everytime it does it. (Currently, there is no way to turn it off), I am working with the dev team to fix that
  8. What CPU usage and CPU do you have? Did you get it installed? or is the installer using a lot of CPU ?
  9. IF anyone experiencing high CPU usages in 6.0.8, let me know how 6.2 works for you.
  10. There was one signature issue, which was corrected. Report FPs via the immunet website. But 6.2 still fully protects as does 6.0.8
  11. Can you send me the installer log. Send the %temp%\immpro_install.log via a message to me
  12. It blocks the process from accessing protected services, but if you were to launch the process, then no.
  13. submitting files, via false positives you can do via the immunet website. Unless you mean to submit files to be scanned. Then do a custom scan, and select what you want. As far as the history, which tab is having issues? Default, clean file history? Quarantined file history ? Scan history, file events? block process history? The file extensions excluded you can remove them if you wish, especially if you use other anti-viruses WITH immunet.
  14. That has always happened (since 6.0.8, it is just saying that the process is trying to access a protected process). Now, the notifications are shown in 6.2 as they weren't before, you can ignore it.
  15. if you are referring to the 'blocking' notification, Immunet has been doing that since the previous version, it just never notified the user before (that was added in the latest version). Which, at this time there is no way to turn off that notification, but I can put a request in to the dev team to do that. https://en.wikipedia.org/wiki/Local_Security_Authority_Subsystem_Service in regards to the lsass.exe is above. (make sure that it is the correct lsass.exe) coming from the correct paths. to make sure a file is clean, just scan it. To see if it is signed: https://docs.microsoft.com/en-us/windows/desktop/seccrypto/using-signtool-to-verify-a-file-signature
  16. we notify and block the process which try to access protected processes ( Winlogon.exe ,lsass.exe, etc.). Once the SPP rule is triggered, the notification is reported on couple of conditions and one them is when “process is not clean and not signed. “ You can try to add the exception to that file path in the settings, and turn off 'blocking mode" to see if that fixes anything for the better. Though realistically, it shouldn't prevent you from accessing the exe file at all, just that for whatever reason that program is trying to access something else
  17. when you go to : http://www.immunet.com/ and hit "download' it downloads 6.2.0 IF it is NOT downloading that version for you, you might want to clear your browser cache and cookies.
  18. on the immunet main page, when you click download- it should only download the 'latest' version. If you had 6.0.8 before, uninstall it and then use the new install for 6.0.2. IF you didn't have a previous version of Immunet installed, and this is a fresh install. Make sure you have an active internet connection, and are installing with admin rights when you attempt to install.
  19. Did you install via safemode with networking? (fresh install of 6.0.2 )?
  20. Try 6.0.2 it has a fix in it, that was having issues with copy fail messages- this was due to a 'weird' bios name. If you have 6.0.8, it MIGHT not upgrade correctly. You may have to uninstall it and install 6.0.2 fresh
  21. Hello, It's a known issue right now with higher resolutions. It is on the developers radar to fix, though there is currently no ETA on it.
  22. I had no issues when using Win 10 pro, what error message do you receive? Are you running as an administrator? Have you tried to update it via safemode with networking?
  23. Welcome! Let me know if you have anymore issues.
×
×
  • Create New...