Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
After installing 360 v2, logging into Windows takes forever. Looking in the event log I find two errors:
Event ID 7009 - The Automatic LiveUpdate scheduler service doesn't connect within timeout
Event ID 7000 - The Automatic LiveUpdate scheduler service failed to start because of the timeout
On top of that, logging in is now slow as molasses because of this. I've scratched my head trying to figure out what the cause might be, but this goes beyond what I know about my computer and the murky depths of Windows. All I understand from this is that the service in question does not start for some reason, and after 30 seconds Windows gives up and moves on.
As for OS, I'm carrying the burden of Windows XP SP2 on my shoulders.
Can someone brighter than me illuminate what the problem could be?
Since installing v2 earlier today.
Looking through my services in msconfig and the registry, there appears to be two services. One which is named in English and running, and another one named in Swedish which is not running and the one which fails to start up on boot. Maybe one of them is the LiveUpdate component from the v1 install and the services clash.
It seems suspicious given that in the entries for one of them, even the registry keys themselves are translated into Swedish, having umlauts and all. Could it be a localization snafu?
Strange.
You don't happen to be in Sweden?
Yes, I do live in Sweden (hence the reason I use a translated version of Norton 360… that was what I could get hold of at the time I bought it). I’m not sure how much luck I would have with the Swedish tech support though, so I thought I’d try my luck here first.
What I suggest is to run Norton Removal Tool
Than reinstall NIS
Thanks. I followed those directions, but they did not get rid of the translated registry keys. I then figured that reinstalling and then uninstalling 360 v2 might get rid of them. It didn't. But after manual deletion of those rogue keys and another reinstall of 360 v2, things are working fine. There are now no registry keys for LiveUpdate with translated key names and no errors in the Windows event log.
Weird to say the least. Maybe those keys were left over from v1.
It seems it didn't fully resolve boot speed though, but as I've been stricken by the notification area bug maybe I'm just perceiving it that way since I don't see the icons of things that already took ages to load. But at least I've gotten rid of a pesky error, that's something I guess. :)
So for how long did Norton not update?