Jump to content

Rob Schember

Members
  • Posts

    8
  • Joined

  • Last visited

About Rob Schember

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. I think there may have been some corruption in the scheduled tasks. I was able to resolve the issue by deleting all of the scheduled tasks that were being pushed down by ESET PROTECT and recreating them. All computers have been stable all weekend.
  2. Hi @Peter Randziak -- I was able to resolve the issue by deleting all of the scheduled tasks that were being pushed down by ESET PROTECT and recreating them. All computers have been stable all weekend. Thank you, --Rob
  3. Here's a screenshot. Every time I get a successful update of any module, my computer shuts down.
  4. I'm still having problems with computers shutting down after a successful update. If I run the "Check for updates" option manually from the GUI on any computer, even those with the new 2011.5 Configuration module, ESET will shut the computer down with a 30 second warning if any new updates were downloaded, even just Detection Engine updates. This also happens with scheduled updates, which run "continuously" every 240 minutes.
  5. That issue was regarding shutting down the computers after a scheduled scan. This issue is regarding shutting down the computers after a module update. This is occurring even with the new configuration module 2011.5 from the pre-release channel which was reported to fix the issue with the problem in that other thread.
  6. Note -- this is not the same problem as reported with ESET shutting down computers after a scheduled scan. ESET is shutting down all of my computers after a successful MODULE UPDATE. Steps to reproduce the issue are below: Using Endpoint Antivirus 9.1.2051.0, even with the new configuration module 2011.5 from the pre-release channel, I set my automatic update schedule to check every 60 minutes. Every time it detects a new version of the Detection Engine (or any other module) and updates it, ESET shuts our computers down with a 30 second warning. This began with the upgrade to 9.1.2051.0 from 9.0.2046.0. I opened a support ticket regarding this issue.
  7. I do have a scheduled scan task set for 7pm on Wednesday nights, and when I came in this morning, ALL of my computers were shut down, even though the scan task is set to "No Action". However, this is a different issue, so there appears to be multiple issues with shut downs happening here. This started happening before the scheduled scan ever would've triggered at 7pm. After a module update, the computers show a window with a 30 second timeout to shut down the computer! Another user posted the window I'm talking about. See the attachment here. However, in my case, instead of "Device restart", I believe it said "Device shut down".
  8. I can confirm we're having the exact same problem here since the upgrade to 9.1.2051.0. It seems to be triggered by a module update as both times I noticed it happen, I saw the program was running a startup scan, which happens immediately after a module update. Twice so far, I was shown an ESET window stating my computer was going to be shut down and to save my work. The window had a 30 second countdown timer. I was able to click the "Cancel shutdown" option once, but the second time I didn't see the window in time to react, so my computer was shut down. This has never once happened before the update to 9.1.2051.0 and we've been using ESET for 10+ years.
×
×
  • Create New...