More Windows defender errors and WSUS

Is there any update more dificult to get going then this one? Judging by
the posts I see maybe not.

Anyway a new twist on what I have been seeing.

At the client level all clients are updating off the WSUS server properly
and have been for a couple months. We installed WIndows defender beta 2
build 1.1.1347 on each PC. When Defender attempts to get it's updates we get
an error on the PC saying:

" Unable to complete update: 0x80240022. The wrong diskette is in the drive
Insert %2 (volume serial number %3) into drive %1.

At the server level these def updates are set to download, there have been
downloaded , they have been manual approved for the PC's. The PC's do detect
that they need to install this updated and the progress is listed as failed.
At the server it's saying the client was unable to download the file. BUT
the WSUS server itself has downloaded the file.

In my case I have at least 7 separte WSUS servers set up at different
clients that are all running perfectly fine. WE have windows defender
installed and definitions being updated just fine at 4 sites so it is not
like I am a novice at this.

I have compared the working sites with this non-working one and can find
absolutely no difference.

At this point I have been working on this for 2 days an am about to loose
my mind. I have taken clean clients and installed defender before joining
them to WSUS and the opposite, joining them to WSUS and then installing
Defender. Doesn't make a difference. Once I need to get the definitions
updated Defender gives this error on ALL clients at this site.

I have read many threads on other WSUS \defender problems but they all
center arround sever config issues relating to setting up the proper class
functions and approving updates and such. All that is set on this server and
working.

Any IDEAS???

Hi,

Post the latest detection from %Windir%\WindowsUpdate.log.

Happy Patching,
Mohammed Athif Khaleel
http://msmvps.com/athif

Seekyouwillfind wrote:
> Is there any update more dificult to get going then this one? Judging by
> the posts I see maybe not.
>
> Anyway a new twist on what I have been seeing.
>
> At the client level all clients are updating off the WSUS server properly
> and have been for a couple months. We installed WIndows defender beta 2
> build 1.1.1347 on each PC. When Defender attempts to get it's updates we get
> an error on the PC saying:
>
> " Unable to complete update: 0x80240022. The wrong diskette is in the drive
> Insert %2 (volume serial number %3) into drive %1.
>
> At the server level these def updates are set to download, there have been
> downloaded , they have been manual approved for the PC's. The PC's do detect
> that they need to install this updated and the progress is listed as failed.
> At the server it's saying the client was unable to download the file. BUT
> the WSUS server itself has downloaded the file.
>
> In my case I have at least 7 separte WSUS servers set up at different
> clients that are all running perfectly fine. WE have windows defender
> installed and definitions being updated just fine at 4 sites so it is not
> like I am a novice at this.
>
> I have compared the working sites with this non-working one and can find
> absolutely no difference.
>
> At this point I have been working on this for 2 days an am about to loose
> my mind. I have taken clean clients and installed defender before joining
> them to WSUS and the opposite, joining them to WSUS and then installing
> Defender. Doesn't make a difference. Once I need to get the definitions
> updated Defender gives this error on ALL clients at this site.
>
> I have read many threads on other WSUS \defender problems but they all
> center arround sever config issues relating to setting up the proper class
> functions and approving updates and such. All that is set on this server and
> working.
>
> Any IDEAS???

"Seekyouwillfind" <seekyouwillfind@news.postalias> wrote in message
news:uOCs2TrmGHA.492@TK2MSFTNGP05.phx.gbl...


>2006-06-27 14:12:29 1096 d4c DnldMgr Progress failure bytes total =
>2862920, bytes transferred = 0

>2006-06-27 14:12:29 1096 d4c DnldMgr Failed job file: URL =
>http://mladmin/Content/55/D37281B019...90FBD14555.exe,
>local path =
>C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\195fe6efc0a5c2f97e2ae0c0bd9a4899\d37281b0194bfdefa5e35921617aee90fbd14555

>2006-06-27 14:12:29 1096 d4c DnldMgr Error 0x80244019 occurred while
>downloading update; notifying dependent calls.

The most common cause of this error sequence is that URLScan is installed on
the WSUS server, and the documented procedures (with respect to
reconfiguring URLScan) were not followed.

See p16 of the Getting Started on Windows 2000 Guide

--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
....

Sorry URLScan is NOT installed on this server and this server is running
win2003 SP1 not win 2000

I Still have not solved this problem. Can anyone who really understands the
log files look at what I posted and give me a clue as to why WSUS sees that
the client needs the WIn defender def updates but is unable to get the
client to pull just those. Again these same clients pull EVERY other WSUS
update without failure. The Win Defender Defs ARE downloaded and sitting on
the WSUS server.



