Windows-Update fails with 8024401b

Hi all,

I'm getting frustrated by Windows-Update on an XP SP2 (German) behind
proxies.

The Update-Page works properly up to the point where the downloads
should start.
The Popup-windows shows me the attempts to download the Software and
after each attempt it says "Fehlgeschlagen!" which means as much as
"Failed!".

I dug into this problem and found out that BITS is having trouble to
download.
It contacts the wrong proxy (one asking for authorization).

I searched really hard and set the proxies correctly whereever I found
a chance:
1. In Internet-Settings of both (my account and the administrator
account.
2. BITSADMIN /UTIL /SETIEPROXY (for all three "account"s there).
3. proxycfg

All these are now set to use the proxy "cachespc:8133" (which works in
the browser)
However when I do a

BITSADMIN /LIST /ALLUSERS /VERBOSE

while windows-update is trying to download, I see the following:
OVERRIDE PROXY LIST: cachestd:80;cachespc:8133

Naturally the download fails, because cachestd:80 requires
authentication (while cachespc:8133 wound not).

To verify that this is really the source of my problem, I defined
cachestd to point to 127.0.0.2 in etc/hosts. And the Update worked (but
I cannot leave it like that, because we need to use the real cachestd
as well).

To find out where this damn "override proxy list" comes from, I
searched for
the string "cachestd:80"
1. on the entire disk
2. through the entire registry

No luck. It just isn't there.

Can anyone tell me where the "OVERRIDE PROXY LIST" is set by the
Windows-Update machinery.

BITS itself seems to work correctly now (after I set the proxies with
/UTIL)
I can download files with BITSADMIN /TRANSFER.

Any ideas are welcome.

"Perlfan" <> wrote in message
news: oups.com
....
> 3. proxycfg

That just displays the setting and apparently sometimes
hides that it is really displaying the wrong thing.

Try setting what you want explicitly, e.g. using

proxycfg -d


> To find out where this damn "override proxy list" comes from, I
> searched for
> the string "cachestd:80"
> 1. on the entire disk
> 2. through the entire registry

What tools were you using to do that with?
If the string is stored as Unicode or in binary would they find it?

If the above workaround with proxycfg -d doesn't help
I would try monitoring registry accesses with RegMon
in hopes that it will give you some clues about the origin
of that string.

FWIW doing that now with

proxycfg -d

shows exactly the same key and values that the command
itself displays in the cmd window.

Now I'm not certain what others are seeing when they claim
that this step is needed. Perhaps it is picking up the IE proxy
information instead?

To see it and, if necessary, trace it: Run...

msinfo32 /category IEConnectivity

The RegMon filter I used to show the origin of most of the values
being displayed was: Include: proxy Exclude: ProxyStubClsid32


HTH

Robert Aldwinckle
---


> Hi all,
>
> I'm getting frustrated by Windows-Update on an XP SP2 (German) behind
> proxies.
>
> The Update-Page works properly up to the point where the downloads
> should start.
> The Popup-windows shows me the attempts to download the Software and
> after each attempt it says "Fehlgeschlagen!" which means as much as
> "Failed!".
>
> I dug into this problem and found out that BITS is having trouble to
> download.
> It contacts the wrong proxy (one asking for authorization).
>
> I searched really hard and set the proxies correctly whereever I found
> a chance:
> 1. In Internet-Settings of both (my account and the administrator
> account.
> 2. BITSADMIN /UTIL /SETIEPROXY (for all three "account"s there).
> 3. proxycfg
>
> All these are now set to use the proxy "cachespc:8133" (which works in
> the browser)
> However when I do a
>
> BITSADMIN /LIST /ALLUSERS /VERBOSE
>
> while windows-update is trying to download, I see the following:
> OVERRIDE PROXY LIST: cachestd:80;cachespc:8133
>
> Naturally the download fails, because cachestd:80 requires
> authentication (while cachespc:8133 wound not).
>
> To verify that this is really the source of my problem, I defined
> cachestd to point to 127.0.0.2 in etc/hosts. And the Update worked (but
> I cannot leave it like that, because we need to use the real cachestd
> as well).
>
> To find out where this damn "override proxy list" comes from, I
> searched for
> the string "cachestd:80"
> 1. on the entire disk
> 2. through the entire registry
>
> No luck. It just isn't there.
>
> Can anyone tell me where the "OVERRIDE PROXY LIST" is set by the
> Windows-Update machinery.
>
> BITS itself seems to work correctly now (after I set the proxies with
> /UTIL)
> I can download files with BITSADMIN /TRANSFER.
>
> Any ideas are welcome.
>

Thanks for your answer, Robert.

I'll try what you proposed on Monday (because the machine in question
is in my office).

I also thought about the proxy being stored in Unicide.

Since I've Cygwin on that machine (I'm a bit more familiar with Unix
than with Windows :-),
I searched with a find / grep combination that reveales Unicode
occurences.

But it didn't find it (except in a .REG REGEDIT V5 file that I made to
verify that my grep finds the Unicode).

I'll try the rest on monday and let you know.