Updated were unable to be successfully installed

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

Guest

Windows Automatic updated is working, but the updated download fails to
installed.
with Error message:

The following Updates were not installed
Definition Update 1.13.1276.3 for BETA Windows Defender (KB892519)

Call up Support Centre but told no support for the BETA softwares. Please
help, Thanks. (Using Windows XP (Home), Norton Anti-virus and Lavasoft
AD-Aware SE Professional.)
 
I have the same problem. I reviewed the Update History from the Windows
Update page and the initial download of the update has beside it in the
"Source" column: Other Source. That doesn't sound good. Let me know if you
come up with anything. Thinking about uninstalling the beta and using my
other antispyware programs. I think I'll also do a full antivirus scan while
I'm at it.
 
I posted to you earlier on this before I did the following: I uninstalled
Windows Defender, and used a registry cleaner to clean out the registry
(Regscrub XP - google it and it will turn up) and rebooted. I went back to
the Defender download page, downloaded it again, and allowed it to do its
initial update. Everything seemed fine, but I got curious about what might
have happened. I went to the Windows Update site and called up the Update
History. What I found (and this may or may not have something to do with it)
is that another update, Definition Update 1.13.1272.4, KB892519 loaded before
the update Definition Update 1.13.1276.3 (which, interestingly, is also
called KB892519). Not sure what that means, but it was the only
inconsistency in the update history. In short, Definition Update 1.13.1276.3
KB892519 does not seem to load without the prior update. Don't know whether
this helps, but in any case, everything seems to be fine, and Windows
Defender Definition Updates (so far) are current.
 
The kb reference is always the same. Last I looked, that article no longer
exists.

such are the vagaries of a beta--nothing to worry aboutm though.

--
 
The new problem of updating of Definition 1.13.1276.16 can in a slightly
difference form as compare with the previous updating problem of Definition
1.13.1276.3. What is actually happening New Definition Updating 1.13.1276.16
is never been updated to the PROGRAM even though the Windows Automatic
updating is SUCCESSFUL. Hence the Windows Automatic Updating keep repeatative
wanting to have the same updating. It is very annoying. Can anyone help me?
 
Run the Windows Installer Cleanup Utility and remove the Windows Defender
Definitions only (not the Windows Defender program). Then run WD update -
either Help, About, Check for Updates or use Microsoft Update to download
and install the new definitions.

If you don't have the Windows Installer Cleanup Utility, you can download it
from:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

I don't know what causes the failure to update, this method seems to fix the
problem.
 
Check the current time in this group--there are some other users seeing this
repeated update issue, and thinking about it--they believe it to be a defect
in the .MSI file--perhaps uninstalling it via the msiexec switches would be
a fix?

--
 
We don't have enough experience over time to say this--I think there have
now been 3 updates, and only one has exhibited this behavior for some
users--certainly not all.

--
 
Will see what happen during the next Definition Updating, before I give it a
vote. Hopefully the problem is gone forever.
 
The same old problem still persists, I could not update to the New Definition
1.13.1286.1. Hence Windows Automatic Update would be repeatative yet it would
said each time it was successful but actually not the case.

So I tried RUSTY suggestion i.e. to do a Definition Intaller Cleanup with
the Utility download from:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

After remove the old Update Definition 1.13.1276.3 ONLY (NOT WINDOWS
DEFENDER), then reboot it before manually Update the Definition, this works.
this method seems to fix the problem. But I don't know whether it will happen
again during the next updating.
 
Thanks for the report. I can't say for sure what will happen next time
either--good luck!

--
 
More serious problem, the New Definition 1.14.1513.1 was detected by Windows
Automatic Update and was downloaded and installed successfully.
But Windows Defender still show the OLD Definition 1.14.1288.5 built on
03/02/2006 at 09:27. So the New Definition was not installed.
On checking Windows Defender manually updating, it says the the Definition
is up-to-date. Hence, it is not recognising there is a New Definition now.
Please advise what to do next.
 
Hi Bill, I have re-installed the Windows Defender, then it automatically
updated the latest Definition. So now I will wait and see what will happen
when next Definition is due later.
 
I think you are in good shape.
--

pnjchai said:
Hi Bill, I have re-installed the Windows Defender, then it automatically
updated the latest Definition. So now I will wait and see what will happen
when next Definition is due later.
Click to expand...
 
Hi Bill, I am surprised my Windows XP (Home) went corrupted and not
functioning properly. Hence I had to re-install the whole system.

However, after I re-installed the Windows Defender (Beta 2) again, I was
able to update the definition. But when I tried to start the Windows
Defender, another problem appeared, it said "User Interface has encountered a
problem and needs to close. We are sorry for the inconvenience." So I send
Error Report to Microsoft. i.e.(f8bc_appcompat) in a notes format. If you are
interested, please let me have your email to send to you.

I like to know now what to do, as I cannot even scan my system with it.
Should re-install the Windows Defender?
 
Back
Top