"Lawrence Garvin (MVP)" <onsitech@news.postalias> wrote in message
news:Om%23%23CXJnGHA.4684@TK2MSFTNGP02.phx.gbl...
> "Seekyouwillfind" <seekyouwillfind@news.postalias> wrote in message
> news:uOCs2TrmGHA.492@TK2MSFTNGP05.phx.gbl...
>
>
>>2006-06-27 14:12:29 1096 d4c DnldMgr Progress failure bytes total =
>>2862920, bytes transferred = 0
>
>>2006-06-27 14:12:29 1096 d4c DnldMgr Failed job file: URL =
>>http://mladmin/Content/55/D37281B019...90FBD14555.exe,
>>local path =
>>C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\195fe6efc0a5c2f97e2ae0c0bd9a4899\d37281b0194bfdefa5e35921617aee90fbd14555
>
>>2006-06-27 14:12:29 1096 d4c DnldMgr Error 0x80244019 occurred while
>>downloading update; notifying dependent calls.
>
> The most common cause of this error sequence is that URLScan is installed
> on the WSUS server, and the documented procedures (with respect to
> reconfiguring URLScan) were not followed.
>
> See p16 of the Getting Started on Windows 2000 Guide
>
> --
> Lawrence Garvin, M.S., MVP-Software Distribution
> Everything you need for WSUS is at
> http://technet2.microsoft.com/window...s/default.mspx
> And, eveything else is at
> http://wsusinfo.onsitechsolutions.com
> ...
>
>

"Seekyouwillfind" <seekyouwillfind@news.postalias> wrote in message
news:uYLFKyRoGHA.2312@TK2MSFTNGP04.phx.gbl...

>> The most common cause of this error sequence is that URLScan is installed
>> on the WSUS server, and the documented procedures (with respect to
>> reconfiguring URLScan) were not followed.
>>
>> See p16 of the Getting Started on Windows 2000 Guide

> Sorry URLScan is NOT installed on this server and this server is running
> win2003 SP1 not win 2000

Fair enough. I merely pointed out the /most common/ cause.

Since the server is running Win2003SP1, did anybody, perhaps, engage the
Security Configuration Wizard on this server system and apply a security
configuration that might be interfering with HTTP transfer of EXE files?

> I Still have not solved this problem. Can anyone who really understands
> the log files look at what I posted and give me a clue as to why WSUS sees
> that the client needs the WIn defender def updates but is unable to get
> the client to pull just those. Again these same clients pull EVERY other
> WSUS update without failure. The Win Defender Defs ARE downloaded and
> sitting on the WSUS server.

>>>2006-06-27 14:12:29 1096 d4c DnldMgr Error 0x80244019 occurred while
>>>downloading update; notifying dependent calls.

The issue is, quite simply, that the client (WUA) cannot see the file it
wants to download. The 0x80244019 error code is an HTTP '404' error message.
The fix, no matter what the reason that caused the problem, is to repair
whatever is hiding that file. Perhaps the file is really not there. Have you
verified that the file is, in fact, physically present in the filesystem at
the specified directory? You've not suggested that you're getting errors on
other files, so I'm not inclined to point to misconfigured pathnames in
virtual directory configurations, but that is another cause of '404' errors
trying to download files.

Another cause that occurred occasionally in the early days of the release,
was when the WSUS server was moved between the port 80 and port 8530 server,
after clients had started registering. The client synchronized with the
server on one port, sent a command to BITS to retrieve the file from the web
server on that port, and then the web server disappeared, having been moved
to the other port, leaving the BITS client confused as to why it couldn't
find the file.

Which brings us to another question.
Have you tried to browse to the file using Internet Explorer and the URL
logged in the WindowsUpdate.log?
http://mladmin/Content/55/D37281B019...90FBD14555.exe

If not, can you browse to that URL from Internet Explorer on the console of
the WSUS server?

If not, rename the file to D37281B0194BFDEFA5E35921617AEE90FBD14555.txt
and try
http://mladmin/Content/55/D37281B019...90FBD14555.txt
from both the client system and the console of the WSUS server.

--
Lawrence Garvin, M.S., MVP-Software Distribution Everything you need for
WSUS is at
http://technet2.microsoft.com/window...s/default.mspx
And, eveything else is at
http://wsusinfo.onsitechsolutions.com
.....

[sidewinder58]

Just thought I'd add to this lot seeing as I ended up here:

Defender uses a webservice to obtain it's updates. I realized this when I looked in WindowsUpdate.log. I found the spot where it logged the 80244019 error code, and it so nicely puts beneath the http and soap error codes as well. Seeing as it was an http 404 error it had to be a bad url. Even though it's not windows update per se, it still keeps info about what defender is doing while updating.

I found in mine that it was looking to my group policy and getting the update server url and then appending '/ClientWebService/client.asmx'. This you most likely know is from WSUS and the like... having to override the location of windows update targets. Also, I have trouble remembering where those settings are so for your benefit, they are in 'Group Policy' (gpedit.msc), then browse 'Computer Config >> Admin Templates >> Windows Components >> Windows Update'.

Next (For good measure), I went to Command Prompt and ran gpupdate /force. Jst making sure that the url changes are applied.

Back to defender and voila, she works!!!