How to Configure Proxy Settings in Windows 10 and 11 (2026 Guide)

TL;DR: Configure proxy in Windows 10/11 via Settings → Network & Internet → Proxy (easiest, for most apps). For command-line tools and Windows Update, use netsh winhttp set proxy. For SOCKS5 proxies, use Proxifier or browser-level settings. Chrome, Edge, and most apps automatically use the Windows Settings proxy. Firefox requires separate proxy configuration.

---

Why Use a Proxy on Windows?

A proxy server acts as an intermediary between your Windows PC and the internet. Traffic routes through the proxy server, which:

• Masks your IP address — websites see the proxy server's IP, not yours
• Bypasses geo-restrictions — access content restricted to other regions
• Enables network monitoring — enterprises route traffic through proxies to enforce policy
• Improves privacy — your ISP sees only proxy traffic, not your destination sites
• Supports web scraping — automated tools route requests through proxy IPs to avoid bans

Windows 10 and 11 support both automatic proxy detection (via WPAD/PAC files — used in enterprise environments) and manual proxy configuration (for private proxy servers and VPN-adjacent use cases).

---

Overview: Windows Proxy Configuration Methods

| Method | Best For | Applies To | |---|---|---| | Settings App (GUI) | Personal use, simple setup | Most WinINet apps (Chrome, Edge, most desktop apps) | | Internet Options | Legacy IE apps, IE-based embedding | IE, apps using WinINet directly | | Registry (HKCU) | Programmatic/script configuration | Same as Settings App | | netsh winhttp | Windows Update, system tools, .NET apps | WinHTTP stack (curl.exe, Windows Update) | | Proxifier (third-party) | SOCKS5, per-app routing | Any app — overrides all network stacks | | Firefox proxy settings | Firefox-only | Firefox browser only |

---

Method 1: Windows Settings App (Recommended for Most Users)

This is the simplest method and applies to Chrome, Edge, Microsoft Store apps, and most desktop applications.

Steps for Windows 10

1. Press Windows key + I to open Settings
2. Click Network & Internet
3. In the left sidebar, click Proxy
4. Under Manual proxy setup:
   • Toggle Use a proxy server to On
   • Address: Enter your proxy server's IP address or hostname
   • Port: Enter the port number (common ports: 8080, 3128, 80, 1080)
   • Don't use the proxy server for: Add bypass exceptions (e.g., localhost;127.0.0.1)
5. Click Save

Steps for Windows 11

1. Press Windows key + I
2. Click Network & internet (left sidebar)
3. Scroll down and click Proxy
4. Under Manual proxy setup, click Set up
5. Toggle Use a proxy server to On
6. Enter Proxy IP address and Port
7. Click Save

Automatic Proxy Setup (Enterprise/PAC File)

If your organization provides a PAC file URL:

