WD wants updates when there are none

  • Thread starter Thread starter Hilarion
  • Start date Start date
Hilarion said:
I've read some posts on this newsgroup about Norton Symantec security
software and I decided to try those things:

1. I uninstalled the Symantec software, and as Robinb suggested, used
their removal tool and CCleaner to clean the system from any remains
of the software. The issue with Windows Defender remained.
2. I tried your suggestion from another thread to rollback WD definition
database (and engine version) to original state using:
"mpcmdrun -RemoveDefinitions -All". The rollback worked, but when
I ordered WD to check for updates, it did update but is still
suggesting to check for updates.

If you have any other suggestions, then please do not hesitate to post
them. And thank you again for your help.
Click to expand...

I also tried one more solution given by warnellg in the thread "Windows
Defender is turned off/There are no new definitions availa", I mean
I deleted "C:\Windows\System32\wbem\repository" (had to stop WMI
service). It did not help too, but when I was wandering around Windows
management applications, I noticed something strange in system logs:
they were showing April 28, 2007 at current entries! And that was it!
My system date was set to future date, so the definition updates for
WD were always more than 11 days old, so WD considered itself not
up to date. When I changed the system date to current, WD stopped showing
the "should update" warning instantly, and the security center did the
same after system restart. So now everything is fine.

I did not check nor even suspect date settings, because I checked them
when I got the notebook and did not change those (at least not
intentionally). I suppose I accidentally clicked date change when I was
playing with "time from network" settings.

I apologise everyone here for the time I took from you by this thread.

I feel really stupid now, and probably I am.

Kamil 'Hilarion' Nowicki
 
No need to apologize, I'm sure we're all delighted that you resolved the
issue with that hard to spot but easily fixed solution.
 
Back
Top