Can't get past 1.0.0.0 signatures - tried KB articles already

G

Guest

Ok this sucks having to post it since there are tons of posts about it but
I've tried everything I've read so far.

* Had to install the Windows Installer 3.1 - done
* Ran through windowsupdate express until no updates were available - done
* Installed WD, reboot, updated - Msg saying it is up to date, yet still
saying definitions are 96 days old (v. 1.0.0.0).
* Followed kb915105 article (uninstalling definitions then updating them
again) - get same message as before saying it's up to date but it still says
96 days old.
* Tried kb918355 article - WU is done, nothing left to install - did
previously listed kb article - windows update works fine since I just
installed numerous updates from it - I have it running on another computer of
the same make/os since months ago with no problems so network environment
shouldn't be the problem.

Also checked the windowsupdate.log file which shows a successful install:
2006-05-02 14:09:48 1780 3f8 Report REPORT EVENT:
{A50214B0-11C9-44EC-8D23-DCF42C018C84} 2006-05-02
14:09:43-0400 1 183 101 {8DC24D93-135E-4249-AC09-6ECED27AB991} 100 0 Windows
Defender Success Content Install Installation Successful: Windows
successfully installed the following update: Definition Update 1.14.1410.10
for BETA Windows Defender (KB915597)


Current WD version shows 1347 so it's up to date and I've rebooted after
installing the last updates but they still show up as v1.0.0.0.

Any other suggestions to try?

Thanks.
 
B

Bill Sanderson MVP

Great. I've yet to have a complete failure on a machine I'm hands on with.
I know this is annoying, but I believe it will get taken care of.

--
 
B

Bill Sanderson MVP

Terrific. That URL is extracted by digging into the
\windows\windowsupdate.log file from a machine which has just updated (or,
in fact, failed to update!)

So--if you get stuck to this extent in future, you know where to find the
info--I'm not going to commit to posting it (as definitions change) , but I
will in cases where it seems to be needed.

--
 
G

Guest

I had a problem similar to this, but took a different path. I was able to
up-date from 1.0.0.0 to 1.14.1436.4 by going through window update using the
"custom" scan rather than the "express". This by-passes through what MS
interprets as a "high-priority" update or not. In custom it will list the
newest Defender definition file as an update. Install this update and viola
everything works!!

My computer was in a network setting and this was the only way it worked to
update the definition file.

Personally, MS did a step backwards by 1) Not having any support service to
get through this problem and 2) the fix is a round-about way to get
definitions installed. Why were the Beta 1 definitions updates not a problem
for users??

I've read that once past definition 1.0.0.0 it's possible to use the updater
within defender itself. I haven't tried so don't quote me on this point
 
G

Guest

Hello

after same bug ( Windows Defender stil in 1.00000 spyware database version )
I tried manual method, and this worked fine !!!

another point I found why Windows Defender can't update by itself !
It points to the WUS server of my company, and this WUS as not update for
WinDefender for instance !

Thanks fo all
 
B

Bill Sanderson MVP

Glad that worked. Windows Defender definitions CAN be made available via
WSUS, if the administrator chooses to do so--might be worth asking,
depending on the environment you work in.

--
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Error 0x800b0100 when updating signatures on WinXP 64bit 0

Top