ronxp2000 2 Posted February 18, 2016 Share Posted February 18, 2016 Do I need this service? Can I remote it? Can I uninstall it with SC DELETE? The reason I ask is for years I have 2 event id errors pertaining to this service. Link to comment Share on other sites More sharing options...
ronxp2000 2 Posted February 20, 2016 Author Share Posted February 20, 2016 (edited) I have asked this question 3 or 4 times in years past, ESET will still not answer Edited February 20, 2016 by ronxp2000 Link to comment Share on other sites More sharing options...
ronxp2000 2 Posted February 23, 2016 Author Share Posted February 23, 2016 Well how that service got left there, I do not know. Finally, I took some simple time to resolve this with safety and logic, so I compared some other systems that have ESET on them, and that service was not there. By the name, obviously it seems to be a temporary service used to perhaps install Eset. What ever reason it got there, or improperly was not removed, I am not sure. Anyways I found that it is safe to delete the service from the command line level using: SC DELETE <service_name> This way it takes away the 2 event id errors it caused, and ESet still works properly. Case closed for anyone that comes across this rare instance. Link to comment Share on other sites More sharing options...
Recommended Posts