How to Set Up a Proxy on Windows 10

Windows 10 version and support status

Windows 10 still runs 26.36% of desktop Windows machines worldwide, according to StatCounter figures for May 2026, against 71.69% for Windows 11. Regional shares differ sharply. In the Russian Federation Windows 10 holds 46.44% and Windows 11 holds 50.83%, so almost half of desktop machines there still run the older release. Every instruction on this page targets Windows 10 version 22H2, the only branch Microsoft continues to service.

Confirm your build before changing any network setting, because 21H2 and 22H2 behave differently under Extended Security Updates. Windows 10 left mainstream support on 14 October 2025, and Microsoft’s Extended Security Updates page now states the consumer program runs until 12 October 2027, limited to 22H2 in Home, Pro, Pro Education and Workstations editions. The July 2026 cumulative update KB5099539 moved 22H2 to build 19045.7548.

1. Press Win+R, type winver and press Enter.
2. Check that the dialog reports Version 22H2 and a build number beginning with 19045.
3. If it reports an older version, install pending updates through Settings > Update & Security > Windows Update, then restart and check again.

Configuring Windows 10 System Proxy

The Settings app is the only proxy interface most Windows 10 users need, and it writes to the WinINET layer that browsers and interactive applications read. Microsoft’s own guide, Use a proxy server in Windows, documents three supported methods: automatic detection, a setup script (PAC file), and manual entry of an address and port. Manual entry is the one that matches Proxys.io credentials, since automatic detection only works on networks that publish proxy data through DHCP or DNS.

Step 1. Press Win+I, then open Network & Internet.

1.   Press Win+I to open Settings, then go to Network & Internet and select Proxy.

2.   Scroll to Manual proxy setup and turn on Use a proxy server.

Step 2. Select Proxy in the sidebar, then turn on Use a proxy server under Manual proxy setup.

3.   Enter the proxy IP in the Address box (for example 10.0.0.6) and the port in the Port box (for example 8080).

4.   Add any internal or local domains to the Exceptions field so that traffic bypasses the proxy.

5.   Click Save.

Steps 3 to 5. Enter 10.0.0.6 and 8080, add exceptions, then click Save.

Windows 10 does not store proxy credentials in the Settings UI. When an application first attempts to use the proxy, a login prompt appears, and you enter the username and password provided by Proxys.io. Chromium documentation confirms this is deliberate: Chrome ignores any credentials embedded in proxy settings and routes authentication through its normal prompt flow instead, as described in the project’s proxy support reference. If repeated prompts get in the way of automated work, switch the proxy to IP allowlisting in your Proxys.io account so no interactive login is required.

To disable the proxy, revisit Settings > Network & Internet > Proxy and set "Use a proxy server" to Off. The system then ignores the proxy and reverts to a direct Internet connection. Local addresses never travel through the proxy in any configuration: Chromium applies implicit bypass rules covering localhost, 127.0.0.1/8, 169.254/16 and link local IPv6, so testing a proxy against a loopback address will never show the proxied IP.

Command-Line and WinHTTP Proxy

Windows 10 keeps two independent proxy layers, and confusing them causes most half-working setups. WinINET holds the per user settings written by the Settings app and read by browsers. WinHTTP holds machine level settings used by background services running as Local System or NetworkService. Microsoft’s netsh winhttp reference applies to both Windows 10 and Windows 11. Configuring one layer does not configure the other, which is why a browser can show the proxy IP while Windows Update still connects directly.

1.   Open Command Prompt as administrator.

Step 1. Type cmd in the search box, then choose Run as administrator.

2.   Run netsh winhttp set proxy 10.0.0.6:8080 to apply the proxy at the WinHTTP level.

3.   Run netsh winhttp show proxy to confirm what is currently configured.

Steps 2 and 3. Apply the proxy, then read the configuration back with show proxy.

4.   Run netsh winhttp reset proxy to return to direct access.

Step 4. Reset reports direct access, which means WinHTTP no longer uses a proxy.

Microsoft advises against this command for anything beyond a static, unauthenticated endpoint. Its Delivery Optimization proxy guide, updated in May 2026, states: "We don’t recommend using netsh winhttp set proxy". The reasons listed are no proxy auto detection, no support for explicit PAC URLs and no proxy authentication. For an authenticated Proxys.io proxy, configure the Settings panel instead, or copy the existing WinINET configuration across with netsh winhttp import proxy source=ie.

Precedence between the two layers depends on whether a user is signed in, and Microsoft documents the order in the same guide. With an interactive user signed in, the Windows proxy wins and the netsh configuration is ignored. With no user signed in, the netsh configuration takes precedence, which can produce HTTP_E_STATUS_PROXY_AUTH_REQ or HTTP_E_STATUS_DENIED errors on background downloads. The import command takes a one-time snapshot, so run it again after every change you make in the Settings panel.

For command-line tools and environments, you can also set environment variables. These cover console programs that read them directly, including curl, git and most package managers, and unlike the Settings panel they carry the username and password inline, so no prompt appears. Open Command Prompt or PowerShell and run:

set HTTP_PROXY=http://user123:pass123@10.0.0.6:8080

set HTTPS_PROXY=http://user123:pass123@10.0.0.6:8080

On PowerShell the equivalent is $Env:HTTP_PROXY = "http://user123:pass123@10.0.0.6:8080". Variables set this way apply only to the current console session. To make them permanent, add them under System Properties > Advanced > Environment Variables, and remember that any tool storing its own proxy configuration, such as git or npm, will use that configuration ahead of the variables.

Proxy Settings in Browsers and Apps

