r1man

I could find out that it was the DriverEasy software, that I used after clean installation of Windows to update all the drivers, caused the problem.
Maybe it did download excess drivers and unnecessary ones. 
I did clean install of Windows two times and tested few times, and thus finally could determine it was DriverEasy making the problem.

I could find out that it was the DriverEasy software, that I used after clean installation of Windows to update all the drivers, caused the problem.
Maybe it did download excess drivers and unnecessary ones. 
I did clean install of Windows two times and tested few times, and thus finally could determine it was DriverEasy making the problem.

The issue was resolved on Friday with the release of the Advanced antispam module 7909.1.

@macros While I haven't had time to gather the logs yet, but I am fairly confident the issue is between EIS and the VPN.  I hadn't updated to EIS 15 on my desktop, but when I did, I started getting the same errors.  So far split-tunneling fixed the LiveGrid and firewall issues on 2 computers.  I've read in some other posts this happened to others using ExpressVPN (my VPN) as well as other brand VPNs.
I'll update when I can for your troubleshooting, but I thought I'd post this in case it helps someone else in the meantime.

I will switch to Kaspersky if this is not going to be fixed soon.

I have a similar problem. I just installed expressvpn here in Toronto. After a while I got the "... LiveGrid servers cannot be reached" message. At one point, I turned off expressvpn and, after a while, LiveGrid started working again. At this moment, turning the ESET GUI off and on does not help. I am pretty sure a PC restart will clear the message. In my case I can cope with this by only using the VPN when I really need it.

One thing that I don't like about LiveGuard is that it seems to send every new file created on the device to LiveGuard upon execution. Even if it's an old, trusted and safe file. As you soon as I try to execute a new file that wasn't on my device before, ESET sends that to LiveGuard. Eg: If I just extract a newly downloaded 7zip installer from a zip file where the installer exe is trusted by literally every AV, as soon as I execute it, it gets blocked and submitted to LiveGuard for analysis. What's the point of this? A ESET's reputation check shows that the file is old with reputation status being Fine & green and the number of users is also high with a green mark. 
ESET should feed from this LiveGrid status and determine that the file is trusted, whitelisted and not necessary to submit it to LiveGuard for analysis. This alone would massively reduce the load on LiveGuard's server. This type of unnecessary submission needs to be avoided. Kaspersky and Norton makes use of their cloud reputation appropriately, which is something ESET is not doing here. The LiveGrid reputation should mean something. The LiveGrid and the LiveGuard combo should communicate with each other to determine what needs to be submitted and what not. Otherwise, LiveGuard servers are going to be bombarded with excessive unnecessary submission. 
Unnecessary submission is going to annoy even expert users.

I just checked U.S. prices for Eset. ESSP costs $10 more per year than EIS. As such and for me personally, the increased price is not a major factor.
This important LiveGuard feature being included only for ESSP does "leave a bad taste in my mouth." For starters, Eset should have had LiveGuard capability in its consumer product versions long ago. Like feature capability has existed for some time in Eset competitor consumer products as you noted. This includes Microsoft Defender that doesn't cost anything. I also have no need for the extra features ESSP provides and feel upgrading to it for LiveGuard capability is shady marketing tactic.
It also should be noted that EIS costs on the average, significantly more than its competitor's equivalent products.
Bottom line to Eset - include LiveGuard in EIS or be prepared for a significant loss of your existing EIS product base.

Yes, an upgrade to v14 has been released on the pre-release update channel. We are releasing v14 for general public in the following days and will post an announcement then as well.

Read Marcos' post above, it is literally a few posts above!

https://www.computerworld.com/article/3567096/outlook-went-down-for-four-hours-wednesday-what-happened.html

Itman doesn't work for ESET so he cannot know. I do and I don't know either because the module is being tested and no ETA is available. All we can say at this point that the module will be released soon, most likely within a couple of days.

I mean newly created and modified files

We have tested a new cleaner module and the results are promising. Extensive scanning of WMI and registry will be probably accomplished only with the In-depth scan profile where the scan time doesn't matter.
If anybody's willing to test it, please let me know.

I am 100% there with you, I am now disappointed that you make the effort to test the software, report the errors found to the German support and all reported errors in the final, or so-called final, in my eyes nothing more than a very bad beta version is to find again + to find the errors of the previous build again, if this continues with Eset, I will also consider whether I should pay for it and that although I am an absolute Eset I'm a fan and have been using it since NOD v2, I am really very disappointed!

Mobile Security needs some kind of permissions for Anti-Phishing to work properly , have you enabled that?

Make sure that you are using a supported browser. Try it with Chrome and Firefox. On my mobile phone the website you sent me through a PM was blocked by ESET Mobile Security.
Make sure that this test page is blocked:
https://www.amtso.org/check-desktop-phishing-page/

If you ran a custom scan, make sure that you didn't enable scan without cleaning:
 

The only known issue with v13.2.15 is that the registry and WMI scanners attempt to scan also non-existing objects. This will be fixed via a module update soon. As for other issues, I'm not aware of other users having reported them with one exception. Please report them to your local ESET support with steps how to reproduce them. If necessary, the support will ask for further logs necessary for troubleshooting.
As for a bug-free software, there's nothing like that. We don't live in a perfect world and every software maker releases new versions and updates to address reported issues. Even Microsoft releases monthly updates with fixes.

Yes.

I would simplify it further; "Used" and "Available for use."

I will also add that in-product updating is always a more secure update method that manual updating; contrary to popular belief. Manual updating opens one up to a phishing attack. A recent example is the WastedLocker ransomware that deployed a fake Google Chrome update request.

I guess the wording could be better and read "Consumed seats" and "Available seats" or something along that line. "Available devices" means that you can activate the license on 1 more device.

What it's showing is one license seat has been activated and one license seat is available.
Eset's uses the term "seat" to refer to how many devices Eset can be installed on. In your case, you only have one Eset license issued to you and that license can be installed on up two a maximum of two devices; i.e. seats.

Correct. However, I don't see any good reason for not updating modules automatically.