Windows 11 proxy settings not working — a proxy that’s configured but not being used, proxy authentication failing, or internet connection broken after proxy configuration — is a layered problem because Windows has multiple places where proxy settings are stored and applied. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Important context first: Windows has two separate proxy systems: the WinHTTP proxy (used by system services and some applications) and the WinINET proxy (used by most desktop applications and browsers). Configuring one doesn’t automatically configure the other. Most user-visible proxy issues involve WinINET; services like Windows Update use WinHTTP.
Check 1: Verify the proxy is configured correctly
Settings → Network and internet → Proxy → review the current configuration:
- “Automatically detect settings” — uses WPAD to find proxy automatically
- “Use setup script” — uses a PAC (Proxy Auto-Configuration) script URL
- “Use a proxy server” — manual IP and port configuration
Confirm the proxy address and port are entered correctly — a single wrong digit or an http:// prefix where just the IP is expected causes silent failure. For corporate proxies: get the exact address and port from IT rather than guessing.
Fix 1: Proxy not being used by browsers
Google Chrome uses Windows’ proxy settings by default — changing proxy in Windows Settings applies to Chrome without any browser-specific changes. Firefox and some other browsers maintain their own independent proxy settings. Firefox → Settings → General → Network Settings → check whether Firefox is using “System proxy settings” or a custom configuration.
If a specific browser ignores the Windows proxy: that browser likely has its own proxy configured to a different value, or to “No proxy.” Update the browser’s own proxy settings to match Windows’ configuration, or set it to “Use system proxy settings.”
Fix 2: Applications bypassing the proxy
Some applications (Slack, Teams, Spotify, many games) use their own network libraries that may not respect the Windows proxy settings. For these applications: configure proxy within the application’s own settings if available, or use a system-level proxy tool that intercepts all traffic rather than relying on per-application proxy support.
Fix 3: Proxy exceptions (bypass list)
Settings → Proxy → “Use a proxy server” → “Don’t use the proxy server for local addresses” and the “Exceptions” field. If you want to access internal servers or specific external services without going through the proxy: add them to the exceptions list. The format: 192.168.1.* for a subnet, *.company.com for a domain, or internalserver for a hostname.
Misconfigured exception lists either send internal traffic through the proxy (causing failures) or bypass the proxy for addresses that should use it.
Fix 4: WinHTTP proxy for Windows services
Windows Update, Microsoft Defender, and system services use WinHTTP rather than WinINET. When Windows services need to use a proxy and Settings’ proxy configuration isn’t applying to them: configure WinHTTP separately.
Administrator Command Prompt:
netsh winhttp show proxy
To set WinHTTP proxy:
netsh winhttp set proxy proxy-server="http://proxyaddress:port" bypass-list="localhost;127.0.0.1;*.local"
Or import from WinINET settings:
netsh winhttp import proxy source=ie
Fix 5: Authentication failure
Corporate proxies often require authentication. When a proxy authentication prompt doesn’t appear or keeps failing:
- Windows Credential Manager sometimes stores stale proxy credentials — Control Panel → Credential Manager → Windows Credentials → look for any “Proxy” entries → edit or remove them
- Proxy authentication type mismatch: NTLM, Kerberos, and Basic authentication all have different Windows behaviour. IT can confirm which authentication type the proxy uses
- On domain machines: Kerberos authentication should work transparently — if it’s failing, the machine’s domain connection may have an issue
Fix 6: Internet not working after proxy removal
If internet connection broke after removing or changing proxy settings: a residual proxy configuration is still active. Administrator Command Prompt:
netsh winhttp reset proxy
ipconfig /flushdns
Also: Settings → Proxy → disable all three options (detect, script, manual) → restart. These two steps clear both the WinHTTP and WinINET proxy configurations.
Our guide on network connectivity troubleshooting covers the DNS and connectivity restoration that often accompanies proxy configuration issues. For VPN and proxy interactions that affect all applications, our VPN configuration guide covers how VPNs interact with proxy settings. Microsoft’s proxy configuration documentation covers the Group Policy proxy settings (which override user-level settings in enterprise environments) and the WPAD auto-detection mechanism.
PAC file proxy (automatic configuration script)
PAC (Proxy Auto-Configuration) files are JavaScript files that determine whether each URL should use a proxy or connect directly. If configured and the PAC file URL is reachable, Windows queries it for every connection. When the PAC file URL is unreachable (the server hosting it is down, DNS can’t resolve it, or network access is required to reach it), Windows waits for the PAC lookup to time out before connecting — causing significant slowdowns that look like internet performance problems.
To check if a PAC file is configured: Settings → Proxy → “Use setup script” → look at the script address. In a browser: navigate to the PAC URL — if it returns a JavaScript file, it’s working. If it times out or returns an error: the PAC file is unavailable and is causing connectivity delays. Remove it and use manual proxy configuration until the PAC file server is restored.
Group Policy proxy override
In enterprise environments: Group Policy pushes proxy settings to all domain machines. When Group Policy is configured with proxy settings: the Settings → Proxy page may appear to let you make changes, but changes are overridden by Group Policy at each policy refresh (every 90 minutes or at logon).
Check for Group Policy proxy: run gpresult /r in Command Prompt → look for proxy settings under “User Configuration” applied policies. If proxy settings appear in Group Policy: only IT administrators can change the proxy configuration for domain machines. Local changes won’t persist.
WPAD and automatic proxy detection
WPAD (Web Proxy Auto-Discovery Protocol) allows Windows to automatically find the proxy server without manual configuration. It works by querying DNS for “wpad.[yourdomain].com” and looking for a PAC file there. When WPAD is enabled but no WPAD server exists: Windows spends time looking for a proxy that isn’t there, causing connectivity delays.
For home networks where no proxy is needed: Settings → Proxy → turn off “Automatically detect settings.” This eliminates the WPAD lookup that’s causing the delay. For corporate networks: WPAD often provides the correct proxy automatically and should remain enabled unless IT has configured a manual PAC file instead.
Proxy and VPN interaction
VPN connections create their own network interface and often have their own proxy or routing rules. When a VPN is connected: proxy settings that worked before may not apply to traffic going through the VPN adapter — the VPN may bypass the proxy entirely or route traffic to a different proxy server than the one configured in Windows.
Check: connect to VPN → verify internet access works → check which proxy the VPN client is configured to use (VPN clients often have their own proxy settings separate from Windows). If internet works through VPN but not after disconnecting: the VPN changed routing or DNS settings that interfered with the normal proxy path. Running netsh winhttp reset proxy and then re-applying the correct proxy settings after VPN disconnect usually resolves this.
Checking the current effective proxy settings
Administrator Command Prompt:
netsh winhttp show proxy
And for user-level proxy (WinINET, which most applications use):
reg query "HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings" /v ProxyEnable
reg query "HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings" /v ProxyServer
These commands show the actual current proxy configuration, which may differ from what the Settings page shows if something else is modifying the registry. If the registry shows proxy enabled but Settings shows it disabled: a script, Group Policy, or application is writing to the registry directly.
Proxy configuration for specific use cases
| Scenario | Recommended proxy setting |
| Home network, no proxy needed | All toggles off in Settings → Proxy |
| Corporate environment with manual proxy | “Use a proxy server” with address and port from IT |
| Corporate with automatic proxy detection | “Automatically detect settings” (WPAD) or “Use setup script” (PAC URL) |
| VPN with split tunneling | VPN client handles routing; proxy settings may need bypassing for VPN traffic |
| Windows services need proxy (Windows Update, Defender) | Configure WinHTTP proxy with netsh commands additionally |
Malware changing proxy settings
Some malware modifies Windows proxy settings to route traffic through a malicious server. Signs: proxy settings changed without your action, all traffic is slow or being redirected, a proxy server is configured that you don’t recognise. Run a Malwarebytes scan → check Settings → Proxy for unexpected settings → remove any proxy you didn’t intentionally add. Also run netsh winhttp show proxy to check whether WinHTTP was also modified.
After removing malware-installed proxy settings: run the proxy reset commands and confirm internet access is working correctly before configuring any legitimate proxy settings.
Testing the proxy configuration
To confirm the proxy is working as intended: open Command Prompt → curl -x http://proxyaddress:port http://httpbin.org/ip. This sends a test request through the specified proxy and returns the IP address as seen from the internet. If the IP matches the proxy’s exit IP: the proxy is working correctly. If it returns your real IP: the proxy isn’t intercepting the request. If it times out: the proxy address or port is wrong.
This test is more reliable than browser-based testing because it’s direct and explicit about which proxy is being used, rather than depending on browser proxy auto-detection.
Proxy configuration problems are more common than expected because Windows has so many layers where proxy settings can be defined — Settings UI, WinHTTP, WinINET registry, Group Policy, individual application settings, and VPN client settings. When troubleshooting: systematically check each layer rather than assuming the Settings page shows the complete picture. The netsh winhttp show proxy command is the most reliable source of truth for what Windows services actually use, and the WinINET registry keys show what most desktop applications use.
For IT administrators configuring proxies across an organisation: the most reliable approach is Group Policy for user-level proxy settings and a deployment script for WinHTTP configuration, rather than relying on individual users to configure proxy settings manually. This ensures every machine has the correct configuration from day one, and changes propagate automatically when the proxy server address needs to be updated. Manual per-machine proxy configuration creates a maintenance burden that multiplies with every user who needs reconfiguration.
Diagnosing with Fiddler
Fiddler (free tool from Telerik) acts as a local proxy that captures all HTTP and HTTPS traffic. When proxy settings seem correct but applications still can’t connect: running Fiddler as an intermediary shows exactly what traffic is being sent, whether it’s going through the corporate proxy, and what the proxy’s response is. Fiddler automatically configures itself as the system proxy and shows every connection attempt, making it the most detailed diagnostic tool for proxy configuration issues.
Fiddler is particularly useful for diagnosing proxy authentication failures — it shows the exact authentication challenge from the proxy and whether Windows is responding with the correct credentials. This level of detail isn’t available from Windows’ built-in proxy diagnostics.
Understanding when proxy settings matter: for home users, proxy settings should usually be empty (all off in Settings → Proxy). Adding a proxy incorrectly is a more common problem than needing one and not having it configured — if you’re not sure whether you need a proxy, you probably don’t. Home internet connections route directly through the ISP without any proxy. Corporate networks, university networks, and some secure environments use proxies for security scanning and access control. If you encounter proxy settings on a home network that you didn’t configure: check for malware (some malware installs a local proxy) or recently installed software that added proxy settings as part of its setup.
A practical checklist when proxy troubleshooting gets complicated: (1) Is it configured in Settings? (2) Is WinHTTP configured the same way? (3) Is Group Policy overriding it? (4) Is the specific application using Windows proxy or its own? (5) Is authentication working correctly? Working through these five questions in order resolves the vast majority of proxy configuration problems. The Settings page is only layer one of a five-layer stack — knowing the other four layers exist is what distinguishes effective proxy troubleshooting from frustrated random changes.
When all else fails and you need internet access immediately despite proxy issues: temporary workaround — run netsh winhttp reset proxy and netsh winsock reset in an Administrator Command Prompt → restart → this removes all proxy configuration and resets the networking stack. You’ll lose any proxy configuration that was legitimately needed, but you’ll have direct internet access immediately. Reconfigure the proxy correctly once access is restored and you can research the proper settings. See also Windows 11 Widgets Not Working for a related case.
