howardagoldberg

But how would I gather logs after the fact, if this is completely random and unpredictable? I can't run with logging enabled indefinitely 'just in case' ...

@Marcos ... I have never seen this error before on my system (again, have been running ESET on it for 4+ years), or any other system I have ESET installed on (I have been a user for probably 20 years). So: 1) How would I go about reproducing an issue that I suspect is actually a glitch on ESET's end and/or somewhere between my ISP and ESET's servers, and 2) More importantly - if the GUI is 'all green' with no orange/red warning messages, is it safe to assume I am fully protected? Again, the error message popped up, and within the 20 seconds it took me to open the GUI, it had 'resolved' (ESET was 'all green'). Is it possible for someone at your end to check ESET's logs to see if there was a momentary communications glitch? That seems like the most probable cause, I was only looking for confirmation, since as far as I know, it will be impossible for me to manually reproduce what seems to be a very esoteric issue (even if it happens again). Also, to reiterate -- I have another computer on the same desk, connected to the router in the same way as this system (ethernet), with a similar software configuration (including ESET AV and Windows Firewall) - and no such error was displayed or recorded. That further bolsters the likelihood that this was not a local issue.

@Marcos As stated in my original post: I use Windows built-in firewall and have not made any changes to it. No updates installed in at least 96 hours. ESET has been installed on this system for years, and this is the first time I saw this error message. At this moment, if I open up the GUI, it's all 'green' with no errors. So, again ... my question is: should I be concerned or is this likely a momentary communications glitch at my and/or ESET's end? My other computer, with a similar configuration on the same network, shows no error in the log. I read the KB ... there is nothing in it that applied to me as I never made changes to what ports were open, etc.

This morning, about 15 minutes after booting up my computer, the warning message (orange) below popped up in the notification area: ESET Antivirus 14.0.22.0 03/02/2021 6:25:09 AM; ESET Kernel;Limited Direct Cloud connectivity. For more info see: https://support.eset.com/en/kb332 I have had ESET installed on my system for about four years (since I put it into operation, in fact!) and have never seen this error before. By the time I opened up the ESET GUI, the notification had disappeared (except of course, in the log), and the GUI was showing all green with no issues. I have changed nothing in terms of ports on my router (or computer or firewall - using Windows firewall), and no updates for Windows have been installed over the past (at least) 96 hours. Is this something I need to be concerned about, or was this just a temporary communications glitch between my system and ESET? I have a similarly configured system sitting on the same desk, attached to the same network, also running ESET and no warning issued popped up and does not exist in the log. Please advise. Thank you!

I would have to go through the many posts I've made over the years I have participated in this forum to give you specific examples, but suffice it to say ... I have posted at least several dozen times, and the responsiveness of other forum members and ESET staff has generally been outstanding. By the way, I am not an ESET employee - just to be clear. I have been using ESET products for probably 20 years now. I have their products installed on 3 Windows machines, 2 Macs, and 1 Android. This forum has been the source of much valuable information and support.

Sometimes it even takes a day or two for the change log to go live on the Microsoft (Office) 365 page! The stagger the rollout of updates, and don't always update the change log until the release has been widely installed.

These forums are not the official support pages. Change logs are posted here as a courtesy. Bookmark https://www.eset.com/us/home/antivirus/download/, click on 'Advanced download,' and the current change log will be available. ESET has some of the best support in the industry. The fact you don't want to go to the official change log page seems to be the issue.

I don't normally jump in on these types of conversations (rants) ... but I have to say that of all the technology companies I deal with (and have dealt with), ESET is probably the most professional and transparent - and willing to acknowledge when there is an issue. These peer to peer forums are not official support pages, although to ESET's credit, their staff are here all the time providing direct and indirect assistance. In other words, they are paying attention. As @Marcos pointed out, the official change log page was updated at about the same moment that the update went live for those on the stable release channel who were seeking it via 'check for updates.' Add a bookmark to your browser favorites and move on. 🙂

@Marcos ... it worked! Thank you 🙂

