Amon / File Damaged / Use Default ?

Yesterday after rebooting my laptop, I got an error message from Amon stating that the file(s) were damaged and that the default configuration would be used......1st time in over a year I ever had any sort of problem with NOD32. I opened up Amon and reset the options the way that I like them, rebooted, and then checked the options again (to be sure they "stuck"). Everything worked like it was supposed to..............question is, what happened?

 

Anyone from Essett got a response on this one? Rod?

 

> Yesterday after rebooting my laptop, I got an error message from Amon stating that the file(s) were damaged and that the default configuration would be used......1st time in over a year I ever had any sort of problem with NOD32. I opened up Amon and reset the options the way that I like them, rebooted, and then checked the options again (to be sure they "stuck"). Everything worked like it was supposed to..............question is, what happened?

=====

> Anyone from Essett got a response on this one? Rod?

Sorry ... that's like phoning your doctor and asking him why you have a stomach ache ... without seeing the computer, there's no way of knowing what happened.

Corruption is a fact of life on computers. To be on the safe side, I would uninstall and re-install a fresh NOD32 ... but I'm a bit paranoid about these things.

 

Well when it loaded the default values and I went in and changed it to my preferences, it has been fine since. Just strange that it occured..........as stated, I've been using it for well over a year with no problems to speak of....then this happened.