xxJackxx

We disabled caching on the US backend a few hours ago which seems to have helped.

Now it is connected to liveguard again, It is connecting and disconnecting at intervals.
Now it is disconnected again.
 
essp_logs.zip

time.windows.com is very inconsistent due to the volume of traffic it receives. It may all be coincidence. It fails more often than not for me regardless of firewall used (or not used). You may want to find a different server to sync with if you have ongoing problems. I doubt the firewall is the issue.

22H2 seems to have a multitude of problems. I would only use it to test at this point. Which I have stopped doing for the moment. Reporting issues like this is good, it helps these 3rd party vendors discover and fix issues. Though this one is likely on Microsoft as they have made changes to Defender, and also to Core Isolation from what I have heard. I would not recommend it for a daily driver. I'm going to give them a month or 2 before trying it again.

Well, I'll give my own answer. So far it seems ok but "secure all browsers" does not work. With 22H2 browsers will not launch with this setting. Firefox gives a "couldn't load xpcom" error until I turned this setting off. Otherwise I have seen no other issues. Yet.

I had actually just come here looking to  ask the same question. I have been running defaults for quite some time so everything is automatic. Is Smart mode the recommended setting over automatic if no custom rules are set as implied? Is there any reason I would not want to do so?

I don't understand why this is even a conversation. The Kaspersky UI has changed very little since 2012 and I would take the ESET UI over it any day. That said it wouldn't hurt my feeling if they added a little more color to it but it is perfectly functional as is. I remember when all vendors used to replace the UI every year and it took another half year to work out the bugs.