The essential points from this guide -- each one is explained in detail below.
TL;DR: Set a Windows proxy under Settings > Network & Internet > Proxy for most apps, but Internet Options and netsh still control legacy and command-line traffic separately.
Windows 10 and Windows 11 share the same proxy settings screen, reached through Settings > Network & Internet > Proxy.
The "Windows could not automatically detect this network's proxy settings" error usually means auto-detect failed to find a WPAD file, not that the proxy itself is broken.
Internet Options, reached through Control Panel, still governs proxy behavior for apps that read the older WinINET configuration instead of the newer Settings app.
The netsh winhttp command sets a separate, system-wide proxy used by background services and command-line tools, independent of the Settings app or Internet Options.
Proxy software for Windows, like Proxifier, adds per-app routing and authentication fields the built-in Settings panel does not support.
Windows 10 and Windows 11 share the same proxy settings screen, so the steps below work on either version. Here is how to turn on a proxy on Windows 10 or 11 through the built-in Settings app:
1. Open Settings and click Network & Internet. 2. Select Proxy from the left-hand menu (Windows 10) or scroll down to Proxy under Advanced network settings (Windows 11). 3. Under Automatic proxy setup, leave "Automatically detect settings" on if your network offers a WPAD auto-configuration file, or turn it off if you plan to enter a server manually. 4. Scroll to Manual proxy setup and switch "Use a proxy server" to On. 5. Enter the proxy address in the field, for example gw.knoxproxy.com, and the port number in the separate Port field. 6. Add any sites you want the proxy to skip in the box below, separated by semicolons, then check "Don't use the proxy server for local (intranet) addresses" if needed. 7. Click Save. Windows applies the change immediately, with no reboot needed.
Whether you call it a proxy windows 10 setup or a windows 10 proxy server configuration, the steps above are the same. This is proxy settings windows 10 configured system-wide, meaning most apps that read the standard WinINET network stack, including Microsoft Edge and Chrome, pick up the change right away. The Settings app has no field for a username or password, so if your proxy server requires authentication, Windows prompts for credentials the first time an app connects through it, or you need one of the proxy software options covered later in this guide.
Windows 10 proxy settings and Windows 11 proxy settings live under slightly different menu paths, since Windows 11 nested the Proxy page one level deeper inside Advanced network settings, but every field inside the panel works the same way on both versions. If you cannot find the Proxy page at all, search "proxy" directly in the Settings search bar; it is faster than navigating the full menu tree. For a full breakdown of what each field in this panel controls, see What Are Proxy Settings?, or How Do Proxies Work? for the fundamentals of proxy routing itself.
Not every Windows app reads the modern Settings panel. Internet Options and the netsh command each control proxy behavior for a different slice of Windows software, and knowing which one an app reads saves a lot of troubleshooting time.
Internet Options is still reachable on both Windows 10 and Windows 11: open Control Panel, click Network and Internet, then Internet Options, and open the Connections tab. Click LAN settings to reach the same proxy address, port, and bypass-list fields shown in the Settings app; Windows keeps these two panels in sync, since Internet Options is really an older window into the same WinINET configuration. Some legacy desktop apps and installers only expose a proxy toggle inside their own settings that map back to this panel, so keep it in mind if a proxy server windows 10 setup works in Edge but not in an older third-party program.
netsh controls a separate configuration called WinHTTP, used by background Windows services, Windows Update, and command-line tools that never read WinINET at all. To set a proxy at this level, open Command Prompt as administrator and run:
netsh winhttp set proxy proxy-server="gw.knoxproxy.com:7000" bypass-list="localhost"To check what is currently active, run netsh winhttp show proxy, and to clear it, run netsh winhttp reset proxy. This is the layer that matters most for a windows proxy server used in scripts, scheduled tasks, or any tool that runs outside a normal browser session, since those processes frequently skip WinINET and read WinHTTP instead.
A proxy server on Windows 10 configured only through the Settings app will not automatically reach WinHTTP-based tools, and the reverse is also true. If a specific app ignores your proxy settings entirely, check whether it reads WinINET or WinHTTP before assuming the proxy itself is broken.
Windows could not automatically detect proxy settings means Windows tried to find a WPAD (Web Proxy Auto-Discovery) file on the network and failed, not that a proxy server rejected the connection. This message shows up specifically when "Automatically detect settings" is switched on but no auto-configuration file exists at the expected network location.
Three situations trigger this error most often. First, home and small business networks rarely publish a WPAD file at all, so Windows' automatic search comes back empty by design, not by mistake. Second, switching between networks, home WiFi to a coffee shop, a VPN, a corporate network, can leave a stale auto-detect setting pointed at a configuration that no longer applies. Third, a network adapter driver issue or a corrupted WinHTTP configuration can block detection even when a valid WPAD file exists.
Fixing this error takes four steps, in order:
1. Open Settings > Network & Internet > Proxy and turn off "Automatically detect settings" entirely.
2. If you have a specific proxy server address, switch to Manual proxy setup instead and enter it directly, skipping auto-detection altogether.
3. Run the Windows Network Troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Internet Connections), which resets several adapter-level settings tied to this error.
4. From an administrator Command Prompt, run netsh winhttp reset proxy to clear any stale WinHTTP configuration that might interfere with detection.
Most home users never need automatic detection turned on at all, since it exists mainly for corporate networks that publish a WPAD file through DHCP or DNS. Switching straight to manual proxy setup with a known server address, like the ones described in what a proxy server is, avoids this error entirely instead of troubleshooting a detection process you do not need.
The built-in Settings app and Internet Options cover basic HTTP proxy setup, but both fall short in three common situations: routing only specific apps through a proxy instead of the whole system, using SOCKS5 instead of a plain HTTP proxy, and entering a username and password directly into the connection instead of relying on a login prompt. Dedicated proxy software for windows fills these gaps; if the term itself is new to you, the proxy glossary entry covers the basic definition first.
Proxifier is a common answer to what proxy software to use on Windows. It intercepts traffic at the application level, so you build rules that send one program through a proxy while everything else on the machine connects directly. Add your proxy server under Proxy Servers in Proxifier's settings, entering the hostname, port, and proxy type (HTTP or SOCKS5), plus credentials if your provider requires them, then assign that server to specific apps through a Proxification Rule.
For browser-only proxy for windows needs, an extension like SwitchyOmega or FoxyProxy adds a per-site proxy switcher directly inside Chrome or Firefox, without touching any system-wide setting or affecting other apps on the machine. This is the simpler choice when only your browser, not the whole operating system, needs to run through a proxy.
A PAC (Proxy Auto-Configuration) file automates proxy selection by URL pattern instead of pointing every connection at one fixed server, and both the Settings app and most proxy software accept a PAC file URL directly in their automatic configuration field.
To connect any of this proxy software for windows to KnoxProxy, enter the gateway hostname, gw.knoxproxy.com, along with port 7000 for HTTP or port 7001 for SOCKS5, then your KnoxProxy username and password. Residential proxies start at $2.10/GB and work well with all three tools above, since the rotating IP pool reads as ordinary consumer traffic to whatever site or service you connect to. Check the full pricing page for volume tiers before you commit to a plan.
Connection refused or timeout errors after entering a proxy address usually mean the hostname or port was typed wrong, or the proxy server itself is unreachable from your current network. Double-check both fields character by character before assuming the account is broken; a single misplaced digit in the port field is the most common cause.
Authentication prompts that keep reappearing point to a mismatch between what your proxy provider requires and what Windows' built-in dialog supports. The Settings app and Internet Options only support a browser-style credential prompt the first time an app connects, not a saved username and password field, so if that prompt keeps resurfacing, switch to proxy software with a dedicated authentication field instead.
A proxy that works in Edge but not in another app almost always means that app manages its own network connection instead of reading Windows' shared WinINET or WinHTTP configuration. Java-based tools, some command-line utilities, and certain older desktop apps fall into this category and need a proxy set through their own preferences.
If your traffic still shows your real IP address after setup, run a quick check with KnoxProxy's proxy tester to confirm the exit IP actually matches your proxy provider. If it does not, revisit the settings menu you just edited rather than assuming the account itself has a problem; a proxy configured in the wrong panel, WinINET instead of WinHTTP for example, is a far more common cause than a bad account. For setup on a different device, see the Mac, Linux, or iPhone guides, and for how proxies fit alongside a VPN, see Proxy vs VPN.
netsh winhttp reset proxy afterward if command-line tools still show a proxy active.Ready to put this into practice? Browse Residential Proxies
KnoxProxy Research Team · Technical Content
Network engineers and proxy infrastructure specialists with 10+ years in anti-bot systems, web scraping, and IP routing.
90.4M+ ethically sourced residential IPs across 195 countries. Instant activation, 14-day money-back guarantee.