Jump to content

cmit

Members
  • Posts

    92
  • Joined

  • Last visited

Posts posted by cmit

  1. On 6/26/2020 at 10:58 PM, Marcos said:

    In managed environments update to a newer product version will not be automatic by default. We understand that many administrators want to test new versions before they are rolled out to clients.

    My understanding is that admins will have to enable it via a policy first and also when a new program update is ready, accept the EULA in the ESMC console first.

    Next week a new hotfix version of Endpoint 7.3 should be released.

    what will be the exact version # of this hotfix?

    any news about this issue today?

  2. On 6/23/2020 at 10:36 PM, Peter Randziak said:

    Yes we have an update, the hotfix version should be available by the end of this month.

    Peter

    Do you mean this version (7.2.2072.0) that did not exist before when this v7.3 auto-shutdown issue started being reported in this forum topic?

    hxxp://us-repository.eset.com/v1/com/eset/apps/business/eea/windows/v7/7.2.2072.0/eea_nt32.msi.changelog.html

    image.thumb.png.1ef8c1fdc6e4d298e99511dacfb75c45.png

  3. On 6/25/2020 at 3:59 AM, MichalJ said:

    Hi @ShaneDT Indeed, you are right, and I can assure you, that enabling automatic product updates, for both the endpoint clients, and the management environment (both cloud / on premise) is our uppermost priority. 

    Doesn't "enabling automatic product updates" mean it would be even more troublesome if we had to roll back the product version if a newly officially released version has major issue again (i.e like this computer-auto-shutdown case)?

    This is exactly why I manually test the newly released upgrade on my testing computers first.

  4. 22 hours ago, JoeC said:

    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.

     

    Somebody from ESET should be responsible to fully explain how this troublesome issue happened.

    Not sure if everyone from the ESET Tech Support team(s) is always keeping communicated with ESET QA and development teams about details of every released version of ESET products.

  5. 3 hours ago, Marcos said:

    You can temporarily remove scheduled scan tasks. Actually we do not recommend running a scheduled task too often, once per month should be enough as long as all protection modules are kept enabled and the product is kept updated.

    If I remember correctly, sending a scan task from ESMC doesn't cause the machine to turn off so you could use this as a workaround.

    Please explain in more detail of why 'do not recommend running a scheduled task too often'. In this 'computer auto-shutdown after scheduled scan' case, your ESET product cannot be kept updated. Some people may have different opinion that at least a smart scan should run daily.

  6. 7 hours ago, Marcos said:

    We expect a hotfix to be available in 2 weeks if no issues are found during tests.

    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

  7. 5 hours ago, Marcos said:

    I've sent a scan task to a client with Endpoint 7.3. After the scan completed, the machine was not rebooted.

    image.png

    not reboot. the machine gets "shutdown" even though the the scheduled scan task's "Action after scan" has the "no action" option selected.
    The ESET EndPoint AntiVirus itself's computer scan's "Action after scan" option has changed from "no action" to "shutdown".
    This issue did NOT happen in vVersion 7.2.2055.0 but in the v7.3.2032.0 changelog it says this issue is "fixed"?
    ("Fixed: A finished on-demand scan initiated from central management console can result in shutting down the scanned computer even without activated shutdown option.")

    This is a huge issue for cooperate computers that need to stay on 24/7!
    Right now we had to roll back to v7.2.2055.0.

  8. We don't use MS Exchange Server so we don't use ESET Mail Security.

    May I confirm:
    In this module not-yet-updated case, is the ESET Dynamic Threat Defense any useful for MS Outlook users if the detection engine hasn't had this new virus data?

    If yes, what exactly more protection layers does EDTD has comparing to only have the ESET EndPoint AntiVirus installed in this case?

  9. 31 minutes ago, Marcos said:

    We started building engine 21366 an hour ago. It should be on update servers within 15-30 minutes.

    detection engine still in v21365. should be v21366 by now but still not. please check asap. thanks.

  10. 3 minutes ago, Marcos said:

    It depends, most of threats are detected via LiveGrid or streamed updates within a few minutes without updating the engine.  If you provide the subject of the email, I can check when the detection was added.

    [TRACK#5EC6A2EF0178] from the ESET Malware Response Team's reply.

  11. 5 minutes ago, Marcos said:

    One hour since when? Modules are updated about 6 times a day.

    since customers submitted a threat example to ESET Malware Response Team and after they have confirmed replied that "The detection for this threat will be included in the next update of detection engine."

    6 times a day means every 4 hours which isn't it too long? i.e. shouldn't it be once every 30min? what happens if before the update kicks in and computer already affected because of this? or is the real-time engine gonna have another layer of protection?

    just trying to understand exactly how ESET works.

  12. On 5/12/2020 at 10:23 PM, Marcos said:

    The engine seems to have updated to the latest version alright today, no errors are logged:

    13. 5. 2020 4:48:54    ESET Kernel    Detection Engine was successfully updated to version 21318 (20200513).    SYSTEM    

    Please keep an eye on this machine and make sure it updates the modules automatically. Should the issue return, enable advanced update engine logging and keep logging enabled for the next few hours, at least until a newer engine is released and at least one hour has passed to ensure that the automatic update task was run. Then disable advanced logging and collect fresh logs with ESET Log Collector.

    In your configuration I've noticed that you have the LiveGrid Feedback system disabled. I'd strongly recommend enabling it. It would not only enable us to add a proper detection and cleaning for new malware but it would also activate some additional protection mechanisms, e.g. in Ransomware shield.

    how long does it take for the newer detection engine version to kick in once the ESET Malware Team upload the new virus data to servers? it's been over 1 hr but our modules haven't got updated.

  13. @itman thanks a lot for your help but this is still going nowhere.

    People from ESET still do not have a proper solution nor willing to have an explanation about this.
    I'm definitely not the only ESET customer having this issue.

    This suggested temp solution probably should not be posted if it's not recommended to disable the SSL protocol scanning.
    (Re-enabling the SSL/TLS rotocol filtering or re-enabling the 'add the root certificate to known browsers did not resolve the issue for all ESET cusotmers)
    https://support.eset.com/kb3126/?locale=en_US&viewlocale=en_US
    image.png.fd0a48e167363604b90a2bf806d6b407.png

    At this point I'm still not 100% sure if this is totally ESET's issue or the web browsers themselves.
    (I don't believe it's all ESET's issues)
    Thanks to the people from ESET (who are supposed to be responsible for responding) for not able to at least try to explain nor break down this type of issue that's been going on for years.

     

    https://stackoverflow.com/questions/36309562/err-bad-ssl-client-auth-cert
    image.png.c07e970d52284324d21a933861af0537.png

    image.png.aed23ea4379e3587b401e7d6f8f2197d.png

    https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/i-get-error-message-errbadsslclientauthcert-while/fd1cabfe-1778-42a9-8fc1-ab2dd02b6db4?page=2
    image.thumb.png.002ea6c4002fc32a556e8995f2c0ff50.png

    image.png

×
×
  • Create New...