Peter Randziak

Hello Ryan, are you able to see last connected time for those clients? If yes, does it update or is there still the same value? Does ERA server reboot make any difference? Regards, P.R.

Hello Lindend, you can send me a link to the memory dumps via a private message, please attach output from ESET Log Collector tool to them as well. Regards, P.R.

Hello Leon, can you check if there is no other AV installed on the system? If not you can send me output from ESET Log Collector tool and dump from erkn created via Procdump (run procdump -ma ekrn from an elevated command line, please let ekrn consume CPU for about 5 minutes before creating the dump) for analysis. Regards, P.R.

Hello Interos, We do not have currently an open BETA for ESET Cyber Security (Pro) – our product for macOS, but we plan one in the future, it will be announced via the ESET Security Forum as well. Regards, P.R.

Hello Pedro, Most of the cases is caused by incorrect proxy settings, issues with Internet connection and in case of older systems like XP by missing root certificates as well. Regards, P.R.

Hello, @Maxx2777 in case you have Endpoint 5 version lower than 5.0.2254 please upgrade it so you won't suffer from the first mentioned issue with updating i.e. premature x64 .nup update file deletion. Those, who have only 5.0.2254+ deployments, are you able to estimate how much time after a system restart does it approximately takes until the issue starts to manifest again? Regards, P.R.

Hello Slarkins. there are 2 issues described: 1. premature x64 module update files deletion (fixed in 5.0.2254.0+) 2. issue is related to memory allocation (can be fixed by rebooting the operating system, a permanent fix will also be provided by means of an Internet protection module update (version 1256) soon.) So in case you have an Endpoint of v. 5.0.2254.0 it should be the second issue. Hopefully this clarifies it a bit, P.R.

Hello, in case you are not able to upgrade to the new version (it notifies you, but nothings happen after clicking on the upgrade button) please 1. take Procdump from ekrn right after the issue manifests (download Procdump tool from https://technet.microsoft.com/en-us/sysinternals/dd996900.aspxrun cmd as an administrator and run procdump -ma ekrn) 2. collect logs by means of ESET log collector as described here: hxxp://support.eset.sk/kb3466/?viewlocale=en_US Pack these two logs, upload them to a safe location and send me a download link with reference to this forum topic, we will check it. Thank you, P.R.

Hello, in case you are not able to upgrade to the new version (it notifies you, but nothings happen after clicking on the upgrade button) please 1. take Procdump from ekrn right after the issue manifests (download Procdump tool from https://technet.microsoft.com/en-us/sysinternals/dd996900.aspxrun cmd as an administrator and run procdump -ma ekrn) 2. collect logs by means of ESET log collector as described here: hxxp://support.eset.sk/kb3466/?viewlocale=en_US Pack these two logs, upload them to a safe location and send me a download link with reference to this forum topic, we will check it. Thank you, P.R.

Hello, Yes Internet protection module updates are being downloaded alongside Virus signature database updates (in version 5 +) please find more info about the issues in recently published ESET customer advisory covering these issues. Regards, P.R.

Hello, is still somebody facing the issue? All the logging should be stopped few moments after the issue manifests. Regards, P.R.

Hello, you you be able to provide us with an application crash dump? You need to download a Procdump tool from Microsoft site: https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx run a scan by ESETOnlineScanner than run the Procdump from elevated command prompt with command procdump -ma -e ESETOnlineScanner once ESETOnlineScanner crashes, it will dump a process memory into a file (with .dmp extension). Please pack it with output from ESET Log Collector output, upload it to a safe location and send me a private message with the download link, we will check it. Regards, P.R.

Hello Drasp, as it seems, that excluding makes the problem go away please do the log without it, so it will capture the issue.

What we know is that it seems that the update files are downloaded successfully, but the application of them is not successful, so your statement supports that theory, but does not help us to determine to root cause of it.

Hello Slarkins, I'm sorry that we request such amount of logs, but many users are reporting it, but no-one has supplied us yet with all the logs we need to check the issue as there are more theories, what might be causing it. Once fixed, it should work transparently again. Probably the most important change is that we need a Procdump of ekrn from such state as well. Regards, P.R.

Hello Slarkins, As the issue persists, please continue as follows: 1, download and install Wireshark as well as Process Monitor. 2, run the following command from the command line prompt started with administrator rights logman start updater -p {f329ae9a-556d-4934-920f-234e835d9ece} 0xffffff 10 -o C:\eset.etl -ets 3, start logging with Wireshark and Process Monitor 4, run update (wait until an error occurs) 5, stop logging in Wireshark and Process Monitor and save the logs 6, run the command "logman stop updater -ets" with administrator rights 7, run procdump from elevated command line with -ma switch for ekrn i.e. procdump -ma ekrn 8, collect logs using ESET Log Collector (ELC) from both the workstation and server where a mirror is created 9, create a listing of the mirror folder (e.g. dir c:\mirror > mirror.txt) on the server 10, compress all logs + the listing of the mirror folder, upload them to a safe location along with ELC logs and pm me the download link. I will check it with Devs with priority. Thanks, P.R.

Hello, we are aware of the issue, the fix will be delivered by means of Translation support module update. It should be already available on the pre-release update channel. Regards, P.R.

Hello Ego, We had an issue with the Beta platform provider, which is now resolved. We are sorry for the inconvenience.

Hello, please restart the affected machines and in case the issue persists please create a procdump from ekrn and send me a download link to it via private message, we will check it. Regards, P.R.

We are happy to announce that the BETA versions of our products – brand new ESET Internet Security, providing multiple layers of security without significant impact on performance, and ESET NOD32 Antivirus, offering fast anti-malware – are both ready to download and test on https://www.eset.com/int/beta/edition2017/ What's new in BETA? Webcam Protection (ESET Internet Security only) – Lists all applications that have been using the webcam and allows the user to block access. Home Network Protection (ESET Internet Security only) – Shows devices connected to your network and offers a router scan to check for router vulnerabilities. Script-Based Attack Protection - Protects you against malicious Windows and PowerShell scripts. UPDATED - Parental Control (ESET Internet Security only) – Now with updated categorization. To report issues, please fill in the built-in support form or hxxp://www.eset.com/int/beta/form .

Hello, please find the steps in our online help here: hxxp://help.eset.com/era_install/63/en-US/migration_same_version.htm P.R.

Hello BDeep, please find the information in this KB article hxxp://support.eset.com/kb332/?locale=en_US P.R.

You can re-try it, we fixed the issue on the server side.

You can re-try it, we fixed the issue on the server side.

thank you for reporting it, we are looking into it right now.