DavidC

Hi, Is there any option to force synchronize license count between the 2 consoles ?

Hi, In order to add information, note that trying to upgrade to V10, this error appears: We cannot find the installation of ESET Server Security in windows installer database. After clicking OK, ESET install helper will run to restore Server Security Sentries. If i try to continue, it says that the folder already exist. i manage it with eset uninstaller and after that, an install.

ok, thanks. I'll do that.

Hi Marcos and thanks for you response. So, we have to upgrade ESET version. Maybe a conflict that appears when WU and Update Catalog. Another question appears to me : ESET protect cloud console says there's no automatically upgradable product for these computer. The clients computer are already upgraded to Endpoint Antivirus 10 but none of the servers are. All servers are in Server Security 8 and i don't find how to do it (manual or automatically) How do i do this ?

efsw_logs-2.zipAnd the efsw logs

ok, He had mixed 2 machines (that was causing error, and production "restored" machine) New try: - restored machine with backup from just before crash (3-4 hours before) - verified that the problem exists : normal boot stays with spinning wheel, but forcing elam-disabled boot mode starts the machine - disabled adsync and windows search services, problem persist after reboot (no boot on normal mode) - in elam-disabled mode, I enable crash ctrl keys, complete dump option, and did the recollection of logs. I confirm that there's no Eset icon in the task bar. - trying to boot in normal mode : never-end boot, generate a memory dump but no sufficient disk space (only 10Gb) - reboot in elam-disabled mode, to retrieve disc space - trying to boot in normal mode : never-end boot, generate a memory dump successfully We are looking for what was the problem in the backup VM because production is already restored but the problem has appeared 2 times in 2 months. MEMORY-2.rar

Well... Let me verify with my collegue what he has done. He had to do all actions with the backup just before the reboot and crash (4h before).... Maybe he have done something wrong. With backup just before crash, becaise production was restored from another backup (30hours before)

memory dump MEMORY.rar

efsw_logs.zip

Hi, We have a VM windows server 2019 with ESET Server Security for Microsoft Windows Server installed. Since 2 "windows update tuesday's", on reboot, server doesn't boot (spinning wheel). The first time, we done a restore of previous backup (2 days before), it's has booted well, done all updates, no more problems. The 2on time, same problem, same solution (with 2 days before backup). This time, we have more time to test what appends and after restore backup from some previous hours, we can reproduce the problem. The only way to start the server was starting in safe mode or disabling ELAM. Removing eset product with uninstaller in safe mode "repairs" it definitively. Do you have a feedback of this problem ? Some ideas to avoid new problems ?