Jump to content

Wookiee

Administrators
  • Content Count

    132
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by Wookiee

  1. Wookiee

    6.2.0,fails to install

    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?
  2. Wookiee

    0 people protected

    Welcome! Let me know if you have anymore issues.
  3. Wookiee

    Auto Update

    I believe it should auto update if the computer is on, if not- then you will need to manually launch it.
  4. Wookiee

    Cannot update

    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
  5. 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.
  6. Wookiee

    Immunet 6.2.0.10768 Errors

    I'll look into it ZomBunny, thanks
  7. 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
  8. The print statement is simply a print statement. It does NOT affect the protection.
  9. Wookiee

    Cannot update

    I would use ClamAV probably. though, it still might choke the processor on large scans
  10. Wookiee

    Cannot update

    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.
  11. Wookiee

    0 people protected

    It's just a bug, no one is not protected. This doesn't change the way Immunet works, or it's detection
  12. Wookiee

    Immunet 6.2.0.10768 Errors

    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
  13. Wookiee

    Immunet 6.2.0.10768 Errors

    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.
  14. Wookiee

    Immunet 6.2.0.10768 Errors

    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)).
  15. Wookiee

    Immunet 6.2.0.10768 Errors

    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?
  16. Wookiee

    Immunet 6.2.0.10768 Errors

    The message is just not updating. You aren't unprotected.
  17. This was due to a signature that was corrected. Update your signatures
  18. This is known, and is being worked on by the dev's to correct
  19. The new version should fix this issue, upgrade.
  20. Wookiee

    Immunet 6.2.0.10768 Errors

    Yes, the 0 cloud users is being looked into by the dev's- it is working for some- not everyone
  21. Wookiee

    Immunet 6.2.0.10768 Errors

    The process blocking has been a part of Immunet for sometime, just the notifications for it are new.
  22. Wookiee

    Immunet 6.2.0.10768 Errors

    The reason a fresh install works where as an upgrade doesn't for the 0 cloud users is because NEW installs goes to a newer cloud env, that eventually everyone will be pushed to. Upgrades don't. It's something we plan on fixing.
  23. Not a problem! It's what I expected, a bios name issue. Glad it's working
  24. We don't have anything to decrypt your data if a ransomware attack happens. We look for more malware and things like that. You might want to turn 'blocking' on if it isn't already in the immunet settings though. That could help. There should be ransomware specific softwares that could have key(s). The .krab file is a grancrab, which signatures DO exist for detecting but Immunet and clamav does NOT decrypt it. Below is a NON CISCO tool, use at your own risk. https://www.nomoreransom.org/uploads/GANDCRAB RANSOMWARE DECRYPTION TOOL.pdf
  25. There is a few issues fixed with the new release, you could try 6.2.0 and see if it fixes the crashing. We had an issue with a bios name, that was corrected in 6.2 that would cause these issues
×