Jump to content

itman

Most Valued Members
  • Content Count

    6,469
  • Joined

  • Last visited

  • Days Won

    174

Everything posted by itman

  1. How many seats did you purchase for the Eset multi-device license? If was one seat, you can't install that license on Linux since it is already installed on your Android device.
  2. The issue on the Win 10 2004 devices is not about network traffic per se being blocked to the Eset servers. The above posted Wireshark log shows that the servers are being reached. The problem appears to be in the handshaking processing that occurs between the client and servers. That processing is failing and the communication session is being dropped. It appears that ACK request from the Eset servers is not being properly received on the Win 2004 devices. It is starting to look like this issue is due to the Win 10 2004 upgrade which to date has been problematic. One way to verify this would be rollback one of the devices back to ver, 1909. Install Eset on that device and verify that it installs and updates w/o issue. If no problems surface, then again upgrade the device to ver. 2004. My PC is currently being blocked from the Win 10 2004 Feature Upgrade via Win Update due to compatibility issues. And I am in no rush to upgrade to it.
  3. There is a recent forum posting in regards to Eset and PiHole here: https://forum.eset.com/topic/23452-pihole-eset-smart-security/ . It appears Eset works fine with Pihole installed. However in this case, it appears the OP was inadvertently blocking necessary Eset server communication. Believe something along this line is the reason for Eset installer and other subsequent network connection issues.
  4. The question is if EMSC has a predefined Notification for phishing detection? If not, it appears you will have to create a custom one for it.
  5. Temporarily disable PiHole on that device or the device itself. Your ISP DNS server IP address are hard-coded into the router if it is an ISP issued router. Any DNS settings specified within the Win OS are the ones the ISP uses to forward to from its own DNS servers. The bottom line is something within your existing network configuration is interfering with communication to Eset servers. It might be an issue with how the router you use is configured. It also might an issue with the ISP you are using and how it forwards Internet traffic.
  6. Based on what is posted here: https://www.andrewdenty.com/blog/2020/01/25/installing-pi-hole-on-windows-10.html , Pihole performs localhost; e.g. 127.0.0.x, proxy activities. Suspect this might be the problem since the initial Eset network connection alert referred to local proxy as a possible conflict source. Additionally, Eset internally proxies Internet traffic to support its various Web Access protections. Overall, I would say PiHole has to be uninstalled to avoid conflicts with Eset. You can temporarily disable Pihole and see if all Eset issues are resolved.
  7. itman

    ESETMC.exe

    Do not delete the desktop.ini file! That file should have only been visible if you enable displaying of OS files in Win Explorer View settings. Also if this View setting is enabled, make sure you disable it. Deleting the ESETMC.exe shortcut file should prevent ESETMC.exe from running at system start up time. This in turn should eliminate the Eset Trial popup from appearing. When you get around to installing Eset on this device and activating it using your existing Eset license, you should have no further issues. No guaranties however ....................
  8. itman

    ESETMC.exe

    I was also going to suggest this. Look in Program Files folder for a sub-folder related to this. Might be named ESETMC. With luck, there should be an uninstaller for this located there. It is also possible MicroCenter created a C:\ root directory folder for this. Check there also. Finally, check this directory, C:\Users\XXXXX\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup, for any entry related to ESETMC.
  9. itman

    ESETMC.exe

    If MicroCenter preinstalled Eset, I suspect what is installed on the device is an installer created by them. As previously posted, look for a reference to this in Win Control Panel -> Programs -> Uninstall a program section. If a reference to "Eset trail version" exists, then uninstall it. Otherwise, you're best source for a solution to the repeated popups about the Eset trial version at boot time is to contact MicroCenter technical support for assistance on the issue.
  10. Another possibility here is an issue with the ISP DNS servers for some reason. You could try switching temporarily to use of third party DNS server provider; e.g. Cloudflare, Google, etc., and see if this resolves the Eset network connectivity issues.
  11. Tobil has an article about excessive CPU use caused by AV scanners here: https://help.tobii.com/hc/en-us/articles/115004039965-High-CPU-usage . Since the article is 3 years old, it is not a new issue. It appears the present Eset real-time performance exclusion might be be the best current mitigation until Eset can research the issue and find a fix. You might want to open a technical support request to Eset so the issue is documented. I also noticed in the VirusTotal analysis that this is a .Net app and a lot of downloading occurs from it. Suspect the scanning of these downloads is why CPU acitvity spikes.
  12. Do you have Eset Gamer mode enabled in Computer protection section? Another possibility is Eset Webcam protection in the same section. Eset might be somehow treating this eye interaction device as a webcam.
  13. Have you been receiving WD virus signature updates w/o issue?
  14. What anti-virus and/or other security solutions are currently installed on the device?
  15. Same procedure you did for regular Chrome updating. Looks like there are three services associated with it:
  16. If you do not have the latest version of Eset Smart Security installed, refer to this thread: https://forum.eset.com/topic/23180-undocumented-serious-error-0x4002/ If you have the latest version of Eset Smart Security installed, refer to this Eset knowledge base article: https://support.eset.com/en/kb537-undocumented-serious-error-in-eset-windows-home-products
  17. If you reinstalled Win 10, did you also reinstall McAfee LiveSafe afterwards? Or did McAfee come per-installed on the device originally, and you used the PC manufacturer's recovery disks to reinstall Win 10? If so is this how McAfee LiveSafe ended up being reinstalled on the device?
  18. There is also this "tidbit" in regards to the McAfee removal tool: https://service.mcafee.com/webcenter/portal/oracle/webcenter/page/scopedMD/s55728c97_466d_4ddb_952d_05484ea932c6/Page29.jspx?wc.contextURL=%2Fspaces%2Fcp&articleId=TS101331&_afrLoop=1332606635327720&leftWidth=0%&showFooter=false&showHeader=false&rightWidth=0%&centerWidth=100%#!%40%40%3FshowFooter%3Dfalse%26_afrLoop%3D1332606635327720%26articleId%3DTS101331%26leftWidth%3D0%25%26showHeader%3Dfalse%26wc.contextURL%3D%2Fspaces%2Fcp%26rightWidth%3D0%25%26centerWidth%3D100%25%26_adf.ctrl-state%3Dy2zoa9439_9 Appears to me that McAfee should have been uninstalled using Win uninstall apps feature; i.e. Control Panel -> Programs -> Uninstall a program.
  19. Long thread on uninstalling McAfee with their uninstaller tool and it freezing here: https://community.mcafee.com/t5/Consumer-General-Discussions/McAfee-Remover-frozen/td-p/525237/highlight/true . Try what is shown in the following posting first: If this doesn't work, try what is given in the posting following this.
  20. Reviewing this: https://support.eset.com/en/kb6994-configure-smtp-client-threat-notifications-using-eset-security-management-center-7x , what policies are set up?
  21. I am confused by what is posted in this thread. As far as Eset Endpoint sending detection e-mail for web based detection's, I don't know if that feature even exists? -EDIT- Yes it does. Either at Endpoint or ESMC level: https://support.eset.com/en/kb7247-configure-eset-endpoint-products-to-send-automated-detection-notifications-7x
  22. So far, so good. Will post again if it starts acting up again.
  23. Appears the AV scanning of e-mail to their servers is an "add-on" feature: https://www.register365.com/email-hosting/features/anti-virus . If not used, this would explain how all this garbage e-mail is arriving on the local device. Also a factor is what security product is being used. AOL e-mail for example, uses Symantec Endpoint. Of note is free e-mail providers such as AOL, Google, etc. scan all incoming e-mail when it arrives on their servers and prior to forwarding it to the e-mail recepient.
×
×
  • Create New...