Jump to content

The Eset install launcher (0888) service failed to start due to the following error

Recommended Posts

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

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...