Jump to content

Wookiee

Administrators
  • Content Count

    267
  • Joined

  • Last visited

  • Days Won

    22

Everything posted by Wookiee

  1. 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.
  2. 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.
  3. 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
  4. 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
  5. 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.
  6. 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.
  7. Did you install via safemode with networking? (fresh install of 6.0.2 )?
  8. 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
  9. 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.
  10. 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?
  11. Welcome! Let me know if you have anymore issues.
  12. I believe it should auto update if the computer is on, if not- then you will need to manually launch it.
  13. Is there a reason you stay on XP? WIndows XP is end of life, and honestly, it's not the best to stay on an operating system that isn't going to be updated anymore. You should consider an upgrade. https://www.microsoft.com/en-us/windowsforbusiness/end-of-xp-support
  14. Your cloud stats should be fixed for 6.0.8 and 6.2 users. You should no longer see '0 people protected' or any variation of that. If you have questions, let me know.
  15. Sorry, it's just a API call that isn't working that pulls the stats. It's just a sentence, that isn't pulling that stats correctly. It doesn't affect anything
  16. The print statement is simply a print statement. It does NOT affect the protection.
  17. I would use ClamAV probably. though, it still might choke the processor on large scans
  18. Hey Larry! Not maintaining an antivirus software seems silly. I don't know why they didn't maintain it. We, at Immunet and ClamAV update it often. As far as speeds go, ClamWin is our engine but not maintained by us. ClamAV is maintained by us as well.
  19. It's just a bug, no one is not protected. This doesn't change the way Immunet works, or it's detection
  20. Can you send me the quarantined file ? So, I can run some tests via a private message? I can see if I can get it working. Though, the cloud option being '0' shouldn't matter because signatures are what protect / find files to which are quarantined. The virus definitions are updated a few times a day (similar to ClamAVs). I would say if , you updated on both systems for the signatures. It would both technically contain the latest
  21. The cloud stats message, shouldn't have anything to do with you having the latest signatures. It should not leave you unprotected. You will need to make sure you are running the same signature set on both versions.
  22. If you can obtain the files, I can do a comparison, but these would all be signature based. Signatures are what 'find' the malware / ransomware etc. The signatures aren't going to change version by version from 6.0.8 to 6.2, unless the malware itself is changed (or there was an issue with the signature in the first place, to which we push updated signatures out). I am not disbelieving you, But without knowing the exact file, the exact signature- this is a lot of 'he said', 'she said'. There was a few issues with some signatures about a week ago, in regards to detecting certain files, as malicious when they weren't, which were corrected. I would need the malware file(s), to conduct any test to see the following: 1) IF something has changed between versions (signature versions or software versions) 2) what signature(s) are being detected Though, nothing should of changed (other than the signatures possibly and I don't know that without the sample malware file(s)).
  23. That could simply be a signature issue, what file(s) of malware are you running against? Have you submitted FPs? Is ClamAV enabled or disabled? Are you mirroring the settings of 6.2 and 6.0.8?
  24. The message is just not updating. You aren't unprotected.
×
×
  • Create New...