I have a 3-user license for ESET Anti-Virus (Windows). At the moment, I am only using 1 seat. Can I use this license key to install Cyber Security on a Mac? Thank you for any insights you can provide!

I purchased ESET Mobile Security via the Play Store two years ago, and would like to add it to my License Manager. However, I cannot find the actual license key, only the public key. Is there a way for me to add this license to my license manager account? Thank you for any insights that can be provided!

It is available at https://www.eset.com/us/home/antivirus/download/ > advanced download

Marcos, respectfully, that does not answer my question at all. Why was the module 'downgraded' from 1380.2 > 1379.6? Did something strange happen at my end (on two different systems) or is the current official version 1379.6? Thank you!

That's what I am suspecting ... but given that 1380.2 was pushed out to address specific vulnerabilities, it would be great to have some information on what is going on ... thus, my post! 🙂

It is weird, and again it's on both of my W10 systems. I have *never* used pre-release updates on either system, so I never disabled them 😉. And again, the date for the 1379.6 version is 7 days more current, but the version number of the module has 'regressed.' Only explanation is this was pushed out by ESET. If it was only on one system, I would look to a 'local issue' ... but it's clearly reproducible.

I am running two systems on Windows 10 x64 (1909). Last evening, I noticed the the HIPS module was at version 1379.6 (01/27/2020). The prior module was version 1380.2 (01/20/2020) The date of the 'current' version is later (January 27) than the past version (January 20), but the version number seems to have been downgraded? Are we still protected from the vulnerabilities that 1380.2 was pushed out to address? Please advise. Thank you! @Marcos @Peter Randziak

Thank you, @Marcos!

My son just 'upgraded' from a three-year old Windows 10 system to a Mac Pro. We have a license for ESET Anti-Virus on Windows, can that license be used to activate ESET Cyber Security on Mac? I did search the forums before posting, as I am certain I have seen this question here before, but I was not able to hunt down the post - so please forgive me if this has been answered already! Thank you 🙂

Correct. But I gave ESET full location permissions, and the issue persists. Giving location permissions actually solved the issue right after the release of Android 10, but a more recent update to the ESET app reintroduced the issue - even if ESET has location permissions granted. (Currently my app is at version 5.2.42.0-0)

@Marcos @Peter Randziak This is still an issue after today's update to 5.2.31.0. Please advise. Thanks!

^^^ This is still an issue. Any updates @Marcos?

@Marcos @Peter Randziak ... ^^^ any thoughts? I just left my house to run an errand. When I returned, and the phone reconnected to WiFi, ESET is throwing up the 'insecure network' notification. This is def a bug ...

There is already a thread about this topic: Issue was re-introduced with the update to 5.2.18.0 last week, with somewhat different symptoms. I posted a detailed account of the issue on the thread above. @Marcos @Peter Randziak

@Marcos @Peter Randziak Late last week, ESET Mobile Security for Android was updated on my device to version 5.2.18.0. With the update, this issue has returned with somewhat different symptoms, but it is easily reproducible: 1) While on my home network, no 'warnings' from ESET. 2) If I leave my home, keep WiFi on (but not connected, obviously), phone automatically switches to LTE, no issues. 3) RETURN home. Phone reconnects to home WiFi network. Now, ESET throws a warning that I am connected to an insecure network and I should disconnect. 4) Toggle WiFi off. Toggle WiFi on, issue 'resolves.' But obviously, it's a bit of an annoyance to have to toggle WiFi off and on again on my home network that is fully secured. Clearly, this is a bug. I am running the latest version of Android 10 (with both the system and 'play' October security patches) on a Pixel 3 running on Verizon wireless. Location setting for the app is to allow location access at all times. Please advise. Thank you!

Thoughts: 1) Is the permission for location set to 'always' or 'just when app is in use?' It needs to be set for always. 2) Are you certain that the WiFi network you are on is actually secure (WPA2 or better)? 3) After setting the location permission for ESET, toggle your WiFi off, let the phone connect to LTE, then turn the WiFi back on. I had to toggle the WiFi in order for ESET to 're-scan' the network I was connected to. Hope that helps!