rpearce@law.fordham.edu 1 Posted February 16, 2014 Share Posted February 16, 2014 I click on the icon and nothing happens. When I first installed it, it worked. After closing the application, I can't reopen it. Help! Link to post Share on other sites
ellj20 0 Posted February 17, 2014 Share Posted February 17, 2014 (edited) I have the same issue with mine as well!!!! Edited February 17, 2014 by ellj20 Link to post Share on other sites
SweX 870 Posted February 17, 2014 Share Posted February 17, 2014 I think ESET may want more details from you like what version of OS X you use, and what version of ECS you got installed. And what icon exactly you're talking about and where that icon is located. The more information you can give the better. Link to post Share on other sites
ellj20 0 Posted February 18, 2014 Share Posted February 18, 2014 (edited) I'm using all the latest stuff downloaded from your eset website and I'm using mavericks 10.9.2 (13C59). None of the icons work. Edited February 18, 2014 by ellj20 Link to post Share on other sites
ellj20 0 Posted February 18, 2014 Share Posted February 18, 2014 If I reinstall the eset then it works but until I shutdown my system and power back on it will not do a thing no launch not even able to update the eset application Link to post Share on other sites
Administrators Marcos 3,693 Posted February 20, 2014 Administrators Share Posted February 20, 2014 Could you confirm that you're using the latest version of ESET CyberSecurity for Mac 5.0.115 which added support for Mavericks (OS X 10.9)? Link to post Share on other sites
ESET Staff filip.maliarik 0 Posted February 20, 2014 ESET Staff Share Posted February 20, 2014 Hello, Do you know how to check system.log for errors when you try to run ECS from Applications? Process should launch, but as you stated it crashes for some reason. Error message might help, to which part of ECS should we focus to... If you don't, I can share our logs collection script with some instructions how to use it Link to post Share on other sites
Solution rpearce@law.fordham.edu 1 Posted February 20, 2014 Author Solution Share Posted February 20, 2014 Many thanks -- turned out that when I rebooted it started working again. Link to post Share on other sites
Recommended Posts