Jump to content

Marcos

Administrators
  • Posts

    25,066
  • Joined

  • Last visited

  • Days Won

    1,044

Everything posted by Marcos

  1. We can confirm that nothing is detected in the application mentioned.
  2. Update 8765 was throttled so not all users have received it yet. We're preparing update 8766 already which will be distributed in a standard way.
  3. How's that if there's report of HIPS breaking and not working in win 8.1? I haven't tried it yet but there are quite a few in the forum.... not a complain either, just a question. If one is having issues with Windows 8.1 build 9600 (RTM), maybe they don't have the most current HIPS and Anti-Stealth modules installed yet or haven't restarted the system after the modules were updated. The modules adding compatibility support for Windows 8.1 RTM were released for v7 users just yesterday.
  4. If you could provide us with step-by-step instructions, we'll try to reproduce it in our environment to pinpoint the issue.
  5. Windows 8.1 RTM hasn't gone retail yet and it's already fully supported by v7
  6. It is apparently ransomware displaying a fake warning to scare the user and to get him or her to pay money to remove the screen lock. If ESET was updating properly before you encountered this infection, the following procedure should clean it out completely: - restart the computer - wait at least 5 minutes after the system starts up and the screen locks - restart the computer The ransomware should be cleaned then. I'd also recommend installing the latest v7 beta which turned out to be very stable and provides superior protection against new born malware especially thanks to the advanced memory scanner and exploit blocker.
  7. Please follow these instructions to generate install logs. Once done, create an ESET SysInspector log as well and compress all logs into an archive. You can send me the archive with logs by attaching it to a personal message.
  8. If somebody is having issues with v7 on Windows 8.1 build 9600, try running update manually and restarting the computer. Should the problem persist, post information about installed modules here.
  9. A Process monitor log from a successful replication of the issue might shed more light. Once you have created the log, compress it, upload it to a safe location and pm me the download link.
  10. Couldn't it be that the message reads something along the line that the installation process ended prematurely instead of that it was interrupted?
  11. SMTP alerts are throttled, ie. sent in batches every few minutes.
  12. You can use an ESET Smart Security license to download and update ESET NOD32 Antivirus but not vice-versa. Yes, update files are same, however, not all product versions may necessarily have the same version of modules installed at all times Only components used by a particular product are updated, ie. ESET NOD32 Antivirus will not download firewall module updates. If an update attempt fails, you'll receive a message about this. You can also compare the version of the installed virus signature database with the version listed on ESET's website if you want to make sure you're fully updated.
  13. Of course the official installers signed by ESET do not contain any malware. If you've come across a suspicious installer or application purporting to have been made by ESET, please submit it to us as per the instructions here for further analysis.
  14. I can't see any issue here. What "entry string" disappears in the Computer scan window but it shouldn't?
  15. On my computer it took 7 minutes to scan 202,000 files so your scan time seems to be normal.
  16. You should add * after the last slash so that everything on the mentioned website is blocked.
  17. ESET Endpoint Antivirus doesn't include Web control (equivalent to Parental Control in home version), only ESET Endpoint Security does. Web access protection and Web control are different protection modules.
  18. You can ignore this message, it's merely a notification that an application is transmitting non-standard data via the ICMP protocol. This kind of detection has recently been disabled by default.
  19. No release date has been set yet. The current v7 beta has turned out to be perfectly stable and I'm not aware of any severe issues with it.
  20. Could you please check if Web control is actually enabled on the client and that the policy was applied properly?
  21. No wonder that Windows 8.1 RTM is not yet supported as it leaked and is not officially available to the public yet. The appropriate modules will be updated shortly to support it provided that you have v7 and pre-release updates enabled.
  22. With personal firewall completely disabled, ESET cannot affect network communication in any way as it's not integrated in the system at all. You can also try installing the latest stable beta v7 downloadable from hxxp://www.eset.com/int/beta/v7.
  23. I'd suggest installing the latest version of ESET Endpoint Security 5.0.2214 instead of an old version ESS BE 4.2 which also contains bugs fixed later in Endpoint v5. If installing the latest version of EES doesn't help, try excluding the file c:\Database\tempres.bin or the whole folder c:\Database\*.* from scanning and let us know about the result. If the clients you've mentioned don't have a business / Endpoint license purchased (typically for 5 and less computers), they could try installing the latest stable beta v7 downloadable from hxxp://www.eset.com/int/beta/v7 (at least just for a test) and see if it resolves the issue.
  24. Does disabling firewall via gui or changing integration to "Personal firewall is completely disabled" in the advanced setup make a difference?
×
×
  • Create New...