0x80240022 redux

[Guest]

Maybe I'm on the wrong forum....is this not the place to seek input on issues
surrounding Windows Defender and Spyware signatures (and their updates)? I do
recognize that this is beta software, and that it's "consumer" software, but
I know I'm not alone in being a SysAdmin running WSUS on my Active Directory
domain. Is anyone else out there successfully using this paradigm with
Windows Defender? Anyone else getting the diskette error with WSUS as the
Automatic Updates source?

I'm feeling a little pressure, here, and will need to bail on the Microsoft
product in a day or two if I can't figure this out....help? Please see the
bottom post for details on my environment.

Thanks!

Ben

<previous posts rom 2006-06-07 and 2006-06-08>
Two days later; condition persists. Any thoughts from the professional
community on this one. Anyone? Bueller?

Thanks. -Ben

 

[Steve Dodson [MSFT]]

Ben,

Can you verify you are downloading WD updates to your WSUS server? Also, can
you verify the clients are running the latest version (1.1.1347.0) from
www.microsoft.com/antispyware? If they are not at 1347, you should download
that build as well. If you are looking at corporate versions
http://www.microsoft.com/clientprotection may be a better fit for
manageability.
--
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.

 

[Guest]

Hello Benjobobby,

Have a look at this article.It may be relevant to your problem.
Subject: 0x80240022 update fails - how I fixed it
6/7/2006 9:56 AM PST
By: andreww
In: microsoft.private.security.spyware.general

I wºuld recommend you use the Search For: box, and enter the error number to
get the lates news or advance in eªch NG.

Good luck

For the benefit of the community reading this post, please rate the pºst.

I hope this post is helpful.

Let us know how it works ºut.

Еиçеl
--

 

[Guest]

Hi, Steve. First of all, thank you very much for your response - anything
taking me closer to a solution is appreciated!

Yes, WD updates (and all other pertinent ones) are definitely downloading to
my WSUS server. The non-WD updates are getting applied properly as well. We
are at the latest version of WD (.1347). I verified that my WSUS server had a
"check-in" form my client (all of them, in fact) quite recently, so I'm
pretty sure the WSUS mechanism is working. I just verified that the most
recent WD updates (and ONLY the most recent) are approved for installation
there, too.

I reviewed the materials on the MS corporate malware products. They feel
like a bit too much for our small organization. I don't need that much direct
oversight - just need to know that the systems picked up the definitions. In
addition, anything I can save from my budget is welcome. In addition, it
doesn't look like it's available quite yet.

A final outstanding question: do you know of successful implementations in a
scenario like ours?

Thanks!

Ben

Ben,

Can you verify you are downloading WD updates to your WSUS server? Also, can
you verify the clients are running the latest version (1.1.1347.0) from
www.microsoft.com/antispyware? If they are not at 1347, you should download
that build as well. If you are looking at corporate versions
http://www.microsoft.com/clientprotection may be a better fit for
manageability.
--
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.

Maybe I'm on the wrong forum....is this not the place to seek input on
issues
surrounding Windows Defender and Spyware signatures (and their updates)? I
do
recognize that this is beta software, and that it's "consumer" software,
but
I know I'm not alone in being a SysAdmin running WSUS on my Active
Directory
domain. Is anyone else out there successfully using this paradigm with
Windows Defender? Anyone else getting the diskette error with WSUS as the
Automatic Updates source?

I'm feeling a little pressure, here, and will need to bail on the
Microsoft
product in a day or two if I can't figure this out....help? Please see the
bottom post for details on my environment.

Thanks!

Ben

<previous posts rom 2006-06-07 and 2006-06-08>
Two days later; condition persists. Any thoughts from the professional
community on this one. Anyone? Bueller?

Thanks. -Ben

 

[Guest]

Thanks, Еиçеl,

Unfortunately, none of the solutions in that thread worked. I'm able to
update manually, so I'm pretty sure Bill's commentary doesn't match the
situation. Larry's post about removing and recreating the
"SoftwareDistribution" folder tree was unsuccessful. I searched the forums,
and will do so again.

Hopefully folks have some more suggestions! Thanks. -Ben

 

[Bill Sanderson MVP]

