POSSIBLE ANSWER TO UPDATE PROBLEM

[Guest]

Hi everyone...

Just found a new problem I want to see if everyone who already knows how to
use the msiexec /x {xxx-xx-xx-xx}.... command finds they have a new problem
or if it's just me. I see many people with the similar problem, so I'll
propose my theory. Looking at Event Viewer, I get this log:
-------------------------------------------------------------------------------------
Installation Ready: The following updates are downloaded and ready for
installation. This computer is currently scheduled to install these updates
on Friday, March 17, 2006 at 3:00 AM:
- Definition Update 1.14.1325.6 for BETA Windows Defender (KB915597)
-------------------------------------------------------------------------------------

Followed by this log in Applications:
-------------------------------------------------------------------------------------
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11708
Date: 3/16/2006
Time: 10:45:00 PM
User:
Computer:
Description:
Product: Windows Defender Signatures -- Installation failed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 41 35 43 43 32 41 30 {A5CC2A0
0008: 39 2d 45 39 44 33 2d 34 9-E9D3-4
0010: 39 45 43 2d 39 32 33 44 9EC-923D
0018: 2d 30 33 38 37 34 42 42 -03874BB
0020: 44 34 43 32 43 7d D4C2C}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------------

If you can not update, there is a good reason... it says the update is meant
for March 17th, a FRIDAY... take a look at your calendar now. What day is it?
Currently, I see Thursday March 16th...If you're worrying that your computer
is going to crash, you can get over it now. The program must have been
released early without the key. Try again tomorrow, and if you still have
trouble, then post something. They must be in the process of embedding the
key in the update. I am looking at update *.1325.6.

Good nite all!

Jordan

 

[Guest]

You're right. I set my date ahead to the 17th and the update installed fine.
However the Home screen still says I have not updated in 51 days. So maybe
another glitch.

 

[Guest]

Well, lately you will see this new statement in Windows Update will say it
was successful, but if you look at your Event Viewer, it will tell you the
truth. If it is a success, your signature version should say Signature
Version: 1.14.1325.6
I don't know if they are also updating the engine, though...I thought they
were going to fix the problem with the automatic update. If so, that should
be changing as well. I was working on my computer and had to reinstall their
installer and do the agreement thing, so I found out one reason why it wasn't
installing for me. I had separate problem with Internet Explorer, Windows One
Care, and another program. Once I rolled back, I lost my data of being
registered for automatic updates. You must visit that Windows Update place if
you make big changes to your system, especially roll backs. I'll post again
and say if it completes for me in a moment.

 

[Guest]

Yup, just as I suspected... it still doesn't go through yet. You'll see a
success on the outside with the popup, but look at the '"About" menu in the
program as well as your event viewer in Administrative tools, you'll still
see failure and the old values of the version. The msiexec doesn't work yet,
so give it some time until it is valid. They might have set up a validity
check that it won't register until 3AM on... why its available now I
question. What country is the time considered for? Is it automatically
adjusted for our time zones, or is it the time that Microsoft will release
the update... hmmmm, makes you think...Think I'll go to sleep. Good nite, and
good luck everyone!

P.S. Attention Microsoft! This update is not valid yet... why is it
available to us now?

 

[Guest]

Interesting observation, however this morning at 0700 17/03/06 CET time zone,
WD failed to update exactly as it has every time for the last few weeks ! The
event viewer showed a number of failures to install code error 1603, And so
had to install using a method that works on most occasions ! at least on my
machines !

 

[Guest]

Jordan,
Having the same problem. It is the 17th still will not update?

Thanks
JoJo

 

[Guest]

I'm having a bit of trouble with my computer for other reasons. I'm not sure
why, but I even try the one line command in Start-> Run

Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

Ok->Yes,

But I get an error it can't find the last update. This might be a personal
problem though. But if you haven't tried the way above, that's worked many
times in the past. If anyone else gets this error: "The patch could not be
opened. Verify that the patch exists and that you can access it, or contact
the application vendor to verify that this is a valid Windows Installer patch
package."

First update I have seen this... but I might have lost the code while doing
some work on repairing my other programs. If someone else sees this when they
run that msiexec uninstall patch command, then it might be a different
problem. I'll get back to you all later. I'll try looking for it.

J-Monkey

 

[Guest]

I am also unable to run the "patch fix". In the past, it has fixed the issue
and performed the update. Today, I started getting the error about unable to
open the patch. However, on another pc it worked. I have two pcs. WD never
runs the same. Sometimes it shows up in the system tray on one or the other
(seems to bounce around). If my opinion means anything, bring back the old,
reliable, stable, always worked anti-spyware version.

 

[Guest]

The update seems to be working alright for me. I initially had trouble with
it, like most everyone else did. Then I tried that fix you mentioned Jordan,
and things are working fine now (finally!).
Also: You may need to press the Check for Updates button a couple times, and
wait for WD to do its update cycle thing, before the update will "stick."
Personally, I think MS should have just improved on the Microsoft
AntiSpyware, instead of rewriting it.

-H.

 

[Guest]

Sorry for the late reply. Yes, I can agree to an extent with thiis,
Antispyware actually did a very nice job. It seems they are going about this
program a bit differently. And now processes are available to observe. I see
one alternative program out there I believe MS should look at that does a
nice job. It is a combo of this and Windows OneCare... all compiled into one
environment. However, it can be troublesome if you don't know windows inside
and out. It doesn't tell errors straight out, and if you go to look at what
it did later, a beginner would not understand it. I do not mention names of
products, but it is a very good product when used correctly. I hope Microsoft
can take a look at iolo and build their own version that is safe to use and
bring out what this company left out, bring forth a safe yet effective
program.

 

[Guest]

By the way forgot if I mentioned...I have a problem with my windows
libraries. That's why I can't access it. Something between Internet Explorer
and some system registeries of windows...