Bart31

Last Friday, all systems updated automaticly back to 1745.13 version and have not had any problems anymore. In all cases, the network was using ESMC (no local installations).

I think we were running 1.8.0_191. We reinstalled the webserver, selected this version of Java and the webserver was running again. 1) As a test I installed a new EMSC on a new Server2016 environment, running java 1.8.0_231. That also installed correctly. 2) On another existing server 2016 environment, running Java 1.8.0_144 and 1.8.0._171, I manually updated Java to the newest 1.8.0_231 version. The installer recommended uninstall of the 144 version, which I did. After that, the ESMC webconsole still worked (also after a reboot of the windows server). My conclusion would be, that is has nothing to do with Java. On this Server 2016 environment, there were some Windows Updates ready to be installed (.NET updates KB4519562 and KB4524095). I did these updates and rebooted the server. Still working. So I think we can rule those updates out too.

Last week we have seen a couple of domain-joined Windows 10 machines, running the ESMC 7.0 service (webconsole), having issues with the HTTP server after Windows Updates. We ended up reinstalling the webserver. Now today I have a Server 2016 server with the ESMC 7.0 with the same problem. Question: Why is Windows Updates killing ESMC 7.0 webconsole services and does ESET have an update to prevent this from happening ?

Hi, Since last monday 28/10 we have Remote Desktop Server 2016 crashing services / hung sessions on five RDS servers (different networks). These problems are not only on RDS sessions, also the administrator on the console experience windows-explorer related issues not responding anymore. In all cases, it's Eset File Security which is locking up and crashing other services. A complete reboot of the RDS has to be done. A manual update after reboot seems to work. But a couple of hours later, the same happens again. At this point, we have disabled the update feature on the GUI client on de RDS. We cannot find a solution yet. Anyone experience the same problems? It's only happening on Remote Desktop Servers 2016. Regards, Bart