Jump to content

Jose

Members
  • Content Count

    101
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by Jose

  1. Jose

    Slow

    Hi Barbee, Immunet should work for you in a Windows 8.1 64 bit machine. Before we start trying to fix Immunet, can you please confirm that Immunet is the guilty party? To do so, we would have to temporarily disable Immunet: -Open a Command Prompt with Admin rights (some instructions on how to potentially do this, here) -Type in net stop immunetprotect (You should receive back a message stating that the service was stopped).] Keep the prompt open. -Attempt to reproduce the original issue. If the issue still happens, it looks more like a non-Immunet issue, and there's not much I can do for you in that case. - Start Immunet once more by typing in net start immunetprotect in the prompt. -Double check whether the problem exists or not. In case that Immunet seems to be the guilty party (the problem disappears with Immunet Off, and reappears when it is on) then please contact me at support@immunet.com (use: 'For Jose' at the end of the Subject line for the email) and we'll take it from there. -Jose
  2. Hi ronroseman, Can you describe exactly your situation so that I may reproduce it in-house? Just keep in mind that the current ClamAV version in Immunet is not the latest (there are plans to update the ClamAV engine in the mid term), so that might be part of the issue. Let me know. -Jose
  3. Jose

    Email Notifications

    Hi npoenn, I will bring this up on a meeting, but -speaking from my personal point of view- not entirely sure if this is a feature we want to add, since it would create quite a bit of overhead, and it could potentially be used for spamming third parties. (Or even worse, accidentally sending virus/security information of your computer to others). I will bring it up though, and see what the Devs think. Thank you for your suggestion. -Jose
  4. Hi loskamita, I will note your suggestion and pass it on (I believe similar have already been made: in that case I'll just re-bump it). As a side note, Immunet restore should not fail (the only 'expected' failure in traditional behaviour would be trying to restore a file that the user previously deleted in the history window). If you are having trouble restoring files, let me know. Thanks, -Jose
  5. Hi all, Just to say it once more, if you are still having issues please contact support@immunet.com. Additionally, the 'new' features were not features at all, but bugs with the User Interface. And, to answer loskamita's question about putting BitDefender in Immunet Free, the answer is that it is still on the table and we haven't made a decision one way or another in that respect. We will improve Immunet Free in the future, but this may or may not include current Plus Features (in addition to some entirely new aspects). Thank you, -Jose
  6. Jose

    Help

    Hi Maikuolan, This is not exactly the right place to post: Immunet is powered by ClamAV (as one of its several engines) but we usually don't discuss ClamAV by itself (at least not in the probable depth that you might be looking for). You probably would be aided much better by the mailing lists for ClamAV (not exactly a forum, but you can get feedback there). You can see the ClamAV mailing lists here: http://lists.clamav.net/mailman/listinfo/clamav-users Cheers, -Jose
  7. Hello, At this time we would like to announce a new version of Immunet 3 (version 3.1.13) which should resolve any issues that may have been caused by the upgrade to version 3.1.12 which was released on June 27, 2014, including interacting with the Settings page and losing access to Immunet Plus features. If you have previously performed a clean uninstall and reinstall of Immunet 3.1.12, after an upgrade to 3.1.13, you are now able to re-activate your Plus account via the Settings page. We apologize for any inconvenience that these issues may have caused you. If you are still experiencing issues with this release, please feel free to contact support@immunet.com. Thank you, Immunet Support
  8. Hey, We are aware of this issue and are working on it. I'll update the thread shortly with instructions. Thank you for your patience. -Jose
  9. Hey thecomputerdude, Thanks for taking the time to let us know. Sorry about the delay in getting back to you. I'll talk to the folks over here to get that particular file branded as malicious. It might be useful if you could send us the file to support@immunet.com (please make sure it is ZIPPED with a PASSWORD), so that we can confirm its maliciousness faster ( we can't just brand it malicious because 1 customer and a few competitors say so, we still need to look at the file. No disrespect intended). And to answers your topic title question, yes Immunet continues to add detections for malicious software every day. Thank you, -Jose PS: And also thanks Ritchie.
  10. Hi Vishnu, Hmm... That is probably that the User Interface has not been updated (which might take a little bit of time). If you force the User Interface to restart, it should correctly state whether or not Immunet is connected to the cloud. A way of doing this is to close the Immunet window, AND right click on the Immunet Icon on the lower right pane (hide Immunet). This will still keep the engine running (aka, you are still protected). At this point, attempt to open Immunet again (through the Desktop shortcut, or the start menu). After one attempt, it should recreate the Icon on the lower right. After another click, it should reopen the window. It should now say 'Immunet is connected to...' if it has a working connection. Cheers, -Jose
  11. Hi Vishnu, Just to clarify a couple of things: Plus version still exists and is supported: it is no longer sold however. And the Community panel is from Immunet 3.0 (note the '0'). We are already in versions 3.1+, and that part was removed during the transition. Cheers, -Jose
  12. Hi Vishnu, They GUI will be greyed out only if the following conditions are met: -The Service is not Running (most likely a bug if you did not do it yourself) -The service is not properly connected to the GUI (rare bug) OR -It is not connected to the cloud AND you don't have ClamAV or TETRA enabled (or you do have them but without definitions). Whenever you get the message 'Immunet is connected to... ', then at that point you are connected to the Cloud, whether or not the Threat number is properly shown. -Jose
  13. Hi Vishnu, Thanks for the report, just wanted to let you know this is a known issue, but it is only cosmetic: the agent should still be working appropriately. Let me know if you got any questions. Thanks, -Jose
  14. I'll bring this up (forgot to answer to this topic) for sure to see what they think. Cheers, -Jose
  15. Jose

    Context Menu Tray Icon

    Hey, I would personally keep ETHOS and SPERO active. These two engines are fairly light weight on their own, so their performance impact is quite small, and the added safety does not hurt. TETRA and Clam are the two heavier ones, so one of the two activate at one time is usually best (most people, like in your settings, use TETRA). -Jose
  16. Hi Harvey42s, This could be an issue with Immunet not properly reading or displaying the information. Could you contact us at support@immunet.com with the subject ' Forum - For Jose - Quarantine Is Allways Empty - I Can't Recover Any Files' and attach a Support Diagnostics File? (Instructions below) Cheers, -Jose SDT Instructions: 1) Click Start -> All Programs -> Immunet 3.0 -> Support Diagnostics Tool. 2) A new file will be created on your desktop with a name like Immunet_Support_Tool_[date and timestamp].7z. 3) Please email this file to me.
  17. Hi Harveys42, Echoing Sveni's suggestion, can you please post a screenshot of what you are seeing? -Jose
  18. Jose

    Context Menu Tray Icon

    Hi Sveni, I'll suggest it, but just to elaborate a bit on Block Mode, Immunet has two 'block-type' modes: active and passive. Active (also known as 'Block Mode: ON') is when the files will not be allowed to execute until they have passed inspection: this is by default turned off, since it has a moderate impact on performance (for most uses this is not a problem, but for activities like Gaming, Streaming, others, this is quite cumbersome). Passive (default, Block Mode: OFF) is when the files might (depending on certain other constraints) be allowed to execute before they have passed inspection. In both cases, the queries to the engines are made for the detection, but in Active, Immunet will wait till the query returns the disposition before allowing the file to continue. Cheers, -Jose
  19. Hi Sveni, So I just tried using the program you linked to (Free Commander) and it does not seem to work in my initial test: I will put it up as a bug for the developers to look at. Just keep in mind that the priority for this bug will probably be low. Thanks for the report. -Jose
  20. Hi stabbtt, It is used for on-demand scanning as well as Real-time protection. Clam is one of the engines that we use: we also have SPERO and ETHOS as well as TETRA (if Plus user), in addition to our cloud 'database' (so to speak). All of the engines are used in both Scanning and Real-time protection (assuming they are enabled), but not all the time: if one of the engines marks a file as 'definitely clean' or 'definitely malicious', it might not be necessary to attempt all the engines - which would be resource intensive. (depending on the file and engine, more than one engine might need to confirm this before an action is taken). Cheers, -Jose
  21. Hi sheilaslims, So, stealth items are hidden items within your computer that could potentially be malicious. Our engine will automatically try to remove them but there are two caveats: 1- There will not be a display showing how many of the stealth items were removed 2- Some of the removals require a system reboot. Assuming a second scan was made after a reboot, and there are still stealth items, they might have been created by some programs in your computer (which are not necessarily malicious). Some details on the items that you are seeing would be useful (the screenshot Ritchie and Sveni suggested would work). -Jose
  22. Hi Tinapleez, Please don't jump too hastily into conclusions, particularly when based off the sfc.exe.log : As I have explained in another post (here) the log by default will only log errors, but in most of these cases a simple retry by the program works fine (however, the retried attempt is not written in the log). I have seen your email to our support group, and will be answering it shortly. -Jose
  23. Hi, I understand now. Then use the net stop/start instructions in that case. Exclusions is usually when you are planning on having more than one protection software running at the same time: you add exclusions to avoid them fighting/getting in each others way. Cheers, -Jose
  24. Hi flywelder, I am not entirely sure why you would wish to disable Immunet3 protection, you could potentially add exclusions if you wished to not scan a particular folder (the Combofix one maybe?) Otherwise, you can stop Immunet by going into the Command Line (Click on Start, then Run.... and type in 'cmd'. Press Enter). And typing net stop immunetprotect When you are done, type in net start immunetprotect Cheers, -Jose
  25. Hey, I have gathered your request, and sent it to the proper guys in Development, who will decided proper course of action. Thanks for the feedback. -Jose
×
×
  • Create New...