Jump to content

Chaluha

Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by Chaluha

  1. 36 minutes ago, Marcos said:

    We kindly ask you to respect this forum rules (

    17. Do not pre-announce releases.  Due to differences in scheduling, it may sometimes take several hours after a release has appeared on ESET's web site for the release announcement to appear here in the forum.

    Hi Marcos and would not be better if you let us know that new fixed version is going to be released?

    So we can hope for fix soon at least, instead of waiting and no news here in forum.

  2. 2 minutes ago, Marcos said:

    1, An automatic uPCU to newer versions will be introduced soon, it's been our topmost priority. A prerequisite for this is ESMC 7.2 which has been released just recently.

    2, A reboot is required after upgrade to v7.3. If you have upgraded from v7.3.032 to v7.3.037, a reboot will not be required.

    is there some new fixed version 7.3.2037 after yesterday release 7.3.2036 ?? Or just typing error??

    thanks

  3. 13 hours ago, offbyone said:

    Just installed the new version and the problem still persists.

    I'm really getting disappointed about that software. Don't get me wrong but an endpoint protection software which omit to update its signatures is a security problem.

    Yes I can canfirm that new version did not fixed this problem.  Version 7.2 was working fine. Need to be fixed ASAP.

  4. Hi fixed version is 7.3.2036.0, should be released today.

     

    Version 7.3.2036.0

    • Fixed: System shutdown after a scheduled on-demand scan if no action was selected.
    • Fixed: Sensitivity levels of detection mechanism would block files even if configured to report only.
    • Fixed: Firewall rules editor could crash under some circumstances, particularly after many re-ordering changes.
    • Fixed: The management console of ESET Enterprise Inspector is unable to obtain a copy of quarantined endpoint object.
    • Fixed: Bootstrapped installer would abort if installation folder is not empty, regardless of forced background clean-up.
    • Fixed: Certain sections in advanced settings would not render as a result of processing large configuration lists in the background.
    • Fixed: Uninstallation process is blocked when advanced diagnostic logging of Network protection layer is enabled.
    • Fixed: During product upgrade from version 6.x, Program Component Update (PCU) settings are not properly configured (to defaults) in managed networks.
    • Fixed: Blocking of certain vendors' USB printers in Device control does not work.
  5. Hi fixed version is 7.3.2036.0, should be released today.

     

    Version 7.3.2036.0

    • Fixed: System shutdown after a scheduled on-demand scan if no action was selected.
    • Fixed: Sensitivity levels of detection mechanism would block files even if configured to report only.
    • Fixed: Firewall rules editor could crash under some circumstances, particularly after many re-ordering changes.
    • Fixed: The management console of ESET Enterprise Inspector is unable to obtain a copy of quarantined endpoint object.
    • Fixed: Bootstrapped installer would abort if installation folder is not empty, regardless of forced background clean-up.
    • Fixed: Certain sections in advanced settings would not render as a result of processing large configuration lists in the background.
    • Fixed: Uninstallation process is blocked when advanced diagnostic logging of Network protection layer is enabled.
    • Fixed: During product upgrade from version 6.x, Program Component Update (PCU) settings are not properly configured (to defaults) in managed networks.
    • Fixed: Blocking of certain vendors' USB printers in Device control does not work.
  6. 16 hours ago, cmit said:

    what will be the exact version # of this hotfix?

    any news about this issue today?

    version is 7.3.2036.0, should be released today.

    Version 7.3.2036.0

    • Fixed: System shutdown after a scheduled on-demand scan if no action was selected.
    • Fixed: Sensitivity levels of detection mechanism would block files even if configured to report only.
    • Fixed: Firewall rules editor could crash under some circumstances, particularly after many re-ordering changes.
    • Fixed: The management console of ESET Enterprise Inspector is unable to obtain a copy of quarantined endpoint object.
    • Fixed: Bootstrapped installer would abort if installation folder is not empty, regardless of forced background clean-up.
    • Fixed: Certain sections in advanced settings would not render as a result of processing large configuration lists in the background.
    • Fixed: Uninstallation process is blocked when advanced diagnostic logging of Network protection layer is enabled.
    • Fixed: During product upgrade from version 6.x, Program Component Update (PCU) settings are not properly configured (to defaults) in managed networks.
    • Fixed: Blocking of certain vendors' USB printers in Device control does not work.
  7. On 6/16/2020 at 10:26 PM, MietekN said:

    Try to delete all tasks from the eset scheduler and restore the default.

    Hi it seems to be working. Is there a way to do it via ESMC for all clients?

    Is it just my bug or global and will it be fixed in next Eset Endpoind release?

     

    EDIT:

    YES it is confirmed from ESET support that is 7.3 bug and will be fixed in next build.

    EDIT 2:

    Update not working again after few days🤦‍♂️

     

    Thanks

     

  8. On 12/31/2019 at 1:23 PM, Marcos said:

    We have received no reports of issues with Windows XP from partners around the world. In all cases recent reports were about BSOD that was caused by modules compiles with Spectre mitigation enabled and in all cases update of modules helped. I'm afraid that without manually crashing the system when the blank screen appears and generating a full memory dump we are in a blind alley. Nevertheless, I'd strongly recommend raising a support ticket with customer care.

    Hi for me ESET Endpoint Security v5 working now fine. Just need to delete Eset folder in Program Files before install Eset, otherwise it will load bad modules during installation and crash.

×
×
  • Create New...