Jump to content

Marcos

Administrators
  • Posts

    36,085
  • Joined

  • Last visited

  • Days Won

    1,438

Posts posted by Marcos

  1. Release Date: February 22, 2024

    ESET Full Disk Encryption v1.4.58.0 has been released and is available for download.

    Changelog:

    Version 1.4.58.0

    • ADDED: Automatic application updates now use the proxy settings
    • FIXED: A problem where multiple disks would be grouped as one within the UI
    • FIXED: A problem where upgrading to version 1.4 caused black screen when booting on systems with older UEFI implementations
    • FIXED: The bootloader now adheres to the 'User can change password' policy
    • FIXED: A problem where proxy settings were not being applied
    • FIXED: A problem where the product could become deactivated randomly
    • FIXED: A problem with keyboard keys in the bootloader.  When Caps Lock was on and combined with modifier keys (SHIFT, CTRL, etc) the wrong characters would be outputted
    • FIXED: A problem when EFDE automatically updated, a status message would show stating the update had failed
    • FIXED: A problem in certain environments which would cause the Agent Interface Service to crash
     

    Support Resources

    ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support.

  2. RDP is allowed in the trusted zone. It would be dangerous if it was allowed by the firewall from untrusted networks too.

    Please carry on as follows:

    1. Enable advanced logging under Help and support -> Technical support
    2. Reproduce the issue with blocked RDP
    3. Stop logging
    4. Collect logs with ESET Log Collector and upload the generated archive here (only the ESET staff can access attachments). If the archive is too big to upload here, upload it to a file sharing service and drop me a private message with a download link.

     

  3. 47 minutes ago, Joergen Rune Mortensen said:

    Actually, I have already tried it from another folder (c:\temp), but it does not seem to make any difference. It was also by moving and editing the installation files I was able to point at the exact failing location in the VB-script.

    Please provide a Procmon log from an attempt to run a modified installer that uses a different folder than "temp". Are you able to run other vbs scripts from there?

  4. Endpoint 5 reached EOL in December 2020: https://support-eol.eset.com/en/policy_business/product_tables.html.

    For EOL products module updates are not guaranteed and were terminated without prior notice: https://support-eol.eset.com/en/policy_business/support_levels.html.

    Moreover, Endpoint v5 was missing many of modern technologies to detect and block today's malware and other threats and attacks.

                 
×
×
  • Create New...