mallard65

The use of TOMCAT in Eset products clearly states that that Juli is used and not log4j. It is irrelevant that TOMCAT can be configured to use log4j in this scenario. 

The answer is no per Emsisoft's recommendation: https://help.emsisoft.com/en/1728/are-emsisoft-products-fully-compatible-with-other-security-products/

In case anyone researches this issue later, my problem seemed to have resolved itself.  I don't know what changed.  I stopped using split-tunneling and was prepared to collect the info as directed by macros, but no errors or firewall problems returned.  No idea what changed.  If the problem resumes I'll submit the diagnostics as directed. 

As far as I am concerned, Eset should have developed a signature detection for this software long ago.
Despite WV-X popularity in the security forums such as wilderssecurity.com and malwaretips.com, there are multiple issues with this product many are not aware of. For starters, its kernel mode drivers are not WHQL certified. The software is written in Python. Then there is the issue with the internal certificate modifications this software performs. There are multiple detections on anyrun.com about this activity such as this one: https://app.any.run/tasks/e5f4c11b-c2c0-4651-9bd8-dbf26182dce1/ . Ditto for malicious detection's on other web cloud sandbox analysis sites.

Hello @mallard65
I may confirm that we received multiple reports of an issues with activations (ACT.0).
The issue has been resolved by the teams responsible so if you haven't activated you ESET product yet, please try to do so now.
We apologize for the inconvenience caused.

I am pleased to confirm that I am now able to install and activate the software as expected.
Thank you for your assistance.

You're comparing apples to oranges here:
 
ESET Endpoint products (inclusive of 'Server-branded' AV engines - unaffected, they don't use apache- the installs do not place any form of Apache on these systems
 
--------
Your endpoints aren't at risk directly, if you're solely utilizing HTTP Proxy to distribute content to those systems or connectivity to ESET's public servers, then there is a potential issue (though again ESET saying they don't utilize those components)
 
ESET PROTECT (management console) - there are two web-engines on this system:
The TOMCAT engine, which runs the front-end ESET PROTECT UI Webpage, again not applicable
The only component that is potentially impacted is the APACHE HTTP PROXY component, ESET did release 9.0.10.2 of the Protect console -- but those not wanting to download a gig to update a 12MB install, the literal only change is that under the HTTP Proxy component download, that is showing 2.4.51.0 for downloads
 
So there is either potential on the Log4J or just simply keeping up with the latest release of Apache (which being a security company, makes sense)...
 
In the time it took to explain this, updating the 12mb installer and hopping your config file changes, you'd be done 
 
And the statement is correct about it's not up to ESET to patch endpoints is true -- you deploy your own version updates to your endpoints (though if you're already running 9 on console and endpoints, automation for workstation-version ESET is already in place)

I can understand some people using cracked software at home personally. As an individual, prices for some things can be pretty steep and them thinking what's the worst that will happen they will is lose a few pictures or documents. 
But to see actual IT departments that are responsible for maintaining the health of computers on site is unbelievable. It makes you wonder what other security practices are being ignored. Big data leaks just waiting to happen that would far outweigh the cost of a windows license.  

I was able to find only an expired trial license registered with your forum email address. Please provide your public license ID in the form of XXX-XXX-XXX.

Only available for PUA detections:
 

You can restore anything that has been quarantined. Your restore options vary based on the threat detected. The below screen shot shows an Eset suspicious detection which allows for restore to original directory.

Why would you want to do that? An admin maybe, but personally, I wouldn't want an end-user undoing it. To me, that's a huge security breach.

Unfortunately it seems you fell a victim to scam. To prevent this, we recommend purchasing a license from authorized partners.

I always noticed why when there is a problem with ESET, everyone says it goes to the KASPERSKY product?
I was curious to know why always KASPERSKY?

You can try to create a split-tunnel and then exclude ekrn.exe from Mullvad VPN and include it in the split-tunnel. How to do this is here: https://mullvad.net/en/help/split-tunneling-with-the-mullvad-app/
Appears that Eset LiveGrid doesn't like perhaps the DNS servers Mullvad is using.

Are all the items sold by the company or by users? I ask this as often people have bought licenses from Amazon to find the user had oversold it e.g. it was a license for one user but sold to multiple users. This is why it's always recommended to buy directly 
Best thing as I mentioned previously is to contact that site

The problem is the site appears not to be an official Eset site and so you'd have to contact the site. Is the site well known?

Checking Eset's Worldwide Authorized Partners web site, there is only one authorized web site for Russia. That is the Eset Russian eStore web site which link was posted in a previous reply.
Purchasing an Eset license from any other Russian web site is at your own peril as to license validity. If Eset for any reason decides to cancel licenses issued by these web sites whether via download, card key, or boxed version, your only recourse is through the site where originally purchased.

If you translate that marketing speech into normal everyday talk. You will see it is all puff for easy marketing that doesn't cost them anything. Basically they know that the vast majority of people won't keep the same mobile device for 5 years. So it will be a lifetime license for the device not the user. Even if someone does still have the same mobile device after 5 years the battery will very likely be in very bad shape and not be holding a charge for very long. 
So I would be cautious in the future of services offering lifetime licenses.  

Hello,
https://www.virustotal.com/gui/file/faa55ba4b50f6eebbbaddf029f97e0324fd9dc1d606fed18935d999460dfd361?nocache=1
https://www.virustotal.com/gui/file/57b485a86929cca59150579b362ac8812a67a3e464a7663a5d3d39d4cdf1e0e9?nocache=1
https://www.virustotal.com/gui/file/c960dd553a71f676a30c93a5f6f3aa6a6363cff6547aa1bd07e2d53c1fd240cb?nocache=1
 
Those are PUP for some application that is called ChronoSpeedUp or PCAcceleratePro , even if you uninstall it , it will come back from AutoRun after restart, need to be disabled from AutoRun also
Not detected by ESET , had to clean it manually.
And unfortunately I don't have the files anymore as I've deleted them , PC was scanned with Online Scanner as ESET isn't running on it.
I know I have to send to samples email , but I don't have the sample anymore.
 
Fortinet helped catch it because it blocked all it's traffic from Web Filter as Malicious Websites
 

 
Those are them

I for one am feed up with this constant Eset log upload issue due to their excessive size!
If Eset requires users to create diagnostic logs for them to be able to perform problem resolution, then it is Eset's obligation to provide a "nob" user method to do so from the existing Eset GUI interface. It should not involve user input as to what log options should be selected and the like.
Most important is the upload of these logs be performed automatically after logs have been created to appropriate Eset receiving servers. It is not the user responsibility to figure out how these logs should be uploaded to Eset.

Just click the desired option. However, this question is out of scope of this forum since it's not ESET related.

Unfortunately you have posted anonymously as a guest so we can't advise what ESET partner you should contact. If you are from the US, please find contact information at https://www.eset.com/us/about/contact/.

More secure just to disable all macros by default, I find it the most better solution.

It is not necessary to uninstall ESET prior to upgrading the operating system.
In order to investigate the issue, please sign up for this forum and re-post in the appropriate product subforum. Also we recommend raising a support ticket so that the case is properly tracked and that you get a response in a timely manner.