Peter Randziak

Hello @j-gray, thank you for keeping us posted. I'm sorry to hear that it does not behave well 😞 , I hope it will improve. I may offer you help with issue analysis / the log analysis by ESET HQ as those issues will probably in most cases require developer level support and possibly fixes on their side too... Peter

Hello @Kagom3, there was an outage (~7:00 - 8:30 CEST) affected the activations and part of the licensing related services. Can you try it now and let us know how it went? Peter

Hello @j-gray, you are welcome, sad to hear that it behaves that way. I would recommend to take logs from it and open it with the support team to see what happened and possibly make fixes / improvements so it will work as expected... Peter

Hello @mrac, the local support opened an ticket for the HQ support to assist with the case, the local support already received an answer and will try to do theirs best to reply to you asap. We apologize for the inconvenience caused by the delay. Peter

Hello @mrac, I'm checking it with the Global support team. Peter

Hello @j-gray I checked it with the EEI support specialist. I asked the dev for an update / if we need more data from you to check it (P_EEI-11416) This seems to be more ESET PROTECT related issue. To check it we would need the logs from the EP and the affected machine, where the task was sent. Does it fail in few minutes or after 24 hours? If after the 24 hours, it would mean that EP server hasn't received the result. so it considers the task as failed. If it fails in few minutes we need to check what is in the logs. The question here is if the product is activated successfully. In the EI connector log should be seen the not activated error or if it sends data to the server normally. To check it we would need the EP DB dump and logs from the affected machine (to see what sends the agent and what is in the DB...) btw. you are not an MSP provider, right? As for MSPs we have an issue, where the EI connector reports incorrect status for the license (MSP/SUBSCRIPTION type licenses), but sends the data to the server. It might be an similar issue (P_EEI-11688) Peter

Hello @Tola, we reached to Avast (Huawei apparently uses engine made by them) regarding the detection, they already fixed it. Peter

Hello @Rob Schember, if the issue persists, send us the output from ESET Log Collector to check, as requested above Peter

Hello @Rob Schember, I just wanted to ask you for an update, how the situation evolved on your side, as the behavior you described was quite unpleasant... Peter

Yes, based on my knowledge of the issue it should be safe to plan upgrade / new deployments to 9.1. Peter

Hello @Trooper ESET PROTECT Cloud hasn't used the affected Configuration module, so #1 from the list is not applicable https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510/?do=findComment&comment=153054 #2 and #3 from the list should be resolved automatically with the fixed Configuration module so based on my current knowledge of the issue, you do not need to take any action. Peter

Hello @Rob Schember, I replied at https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510/?do=findComment&comment=153066 I hope you will be able to fix it based on it. If not, we are ready to assist you, but I won't be available much during the weekend (CEST), if you need the assistance now I would recommend to contact the local support... Peter

Hello @Rob Schember, I assume that the computers are managed by ESET PROTECT / ESMC / ERA, right? I would first check the Action after scan in the scheduled tasks. The policy / settings corruption might happen in 3 scenarios, see https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510/?do=findComment&comment=153054 for details. If the issue occurs on your ESET PROTECT management console you need to 1. switch it to pre-release update channel to get the fixed Configuration module 2. Manually fix the policies / scheduled tasks (if the policy is already corrupted, the Configuration module 2011.5 is not able to repair it, thus the manual fix is needed) Please do not edit the policies using the older Configuration module, as it might cause further issues If it won't help, get an ESET Log Collector output from the affected machine, upload it to a safe location and send a private message with download details to me and Marcos to check with a reference to this post. If correctly-looking policies would apply incorrectly on Endpoint 9.1 , the problem should be solved automatically (by just updating). Peter

No the Configuration module is being updated as a module (like the Detection engine) so there won't be a service release of the endpoints to address it. The issue is in the mentioned module... Peter

There are 3 scenarios / places where the issue might occur: 1. Edit of the policy in EP/ESMC/ERA 2. Merge of policies on EP/ESMC/ERA agent 3. Apply the policy on the Endpoint By the releases of Configuration module we covered #2 and #3. #1 bas to be fixed manually in the management console, but to edit such policy, make sure Configuration module 2011.5 is used, for EP/ESMC/ERA it is available on pre-release update stream. Editing the policy by means of older Configuration module may damage it further. Peter

Hello guys, Configuration module 2011.5 is now available for Endpoints v.9 (release update stream), EP/ESMC/ERA servers (pre-release update stream) EP/ESMC/ERA agents (release update stream) Peter

Hello @Rob Schember This is a known issue that has been discussed at https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510 I would recommend to watch it for further updates... Peter

Hello guys, Fixed configuration module 2011.5 is now available on pre-release update stream for EP/ESMC/ERA management agents and Endpoints Reverting update to Configuration module 1998.2 has been released for EP/ESMC/ERA servers (on release update stream, since ~ 11:25 CEST) in order to prevent further policies corruption. Peter

Hello guys, Configuration module 2011.5 is now available on pre-release update stream for EP/ESMC/ERA management agents and Endpoints Reverting update to Configuration module 1998.2 has been released for EP/ESMC/ERA servers (on release update stream, since ~ 11:25 CEST) in order to prevent further policies corruption. Peter

Hello @Trooper, it has been reported at https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510 https://forum.eset.com/topic/32896-latest-endpoint-security-reboots-itself-after-updateagain/ I would recommend to check those for further updates. We apologize for the inconvenience caused by it. Peter

Hello @StooIT Yes, exactly. This is a first report of such issue, I noticed so I would recommend to grab the logs and open a case with a support team to have it checked. Peter

Hello @JimChev3, it has been reported at https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510 https://forum.eset.com/topic/32896-latest-endpoint-security-reboots-itself-after-updateagain/ I would recommend to check those for further updates. We apologize for the inconvenience caused by it. Peter

Hello guys, our technology and tech support teams are on it, we are investigating this with a priority. We probably already identified the module version causing the issue. We apologize for the inconvenience caused. Peter

Hello guys, our technology and tech support teams are on it, we are investigating this with a priority. We probably already identified the module version causing the issue. We apologize for the inconvenience caused. Peter

Hello @BenoitR, the ESET Server Security for Microsoft Windows Server supports the Auto-update. Additional release for automatic updates of the build 9.0.12013.0 will replace the original major release build 9.0.12012.0, and is planned after the safety period (~30 days). Peter