There are certainly others using WSUS to distribute Defender signatures--in
various size organizations. You can find posts by such folks in both the
public WSUS support forums, and here--in both Installation, Networking, and
here, I suspect. I have a post in .networking that gives what I believe to
be complete instructions for how to configure things at the WSUS server
end--they are from a WSUS MVP, as I recall.

--

Hi, Steve. First of all, thank you very much for your response - anything
taking me closer to a solution is appreciated!

Yes, WD updates (and all other pertinent ones) are definitely downloading
to
my WSUS server. The non-WD updates are getting applied properly as well.
We
are at the latest version of WD (.1347). I verified that my WSUS server
had a
"check-in" form my client (all of them, in fact) quite recently, so I'm
pretty sure the WSUS mechanism is working. I just verified that the most
recent WD updates (and ONLY the most recent) are approved for installation
there, too.

I reviewed the materials on the MS corporate malware products. They feel
like a bit too much for our small organization. I don't need that much
direct
oversight - just need to know that the systems picked up the definitions.
In
addition, anything I can save from my budget is welcome. In addition, it
doesn't look like it's available quite yet.

A final outstanding question: do you know of successful implementations in
a
scenario like ours?

Thanks!

Ben

Ben,

Can you verify you are downloading WD updates to your WSUS server? Also,
can
you verify the clients are running the latest version (1.1.1347.0) from
www.microsoft.com/antispyware? If they are not at 1347, you should
download
that build as well. If you are looking at corporate versions
http://www.microsoft.com/clientprotection may be a better fit for
manageability.
--
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.

Maybe I'm on the wrong forum....is this not the place to seek input on
issues
surrounding Windows Defender and Spyware signatures (and their
updates)? I
do
recognize that this is beta software, and that it's "consumer"
software,
but
I know I'm not alone in being a SysAdmin running WSUS on my Active
Directory
domain. Is anyone else out there successfully using this paradigm with
Windows Defender? Anyone else getting the diskette error with WSUS as
the
Automatic Updates source?

I'm feeling a little pressure, here, and will need to bail on the
Microsoft
product in a day or two if I can't figure this out....help? Please see
the
bottom post for details on my environment.

Thanks!

Ben

<previous posts rom 2006-06-07 and 2006-06-08>
Two days later; condition persists. Any thoughts from the professional
community on this one. Anyone? Bueller?

Thanks. -Ben

:

I'm using these versions:
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1440.0
Definition Version: 1.14.1464.7

along with WSUS as my Auto-updates source and continue to get the
"diskette"
error. Per Bill Sanderson's comments in a post recently, I've ensured
that my
WSUS is configured properly. Only the most recent (6/6) definition
update
is
approved for installation; the others have been declined. My clients
pick
up
all the other WSUS updates just fine. Oh, and I don't have 550 systems
to
roll out

(only about 30 to test)

When I go to update.microsoft.com and pull the definition updates
manually,
it works fine.

Thoughts? Thanks.

Ben

 

[Bill Sanderson MVP]

Let's see if I can recap what's going on --having read more since I last
responded.

You've got a functioning WSUS server, and clients receiving other updates
via WSUS without problem. Your clients are on the latest Windows Defender
code.

A typical client can also update manually via update.microsoft.com without
problems.

However, when they try to update Windows Defender via WSUS, they get the
subject error.

I tend to suspect the configuration at the WSUS server, but perhaps that is
just because I've never worked with that and thus don't have a clear picture
of it. And I know you've looked over my message in .networking that talks
about this configuration.

Can you post a segment of %windir%\windowsupdate.log that shows an attempt
to update defender via WSUS?

It's possible that you might do better in the WSUS support forum/newsgroup
at:

http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services

--

Hi, Steve. First of all, thank you very much for your response - anything
taking me closer to a solution is appreciated!

Yes, WD updates (and all other pertinent ones) are definitely downloading
to
my WSUS server. The non-WD updates are getting applied properly as well.
We
are at the latest version of WD (.1347). I verified that my WSUS server
had a
"check-in" form my client (all of them, in fact) quite recently, so I'm
pretty sure the WSUS mechanism is working. I just verified that the most
recent WD updates (and ONLY the most recent) are approved for installation
there, too.

