The ESET Service service hung on starting.

It does this on every restart and will not login if given enough time to resolve. It will login only after a hard reboot. Running eset version 4.2.40 on Windows 7 ultimate 64 bit.

 

did you try if the latest version ( 4.2.5.8 ) fixes the issue?

 

Reboot your PC in Safe Mode, Navigate to the service by typing services.msc in your Run Box.

Ensure that it is as shown in the screenshot -

If the above solution does not work.

Export your settings, Uninstall your current version, download the latest version from the download centre

 

I did not know until now that settings can be exported and then imported later. Interesting ... I hope to watch it when I have problems

 

Being able to export | reimport your settings is very handy in the context that you would not be required to reconfigure the installation from the begining if one chose to uninstall and reinstall a current build or newer build.

 

Upgrading to the latest version or ESET did not resolve the problem. Changing to a different AV program has resolved the issue.

 

This is moot now that you have chosen another AV solution. Perhaps having used the manual uinstaller, then having upgraded to the New build may have solved your issue.

 

It also hung on starting on my Windows7 laptop. Updating didn't work and, initially, the uninstaller failed telling me another program was using the log file. The "other program" was NOD32, so that was fixed by stopping it from Services. Read today that there was a problem with NOD32 slowing down a Windows7 PC (or even causing a BSOD) after the latest MS patch if NOD32 didn't have the very latest dataset. My problem might have been another symptom of the same root as I suspect the MS patch beat NOD32 to the punch.

However, I've since installed Microsoft's free Security Essentials (as recommended by Fred Langa) - trying it out on one PC before my 3 PC NOD32 license expires (the above problem just self-selected which PC I'd try it on).

 

On a MS Windows XP Pro. SP3 (32-bit, latest updates installed) and NOD32 AV v. 4.2.64.12 I also have this problem. During every boot the following error is logged:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Description:
The ESET Service service hung on starting.

It seems it is a transitional problem as a few seconds later another event is logged which says:
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Description:
The ESET Service service entered the running state.

The ESET Service recovers because the "Restart the Service" action is set in case of service start failure.

Is it something I should worry about?

I've checked a couple of other Windows machines in the LAN but they don't have the problem. NOD32 has been used for a couple of years in the LAN and has been upgraded to a new version at least once a year.

-- rpr.

 

Was this issue ever resolved? I see it in the event logs for almost all of our XP SP3 machines now... and yes, we're running the latest version of EAV.

One of them was even reformatted yesterday morning and has started showing the same error on every boot following the first round of updates from our WSUS server.

 

Should you experience this problem with v. 4.2.67, generate a complete memory dump as per the instructions here and convey it to ESET. Do you have certain exceptions / exclusions set?

 

Same problem here. ESET is on thin ice with me as I have had nothing but a bad experience with them. Anyone remember the day they pushed out definitions that casued every server and PC to crash?

A full memory dump?? Are you serious ... that is your solution? How bout maybe delaying the service startup time or maybe it needs to wait for another service to start up before it does? Do you not realize that in the real world on servers how long a full memory dump takes and most companies can not afford that downtime?

Please find a solution for this.

 

I do remember. And I also remember that not one of our 122 PCs and servers crashed or experienced any problem. And I also remember that almost every other vendor has had issues in the past, such as when McAfee quarantined svchost.exe and rendered systems completely unbootable.

I agree, a full memory dump isn't great. But if ESET can't recreate a problem and you can, then it's an enormous help to them. As a software developer myself, I know that unless you can recreate a problem or see some evidence of it, it's complete guesswork trying to find the cause.

Is it not better to have an extra 5 minutes of downtime once, and help get the problem fixed, than ESET being unable to fix it.?

I'm sure they will be trying very hard, but I'm also sure they could use you help.

A complete memory dump (which I believe is limited to 2GB anyway, regardless of installed RAM) would probably be a big help.

Just my view.



Jim