4.0.437 says definition files are outdated when they're not

[gugarci]

I've experience the following problem now 2 time recently during a power loss after restarting my PC. I'm using 4.0.437.

The battery in my mother board is dead and when we loose power the computer's date and clock always set itself back to Sept of 03. What's been happening of late is after fixing the clock and date Eset will turn orange to tell warned me that my definition files are out of date.

But if you look at the current definition files from withing the Eset GUI the files are not outdated they are current. Also the date of the last successful update for the definition files will show an older incorrect date.

When this happens If i try to have Eset check for updates manually it will try to connect but it never completes the task. It just hangs there for ever like it's trying to connect.

I've solved this situation twice now using system restore. But I was wondering if anyone else has experience this issue before. I'm thinking of trying to clear the update cache next time to see if it solves anything. But I might have tried this before without success, but I'm not 100% sure if I did.
Thanks.

[jimwillsher]

Why not replace the battery in the board :-) It takes 5 minutes and costs 50pence / $1.

Going through the system restore option is a sledghammer to crack a nut...


Jim

[gugarci]

I'm going to do that but this is something that shouldn't be happening anyway.