G
Guest
New definitions - again, I seem to have to go the "long" route to update -
there is still a problem with this on some pc's it seems.
there is still a problem with this on some pc's it seems.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Guest
I agree with U - SameOldStory.JohnBurns said:New definitions - again, I seem to have to go the "long" route to update -
there is still a problem with this on some pc's it seems.
Why is it, that only WD shows this particular awkwardness...
It is upsettin' in the meantime- when a large sum of folks yell the same
however this goes on unnoticed. I am gettin' sick and tzired of WD for my
part.
I was very patient but hey, this bug should have been taken care of a long
time ago.
I have no problem whatsoever when updatin' other products (Ewido, NOD,
Outpost, Spywareblaster just 2 mention some).
G
Guest
After updating automatically the last 4 times, I too , had to go the long
way round to get this latest update. Doesn't make sense at all.
way round to get this latest update. Doesn't make sense at all.
G
Guest
This time after the update failed again, I decided to uninstall/clean folders
and registry/reboot/reinstall. It then updated OK.
My reason for doing that is that I have discovered that if I use Windows
Installer cleanup utility to remove the WD definition updates (which has been
the only way for me to get WD to update), for some reason it messes up Office
updates: checking for Office updates gives error that it could not find the
msp files.
I had been having that problem every so often, and each time fixed it by
reinstalling Office, but that's a pain. So I decided to track down the cause
by checking for office updates after each change to my system. That way I
established that it happens each time I use Windows Installer cleanup (which
I had only been doing for WD updates). I can recover Office update
functionality by using system restore to a point before using windows
installer cleanup utility , but of course that then removes the WD update as
well.
So I'm not going to use windows cleanup utility again.
Sooner rather than later, if WD won't update normally I'll give up on it
altogether. Fed up to the backteeth with this.
and registry/reboot/reinstall. It then updated OK.
My reason for doing that is that I have discovered that if I use Windows
Installer cleanup utility to remove the WD definition updates (which has been
the only way for me to get WD to update), for some reason it messes up Office
updates: checking for Office updates gives error that it could not find the
msp files.
I had been having that problem every so often, and each time fixed it by
reinstalling Office, but that's a pain. So I decided to track down the cause
by checking for office updates after each change to my system. That way I
established that it happens each time I use Windows Installer cleanup (which
I had only been doing for WD updates). I can recover Office update
functionality by using system restore to a point before using windows
installer cleanup utility , but of course that then removes the WD update as
well.
So I'm not going to use windows cleanup utility again.
Sooner rather than later, if WD won't update normally I'll give up on it
altogether. Fed up to the backteeth with this.
G
Guest
Same problem here. Even though WD says it has successfully
updated the definitions, the main screen reports the previous definitions.
I Had to manually delete the previous version so as to update to
the new version. This issue has been around for some time. But, the
developers does not appear to do something about it.
Vista will include WD by default. Unfortunately, it will be released
in 2007. It does not appear as if the developers will do something
about the update problems until Vista is official.
updated the definitions, the main screen reports the previous definitions.
I Had to manually delete the previous version so as to update to
the new version. This issue has been around for some time. But, the
developers does not appear to do something about it.
Vista will include WD by default. Unfortunately, it will be released
in 2007. It does not appear as if the developers will do something
about the update problems until Vista is official.
G
Guest
Yep -- same old story!
Is now becoming REALLY irritating...
I find the one simple way to solve all the update probs, & the one wh works
every time, is the right-click/Uninstall on C:\Program Files\Windows
Defender\AS_Sigs.MSI
Then run the Update option in Defender itself. That has never yet failed.
dom
:
..
Is now becoming REALLY irritating...
I find the one simple way to solve all the update probs, & the one wh works
every time, is the right-click/Uninstall on C:\Program Files\Windows
Defender\AS_Sigs.MSI
Then run the Update option in Defender itself. That has never yet failed.
dom
:
..
B
Bill Sanderson MVP
The developers are working on the update problem right now.
--
--
S
Steve Dodson [MSFT]
As I look through the newsgroups, I notice a lot of these types of posts. I
do not have a lot of time to read every post in all the newsgroups ( I do
try though ). What will be helpful to us when posting a problem is to state
what the issue is in the title. When I read this title, I may assume you are
announcing the release of 1452 to the group. A better title would be "Update
1452 does not install successfully." This will catch my eye as well as
others in the newsgroup as we try and determine how many people are running
into certain issues.
--
-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.
do not have a lot of time to read every post in all the newsgroups ( I do
try though ). What will be helpful to us when posting a problem is to state
what the issue is in the title. When I read this title, I may assume you are
announcing the release of 1452 to the group. A better title would be "Update
1452 does not install successfully." This will catch my eye as well as
others in the newsgroup as we try and determine how many people are running
into certain issues.
--
-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.
S
Steve Dodson [MSFT]
Have you followed KB 918355? Does it help, is it lacking in areas?
--
-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.
--
-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.
S
Steve Dodson [MSFT]
Right, the MSI cleanup utility sometimes has some side effects and should be
used as a last resort.
--
-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.
used as a last resort.
--
-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.
S
Steve Dodson [MSFT]
Have you followed KB 918355? Does it help, is it lacking in areas?
--
-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.
--
-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.
S
Steve Dodson [MSFT]
Have you followed KB 918355? Does it help, is it lacking in areas?
--
-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.
--
-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.
G
Guest
Hello Steve,
Is any way, to write a KB, similar to this kb/555375, but make it fit to WD?
So we can refer the OP.
Is any way, to write a KB, similar to this kb/555375, but make it fit to WD?
So we can refer the OP.
Steve Dodson said:As I look through the newsgroups, I notice a lot of these types of posts. I
do not have a lot of time to read every post in all the newsgroups ( I do
try though ). What will be helpful to us when posting a problem is to state
what the issue is in the title. When I read this title, I may assume you are
announcing the release of 1452 to the group. A better title would be "Update
1452 does not install successfully." This will catch my eye as well as
others in the newsgroup as we try and determine how many people are running
into certain issues.
--
-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.
JohnBurns said:New definitions - again, I seem to have to go the "long" route to update -
there is still a problem with this on some pc's it seems.
B
Bill Sanderson MVP
I think that one's not bad. I don't like just posting articles like that as
a response, though--usually what I try to remember to do is to attempt
mind-reading and make some form of response to what I think the question
might be, and then add that kind of reference.
As an example, that's probably what I should have done with one of Pedro's
two queries yesterday--in one case he asked the question well, and got an
answer, in the other, his meaning wasn't crystal clear, and the only
response I came up with was a question about what he meant...
--
a response, though--usually what I try to remember to do is to attempt
mind-reading and make some form of response to what I think the question
might be, and then add that kind of reference.
As an example, that's probably what I should have done with one of Pedro's
two queries yesterday--in one case he asked the question well, and got an
answer, in the other, his meaning wasn't crystal clear, and the only
response I came up with was a question about what he meant...
--
Engel said:Hello Steve,
Is any way, to write a KB, similar to this kb/555375, but make it fit to
WD?
So we can refer the OP.
Steve Dodson said:As I look through the newsgroups, I notice a lot of these types of posts.
I
do not have a lot of time to read every post in all the newsgroups ( I do
try though ). What will be helpful to us when posting a problem is to
state
what the issue is in the title. When I read this title, I may assume you
are
announcing the release of 1452 to the group. A better title would be
"Update
1452 does not install successfully." This will catch my eye as well as
others in the newsgroup as we try and determine how many people are
running
into certain issues.
--
-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.
JohnBurns said:New definitions - again, I seem to have to go the "long" route to
update -
there is still a problem with this on some pc's it seems.