appleoddity
Topic Starter
I've been beating my head against the wall over a Windows Update problem today.
Everytime I run windows update and scan for updates I get an error 0x80072EFD.
In the C:\Windows\WindowsUpdate.log I get this error leading to others: WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <168.94.74.68:8080> Bypass List used : <(null)>
TCP/IP settings in control panel and proxy settings in internet options were all correct. I could not figure out how Windows Update was deciding to use a proxy server for its updates. Searching the registry for this particular IP address found nothing.
Here's where it got interesting. I did a WHOIS on the IP address [removed]. Low and behold, registered to Best Buy Co. Performing a port scan on the computer reveals that it is some type of mail server most likely because SMTP and IMAP ports are open. However, port 8080 (as specified in the proxy settings) does not respond.
Searching the internet reveals other instances of this same failure with this exact IP address.
When running Dial-A-Fix previously to try and fix the error, Dial-A-Fix told me that WinHTTP settings was set to use a proxy server and that it would fix it for me. It DID NOT!
So, I began to look into what WinHTTP Proxy Settings were. To make a long story short, Microsoft provides Windows HTTP Services which is a programming interface that developers can use to access the internet without having to know all the dirty details. The windows HTTP client will use the "hidden" WinHTTP proxy settings thus causing any program that relies on the HTTP client to also use the proxy.
These settings are not found in Internet Options or any other place you might think to look. They can only be changed using the proxycfg.exe command. This particular setting is located in the registry at: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHTTPSettings. Issuing the proxycfg command at the command prompt should show the current proxy settings. In this particular instance, it showed that I was not using a proxy setting and that I was configured for direct access. Yet, the registry and error logs showed otherwise.
To remove the offending proxy server setting I went to a command prompt and issued the command: proxycfg -d
Upon verifying the settings in the registry, it was confirmed that the proxy settings were now removed.
It appears that at some point (probably during service), Best Buy inserted a special "hidden" proxy setting into the computer. From the results I found on the internet, it appears that this IP address has also been added into the "Internet Options" proxy settings for many, breaking their internet connection all together. When finished, they were probably supposed to have removed it, but something went wrong. The registry key was "corrupted," and then had to be manually repaired or the settings were just not removed. As a result of this bug in whatever it is that they are attempting there are posts on the internet about failed windows updates and other issues related to them.
One more reason to avoid the Geek Squad.
BTW, Windows updates work now! Anybody want to take a guess at how many updates this customer needed AFTER I installed Service Pack 3 for XP?
Everytime I run windows update and scan for updates I get an error 0x80072EFD.
In the C:\Windows\WindowsUpdate.log I get this error leading to others: WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <168.94.74.68:8080> Bypass List used : <(null)>
TCP/IP settings in control panel and proxy settings in internet options were all correct. I could not figure out how Windows Update was deciding to use a proxy server for its updates. Searching the registry for this particular IP address found nothing.
Here's where it got interesting. I did a WHOIS on the IP address [removed]. Low and behold, registered to Best Buy Co. Performing a port scan on the computer reveals that it is some type of mail server most likely because SMTP and IMAP ports are open. However, port 8080 (as specified in the proxy settings) does not respond.
Searching the internet reveals other instances of this same failure with this exact IP address.
When running Dial-A-Fix previously to try and fix the error, Dial-A-Fix told me that WinHTTP settings was set to use a proxy server and that it would fix it for me. It DID NOT!
So, I began to look into what WinHTTP Proxy Settings were. To make a long story short, Microsoft provides Windows HTTP Services which is a programming interface that developers can use to access the internet without having to know all the dirty details. The windows HTTP client will use the "hidden" WinHTTP proxy settings thus causing any program that relies on the HTTP client to also use the proxy.
These settings are not found in Internet Options or any other place you might think to look. They can only be changed using the proxycfg.exe command. This particular setting is located in the registry at: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHTTPSettings. Issuing the proxycfg command at the command prompt should show the current proxy settings. In this particular instance, it showed that I was not using a proxy setting and that I was configured for direct access. Yet, the registry and error logs showed otherwise.
To remove the offending proxy server setting I went to a command prompt and issued the command: proxycfg -d
Upon verifying the settings in the registry, it was confirmed that the proxy settings were now removed.
It appears that at some point (probably during service), Best Buy inserted a special "hidden" proxy setting into the computer. From the results I found on the internet, it appears that this IP address has also been added into the "Internet Options" proxy settings for many, breaking their internet connection all together. When finished, they were probably supposed to have removed it, but something went wrong. The registry key was "corrupted," and then had to be manually repaired or the settings were just not removed. As a result of this bug in whatever it is that they are attempting there are posts on the internet about failed windows updates and other issues related to them.
One more reason to avoid the Geek Squad.
BTW, Windows updates work now! Anybody want to take a guess at how many updates this customer needed AFTER I installed Service Pack 3 for XP?
