Jump to content

Marcos

Administrators
  • Content Count

    20,046
  • Joined

  • Last visited

  • Days Won

    866

Everything posted by Marcos

  1. I see that you have 2 licenses for ESET NOD32 Antivirus; one for 4 seats and the other one for 1 seat. Since you haven't changed the product with purchasing the renewal, you don't have to do anything but make sure that ESET is activated with the license key BCHP-XXXX-XXXX-XXXX-4MDU on not more than 4 machines and with BCHP-XXXX-XXXX-XXXX-4MDU on 1 machine at maximum. You can use the license manager at my.eset.com to manage your licenses. When either license is due for renewal, I'd contact the seller (ESET LLC) and ask to merge the two licenses into one for your convenience.
  2. ESET LLC doesn't provide a phone support for home users but they offer a live chat. Anyways, the issue you have described will require a support ticket to be created for further investigation and troubleshooting; it doesn't sound like anything that could solved over chat or phone call. Regarding a comparison with MBAM, ESET detects all types of threats; from phishing through scam, adware, potentially unwanted and unsafe applications, suspicious applications to malware (worms, viruses, trojans which include also ransomware, backdoors, etc.). We just don't detect benign files, e.g. binary data files that might come with malware but can't be run and do not contain any recognizable data.
  3. It's weird since ESET NOD32 Antivirus cannot affect ICMP in any way so ping must always work. Only EIS and ESSP which have a firewall might affect ping.
  4. The number of files that could not be open and scanned is 350 which is quite normal, especially if you didn't run the scan as an administrator. There is no reason to roll back to an older version of Windows 10 unless you started to experience serious issues after the upgrade.
  5. 1, Upgrade Endpoint to 7.3.2036 using a software install task. 2, To report other non-ESET applications, create an agent policy with the above setting enabled and assign it to machines in your LAN. When upgrading machines, we recommend to do it gradually. Start with one machine, especially if you employ an http proxy so that it caches the installer and all other machines will then get it from the proxy cache.
  6. You can apply an agent policy that will make the agent report also non-ESET applications that are installed:
  7. I'd recommend submitting the sample to samples[at].com in an archive protected with the password "infected". You can also upload it to VirusTotal and post a link with results here. By simple language hopefully you don't mean anything like a batch file with "format c :" or "del c:\windows".
  8. VirusTotal doesn't leverage LiveGrid, hence the files won't be detected there. At this point we can only check your dlls to see if the SHA1 hashes match those you listed earlier. We won't be able to reproduce the detection any more since the files were already removed from the LG blacklist.
  9. If you scanned the dlls before (on July 17 according to your logs) and the dlls hadn't been updated / changed and ESET had not been re-installed (ie. the local cache wasn't cleared), it doesn't make sense why they would not have been detected 3 hours ago.
  10. It depends on when you scanned them. The hashes were removed from the LiveGrid blacklist about an hour ago, ie. 22:00 CEST.
  11. The files were blocked by LiveGrid, we've already unblocked them. However, you wrote "ESET Context scan does not detect any of these files as suspicious or malicious" which would have happened only if the files had been updated, otherwise the statement wouldn't make much sense.
  12. We use our own firewall that leverages Windows Filtering Platform to filter the network communication on Windows 8+.
  13. It could be that the dlls have been updated in the mean time. Could you please provide current dlls?
  14. A full WMI & reg. scan may take 10-20 minutes, hence it's important to not select them as targets if you want to run a quick scan only. Quick and in-depth scans are subject to further internal discussions and I see there room for improvements.
  15. Since I was unable to reproduce the detection / block, please provide logs collected with ESET Log Collector after selecting also "Quarantined files" in the ELC menu to samples[at]eset.com. You can enclose a link to this topic as well.
  16. If you have Windows 8 or Windows 10, does temporarily disabling Protected service in the HIPS setup and rebooting the machine make a difference? If not, please carry on as follows: - in the adv. setup -> tools -> diagnostics enable all advanced logging options - run update to reproduce the issue - disable logging - collect logs with ESET Log Collector and supply us with the generated archive.
  17. If you don't know all networks from which the machines will update, create 2 update profiles; one with settings for update within your company's network and the other one for update when outside the company's network. Then edit the Regular update task and select a primary and secondary update profile.
  18. How many disk drives do you have installed in the pc? Are they older hard disks or relatively new SSD disks? Try checking the disks for errors using chkdsk. If no errors are detected, I'd recommend opening a ticket with your local ESET support.
  19. You wrote that everything was working, however, the second part contradicts that. Please be more specific as to what you mean that "it can take a few attempts at creating a rule before it actually takes". Do you use interactive fw mode? If so, when you are prompted for an action and you choose to create a rule and then check the firewall rule list, is it empty?
  20. Isn't it stuck at Initializing protection?
  21. If you are new to our forum and are about to post for the first time, please take a few moments to read these basic rules first.
  22. I would recommend opening a ticket with your local ESET support and provide step-by-step instructions how to reproduce the issue. Also enclose logs collected with ESET Log Collector please.
  23. The dump confirmed that real-time protection was starting. The issue will need to be looked at by developers. Therefore I would recommend opening a ticket with your local ESET support so that the case is properly tracked.
×
×
  • Create New...