I reviewed the materials on the MS corporate malware products. They feel
like a bit too much for our small organization. I don't need that much
direct
oversight - just need to know that the systems picked up the definitions.
In
addition, anything I can save from my budget is welcome. In addition, it
doesn't look like it's available quite yet.

A final outstanding question: do you know of successful implementations in
a
scenario like ours?

Thanks!

Ben

Ben,

Can you verify you are downloading WD updates to your WSUS server? Also,
can
you verify the clients are running the latest version (1.1.1347.0) from
www.microsoft.com/antispyware? If they are not at 1347, you should
download
that build as well. If you are looking at corporate versions
http://www.microsoft.com/clientprotection may be a better fit for
manageability.
--
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.

Maybe I'm on the wrong forum....is this not the place to seek input on
issues
surrounding Windows Defender and Spyware signatures (and their
updates)? I
do
recognize that this is beta software, and that it's "consumer"
software,
but
I know I'm not alone in being a SysAdmin running WSUS on my Active
Directory
domain. Is anyone else out there successfully using this paradigm with
Windows Defender? Anyone else getting the diskette error with WSUS as
the
Automatic Updates source?

I'm feeling a little pressure, here, and will need to bail on the
Microsoft
product in a day or two if I can't figure this out....help? Please see
the
bottom post for details on my environment.

Thanks!

Ben

<previous posts rom 2006-06-07 and 2006-06-08>
Two days later; condition persists. Any thoughts from the professional
community on this one. Anyone? Bueller?

Thanks. -Ben

:

I'm using these versions:
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1440.0
Definition Version: 1.14.1464.7

along with WSUS as my Auto-updates source and continue to get the
"diskette"
error. Per Bill Sanderson's comments in a post recently, I've ensured
that my
WSUS is configured properly. Only the most recent (6/6) definition
update
is
approved for installation; the others have been declined. My clients
pick
up
all the other WSUS updates just fine. Oh, and I don't have 550 systems
to
roll out

(only about 30 to test)

When I go to update.microsoft.com and pull the definition updates
manually,
it works fine.

Thoughts? Thanks.

Ben

 

[Guest]

