Failed:Error 0x8DDD0018

The symptoms are that manual updating works fine until it actually
tries to download the update at which point it fails with error
0x8DDD0018.

I've read the various articles on enabling BITS and the other two
services. I've also read and carried out the 7 solution document. I've
done all that and it makes no difference.

Auto-update is working just fine on that machine and has been for some
time. From looking at the update history for this machine the problem
seems to have started after I applied the IE6 security patch released
around the 12th of October.

Since then nearly every manual update has failed. Curiously the first
manual update that was attempted (a Windows Media security fix about a
week later) failed the first two times I tried it then succeeded on the
third attempt. Since then no manual update has succeeded.

Last night I enabled logging on my advert blocking software (and /yes/
I have tried disabling that) and found the last http request being made
by Explorer. I then manually entered this URL and found myself
downloading an installation wizard.

After clicking [Next] on the license agreement this proceeded to try
and download files..and immediately failed saying it couldn't connect
to the server (it didn't say what server). IIRC after clicking retry
additional text appeared suggesting I should retry a few more times
then contact my administrator.

My guess is that what I was seeing here was the underlying update
functionality and that my basic problem with Windows Update is that my
machine can't connect to the server that holds the files.

The machine in question is running XP+SP2. It is on a private network
accessing the Internet through a router. There is one other computer on
the same network and manual update works just fine on that. The only
difference in network configuration is that the second machine is a
mail server so has smtp ports forwarded to it.

So...can anyone shed any light on why this machine should be having a
problem? Better yet can you suggest a solution?

Hmmm. Some further information on this. "Windows Update.log" has the
following entries:

2005-01-26 18:12:29-0000 1072 144 WU client calls back to download call
{7D125A2F-ADB0-497E-BEBD-3A5C679AD586} with code Call progress and
error 0
2005-01-26 18:12:29-0000 1072 1e58 Download job for update
{36C34A9E-10A0-4DB9-BF11-A9DA73CCA680}, revision 100 failed with hr =
80190193.
2005-01-26 18:12:29-0000 1072 1e58 The failure occurred when trying to
download file from
http://www.download.windowsupdate.co...-19990518/cabp
ool/windowsxp-kb887797-x86-express-enu_cecc77521c5d84f78a1387877413af969
2915e1d.exe to
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\bfde49bce9a8e228b7bc78
59c574c3d7\WindowsXP-KB887797-x86-express-enu.exe.
2005-01-26 18:12:29-0000 1072 1e58 Error 80244018 occurred while
downloading update; notifying dependent calls.

According to MS Support this means the server is busy. This does tie in
with the one update succeeding after several retries but surely an MS
server won't remain busy for three months? The support site does also
suggest reinstalling the scripting engine but that hasn't helped.

Maureen Goldman wrote:

> When I had that error code, it was necessary to go into Control Panel
> \ Security Center to turn on automatic updates. After downloading the
> update, I turned it off again, and there has been no problem since
> getting the updates (that is, even though autoupdate remains off other
> than that one time).

Sadly that doesn't help. It was a bit odd though. I was expecting the
option would already be on (since it is patently already working) but
although it didn't say auto updates were off it allowed me to click the
button and changed show 'on'.

"Andrue Cope" wrote:

> The symptoms are that manual updating works fine until it actually
> tries to download the update at which point it fails with error
> 0x8DDD0018.
>
> I've read the various articles on enabling BITS and the other two
> services. I've also read and carried out the 7 solution document. I've
> done all that and it makes no difference.
>
> Auto-update is working just fine on that machine and has been for some
> time. From looking at the update history for this machine the problem
> seems to have started after I applied the IE6 security patch released
> around the 12th of October.
>
> Since then nearly every manual update has failed. Curiously the first
> manual update that was attempted (a Windows Media security fix about a
> week later) failed the first two times I tried it then succeeded on the
> third attempt. Since then no manual update has succeeded.
>
> Last night I enabled logging on my advert blocking software (and /yes/
> I have tried disabling that) and found the last http request being made
> by Explorer. I then manually entered this URL and found myself
> downloading an installation wizard.
>
> After clicking [Next] on the license agreement this proceeded to try
> and download files..and immediately failed saying it couldn't connect
> to the server (it didn't say what server). IIRC after clicking retry
> additional text appeared suggesting I should retry a few more times
> then contact my administrator.
>
> My guess is that what I was seeing here was the underlying update
> functionality and that my basic problem with Windows Update is that my
> machine can't connect to the server that holds the files.
>
> The machine in question is running XP+SP2. It is on a private network
> accessing the Internet through a router. There is one other computer on
> the same network and manual update works just fine on that. The only
> difference in network configuration is that the second machine is a
> mail server so has smtp ports forwarded to it.
>
> So...can anyone shed any light on why this machine should be having a
> problem? Better yet can you suggest a solution?
>

Sadly, I've had the same problem.

It all seems to relate to a particularly pernicious adware "virus" that
won't let go.

I cleared entries from directories, register and anywhere else I could think
of.

I ran Norton, Spyware Doctor, Spybot, Registry Mechanic and Hijack This with
some helpful results but none that cleared the problem.

I was able to get around the "Error 0x8DDD0018" by using the software
mentioned. But now I get a message suggesting downloading something (sorry I
don't have my notes here at the moment) to correct a problem that doesn't
exist.

I agree that the suggestion is typical MS response but since the "adware"
problem surfaced I decided to write their tech support where they are
typically shuffling the message between departments (since 1/12/05).

If I hear or can find anything I'll be sure to inform.

"Andrue Cope" wrote:

> The symptoms are that manual updating works fine until it actually
> tries to download the update at which point it fails with error
> 0x8DDD0018.
>
> I've read the various articles on enabling BITS and the other two
> services. I've also read and carried out the 7 solution document. I've
> done all that and it makes no difference.
>
> Auto-update is working just fine on that machine and has been for some
> time. From looking at the update history for this machine the problem
> seems to have started after I applied the IE6 security patch released
> around the 12th of October.
>
> Since then nearly every manual update has failed. Curiously the first
> manual update that was attempted (a Windows Media security fix about a
> week later) failed the first two times I tried it then succeeded on the
> third attempt. Since then no manual update has succeeded.
>
> Last night I enabled logging on my advert blocking software (and /yes/
> I have tried disabling that) and found the last http request being made
> by Explorer. I then manually entered this URL and found myself
> downloading an installation wizard.
>
> After clicking [Next] on the license agreement this proceeded to try
> and download files..and immediately failed saying it couldn't connect
> to the server (it didn't say what server). IIRC after clicking retry
> additional text appeared suggesting I should retry a few more times
> then contact my administrator.
>
> My guess is that what I was seeing here was the underlying update
> functionality and that my basic problem with Windows Update is that my
> machine can't connect to the server that holds the files.
>
> The machine in question is running XP+SP2. It is on a private network
> accessing the Internet through a router. There is one other computer on
> the same network and manual update works just fine on that. The only
> difference in network configuration is that the second machine is a
> mail server so has smtp ports forwarded to it.
>
> So...can anyone shed any light on why this machine should be having a
> problem? Better yet can you suggest a solution?
>

"gort" wrote:

> Well, that wsn't very helpful...

>Suffice to say that I have had similar problems and wiil address them again soon.

I just had the same error a few minutes ago. What I did was to run
services.msc and modified both Automatic Updates and Background Intelligent
Transfer Services to Automatic Startup Type and started those services. For
some reasons, if I leave those services in Manual state, even if they are
started, Windows Update still fails.

"Andrue Cope" wrote:

> Maureen Goldman wrote:
>
> > When I had that error code, it was necessary to go into Control Panel
> > \ Security Center to turn on automatic updates. After downloading the
> > update, I turned it off again, and there has been no problem since
> > getting the updates (that is, even though autoupdate remains off other
> > than that one time).
>
> Sadly that doesn't help. It was a bit odd though. I was expecting the
> option would already be on (since it is patently already working) but
> although it didn't say auto updates were off it allowed me to click the
> button and changed show 'on'.
>

Vin wrote:

> I just had the same error a few minutes ago. What I did was to run
> services.msc and modified both Automatic Updates and Background
> Intelligent Transfer Services to Automatic Startup Type and started
> those services. For some reasons, if I leave those services in
> Manual state, even if they are started, Windows Update still fails.

Interesting. I have tried setting those services to automatic several
times now during the investigation of this problem and each time when I
next look BITS has gone back to automatic. In any case automatic
updates works and that /musts/ be using BITS so BITS must be working.
At least I'd think so.

This is beginning to annoy me. Tonight I'm installing a packet sniffer
I use at work and I'm going to get to the bottom of this. As a
developer I will not allow myself to be thwarted by an application

I have found a workaround that may eventually point to a solution. I
created a new adminstrator account and the manual update went through
without a problem.

Presumably this suggests that there's a problem with my original user's
registry settings. Could anyone suggest where to start looking for this?

"Andrue Cope",

That error code you were hitting, "0x8DDD0018," translates to: "Error AU
Disabled." It is probably appropriate at this moment to tell you that there
is a difference between the Automatic Updates service name that you can find
on the Services page (services.msc) and the Automatic Updates object in the
Control Panel.

They are named identically, and are related--but there are important
differences. Automatic Updates requires the Automatic Updates service to be
running for the download and installation of updates. This is a service
that monitors the download and installation of Windows Updates in Windows
XP.

The object in the Control Panel schedules what you, as the user, wish to do
with the detection, download, and installation of updates. This is no less
important, as users have ultimate control over the timing and location of
the updates in this process.

I would recommend you go into the services and verify that Automatic Updates
and Background Intelligent Transfer Service are set to "Automatic" and are
"started", then try visiting the Windows Update website again.

Let us know how this goes!

Sincerely,

Pat Walters [MSFT]

"Andrue Cope" <> wrote in message
news:...
> Vin wrote:
>
> > I just had the same error a few minutes ago. What I did was to run
> > services.msc and modified both Automatic Updates and Background
> > Intelligent Transfer Services to Automatic Startup Type and started
> > those services. For some reasons, if I leave those services in
> > Manual state, even if they are started, Windows Update still fails.
>
> Interesting. I have tried setting those services to automatic several
> times now during the investigation of this problem and each time when I
> next look BITS has gone back to automatic. In any case automatic
> updates works and that /musts/ be using BITS so BITS must be working.
> At least I'd think so.
>
> This is beginning to annoy me. Tonight I'm installing a packet sniffer
> I use at work and I'm going to get to the bottom of this. As a
> developer I will not allow myself to be thwarted by an application