Windows Defender beta Check For Updates FAILS!!

[Guest]

ok. like installed your product. knowing it's like a beta, one (and perhaps
more than one) would expect that it may be used for something. like, working.
today like, thinking that your previous version worked. i like remember it
was was from like giant co -- not so? today like too, when i aim and hit
the UPDATE button it displays error.
"the update fails with the error code 0x8024402c".
Can you please like ask the persone who coded this error message to like
explain to me how he intends to explain this and help one (and perhaps more
than one) to fix this.,,,,like yeah,


like, my updates are provided via SUS. Individual updating via, something
like, Windows Update is NOT permitted. What else will work? (I, like use
to use Beta 1 = AntiSpyware, and never had any issues......why this now.
WHY??) Unless you want me un-install and use your competitor's product.
Like many products are available. And like they work, yeah like man.

 

[Bill Sanderson]

I believe this is already answered--Windows Defender definitions aren't
available via SUS. Since you are in a corporate environment, and wouldn't
want to be running beta code on production equipment, you've now time to
plan what's needed to support the application when it is released.

 

[plun]

Hi

Well, with a corporate name as Siemens which stand for quality
I am also sure that Siemens IT dept can answer this and also
make it clear what applications Siemens uses for client protection.

I do not believe that Siemens corporate policies allows any users to
decide this on their own. (as I knows from Siemens, Germany)

regards
plun

 

[Guest]

so basically you removed the feature with this new release......
we shall not use your product in future.....

 

[Guest]

Hi,

Well, with a corporate name as Plun which stand for quality
I am also sure that Plun IT dept can answer this and also make it clear what
applications Siemens uses for client protection.

I do not believe that Plun corporate policies allows any users to decide
this on their own. (as I knows from Plun, Ukraine)

regards
IBM

 

[Bill Sanderson]

The ability to distribute the definitions via SUS was not a part of
Microsoft Antispyware. Nothing was removed. Windows Defender definitions
are available via WSUS, and via Windows Update.

I'm sure that you are aware of this information:
-------
Microsoft will continue to support Software Update Services (SUS) 1.0 until
December 6, 2006. Microsoft will no longer support SUS 1.0 after this date.
SUS 1.0 will no longer synchronize or provide new updates after December 6,
2006. Additionally, as of August 24, 2005, you can no longer download SUS
from the Microsoft Web site. We recommend that you upgrade to Windows Server
Update Services (WSUS) before December 6, 2006.

 

[Bill Sanderson]

Nah--this is "absolut" nonsense. Plun is a Swedish corporation through and
through.

--

 

[plun]

Hi

Of course I am a corp never run a Beta inside a corporate network
is the first rule..........

Maybe within a small group for a start.

Block all users installs with GPOs Every user file within a
fileserver Block C:

Done

regards
plun

 

[Guest]

The ability to update the definitions from Microsoft Antispyware was removed.
Is this not what this forum discussion is all about!
so basically you removed the feature with this new release......
we shall not use your product in future.....

 

[Bill Sanderson]

This is one of many reasons why beta software is clearly labelled as
inappropriate for use in production.
During a beta, many things about a program may change. In this case, the
update method has changed between beta versions.

--

 

[Guest]

"many things about a program may change." Thanks. And clearly it has.
Please do not write "Nothing was removed." when its not factual correct.

 

[Bill Sanderson MVP]

symantics, mr. siemens.

microsoft Antispyware had a mechanism to update definitions.
Windows Defender also has a mechansim--in fact, two slightly different
mechanisms to update definitions.

The ability to update definitions was not removed.
Glad you're still with us.

--

 

[Guest]

Semantics, maybe not. the fact is that the feature / function / mechanism /
thing work differently than before. so different that it is not useable
anymore. whether it's a delta / beta product or not does not matter. my
point is that something changed which makes the product not useable anymore.
this may be a small thing, a large thing, or a changed mechanism. it does
not really matter.

the product is not useable anymore and thus I call this a REMOVAL of a
feature / function / mechanism / thing. clearly something must have been
"removed" or "changed" for it not to work anymore. and even the name of the
product changed. maybe some code were removed or converted. whatever the
case it is a different product, it works different and does not work for me
(or other SUS users.....and there are more than a few). So please do not
make statements like yours below.

And its fine, believe me. I just don’t use your product anymore. And nor
will I ever in future. It’s no issue for you to have customers switch....its
no issue removing features either.....

Its not semantics, it is stating the facts (or perhaps explaining the facts!)

And its fine, believe me. I just don’t use the product anymore. And nor
will I ever in future. It’s no issue loosing customers....its no issue
removing features.....

 

[Bill Sanderson MVP]

I'm sure there are many SUS users. I hope that every organization using
that product has a migration plan well under way by this time.

I agree with you that beta2 is essentially a different product than beta1.
It is intended to serve precisely the same need, and do that better than
beta1 did, but it is different code, with different strengths, weaknesses,
and underlying mechanisms. Beta testing can be a rocky road--sorry that
this one lost you.
--

 

[Guest]

agreed. Please do not write "Nothing was removed." when its not factual
correct.

ok?

 

[Bill Sanderson MVP]

I guess I can agree that the ability to update in your environment was
removed. It isn't clear to me that this is not exactly what the corporate
policy makers at Siemens prefer, however.
--