1. Open Settings → Network & Internet → Proxy
2. Under Automatic proxy setup, toggle Use setup script to On
3. Enter the Script address (e.g., http://proxy.company.com/proxy.pac)
4. Click Save

For Auto-detect settings (WPAD): Toggle Automatically detect settings to On. Windows will query DNS for WPAD configuration. Disable this on public networks — WPAD has known security vulnerabilities on untrusted Wi-Fi.

---

Method 2: Internet Options (Legacy/IE-Based Apps)

Some older applications and IE-embedded browsers (AutoCAD, some ERP systems) read proxy settings from Internet Options rather than the Windows Settings proxy.

1. Press Windows key + R, type inetcpl.cpl, press Enter
2. Click the Connections tab
3. Click LAN settings
4. Under Proxy server:
   • Check Use a proxy server for your LAN
   • Enter Address and Port
   • Check Bypass proxy server for local addresses (recommended)
5. Click OK → OK

Note: Changes here sync with the Settings App proxy — they write to the same registry location (HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings).

---

Method 3: Registry Configuration (Programmatic/Script-Based)

For IT automation, group policy deployment, or scripting proxy changes:

# Set via PowerShell (run as Administrator for machine-wide, or regular for current user)
$registryPath = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings"

# Enable proxy
Set-ItemProperty -Path $registryPath -Name ProxyEnable -Value 1

# Set proxy server
Set-ItemProperty -Path $registryPath -Name ProxyServer -Value "proxy.example.com:8080"

# Set bypass list (semicolon separated)
Set-ItemProperty -Path $registryPath -Name ProxyOverride -Value "localhost;127.0.0.1;*.local;<local>"

# Verify settings
Get-ItemProperty -Path $registryPath | Select-Object ProxyEnable, ProxyServer, ProxyOverride

Disable proxy via registry:

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings" -Name ProxyEnable -Value 0

---

Method 4: netsh WinHTTP (For System Tools and Windows Update)

WinHTTP is a separate Windows networking library used by:

• Windows Update
• curl.exe (Windows built-in version)
• .NET HttpClient (in some configurations)
• PowerShell Invoke-WebRequest (uses WinHTTP in some versions)
• BITS (Background Intelligent Transfer Service)

The Settings App proxy does NOT apply to WinHTTP. Configure it separately:

# Open Command Prompt as Administrator

# Set proxy
netsh winhttp set proxy proxy-server="http=proxy.example.com:8080;https=proxy.example.com:8080" bypass-list="*.local;<local>"

# View current settings
netsh winhttp show proxy

# Import Settings App proxy into WinHTTP (copies from Internet Settings)
netsh winhttp import proxy source=ie

# Reset to direct connection
netsh winhttp reset proxy

Setting WinHTTP proxy via PowerShell:

# Set for .NET WebRequest globally
[System.Net.WebRequest]::DefaultWebProxy = New-Object System.Net.WebProxy('http://proxy.example.com:8080')
[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials

# For PowerShell Invoke-WebRequest/Invoke-RestMethod:
$proxy = New-Object System.Net.WebProxy('http://proxy.example.com:8080', $true)
[System.Net.WebRequest]::DefaultWebProxy = $proxy

---

Setting Up SOCKS5 Proxy on Windows

Windows does not natively support SOCKS5 in its proxy settings. Use these approaches:

Option A: Proxifier (Best SOCKS5 Windows Client)

Proxifier is the industry standard for forcing any Windows application through a SOCKS5 proxy:

1. Install Proxifier
2. Open Proxifier → Proxy Servers → Add
3. Enter:
   • Address: Your SOCKS5 proxy hostname (e.g., gate.limeproxies.com)
   • Port: SOCKS5 port (e.g., 5432)
   • Protocol: SOCKS Version 5
   • Authentication: Enable and enter username/password
4. Configure rules: Profile → Proxification Rules — set which apps use the proxy
5. Test connection: Proxy Checker

Option B: Browser-Level SOCKS5 (Firefox)

Firefox has its own proxy settings independent of Windows:

1. Open Firefox → Settings → General → Network Settings → Settings
2. Select Manual proxy configuration
3. Leave HTTP/HTTPS blank
4. Set SOCKS Host: to your proxy IP, Port: to your proxy port
5. Select SOCKS v5
6. Check Proxy DNS when using SOCKS v5 (prevents DNS leaks)
7. Click OK

Option C: Chrome via Command Line

# Launch Chrome with SOCKS5 proxy
chrome.exe --proxy-server="socks5://proxy.example.com:1080" --host-resolver-rules="MAP * ~NOTFOUND, EXCLUDE proxy.example.com"

See LimeProxies SOCKS5 plans for private SOCKS5 credentials.

---

Configuring Proxy for Specific Applications

curl (Windows built-in, PowerShell, Git Bash)

# Single request
curl -x http://username:password@proxy.example.com:8080 https://ip.me

# Set permanently via environment variables
set HTTP_PROXY=http://username:password@proxy.example.com:8080
set HTTPS_PROXY=http://username:password@proxy.example.com:8080
set NO_PROXY=localhost,127.0.0.1

# Or in .curlrc file (C:\Users\<username>\_curlrc)
proxy = http://proxy.example.com:8080
proxy-user = username:password

Git

# Set proxy for all Git operations
git config --global http.proxy http://proxy.example.com:8080
git config --global https.proxy https://proxy.example.com:8080

# Unset
git config --global --unset http.proxy

# Verify
git config --global --list | grep proxy

Python requests

import requests

proxies = {
    'http': 'http://username:password@proxy.example.com:8080',
    'https': 'http://username:password@proxy.example.com:8080',
}

response = requests.get('https://ip.me', proxies=proxies)
print(response.text)

---

Proxy Authentication in Windows

Most paid proxy services require username/password authentication. Windows handles this differently by method:

• Settings App: Enter credentials only if prompted — Windows caches them in Credential Manager
• Internet Options: Works with Windows Integrated Authentication; basic auth requires browser prompt
• curl/netsh: Pass credentials in the proxy URL: http://username:password@host:port
• Proxifier: Enter username/password in the proxy server configuration
• Browsers: Prompted automatically when proxy requires authentication

---

Verifying Your Proxy Is Working

# Method 1: Check IP via PowerShell
(Invoke-WebRequest -Uri "https://api.ipify.org").Content

# Method 2: Via curl
curl https://ip.me

# Method 3: Browser
# Open Chrome/Edge, navigate to: https://whatismyip.com
# Verify the IP shown matches your proxy server's IP, not your real IP

# Method 4: Trace the route (shows proxy in hop chain)
tracert ip.me

---

Troubleshooting Windows Proxy Issues

| Problem | Likely Cause | Fix | |---|---|---| | Proxy not working in Chrome | Settings App proxy not enabled | Check Settings → Network & Internet → Proxy | | Works in Chrome, not in curl | WinHTTP not configured | Run: netsh winhttp import proxy source=ie | | Works in Chrome, not in Firefox | Firefox uses its own proxy settings | Configure Firefox separately | | Proxy requires auth but Windows loops | Cached bad credentials | Open Credential Manager → Windows Credentials → delete proxy entry | | Windows Update still fails via proxy | WinHTTP not configured | netsh winhttp set proxy ... separately | | Proxy connected but slow | Proxy server overloaded | Try dedicated private proxies | | SOCKS5 not working | Windows doesn't support SOCKS5 natively | Use Proxifier or browser-level SOCKS5 settings |

---

Recommended Proxy Types for Windows Users

| Use Case | Best Proxy Type | Why | |---|---|---| | Web browsing privacy | Residential proxy | Real ISP IPs, not blocked by sites | | Fast browsing / low latency | Datacenter proxy | Server-grade speed, low latency | | Web scraping automation | Rotating residential proxy | Auto-rotating IPs prevent blocks | | App-level anonymity | SOCKS5 proxy | Protocol-agnostic, works with any app via Proxifier | | Privacy + encryption | VPN | Full encryption; proxy does not encrypt |

---

Last updated: March 2026