Marcos

First of all, Endpoint 6.5 is too old for installation on Windows 10. Uninstall it, try to upgrade Windows 10 to rule out that ESET is causing the issue and then install the latest version 7.3 from scratch.

Since you have already uninstalled ESET, the issue cannot be caused by it. Since the issue most likely persists even without any antivirus installed and is not caused by malware, I'd recommend to ask for help in a forum dealing with Windows issues. What you could try is resetting TCP/IP by running "netsh int ip reset" as administrator.

Since there may be various reasons for failed activation, I'd recommend to gather logs as per the instructions above and provide them to your local ESET support for perusal.

Ok, since I'm from Europe I could not get to the US activation form and was redirected to the international activation form https://www.eset.com/int/support/activate/. Microcenter is a US retail seller as far as I know so I concur that you should contact their support or ESET LLC should you be unable to resolve the issue with MC. I've asked a colleague from the US to check if there's an issue with the form and not all states are listed.

Normally a computer restart is recommended after upgrade to a newer version but not immediately required. You can configure Endpoint via ESMC to not change protection status on clients when a reboot is recommended or required and at the same time have the status reported in the ESMC console: Upgrade to v7.3 is an exception due to big changes under the hood and without a reboot real-time protection will not work after upgrade. When we start releasing so-call uPCU program updates (v7 is ready for uPCU), the update will be applied after a computer restart. Again, users may not get any notification and only administrators will see in the ESMC console that a reboot is recommended. They can then send a message to users to reboot the machines for instance.

It appears they were issued by ESET Russia but the French email address is suspicious. Please contact ESET Russia. Why there are so many licenses registered to your email address?

Yes, you can install ESET's products on a dual boot system since only one will be used at a time.

If you see "Verified by ESET, sprol, s.r.o." when clicking the lock icon then SSL filtering is enabled.

Do you have SSL filtering enabled? It's disabled by default in business products. If you have it enabled then there's an option to exclude communication with trusted domains from filtering which is enabled by default. Trusted domains also include bank domains that use an EV certificate. In business environment we do not recommend using consumer products. They don't support remote management and typically receive module updates earlier than business products.

Please provide your public license ID. Are you trying to activate Endpoint for Windows or another product?

It does: https://help.eset.com/efsw/6.5/en-US/ Supported Operating Systems: •Microsoft Windows Server 2019 •Microsoft Windows Server 2016 •Microsoft Windows Server 2012 R2 •Microsoft Windows Server 2012 •Microsoft Windows Server 2008 R2 •Microsoft Windows Server 2008 (x86 and x64) •Microsoft Windows Server 2003 R2 SP2 (x86 and x64) •Microsoft Windows Server 2003 SP2 (x86 and x64) •Server Core (Microsoft Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016) Since it's an old product which is no longer available for download, it can be provided upon request by your local ESET support. Note that installing antivirus on a operating system unsupported by its maker will not make it secure enough; Windows Server 2003 contains vulnerabilities that do not exist in fully supported systems, hence the user should consider upgrade if security of their data matters.

My understanding is that Microcenter users are suppose to fill in the activation form at https://www.eset.com/int/support/activate/. You select USA as the country but there is no option to select the state which is ok and not needed.

Any ESET security product v7+ for Windows scans UEFI. As far as Mac OS is concerned, I recall that we don't support UEFI scan there.

Ok, the difference is that I ran a scan task and did not schedule a scan task. I was able to reproduce the issue now and reported it to developers with high priority. P_EESW-5653

Since this forum is not a channel for disputing detections or url blocks, please follow the instructions at https://support.eset.com/en/kb141-submit-a-virus-website-or-potential-false-positive-sample-to-the-eset-lab to report the url block to ESET. Having said that, we'll draw this topic to a close.