WD Definitions 1.14.1402.2

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

Guest

New definitions out - but still same old update problem for me - have to
delete definitions then update. Getting to be "old" - seems they can't fix
this one.
 
Tried updating with Defender About (and did the waiting) and Microsoft
Updates but neither worked. Run KB915105 Resolution and Defender About again.
It updated without problem in the second Defender icon popup.
 
I got my definition updates via AutoUpdate; no problem, as usual.

I wonder what's the difference between the WD users that regularly
experience update problems, and those who don't. Is there something in
their environment (drivers, processes or services running or not
running, MS installer version, proxy server, firewall, ...) that cause
these endless problems?
 
Well I uninstalled and installed again - then updated, works fine 4 the
moment. But say, all that nuisance. Look at all the othe Anti-Spyware
programs-a lot way smoother to update.
Anyway - it's justa Beta.:)
 
Badly maintained coms?

Stu


Pat Willener said:
I got my definition updates via AutoUpdate; no problem, as usual.

I wonder what's the difference between the WD users that regularly
experience update problems, and those who don't. Is there something in
their environment (drivers, processes or services running or not
running, MS installer version, proxy server, firewall, ...) that cause
these endless problems?
Click to expand...
 
Then you must ask yourself the question. What % is it who DO update
successfully versus those who do not. Those who have problems on here
represent a very small % of the 25 + million who use this application. MS
surely can`t be expected to resolve (programmatically) every which way but
why? GOK they try.... which is one of the reasons they put it out for BETA ..
one minute you love the program, next you hate it depending on whether or not
it updates . Common! make a commitment or leave it alone.

Stu
 
Hey, Stu - I am participating in the Beta Program - not with an attitude - I
have TRIED to find what is different in my pc's without success. I don't
blame anyone - the program is free and is BETA. I just continue to try to
find out the answer for myself with the help of others in these forums. I
may be in the small percentage of users who have problems, but I believe this
helps MS figure out problems which may occur when they get it up and going in
realtime. I don't think your advice of "make a commitment or leave it
alone" is appropriate! You may not have had any problems, but you MAY in the
future, so bear with us who do for now.
 
hi John: As I am having similar problems to yours. Maybe you are willing to
help me doing some research. It is is the Registry, but no change will be
made since Defender doen't allo them. Can I look up the info and post it for
your comparison purpose? Please let me know
 
Efrain - what do you need to know? Tell me how to look it up and I will also
post it for comparison if that will help.
 
Efrain, please see thread above this one "Defender Version Question".
Answers by Donald Anadell and by Joew Faulhaber (MSFT) indicate registry
information explanations - registry is a little different from what Defender
shows on my pc's.
My Registry shows the exact same as Donald Anadell's.
 
Hi John:
Thanks. I read Donald Anadell post. My registry is also exactly as his. I
will have to wait for a future fix. No problem, in the mean time I'll use the
Resolution.
 
That was exactly the reason for my question; to find some hints what
could be causing this problem. But I think it will be difficult to
resolve this in this newsgroup, as there are so many different environments.

At the end it will have to be reproduced by the MS development team;
this is the only sure way to find the source of the problem and resolve it.
 
I installed WD yesterday on a quite terribly infected and really badly
maintained Windows system of a friend. No problem with the update.
 
Back
Top