(cross-post added to Vista Perf & Maint)
"Keith" <Keith@discussions.microsoft.com> wrote in message
> yes, that is the right KB article. :-) And, yes I did everything in that
> article, including step 6, except this line because of this response:
> C:\Users\Keith>proxycfg -d
> 'proxycfg' is not recognized as an internal or external command, operable
> program or batch file.
So, does your OS have that command installed anywhere?
Unfortunately the DLL Help Database hasn't been kept up to date
to know what modules Vista users get.
FWIW in the case of XP it looks as if proxycfg was originally distributed
only in XP Pro and then later distributed in both XPsp1 and XPsp2.
I can't find any information about proxycfg regarding Vista.
There are hits in the KB when both terms are used in a search
but they seem bogus (e.g. no instance of Vista found in the text;
also the same search in TechNet (offline) does come up empty.)
proxycfg is essentially just a way of examining and setting some
specific registry values, so provided Vista maintains the same values
you could probably get the same thing done using RegEdit.
Another way to emulate at least some of its function more procedurally
could be to use bitsadmin /util . I think at least some Vista users get
that tool by default.
> Thank you! :-)
> "MowGreen [MVP]" wrote:
>> You're referring to this KB, correct ? :
>> You may receive an "Error 0x80072EE2," "Error 0x80072EE7," "Error
>> 0x80072EFD," "Error 0x80072F76," or "Error 0x80072F78" error message
>> when you try to use the Windows Update Web site or the Microsoft Update
>> Web site
>> You posted " I am not using a proxy. "
>> Did you try Step 6: Remove the proxy server entry from the WinHTTP
>> proxy configuration