The message shows up at the end of a ritual most Windows users know. The internet stops working, the browser shows an error, you right-click the network icon and run the troubleshooter, it thinks for a while, and it reports "Windows could not automatically detect this network's proxy settings", with a red mark and the words Not fixed. It sounds specific. It is not. The troubleshooter tested whether Windows could reach the web, the test failed, and the proxy configuration is the stage of the test where it lost the trail. The sentence is the diagnostic's best guess about where to look, and it is often right about the neighbourhood while being vague about the house.
The good news is that the neighbourhood is small. In practice, this verdict comes from one of a handful of causes: a proxy or setup script that something configured and that no longer answers, a stale proxy in the WinHTTP layer that Windows services and the troubleshooter itself use, a VPN client or its driver sitting in the network path, damage to the Winsock stack from badly removed security software, or a network adapter driver that broke after an update. This guide takes them in the order that fixes the most machines soonest, and it is honest about which steps do what, because a lot of advice for this error mixes steps that remove the cause with steps that only reset things around it.
| Cause | How it usually got there | The step that fixes it |
|---|---|---|
| A proxy or setup script is configured and does not answer | Leftover from a VPN, antivirus web filter, ad blocker, school or work setup, or unwanted software | Step 1 |
| The WinHTTP proxy is set for Windows services | Same products, one layer deeper; survives the Settings toggles | Step 2 |
| A VPN client or its network driver is in the path | Installed VPN, closed badly or half-uninstalled | Step 3 |
| Automatic proxy detection is failing on this network | A network that announces a proxy badly, or a captive portal | Step 4 |
| The network stack is damaged | Security software or a VPN removed without cleaning up | Step 5 |
| The adapter driver broke | A Windows or driver update | Step 6 |
Step 1: clear any configured proxy, in both panels
The most common cause is the simplest. Something configured a proxy, the program behind it is gone or not running, and every connection now goes to an address where nothing answers. The troubleshooter reaches that address, gets nothing, and blames proxy settings, which is fair.
Open Settings, Network & internet, Proxy. Under Manual proxy setup, if Use a proxy server is on, click Edit, read the address, and switch it off. Under Automatic proxy setup, switch Use setup script off if it is on. Then press Windows+R, run inetcpl.cpl, open the Connections tab, click LAN settings, and uncheck Use a proxy server for your LAN and Use automatic configuration script. The two panels write the same setting and are not always in step, so clear both. While you are on the Connections tab, check the list of VPN and dial-up connections above the LAN settings button; each carries proxy settings separate from the LAN ones, and a leftover VPN entry is a frequent culprit on laptops.
Run the troubleshooter again. If it passes, note the address you removed. A 127.0.0.1 address was a program on this PC, probably a VPN or a filter; an unfamiliar public address is worth a look in our IP lookup and a scan. How to turn off a proxy explains what each kind of address means.
Step 2: reset the WinHTTP proxy
Windows services, Windows Update, the Store, and the network troubleshooter itself do not use the per-user setting you just cleared. They use a separate configuration called WinHTTP, which is normally set to direct access and does not follow the toggles in Settings. A proxy left here keeps the troubleshooter failing after the browser already works.
Open Terminal or PowerShell as administrator and run:
netsh winhttp show proxy
If the answer is anything other than Direct access (no proxy server), and this is not a work machine that is supposed to use one, reset it:
netsh winhttp reset proxy
Then run the troubleshooter again. On a work device, ask the administrator before resetting; that value may be there on purpose.
Step 3: take the VPN out of the path
VPN clients install a virtual network adapter and a filter driver, and some also route traffic through a local proxy. When the client is out of date, closed badly, or partly uninstalled, its pieces stay in the network path while the tunnel they belong to is gone, and the troubleshooter reports a proxy problem because the path it tests no longer leads anywhere.
Disconnect the VPN and run the troubleshooter. An error that clears at that point names the VPN as the cause: update the client, or uninstall it completely, with the maker's dedicated cleanup utility where one exists, because the adapter and driver often survive the normal uninstall. In Device Manager, under Network adapters, an entry named after a VPN product or a TAP or TUN adapter that belongs to a program you have removed can be uninstalled from there.
The same applies to antivirus suites with a web shield or a firewall component, and to any parental-control or "network protection" software. Disable the component temporarily, test, and if that was it, update or reinstall the product.
Step 4: decide what to do with automatic detection
Automatically detect settings, the first toggle on the Proxy page, tells Windows to ask the local network whether it has a proxy, using a mechanism called WPAD. Home routers do not announce one, so on most home networks the lookup finds nothing and Windows connects directly. Two situations turn this toggle into the cause.
The first is a network that announces a proxy badly: a school or office network with a broken configuration file, or a public network that hands out a proxy that does not work. The second is a captive portal, the sign-in page at hotels, airports, and cafes: until you have signed in, every connection is intercepted, the troubleshooter's test fails, and the verdict can land on the proxy step. For a captive portal, open a browser and load a plain http:// page, which gives the portal a chance to redirect you to its sign-in screen, then run the troubleshooter again once you are signed in.
When the error appears only on one particular network, switch Automatically detect settings off while you are on it and test. An error that appears everywhere has a different cause, and the toggle can stay on.
Step 5: reset the network stack
Security products, VPN clients, and network filters insert themselves into the Winsock layer, and a clumsy removal leaves broken pieces in it. When that happens, the troubleshooter fails at the proxy step with nothing configured anywhere, because the machinery it uses to make its test connection is itself damaged. The classic reset commands exist for exactly this situation.
Run these in an administrator terminal, then restart:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
Be clear about what they do. They rebuild the Winsock catalogue and the TCP/IP configuration, flush the DNS cache, and take a fresh IP lease. They do not remove a configured proxy, which is why they belong after step 1 and step 2, not instead of them. Run them on a machine that still has a proxy configured and the error is back before the restart finishes.
If the resets do not help, Windows 11 has a heavier version: Settings, Network & internet, Advanced network settings, Network reset. It removes and reinstalls every network adapter and returns networking components to defaults. You will need to re-enter Wi-Fi passwords and reinstall any VPN client afterwards, which is a feature in this context rather than a cost.
Step 6: roll back or reinstall the network adapter driver
An error that began right after a Windows update or a driver update points at the adapter driver. Open Device Manager, expand Network adapters, right-click your Wi-Fi or Ethernet adapter, open Properties, and on the Driver tab click Roll Back Driver if the button is available. If it is not, choose Uninstall device, tick the option to remove the driver software if offered, restart, and let Windows reinstall it, or download the current driver from the laptop or adapter manufacturer on another device and install that.
When the setting comes back
If you clear a proxy in step 1 and find it configured again after a restart, no amount of resetting will hold. A program is rewriting it: a VPN or security product that left a service behind, or unwanted software that wants your traffic to pass through its server. The guide to a proxy that keeps re-enabling itself shows how to catch the exact program with Process Monitor and remove it, and what an unexplained proxy address implies for the machine.
If you use a proxy on purpose
Some people meet this error because they configured a proxy deliberately and it stopped answering. The troubleshooter is then correct: the proxy is the problem, and Windows cannot detect a working one. Test the address in our proxy checker to see whether it is alive at all. With a public proxy the answer is usually no: it was carrying a crowd's traffic and has since been burned out or switched off. Replace it from our free proxy list, which timestamps the last successful check on every entry. A proxy that the checker reports alive but Windows cannot use usually means a protocol mismatch (the Windows manual proxy field expects HTTP, not SOCKS) or a network that cannot reach the proxy's address, both covered in our guide on the proxy server isn't responding. For a proxy that has to stay up, choose a static ISP address or a residential plan with sticky sessions, and the Windows setup guide shows where it goes.
Confirm it is fixed
Run the troubleshooter one more time and let it report that it found no problems. Then load our IP lookup and check that the address shown is one your ISP issued rather than a hosting company's, which proves that no proxy in any of the layers is carrying your traffic. Finally, restart and check Settings, Network & internet, Proxy once more. If the toggles are still off and the page still loads, the cause is gone rather than paused.