Cannot update definitions

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The definitions in Windows Defender Beta 2 were last updated on 1/25/06, the
indicator in the System Tray says the definitions are out-of-date but when
you select the option to do an update, it says it is already up-to-date.

I followed the steps per the below Knowledge Base article but it did not fix
the problem.

http://support.microsoft.com/?kbid=915105

This happens on every Windows XP computer at my office that I tried this with.

What can I do to get the definitions to be updated?

Thanks to anyone who can help me out.
 
How are Windows patches and updates distributed in your office?

If you go to Windows Update on one of these machines, does it get the
current update, if you do an express scan and apply all offered updates?
 
I have exactly the same problem on a standalone machine. I followed the
Knowledge Base article but nothing changed.
 
I have the same issue on a standalone system. Defender says I have not
updates for 48 days. Icon in tray always has the orange spot with a '!' in
it. Ran your .exe file - no help. When I update, it says it updates and
that I am current. But still have the orange spot with ! and Winodws Live
OneCare also keeps telling me I need to update Defender. Pain in the ass!
Please help.
 
Can you go to http://support.microsoft.com/?kbid=918355 and try the steps
there?

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Windows updates are distributed at my company using a SUS v1.0 (we have not
updated to WSUS yet). I know that Windows Defender updates will not be
distributed via SUS 1v.0. On these computers in question, I manually ran the
Windows updates from the Windows Update webpage and Windows Defender should
automatically update itself.

I also followed the directions in kbid=918355 and it did not help. By the
way, that article says to "Click Check for Updates on the Windows Defender
beta 2 home page" but I can find no such link on that webpage.

At the Windows Update webpage, this item was listed to be installed:

Definition Update 1.14.1436.4 for BETA Windows Defender (KB915597)

I installed it but it responded by saying "Updates were unable to be
successfully installed" but when I check the Windows Update History webpage,
it says that it was successfully installed but Windows Defender still shows
the 1/25/06 definitions.

I then installed the update via that exe link you provided and that worked
(it now shows the 1.14.1436.4 update from 5/1/06).

Is this a one-time fix for that one update or will Windows Defender now
automatically install future updates on that computer?
 
The article need some editing, I'm afraid. The "check for updates" button
is in help, about.

However--all updating within Windows Defender goes via AutoUpdate, which in
your case is going to the SUS v 1.0 server, and thus will not work.

Windows Update should work, if you are not restricted from reaching
Microsoft's servers, which it appears you are not--so the glitch there is
what needs to be addressed.

I don't have a sense yet about whether getting the definitions in place via
the manual method that you (and I, last time around) used, either fixes
anything or will cause further problems down the road. I'm reasonably sure
it doesn't fix anything, and I'm not sure about the "problems down the road"
side of the question.

Steve Dodson is interested in seeing log files from folks having update
problems. Specifically, there is both the Windowsupdate.log file
(\windows\windowsupdate.log) and, additionally, optionally enabled Windows
Installer log files.

In XP, enabling Windows Installer log files is covered in this article:

http://support.microsoft.com/kb/314852/

Note that these logs will build up in \windows\temp if you don't disable
this later, so remember that you need to undo this change, if you choose to
do it.

I'm mentioning this because you have a number of machines--and perhaps
others of them will show some similar symptoms--don't worry about update
within the program--that failure is expected---but failures in the Windows
Update process are not expected--that should work.

My situation is the opposite. My home machine has problems, and none of the
machines in small offices I administer has had any update problems...

--
 
Back
Top