Bart31 0 Posted November 6, 2019 Share Posted November 6, 2019 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 ? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted November 6, 2019 ESET Staff Share Posted November 6, 2019 Is it somehow possible to check whether Java was updated during those updates? What kind of Java are you actually using? Link to comment Share on other sites More sharing options...
Bart31 0 Posted November 6, 2019 Author Share Posted November 6, 2019 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. Link to comment Share on other sites More sharing options...
Recommended Posts