Service wouldn't start

Discussion in 'ESET Smart Security v3 Beta Forum' started by cbuddha42, Sep 18, 2007.

Thread Status:
Not open for further replies.
  1. cbuddha42

    cbuddha42 Registered Member

    Joined:
    Aug 4, 2007
    Posts:
    10
    Hey, last night when I rebooted by computer I found windows would hang after the login and eventually load a black screen then load the taskbar but with nothing on it. Then it hung and wouldn't respond to any input except mouse movement. Similar symptoms happened before but a reboot in to safe mode fixed the problem. This time I had no such luck. Eventually I found I could open task manager at the all black screen before the taskbar loaded and identified that the ekrn service was "starting" and stayed that way. By booting to safe mode and disabling all the services related to ESS I was able to boot normally, but I still could not get to the web. Ping worked to the 1 server I should be able to see to authenticate to before getting to the rest of the web, but I could not reach the same server with an http or https protocol. The most helpful message I could get out of windows network repair was that www.microsoft.com was not set to contact the http server. I assume this means ESS firewall works by redirecting those requests to itself and somehow this setting was still active even though none of the ESS drivers were running. Long story short, I had to uninstall ESS, and now I can reach http pages fine.

    This was ESS beta 2 on Windows Vista Home Premium 32 bit on a Dell laptop with a core duo 2 CPU. This problem occurred seemingly randomly, and I do not know what triggered it. ESS was set to auto update every hour and was showing a green icon before shutdown, so I assume it was fully or near fully updated.
     
  2. ASpace

    ASpace Guest

    You can contact ESET beta team on email betasupport @ eset . sk
    They may want you provide them some log files and some other information for detailed examination
     
  3. Rolmos

    Rolmos Registered Member

    Joined:
    Sep 17, 2007
    Posts:
    6
    Same here, I also use WIndows VIsta Business 32 bit, with a 2 core processor on a Dell laptop (probably a coincidence).

    The computer could not startup after login, and the screen stayed black for over an hour. I was forced to hard reset the computer. I deleted ESS from the startup, and was able to login normally, but when I tried to uninstall ESS to try to reinstall it, the computer would hang again, forcing me to hard reset again... I was finally able to do so by deleting ESS from startup again (it was automatically reactivated), renaming the ESS folder in Program Files, login in normally, and renaming the ESS folder back to the original name seconds before requesting the uninstallation. Problem was solved.

    This happened one morning without having modified anything else on the computer.:blink:


    EDIT:
    This other thread may be related to this problem: https://www.wilderssecurity.com/showthread.php?t=185800
    I also have an Intel 4965agn Wireless card.
     
  4. RoseDreamJ

    RoseDreamJ Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    17
    Location:
    NY USA
    I have had this happen several times as well. I've also had similar issues with other applications before I ever installed ESS. I believe the issue has to do with several applications wanting to check for updates immediately upon boot. When one of these is a firewall or other activity limiting security app, I think all other lesser apps hang while waiting.

    The quick "solution" to the event is a hard reset. :rolleyes: But I think it is indicative that when the hard reset works and the following boot is successful that ESS displays an "Update Successful" alert. To help prevent this, I've set some non-ESS services to "delayed start". I've also set Vista itself to "notify" instead of auto-update.

    Auto-updates are great. But I really wish:

    a) app developers would stop setting their applications to check / update immediately upon connection or making the attempt on first opportunity after a missed scheduled task.

    b) that operating systems of the future would categorize and prioritize objects that load upon boot.
     
  5. cbuddha42

    cbuddha42 Registered Member

    Joined:
    Aug 4, 2007
    Posts:
    10
    Well I tried reinstalling, and I immediately ran into the exact same problem. I had similar complications disabling the services again because the uninstall/reinstall process seems to have left some traces. Enabling the processes in msconfig (they showed disabled even though they were loading), booting, hard reset, safe mode for msconfig and redisable then boot is what I think did it for me.

    As far as the update theory goes. I had limited versions of this issue at least once before (where I got stuck at a black screen) but that time it was easily fixed with a reboot. I don't remember if it said updated afterwards, but this time a reboot didn't help. Also, I don't know what was trying to update at startup. One of the few things I did after reinstalling was change the scheduler to do a nightly scan and make sure it was on hourly updates. Update on login was turned off. Windows update is also turned off on this computer. Other than rocket dock which I don't think has an auto update and some dell power and touchpad utilities that definitely don't, nothing loads at startup.
     
  6. bjevers

    bjevers Registered Member

    Joined:
    Jun 9, 2003
    Posts:
    17
    Location:
    Iowa
    I've had smiilar hangs while booting into the desktop with Vista Ultimate 32bit. What seems to have worked for me is to change the Eset service startup type from Automatic to Automatic (Delayed start).
     
  7. cbuddha42

    cbuddha42 Registered Member

    Joined:
    Aug 4, 2007
    Posts:
    10
    Is this issue fixed in RC1? Or is installing it going to stop my machine from booting again?
     
  8. ASpace

    ASpace Guest

    You are the onliest that can check how are things going on in your specific environment/on your machine :thumb:
     
Thread Status:
Not open for further replies.