3.0.563 Amon won't run at all

Ok I give in... short of I got a bad download, how did you manage to get this thing to run.

Started with 2.7 and years of uninterupted safety.

Upgraded to 3.0.360... ran ok seemingly apart from where the wotsit did delete instead of quarantine go fow web browsing... no don't want a sodin copy! whose bright idea was that then?

Anyway, read there had been a couple of problems so upgraded to 3.0.563...

...the upgrade went ok and checked settings etc etc... couldnt see any difference... until I rebooted... now NOD wont start at all!

Splash screen opens and never goes away, open Nod from the start menu and nothing in the console... apart from the splash screen that will never go away.

Remove altogether and manual clean up, then reinstall - Red eye - if you can get to the advanced setup active monitoring is not ticked - try ticking or starting active protection and nothing but a log entry "Amon didn't start..." really helpful... not, and nothing in event viewer at all.

Gave up! now 2.7 running very fine again.

Any thoughts anyone? TIA

[Clean XP, fully patched, no old AV other than NOD, Outpost currently disabled incase it was getting in the way, 2.7 and 3.0.560 both run OK]

 

If you want to give it another go:

1. Uninstall current version of NOD32 using ADD/Remove Programs in Control Panel
2. Remove Eset folder in:
a. Program Files
b. Documents and Settings\All Users\Application Data
c. Documents and Settings\<Your Name>\Application Data
3. Run Windows Installer Cleaner Utility to remove any traces of NOD
(Only Select NOD32, NOT other applications)
http://support.microsoft.com/default.aspx?kbid=290301
4. Install NOD32 Version 3.0.560

 

Thanks Thankful but I had tried the manual clean up (been there many times before with other apps)

However... after a coffee and a telling off from the wife for swearing so much I did try again.

A cleaned machine, installing 563, Amon wouldn't run.

A cleaned machine, starting with 2.7, upgrading to 560, then to 563, Amon wouldn't run.

A cleaned machine, starting with 2.7, upgrading straight to 563 is running happily so far and that's after 2 reboots?!? That's just wierd.

If it keeps running, fine, I'll keep it on for now.

Thanks
Gordon


BTW My vote is still to delete Web malware, not save copies of it. They still give you the option in the email settings, why not web browsing.

 

Did you run the Windows Installer Cleaner Utility?

 

Amon in 563? This is getting really weird. If people start moaning about modules, that are not even present in a program.
How do you mean everything is screwed up here, since the relase of THE NEW ESET?

 

Hi Thankful

No I didn't use the Windows Installer Cleaner Utility, personally I've never had that much luck with it - I can find files and the depths of the registry it doesn't touch, so I tend to do these things manually. Having said that, my starting point here was a clean build XP with 2.7 so unless the 2.7 uninstall and my cleaning up missed a 2.7 left-over?? No idea.

Start with 2.7 and upgrade straight to 563 seems to be OK though, so we'll leave it at that I think.

BTW: Thanks for the comment but not really helpful big Apple

Actually the driver is eamon.sys [Description "Amon monitor", version "3.0.0.65535", location "C:\Program Files\ESET\ESET NOD32 Antivirus\Drivers\eamon"] but the log file still reports Amon... and er... yes it is still there, and I was reporting what the log actually said.

?? nobody said that, wrong thread I think.