Your assessment appears to be correct - a problem with the WSUS server. I'm
getting download errors in my WindowsUpdate.log file (sorry for the inline
paste - couldn't figure out how to attach a log file snippet). I'm seeking
help in the WSUS forums. Thanks for your suggestion.

-Ben

Log file snippet:

2006-06-13 11:57:41 584 17ac DnldMgr WARNING: BITS job
{526C17C1-C749-45C5-B305-B9EDBA887D71} failed, updateId =
{6CD2C177-3844-489F-8BC4-47CF4593C4A5}.101, hr = 0x80190194, BG_ERROR_CONTEXT
= 5
2006-06-13 11:57:41 584 17ac DnldMgr Progress failure bytes total =
513264, bytes transferred = 0
2006-06-13 11:57:41 584 17ac DnldMgr Failed job file: URL =
http://SERVERNAME.DOMAIN.com/Content/C4/EF8BB4AD1F8D8284D8630A0AA21E6C5766DC2AC4.exe,
local path =
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\dbc4c01e82d8c522e7b0673f7889d624\WindowsXP-KB904942-v2-x86-ENU.exe
2006-06-13 11:57:41 584 17ac DnldMgr Error 0x80244019 occurred while
downloading update; notifying dependent calls.
2006-06-13 11:57:41 5148 1424 DtaStor Update service properties: service
registered with AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2006-06-13 11:57:41 5148 1424 DtaStor WARNING: Update Service: Failed to
update backup store
2006-06-13 11:57:41 584 a20 AU >>## RESUMED ## AU: Download update
[UpdateId = {9D493962-0BB7-4541-AD81-F96263B4B201}]
2006-06-13 11:57:41 584 a20 AU # WARNING: Download failed, error =
0x80244019

Let's see if I can recap what's going on --having read more since I last
responded.

You've got a functioning WSUS server, and clients receiving other updates
via WSUS without problem. Your clients are on the latest Windows Defender
code.

A typical client can also update manually via update.microsoft.com without
problems.

However, when they try to update Windows Defender via WSUS, they get the
subject error.

I tend to suspect the configuration at the WSUS server, but perhaps that is
just because I've never worked with that and thus don't have a clear picture
of it. And I know you've looked over my message in .networking that talks
about this configuration.

Can you post a segment of %windir%\windowsupdate.log that shows an attempt
to update defender via WSUS?

It's possible that you might do better in the WSUS support forum/newsgroup
at:

http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services

--

Hi, Steve. First of all, thank you very much for your response - anything
taking me closer to a solution is appreciated!

Yes, WD updates (and all other pertinent ones) are definitely downloading
to
my WSUS server. The non-WD updates are getting applied properly as well.
We
are at the latest version of WD (.1347). I verified that my WSUS server
had a
"check-in" form my client (all of them, in fact) quite recently, so I'm
pretty sure the WSUS mechanism is working. I just verified that the most
recent WD updates (and ONLY the most recent) are approved for installation
there, too.

I reviewed the materials on the MS corporate malware products. They feel
like a bit too much for our small organization. I don't need that much
direct
oversight - just need to know that the systems picked up the definitions.
In
addition, anything I can save from my budget is welcome. In addition, it
doesn't look like it's available quite yet.

A final outstanding question: do you know of successful implementations in
a
scenario like ours?

Thanks!

Ben

Ben,

Can you verify you are downloading WD updates to your WSUS server? Also,
can
you verify the clients are running the latest version (1.1.1347.0) from
www.microsoft.com/antispyware? If they are not at 1347, you should
download
that build as well. If you are looking at corporate versions
http://www.microsoft.com/clientprotection may be a better fit for
manageability.
--
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.


Maybe I'm on the wrong forum....is this not the place to seek input on
issues
surrounding Windows Defender and Spyware signatures (and their
updates)? I
do
recognize that this is beta software, and that it's "consumer"
software,
but
I know I'm not alone in being a SysAdmin running WSUS on my Active
Directory
domain. Is anyone else out there successfully using this paradigm with
Windows Defender? Anyone else getting the diskette error with WSUS as
the
Automatic Updates source?

I'm feeling a little pressure, here, and will need to bail on the
Microsoft
product in a day or two if I can't figure this out....help? Please see
the
bottom post for details on my environment.

Thanks!

Ben

<previous posts rom 2006-06-07 and 2006-06-08>
Two days later; condition persists. Any thoughts from the professional
community on this one. Anyone? Bueller?

Thanks. -Ben

:

I'm using these versions:
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1440.0
Definition Version: 1.14.1464.7

along with WSUS as my Auto-updates source and continue to get the
"diskette"
error. Per Bill Sanderson's comments in a post recently, I've ensured
that my
WSUS is configured properly. Only the most recent (6/6) definition
update
is
approved for installation; the others have been declined. My clients
pick
up
all the other WSUS updates just fine. Oh, and I don't have 550 systems
to
roll out

(only about 30 to test)

When I go to update.microsoft.com and pull the definition updates
manually,
it works fine.

Thoughts? Thanks.

Ben

 

[Bill Sanderson MVP]

The inline inclusion is fine--that's all that is possible with HTML view--if
you come in via NNTP you can do file attachments, but only other NNTP users
can do anything with them!

I'll watch for your post in the WSUS forum. I can see that there seems to
be an update stuck in some way, but it isn't a Defender related one, so I'm
not sure whether/how resolution of that error will relate to the Defender
definition issue.

--

Your assessment appears to be correct - a problem with the WSUS server.
I'm
getting download errors in my WindowsUpdate.log file (sorry for the inline
paste - couldn't figure out how to attach a log file snippet). I'm seeking
help in the WSUS forums. Thanks for your suggestion.

-Ben

Log file snippet:

2006-06-13 11:57:41 584 17ac DnldMgr WARNING: BITS job
{526C17C1-C749-45C5-B305-B9EDBA887D71} failed, updateId =
{6CD2C177-3844-489F-8BC4-47CF4593C4A5}.101, hr = 0x80190194,
BG_ERROR_CONTEXT
= 5
2006-06-13 11:57:41 584 17ac DnldMgr Progress failure bytes total =
513264, bytes transferred = 0
2006-06-13 11:57:41 584 17ac DnldMgr Failed job file: URL =
http://SERVERNAME.DOMAIN.com/Content/C4/EF8BB4AD1F8D8284D8630A0AA21E6C5766DC2AC4.exe,
local path =
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\dbc4c01e82d8c522e7b0673f7889d624\WindowsXP-KB904942-v2-x86-ENU.exe
2006-06-13 11:57:41 584 17ac DnldMgr Error 0x80244019 occurred while
downloading update; notifying dependent calls.
2006-06-13 11:57:41 5148 1424 DtaStor Update service properties: service
registered with AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2006-06-13 11:57:41 5148 1424 DtaStor WARNING: Update Service: Failed to
update backup store
2006-06-13 11:57:41 584 a20 AU >>## RESUMED ## AU: Download update
[UpdateId = {9D493962-0BB7-4541-AD81-F96263B4B201}]
2006-06-13 11:57:41 584 a20 AU # WARNING: Download failed, error =
0x80244019

Let's see if I can recap what's going on --having read more since I last
responded.

You've got a functioning WSUS server, and clients receiving other updates
via WSUS without problem. Your clients are on the latest Windows
Defender
code.

A typical client can also update manually via update.microsoft.com
without
problems.

However, when they try to update Windows Defender via WSUS, they get the
subject error.

I tend to suspect the configuration at the WSUS server, but perhaps that
is
just because I've never worked with that and thus don't have a clear
picture
of it. And I know you've looked over my message in .networking that
talks
about this configuration.

Can you post a segment of %windir%\windowsupdate.log that shows an
attempt
to update defender via WSUS?

It's possible that you might do better in the WSUS support
forum/newsgroup
at:

http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services

--

Hi, Steve. First of all, thank you very much for your response -
anything
taking me closer to a solution is appreciated!

Yes, WD updates (and all other pertinent ones) are definitely
downloading
to
my WSUS server. The non-WD updates are getting applied properly as
well.
We
are at the latest version of WD (.1347). I verified that my WSUS server
had a
"check-in" form my client (all of them, in fact) quite recently, so I'm
pretty sure the WSUS mechanism is working. I just verified that the
most
recent WD updates (and ONLY the most recent) are approved for
installation
there, too.

I reviewed the materials on the MS corporate malware products. They
feel
like a bit too much for our small organization. I don't need that much
direct
oversight - just need to know that the systems picked up the
definitions.
In
addition, anything I can save from my budget is welcome. In addition,
it
doesn't look like it's available quite yet.

A final outstanding question: do you know of successful implementations
in
a
scenario like ours?

Thanks!

Ben

:

Ben,

Can you verify you are downloading WD updates to your WSUS server?
Also,
can
you verify the clients are running the latest version (1.1.1347.0)
from
www.microsoft.com/antispyware? If they are not at 1347, you should
download
that build as well. If you are looking at corporate versions
http://www.microsoft.com/clientprotection may be a better fit for
manageability.
--
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.


Maybe I'm on the wrong forum....is this not the place to seek input
on
issues
surrounding Windows Defender and Spyware signatures (and their
updates)? I
do
recognize that this is beta software, and that it's "consumer"
software,
but
I know I'm not alone in being a SysAdmin running WSUS on my Active
Directory
domain. Is anyone else out there successfully using this paradigm
with
Windows Defender? Anyone else getting the diskette error with WSUS
as
the
Automatic Updates source?

I'm feeling a little pressure, here, and will need to bail on the
Microsoft
product in a day or two if I can't figure this out....help? Please
see
the
bottom post for details on my environment.

Thanks!

Ben

<previous posts rom 2006-06-07 and 2006-06-08>
Two days later; condition persists. Any thoughts from the
professional
community on this one. Anyone? Bueller?

Thanks. -Ben

:

I'm using these versions:
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1440.0
Definition Version: 1.14.1464.7

along with WSUS as my Auto-updates source and continue to get the
"diskette"
error. Per Bill Sanderson's comments in a post recently, I've
ensured
that my
WSUS is configured properly. Only the most recent (6/6) definition
update
is
approved for installation; the others have been declined. My
clients
pick
up
all the other WSUS updates just fine. Oh, and I don't have 550
systems
to
roll out

(only about 30 to test)

When I go to update.microsoft.com and pull the definition updates
manually,
it works fine.

Thoughts? Thanks.

Ben