Browser share decides how much one system setting actually achieves. StatCounter desktop browser data for June 2026 puts Chrome at 72.24% and Edge at 10.45%, so roughly 83% of desktop sessions run on Chromium browsers that read the Windows proxy by default. Firefox holds 6.31% and keeps its own settings. That gap is the usual reason one machine shows the proxy IP in Chrome and the real IP in Firefox at the same time.

Google Chrome and Microsoft Edge follow the Windows proxy but are not restricted to it. Chromium’s proxy documentation records that Chrome’s manual proxy model is closest to WinInet, and that a proxy can also be applied through the --proxy-server command line flag, an enterprise policy, or an extension. One limit is worth knowing: an HTTPS proxy scheme generally cannot be set through system proxy settings, so it needs a PAC script, a flag or a policy.

Mozilla Firefox has a separate proxy dialog and ignores the Windows panel unless you tell it otherwise. It also supports SOCKS directly, including the network.proxy.socks_remote_dns preference that decides whether hostnames resolve locally or at the proxy, an option Chrome does not expose.

1. Open Settings, go to General and scroll to Network Settings.
2. Click Settings, then choose Manual proxy configuration.
3. Enter the address and HTTP(S) port, or fill the SOCKS Host field with the SOCKS5 port.
4. Tick "Also use this proxy for HTTPS" if one endpoint serves both protocols.
5. Click OK and reload a page to apply the change.

Other applications split into three groups. Many follow the system proxy automatically. Some, including download managers and development tools, expose their own proxy fields, where you enter the same IP and port. Console tools read HTTP_PROXY and HTTPS_PROXY. Anything using SOCKS5 needs software that speaks the protocol natively, because the Windows 10 Settings panel is built around web proxies. HTTPS pages keep their padlock in every case, since the proxy relays encrypted data without decrypting it.

Troubleshooting a proxy that only half works

Connection limits explain slow pages more often than the proxy itself. Chromium documents a ceiling of 32 simultaneous connections across all domains when Chrome talks to an HTTP/1.1 proxy, against a much higher limit for HTTPS proxies negotiating HTTP/2. Heavy tab use or parallel automation against a single endpoint queues behind that ceiling long before bandwidth becomes the constraint. Splitting work across several Proxys.io IPs solves this more reliably than raising timeouts.

A proxy that fails once is deprioritised for five minutes. Chromium marks an unreachable proxy as bad and moves it to the end of the fallback list for that window, which makes intermittent failures look random rather than systematic. Clear the cached state at chrome://net-internals/#proxy, and capture a log through chrome://net-export/ if you need to see which proxy was selected for a specific request and why.

SOCKS5 authentication does not work in Chrome at all. Chromium’s documentation records that the browser supports no proxy authentication methods for SOCKSv5, and that hostnames are always resolved at the proxy with no local option. Use the HTTP(S) port for Chromium browsers and keep the SOCKS5 port for Firefox or software with native SOCKS5 support. IP allowlisting on your Proxys.io account removes the authentication problem in both cases.

Example: Using a Proxys.io Residential Proxy

As a practical example, suppose you have purchased a residential HTTP proxy from Proxys.io with these credentials: IP = 10.0.0.6, Port = 8080, Username = user123, Password = pass123. The configuration takes under a minute and applies to every Chromium browser on the machine immediately, with no restart needed. Firefox users repeat the same values inside the browser’s own Network Settings. To configure it in Windows 10:

1. Open Settings (Win+I) and go to Network & Internet > Proxy.
2. Under Manual proxy setup, turn on Use a proxy server. In the Address field enter 10.0.0.6 and in Port enter 8080. Click Save.
3. Now open a browser (Chrome/Edge). The first time you visit a website, a login prompt will appear. Enter user123 and pass123 when asked. From then on, browsing will go through the residential proxy.
4. Open the Proxys.io proxy checker and confirm that the outgoing IP matches the proxy rather than your own connection.

SOCKS5 takes a different route on Windows 10. The Settings panel is oriented to web proxies, so the SOCKS5 port belongs inside an application that supports the protocol: the SOCKS Host field in Firefox, an antidetect browser profile, or any tool with a native SOCKS5 option. HTTPS traffic works through the same panel entry as HTTP, because one endpoint handles both. Proxys.io issues an HTTP(S) port and a SOCKS5 port with every order, so no extra purchase is needed.

Choosing Proxy Types (Datacenter vs Residential)

Proxys.io offers datacenter and residential proxy IPs. Datacenter proxies come from server hosts and are faster and less expensive, whereas residential proxies are real ISP-assigned addresses that are harder for sites to classify. Both types support HTTP(S) and SOCKS5 connections. In Windows, the setup procedure is identical for either type: enter the given IP address and port in the proxy settings as shown above, then authenticate with your proxy username and password when prompted.

Provider accountability matters more than advertised pool size. Security firm Bitsight enumerated 53.3 million unique residential proxy exit nodes over 55 days between January and March 2026, yet the peak in any single 24 hour period was 8.4 million, about 16% of the cumulative total. The same study flagged 15.49% of those addresses for active malware infections. Headline pool figures and genuinely available clean IPs are not the same number, so ask providers how addresses are sourced.

Residential IP ranges now carry heavy background traffic, which changes how sites treat them. Infoblox reported in June 2026 that more than 65% of its Threat Defense Cloud customers queried domains tied to residential proxy services, with monthly DNS volume to those domains passing 500 billion by April 2026. Detection systems have adapted in response. For long-running projects, a documented datacenter pool often performs more predictably than an anonymous residential one.

Following these steps, your Windows 10 system will send network traffic through the specified proxy. Switching to a different proxy later means editing the same two fields: replace the IP and port in Settings > Network & Internet > Proxy and save. Windows caches nothing beyond that entry, though Chrome can hold a previous endpoint in its bad proxy list for five minutes, so clear it at chrome://net-internals/#proxy if a checker still returns the old address.