Jump to content

howardagoldberg

Members
  • Posts

    233
  • Joined

  • Last visited

  • Days Won

    2

howardagoldberg last won the day on April 5 2021

howardagoldberg had the most liked content!

About howardagoldberg

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA

Recent Profile Visitors

3,274 profile views
  1. Well I'm still seeing it on only 1 of several systems I have ESET installed on. It seemed to abate for a bit, but now it something I have to deal with on nearly every cold boot. It's very annoying, and there is no reason I can identify as to what would be the cause. It started with the latest build.
  2. Just to clarify ... I do not have any other anti-malware solutions installed. So for my system, there is no conflict. I have two very similarly configured systems, and the issue only occurs on a 10+ year old system with a mechanical hard drive. My best guess is that the warning is triggered after a timeout period (the computer take quite awhile to boot up), even though it is likely functioning normally. There is no indication in the Windows Security Center than anything is amiss, and rebooting always resolve the issue.
  3. I am having the same issue. It randomly manifests when booting up from a powered off state. (Does not happen on restarts.) I do not have any other third-party antimalware software installed. Cannot generate a log because there is no pattern as to when the integration fails.
  4. Marcos, thank you for the quick response. I don't think this plan will work. The issue only occurs on first boot up from a powered down state (never an issue when 'restarting' from a powered on state), and it does not manifest every time. I don't want to run the computer for an indefinite amount of time with protected service disabled until the problem reoccurs (nor do I want to create an extremely large log). Any other paths forward?
  5. System: Dell XPS 15 L501X (10+ years old) OS: Windows 10 Pro 22H2 19045.3996 (Fully patched with latest updates, including recent preview update) Issue: On cold bootup (from a powered off state), approximately 50% of the time, ESET displays the following warning: Clicking "Restart device" resolves the issue 100% of the time. Before restarting, I checked Windows Security to see if it detects any issues, and it does not: Have performed a full scan and no threats have been detected. I have another newer system (Inspiron 7353 2-in-1) with the same OS and updates installed, running on the same network with nearly identical software (some additional apps compared to the system in question) installed. which has never experienced this glitch. The computer experiencing the error is used for very limited tasks (Amazon Music, Chrome for weather radar via the National Weather Service, etc.), and therefore is not exposed to suspect websites, etc. My hypothesis is this is a timing issue (old laptop, with a mechanical hard-drive which takes some time to boot, where the error is triggered prior to the integration taking place, but then the app is not refreshed to to display the actual status). Is there any way to resolve this? This began with v17 (I don't believe this error ever displayed with v16 and earlier). It is time consuming to reboot this laptop (because of its age). I am not going to replace the laptop, I understand it's beyond old - when it dies, it dies. But in the meantime, it works for what I use it for. Thank you for any thoughts/suggestions.
  6. This still seems to be an issue. Just received a notification that the servers cannot be reached.
  7. Just for the sake of telemetry .... I just updated ESET AV to 17.0.16 on two W10 Pro systems and no issues with the latest version of Edge (120.0.2210.77)
  8. For the sake of telemetry ... this just happened to me. I have two W10 Pro systems sitting next to each other, both connected directly to the router via ethernet. One system, just displayed the warning (after being online for about 12 hours with no issues). No warning on the other system.
  9. As I have already stated, the problem was resolved after a reboot. This past Sunday (11/26) the error appeared after booting up. I rebooted, no error message. No error message for several cold starts and reboots since then. I had never seen the error before, and have not seen it since. Windows reports that ESET is the AV provider and no issues are indicated. (I have confirmed that AMSI is enabled as per the screenshot you shared.)
  10. I will perform a scan, however - after rebooting (and every reboot since) the message has not appeared. The system in question is over 10 years old, and I use it mostly for streaming music. The only software I have downloaded in recent months is app updates via MS Store or updating MS365, Acrobat, etc. I don't even check email on the system. So there are not many vectors for malware to sneak through (all browsers are updated, and I do almost nothing with browsers on this system except go to the National Weather Service radar page and similar known, safe sites). Seems to me like an ESET glitch. None of my other systems on the same network - which are used for online activities more heavily and across a greater variety of services - have ever displayed the warning, which further increases my confidence that it is not malware. Windows security center also shows ESET as the Security solution with no issues.
  11. Upgraded to 17.0.15.0 in-app (Check for Updates) on Friday, November 24. Today (Sunday, November 26), booted up and received the above error message on the Overview screen of the app. Clicked the 'restart device' link. System took considerably longer to restart than usual, but upon reboot, the error message was gone and now have the expected greenish 'You are protected' banner, The system in question is a fully updated/patched Win 10 x64 system. The hardware is over 10 years old, but have never seen this message before on this or any of my Win 10 or 11 systems. What caused it and how can it be prevented in the future? Is there any risk to the system at this point? No logs to provide, since the error resolved upon reboot.
  12. Still no v17 via in-app upgrade. Is there any official word on the status?
  13. @itman That's interesting and makes sense based on other posts I've seen in the interim. I will wait until the bugs are worked out. Thanks.
×
×
  • Create New...