ProxyVerity
How-to

How to Set Up a Proxy on Windows 11

Step-by-step guide to configuring a proxy on Windows 11, covering manual and automatic setup, SOCKS5, authenticated proxies, per-app tweaks, verification, and troubleshooting.

RB
By Roman Bulatov
Proxy & Network Infrastructure Expert · · 5 min read

Configuring a proxy on Windows 11 is straightforward, whether you need to route all traffic through a corporate gateway, access geo-restricted content, or add a layer of anonymity. This guide covers every method, from manual entry to automatic provisioning, and shows you how to verify the setup works.

Manual Proxy Configuration via Settings

The easiest approach is to use the built-in proxy settings. This applies to HTTP, HTTPS, and FTP proxies (but not SOCKS – we will address that separately).

  1. Open Settings (Windows + I) and navigate to Network & Internet > Proxy.
  2. Under Manual proxy setup, toggle Use a proxy server on.
  3. Enter the proxy IP address and Port (e.g., 192.168.1.50:8080 or proxy.example.com:3128).
  4. Optionally, add addresses that should bypass the proxy in the Exceptions box (use semicolons to separate). Check Don't use the proxy server for local addresses to keep internal traffic direct.
  5. Click Save. Windows will immediately begin routing HTTP/HTTPS traffic through the proxy.

To disable the proxy, simply return to this screen and toggle Use a proxy server off.

Automatic Proxy Configuration (PAC Script or WPAD)

If your organisation or provider supplies a PAC file URL, you can use automatic setup:

  1. In the same Proxy settings, locate Automatic proxy setup.
  2. Toggle Automatically detect settings on to let Windows find a WPAD server on the network. This is common in enterprise environments.
  3. Alternatively, toggle Use setup script on and paste the full URL (e.g., http://proxy.example.com/proxy.pac). Windows will download and apply the script’s logic.

PAC scripts can route traffic based on destination, time of day, or other rules. If both manual and automatic are enabled, the automatic script takes precedence.

Authenticated Proxies

For proxies that require a username and password, enter them when prompted by the system. Windows will cache the credentials for the session. To clear them, run cmdkey /delete:Proxy:<server>:<port> from an elevated command prompt. Alternatively, use third-party tools that handle authentication per application.

Be aware that credentials sent over plain HTTP proxies (without encryption) are visible to anyone on the network. Always use HTTPS proxies or tunnel authentication inside a VPN when possible.

Configuring a SOCKS5 Proxy

Windows 11 does not support SOCKS proxies natively. To use SOCKS5 (often required for torrenting, SSH tunnelling, or certain privacy tools), you need a third-party client that can intercept traffic and redirect it. Recommended options include:

  • Proxifier – routes all system traffic through SOCKS, HTTP, or HTTPS proxies. You can define rules per application.
  • FreeCap or SocksCap64 – create a sandboxed environment where only specified applications use the SOCKS proxy.
  • Netify – a simpler tool for redirecting individual programs.

After installing your chosen tool, enter the SOCKS5 server address, port, and (if required) authentication. The tool will handle the rest.

Per-Application Proxy Configuration

Windows’ proxy settings apply system-wide. To route only specific applications through a proxy, you have three options:

  • Third-party proxy managers (like those above) that support application rules.
  • Application-level settings – many apps (browsers, download managers) have their own proxy fields, bypassing the system proxy.
  • Virtual private network (VPN) overlay if you need advanced per-app split tunnelling.

For example, in Google Chrome you can launch it with the --proxy-server flag: chrome.exe --proxy-server="socks5://127.0.0.1:1080". This overrides the system setting for that instance.

Verifying Your Proxy Connection

After configuration, confirm it is working correctly:

  1. Visit a site like What Is My IP – the displayed IP should be your proxy’s, not your own.
  2. Check for leaked WebRTC addresses (if using a browser) by using a WebRTC leak test site.
  3. Use a custom HTTP header checker to see if X-Forwarded-For or Via headers include your real IP.

For a thorough, independent test, run your proxy through ProxyVerity’s free proxy checker. It verifies status, speed, and anonymity against multiple judges, reporting any headers that may expose your identity.

Common Troubleshooting Tips

If your proxy does not work as expected, try these steps:

  • Check the proxy address and port – a typo is the most common mistake.
  • Verify authentication if required – test with a tool like curl -x http://user:pass@proxy:port http://example.com in PowerShell.
  • Disable Windows Defender Firewall temporarily (if safe) to rule out blocking.
  • Review the proxy bypass list – ensure no unintended entries include the site you are testing.
  • Try a different protocol – if HTTPS fails, test HTTP or vice versa. Some proxies only support one.
  • Restart the network adapter (ipconfig /renew from Command Prompt) after changing settings.

If issues persist, the proxy server itself may be down or misconfigured. Use our continuously verified proxy list to find a reliable alternative.

Important Safety Considerations

Free or public proxies are operated by third parties. They can intercept, log, or modify your traffic – use them only with HTTPS sites and avoid entering sensitive information. Always check a proxy’s anonymity level. ProxyVerity tests each proxy for external IP detection and header transparency, so you know exactly what is exposed.

Legally, ensure your use of a proxy complies with the provider’s terms and any applicable laws. Automated scraping should respect robots.txt and website terms of service.

For most Windows users, the built-in manual or automatic setup and a quick verification with a reliable tool like ProxyVerity’s checker will keep you safe and informed.

Back to ProxyHub