Peter Randziak

Hello @BobMarvin, see https://forum.eset.com/topic/18714-eset-business-for-linux-installs-but-does-not-open-in-deepin-1591/ for example. Regards, Peter

use https://www.eset.com/gr-en/ Peter

Hello @AlessandroG, Thank you for the offer, we appreciate it but seems we know what is causing the BSODs. Our team worked hard on this and spent about a week by debugging and researching those BSODs as we have multiple reports of it from our customers. We are nearly sure that we know, what the root cause, which is not caused by any bug in our security solution, so we are in contact with the driver developer to confirm our assumptions. Once confirmed, it will be up to the driver developer company to address the issue. Moreover our team came up with a proposed workaround on our side to avoid the bug manifestation leading to the BSOD. Regards, Peter Tracking key for us: P_EESW-4003

Hello @Ric, it seems there is an issue with the data replication to the ECA, maybe some connectivity issues. You have a ticket with the ESET support opened, right? Regards, Peter

Hello @milkybar1983, We generally do not support BETA versions or preview builds of any OSes as there are usually many changes until they reach RTM phase and it would cost us significant amount of resources to bring it. Of course the QA / Devs tests and prepare in advance for new major OS releases. We will do our best to bring full support from day one or as soon as possible after the OS release, but I think you may also expect the builds in advance of official full OS release. Regards, Peter

Hello @cybot yes the SecureData feature of ESSP and ESET Endpoint Encryption are based on former Deslock+ technology. the SecureData feature of ESSP is not affected by the issue described at https://support.eset.com/alert1/ When it comes to BSOD related to "Condusiv Diskeeper 18 Pro" I do not have any info on it, but BSOD's can be usually quite well investigated from the complete memory crash dumps so just have it checked by the ESET tech support team. Regards, Peter

Hello @AlessandroG We got an update from the development team. As a work-around please try to may disable the UDP in the Blast protocol, it helped in the testing environment, can you please confirm? To do that please refer to Vmware documentation: (basically set HKLM\SOFTWARE\Policies\VMware, Inc.\VMware Blast\Config\UdpEnabled to 0 (string value) on machines with Horizon agent) https://techzone.vmware.com/sites/default/files/vmware-horizon-7-view-blast-extreme-display-protocol.pdf https://techzone.vmware.com/sites/default/files/resource/blast_extreme_display_protocol_in_vmware_horizon_7.pdf Please keep us posted. Regards, Peter

Hello guys, can you please check if the issue persists as we fixed few memory leaks in modules, which are currently available on the pre-release update channel so please switch to it, update, reboot the system and observe the situation. In case the issue persist, just let us know, so we can troubleshoot it with you. Regards, Peter

Hello @cybot / All the Secure Data feature of ESET Smart Security premium is not affected as it does not contain the affected driver. So you can use the ESSP and Secure Data without any issues even after upgrade to the latest version of Win 10. Peter

Hello @sdnian, thank you for the packet capture, I will have it checked. May I ask you you have any SSL inspection in place? Regards, Peter tracking key: P_EESW-3955

Hello @markice and @asm_dec0de, thank you for your decision to take part. A message with further instruction is awaiting in your personal message inbox, Peter

Hello @mate, I would start with installing the most up to date version of the Endpoint i.e. 7.1.2045.5, you can download it at https://www.eset.com/int/business/endpoint-security-windows/download/ In case the BSOD happens with it as well, please collect the 1. output from ESET Log Collector, pack it along with the 2. full crash memory dump, upload it to a safe location and send me a private message with download details and reference to this topic, I will try to assist you. Regards, Peter

@Duane is a business trial license, which already expired,... So you should contact the ESET representative to prolong it if needed or to buy commercial ESET license. Regards, Peter

The issue has been resolved, you should be able to generate the offline license file now, can you confirm? Peter

Dear @serlockwright, Thank you for the report, we are already investigating the issue, we will keep you posted. We apologize for the inconvenience caused. Peter

Hello @BrianA_MN and @MAsterx1010, sure, thank you for your willingness to participate, will send you the invitations in a few moments. Peter

You are welcome, pleasure is on our side 😉 Peter

Hello Peter / @Faxe, sure, invitation sent few moments ago. Regards, Peter

@Tommy1987, sure, will provide you with details in few moments via a private message. Peter

Hello @trayn, good, well then PM with details sent. Looking forward to your feedback. Peter

Hello @trayn, thank you for your interest, currently we have only the product of version 7 for the file servers. Other types should follow later. Regards, P.R.

Hello guys, we are aware of this issue and the dev team is investigating it. Currently there are 3 tickets with the devs opened with similar symptoms, but so far we were not able to pinpoint the root cause from the available logs so we are waiting for an image of affected system so we can debug it in-house. I will try to keep you posted. Regards, P.R. tracking keys for ESET Staff members P_ESMC-18585 P_ESMC-18339 P_ESMC-18120

Hello @ADS82, sure, will message you in a few moments, sorry for the delay I've been OoO. Regards, P.R.

Hello @T3chGuy007 thank you for providing us with the log We checked them and we found: MSI (s) (BC!EC) [08:06:18:420]: Creating MSIHANDLE (422) of type 790531 for thread 8172 ERROR: (preps) Preparing of service failed. So it seems that the agent cannot be stopped for some reason. Please try to install the stand-alone agent on the affected machine and 1. run the installation with lvx parameter 2. Capture the events in the system during the installation with Process monitor with advanced output enabled, after it fails export the log in native pml format 3. Enable blocking of all blocked operations by HIPS in the HIPS setup on the Endpoint Compress the logs, upload them to a safe location and send me and TomasP a PM with download details so we can check it. Regards, P.R.

Hello @T3chGuy007, So can you please provide us with it so we can check it? I found a similar case reported by our QA "Installation failed with error (package=0, error=8257588" ( reference for us P_ESMC-16163) but it should be fixed in the latest version of ESMC, but not sure if it requires the newest agent as well as you have the old one ESET Remote Administrator Agent 6.5.522.0 "This seems to be caused by policy having connection settings. The custom policy in setup causes those settings to be locked, and the ConfigSetServerConnection is trying to set the setting but it's locked by policy so it fails..." May I ask why do you upgrade via the All-in-one installer? I would recommend first to try to upgrade via the Upgrade infrastructure task, as All-in-one primary usage is for deployment, not for upgrading,... Regards, P.R.