Jump to content

cmit

Members
  • Content Count

    92
  • Joined

  • Last visited

Kudos

  1. Upvote
    cmit gave kudos to JoeC in upgrade to 7.3.2032 - computer gets shut down after scheduled scan   
    I want to add to this that this also happened to me on two computers that I was testing the upgrade on where it immediately performed a scan after the upgrade was completed and promptly shut down the computers. The event log confirmed it was an ESET-initiated shutdown after a scan completion. This is the same as the others have reported, but not a scheduled task, and not on demand, but immediately after the upgrade. Being located 1700 miles away from the office, and during a pandemic where no one else is in the office on a regular basis, it took a full week to get someone in there to turn these computers on. Fortunately, they were computers that were not in use by anyone, so were perfect candidates for this upgrade. Of course, I can't risk updating any other computers to 7.3 until this is confirmed as resolved.
     
  2. Upvote
    cmit received kudos from TomasK in upgrade to 7.3.2032 - computer gets shut down after scheduled scan   
    Per your changelog, is this already a known issue in v7.2 or different? Please explain this confusion.
    This did NOT happened on any of our computers that has v7.2 installed.
    another 2 weeks means Windows 10 computers that are "stuck" with ESET v7.2 can't be upgraded version 2004 of potential BSOD issue (https://support.eset.com/en/alert7506-windows-10-version-2004-bsod
  3. Upvote
    cmit received kudos from schuetzdentalCB in upgrade to 7.3.2032 - computer gets shut down after scheduled scan   
    This issue doens't fully make sense. Please explain what exactly happened on your developers' testings.
    Screenshot below, why this issue mentioned in the changelog of v7.3.2032.0 or this is a different issue?

  4. Upvote
    cmit gave kudos to twinstead in upgrade to 7.3.2032 - computer gets shut down after scheduled scan   
    I'm also confused like cmit. It appears at least that your support team isn't even aware of this problem. This thread is the most current info i have, even though I have a support ticket in about this exact issue. 
  5. Upvote
    cmit gave kudos to Jenova in upgrade to 7.3.2032 - computer gets shut down after scheduled scan   
    Greetings! 
    Listed as fixed in 7.3 "An on-demand scan launched from the ESMC console could shut down the computer even if this post-scan action was not selected" is exactly what started happening after I've upgraded Endpoint clients to 7.3. Never happened before. 
    The process C:\Program Files\ESET\ESET Security\ekrn.exe (WKST-VRN-BKP01) has initiated the power off of computer WKST-VRN-BKP01 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Other (Planned)
     Reason Code: 0x80000000
     Shutdown Type: power off
     Comment: Computer scan completed
    That comes from scheduled scan policy (daily on-demand scan with post-scan action set to "no action"). All upgraded endpoint clients have been shutdown after this scan.
    Fix it please!
  6. Upvote
    cmit gave kudos to MarcFL in Update Error: File not found on server   
    This is happening on my client workstations throughout the country.  This is an Eset issue.  Thanks.
  7. Upvote
    cmit gave kudos to sksksk in File not found on server   
    Starting on Jan 8th we've been getting "File not found on server" errors. for the Update module.  Any ideas?
     
    Thanks
    sk
  8. Upvote
    cmit gave kudos to Gamtat in File not found on server   
    We started getting this error on a regular basis on January 9th.  Clients seem to be updating but instead of seeing this error maybe once every few months I'm seeing it multiple times a day now.
    ESET Remote Administrator (Server), Version 6.5 (6.5.522.0)
    ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0)
    Update module1072 (20180813)
    Translation support module1721 (20181211)
    Configuration module1663.13 (20180709)
    SysInspector module1274 (20180918)
    Server 2008, Windows 7 clients. Using the Apache proxy.
  9. Upvote
    cmit gave kudos to sksksk in File not found on server   
    Still getting this daily.  Randomly.   I confirmed we are updating directly from the ESET servers.  HTTP Proxy logs indicate the fail (no file found on server) and success (no updates are available) logs are identical.
  10. Upvote
    cmit gave kudos to MarcFL in Update Error: File not found on server   
    Several different computers in different states with Eset NOD32 v12.0.31.0 are randomly reporting this error:
    During execution of Update on the computer xxx the following event occurred: File not found on server.

×
×
  • Create New...