Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About aroe

  • Rank

Profile Information

  • Gender
    Not Telling
  1. I have worked with Sammy on this issue, The root cause for this behaviour is a bug that affects Immunet release on Windows XP and Server 2003 only. The bug interferes with Netbios name resolution. We have found the root cause of the bug and are in the process of testing the fix, the fix will be in the next release of Immunet Protect. Best regards, Anthony
  2. Hi all, doudz would you mind sending a support snapshot to support@immunet.com. Instructions on how to generate a support snapshot can be found here: http://support.immunet.com/tiki-read_article.php?articleId=10 I will confirm but this sounds like a bug that was discovered that affects Immunet on Windows XP and Server 2003 only. We have found the root cause of the bug and are in the process of testing the fix, the fix will be in the next release of Immunet Protect. Best regards, Anthony
  3. Could you please follow these instructions and send the support dump to us for analysis: 1. Go to Start Menu at the bottom left of your screen - and All Programs -> Immunet 3.0 -> Support Diagnostics Tool. 2. This will create a new file on your desktop with a name like Immunet_Support_Tool_[date and timestamp].7z 3. Email the support dump to support@immunet.com. We will investigate this problem for you. Thank you danci1973 for reporting this issue.
  4. Hello Crashman. Would you please send a support snapshot to support@immunet.com with the subject "Atten: Anthony. Large Quarantine Issue.". I will investigate this issue for you. Here are instructions on how to create the support snapshot: http://support.immunet.com/tiki-read_article.php?articleId=10 If you scan files that are in quarantine they will not be detected as malware by any antivirus vendor, this is because they are already encoded by Immunet Protect. This means that the signature of the file has changed. This action renders the file harmless if it is malware. Best regards, Anthony
  5. To ease your fears, the community metrics on the user interface (UI) are generated by a separate process than the process that adds detections and members to the cloud. Due to how the metrics are generated, errors in these fields are cosmetic (although I can see why you were worried). We have identified the problem and are working on a fix for you. Thank you for reporting this Sweidre, and apologies for any concerns caused. We do browse the forum frequently, I will try to reply more frequently so that you know that you are being heard. Best regards, Anthony
  6. Hi everybody, just a quick status update. We are working hard on this issue and hope to get an update out very soon.
  7. Thanks for bringing this issue to our attention, the bug has been logged and we will fix it. You are fully protected even though the Immunet User Interface disagrees. The issue here is that a new set of Clam AV definitions need to be downloaded and installed before the User Interface protection status will update. These definition updates are released regularly (close to daily I believe). So your protection status will change when a new version of Clam AV definitions are released. I hope that this helps to alleviate your concerns, we are following this issue closely. Best regards, Anthony
  8. aroe

    Develop Faqs!

    This is a good idea, I will start trying to develop some FAQ answers too. Perhaps we could also gather some of the good answers that we have in the other forums and format them for the FAQ forum (giving credit to the original author)? What do yo think? Anthony
  9. Thanks a lot Sweidre, this is very useful information.
  10. If you discover a bug (flaw or defect) we are very interested in hearing about it. The Immunet Support team members frequent this forum, we read all of your posts and take each report very seriously. We are very grateful for detailed bug reports. One of the first steps in fixing a bug is reproducing the reported issue in the Immunet software QA lab. While a bug can be frustrating, posting a report of a flaw with no details will delay the repair efforts for the issue, if we cannot reproduce the bug at all then we cannot begin to fix it. For this reason, we would be very grateful if you use the following guidelines when reporting a bug: List the version of Immunet Protect that you were using. If you have upgraded from previous versions list those versions too. List the version of Windows that you are using, including the language version and service pack number. List other antivirus software that you have installed, and the versions for those. Describe the flaw in as much detail as possible, attach screenshots of the issue if you can. After you post the bug report to the forum, run the System Diagnostic Tool (SDT) and email the result to support@immunet.com, make sure to reference your bug report on the forum in the email message. DO NOT ATTACH THE SDT REPORT TO THE FORUM POST! Details on how to run the System Diagnostic Tool can be found here: System Diagnostic Tool Link : System Diagnostic Tool Documentation Here is an example of a short bug report with the above details, note that it is not describing a real issue in real software; it is just an example. A good rule of thumb to keep in mind when reporting a bug is “Include as much information as possible.”
  11. The easiest way to submit files to us is email. You can mail samples to submit@samples.immunet.com. This will feed your samples to an automated system and if we can build protections for it they will available over the cloud within a day of your submission and in some cases as soon as 2 hours.
  12. I agree, it is sad that a few bad apples had to spoil it for all guests. But it doesn't take long to register, and I really hope that our guests that were contributing to the community will spend a few moments to register as members and continue to contribute. I think that it will be nice for all of us if we can keep the spam down.
  13. Good morning everybody. We were very grateful to receive a bug report yesterday from a community member that noticed Immunet Protect 3.0 blocks the installation of DirectX (latest version, possibly other versions too) on Windows 7 64-bit. We were able to reproduce the issue and verify that the issue is fixed in Immunet 3.0.1 beta. The beta is available here: http://forum.immunet.com/index.php?/topic/824-immunet-301-beta-available/ I have attached an image of what the issue looks like when it is triggered. If you need to install DirectX and you do not want to use the Beta version of Immunet 3.0.1 you can temporarily disable "Monitor Program Install" while you install DirectX, and re-enable it after you have installed DirectX. This is a tested workaround. To use the workaround: 1.Go to Immunet Settings in the Immunet UI. 2.Go to General Settings -> Set "Monitor Program Install" to off, click the "Apply" button. (Be careful not to browse to untrusted websites when this setting is set to off.) 3.Install DirectX from the Microsoft Website. 4.IMPORTANT STEP! - Re-enable "Monitor Program Install" by navigating to Immunet Settings in the Immunet UI, General Settings -> Set "Monitor Program Install" to on and click the "Apply" button.
  14. Hi Geek4AllSeasons, Thanks for spending the time to write a detailed post describing the issue that you are observing. Could you send the diagnostic tool output to support@immunet.com?
  • Create New...