-
Posts
203 -
Joined
-
Last visited
-
Days Won
12
xxJackxx last won the day on June 9
xxJackxx had the most liked content!
About xxJackxx
-
Rank
Newbie
Profile Information
-
Location
USA
Recent Profile Visitors
1,582 profile views
-
xxJackxx reacted to a post in a topic: The ESET LiveGuard Servers Cannot be reached
-
That only worked one time and then stopped working. Ultimately it was not a fix. As for a possible DNS issue I changed my DNS provider and that also made things seem to work, for a few minutes. Then the problem returned. In any case it seems fine today so unless they give us a specific reason for the issue we may not entirely know why. That said if the problem does not return I'll forget to care. 😁
-
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.
-
As a follow up though this seemed to work at first, when I was on another forum and started typing a reply to a discussion my browser crashed and disappeared. This happened with Firefox and then again the same exact thing happened in Edge. I disable "secure all browsers" and they both work without the crash.
-
As Windows 11 22H2 was released to the Release Preview Insiders yesterday I gave it a go and it was so broken that I had to restore a backup from yesterday morning. Any known issues with ESSP and 22H2? I do realize it is not officially released to everyone but it will be at some point. I am thinking about trying again in case it was an issue with the upgrade process itself but if it is broken again then I need to identify why that is and report issues to the vendor where the conflict lies so it can be resolved by the official release. I am not currently blaming any ESET software but if there are known compatibility issues it will shorten my troubleshooting.