Windows  ·  medium  ·  Networking & connectivity

ERR_PROXY_CONNECTION_FAILED — a proxy is set that should not be

Traffic is being sent to a proxy that is not there. Browsers fail, and so does anything that respects the system proxy — including Windows Update and the Store.

What you see

"Unable to connect to the proxy server" in every browser, while ping works normally. Frequently follows removing malware, or a laptop that has left a corporate network.

What is actually wrong

A proxy left in the WinHTTP or WinINET configuration — by policy, by a removed VPN client, or by adware that set it deliberately. WinHTTP and per-user settings are separate, which is why fixing one often appears to do nothing.

Codes and articles

ERR_PROXY_CONNECTION_FAILEDERR_TUNNEL_CONNECTION_FAILED0x80072EFDproxy server isn't responding

Fixes (3)

Clear the per-user proxy
PowerShell as the affected user10 minuteslow riskreversible

One account. This is the setting the Settings app shows.

  1. Read what is set, and note it in case it was deliberate.

    PowerShell
    Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' | Format-List ProxyEnable,ProxyServer,AutoConfigURL

  2. Turn it off and remove any automatic configuration script.

    PowerShell
    $k='HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings'Set-ItemProperty $k -Name ProxyEnable -Value 0Remove-ItemProperty $k -Name ProxyServer -ErrorAction SilentlyContinueRemove-ItemProperty $k -Name AutoConfigURL -ErrorAction SilentlyContinue

    AutoConfigURL is the one people miss. Clearing the manual proxy while a PAC script is still set leaves the machine exactly as broken as before.

  3. Close and reopen the browser — these are read at start-up.

Confirm it workedBrowsing works and the Settings proxy page shows nothing set.
PowerShell
Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' | Format-List ProxyEnable,AutoConfigURL
If you need to undo itSet ProxyEnable back to 1 and restore the ProxyServer string recorded in step one.
Reset the machine-wide WinHTTP proxy
Elevated Command Prompt10 minuteslow riskreversible

Windows Update, the Store or a service is failing while browsers are fine — or the other way round.

  1. Show the machine-wide setting. This is separate from the user's and is what services use.

    Command Prompt
    netsh winhttp show proxy

  2. Reset it.

    Command Prompt
    netsh winhttp reset proxy

  3. If a proxy is genuinely required for services, import the user's working settings rather than typing them again.

    Command Prompt
    netsh winhttp import proxy source=ie

  4. Restart the update service so it picks the change up.

    PowerShell
    Restart-Service wuauserv
Confirm it workednetsh winhttp show proxy reports direct access, and Windows Update checks successfully.
If you need to undo itnetsh winhttp set proxy with the original value from step one.
Find the policy that keeps putting it back
Elevated PowerShell20 minutesmedium riskreversible

The setting is greyed out, or returns after a restart or a Group Policy refresh.

  1. Check for the policy keys that lock the page.

    PowerShell
    Get-ItemProperty 'HKLM:\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings' -ErrorAction SilentlyContinueGet-ItemProperty 'HKCU:\Software\Policies\Microsoft\Internet Explorer\Control Panel' -ErrorAction SilentlyContinue

  2. On a domain machine, find which GPO is responsible rather than deleting the key.

    Command Prompt
    gpresult /h %USERPROFILE%\Desktop\gpo.htmlstart %USERPROFILE%\Desktop\gpo.html

    Deleting a policy-set value on a domain machine fixes it until the next refresh, at most 90 minutes away. The report names the GPO so it can be corrected once, centrally.

  3. On a machine that has left a domain and kept the settings, remove the stale policy keys.

    PowerShell
    Remove-Item 'HKCU:\Software\Policies\Microsoft\Internet Explorer' -Recurse -Force -ErrorAction SilentlyContinuegpupdate /force
Confirm it workedThe proxy page is editable and stays clear after a restart.
If you need to undo itExport the keys with reg export before deleting them; re-import to restore.

Related faults

0x8024402C / 0x80244022 — the client cannot talk to WSUSWindows

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.