A proxy set in Windows 11 itself carries traffic from nearly every program on the computer: browsers, many desktop apps and plenty of background services. For a team, that is the right tool in a specific situation, such as a shared research PC, a virtual desktop used for regional checks, or a small group of machines that should always appear in one market. It is the wrong tool for a laptop someone also uses for email and client calls.
This guide covers the Settings app route, a PowerShell version for repeatable rollouts, the authentication step that catches most people out, and the checks to run before the machine is handed over.
Good and poor fits for a system-wide proxy
- Good fit: a dedicated workstation for competitor and pricing research, where every app should use the same market.
- Good fit: a separate Windows user account set aside for proxied work on an otherwise normal PC.
- Poor fit: a daily-use laptop. Video calls, file sync and updates would all run through the proxy and count towards your per-GB data. A browser-level setup, such as our Chrome guide describes, keeps the proxy contained.
The steps are the same for datacenter proxies and residential proxies.
What to prepare
From the dashboard, note the host (an IP address or hostname), the port, the username and the password. Our proxies sign in with host:port plus the username and password. Windows collects the login separately from the address, so have both to hand. Decide too which Windows account should carry the proxy, because the setting applies per user.
Configuring the proxy in Settings
- Open Settings from the Start menu, or press Windows + I.
- Choose Network & internet from the sidebar.
- Scroll down and open Proxy.
- Find Use a proxy server under Manual proxy setup and press Set up.
- Turn the Use a proxy server switch on.
- The host goes in Proxy IP address; the port goes in Port.
- Offices with intranet tools should also select Don't use the proxy server for local (intranet) addresses, which keeps internal systems off the proxy.
- Press Save.
You will notice there is no box for a username or password. That is normal for Windows: it asks for the login when the first program sends traffic through the proxy.
The login prompt, and the apps that never show one
Open a browser and load any page. A sign-in box appears and asks for the proxy credentials. Copy them from the dashboard character for character, since usernames often carry a region or session part, and allow the browser to save them, or the box will keep coming back.
Some programs have no way to show that prompt and simply report a connection error. For those, enter the proxy inside the program's own network settings, or use a desktop proxy client that supplies the credentials for them. If the PC sits in a fixed office, IP-whitelist authentication from the dashboard is another way around the prompt altogether.
Rolling out to several PCs with PowerShell
When more than one machine needs the same setup, a short script is more reliable than clicking through Settings each time. Run this in PowerShell under the Windows account that should use the proxy:
$reg = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings"
Set-ItemProperty -Path $reg -Name ProxyEnable -Value 1
Set-ItemProperty -Path $reg -Name ProxyServer -Value "HOST:PORT"To switch the proxy off again for that account:
$reg = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings"
Set-ItemProperty -Path $reg -Name ProxyEnable -Value 0The commands write the same per-user values that the Settings app writes, under the current user only, so other accounts on the PC are unaffected. Credentials are not stored this way, so the login prompt still appears on the first request.
Acceptance checks before handover
Before the machine goes to the team, load our IP checker in a browser. It should report the proxy's address and location. If the office address appears, the setting is off, the login was refused, or the program in use ignores the system proxy.
Second, open the DNS leak test on the same machine. Windows can send web traffic through the proxy while resolving site names over the normal connection, which leaves a record of the domains your team researched with the office provider. If that provider's resolvers appear, set DNS inside the application or use a client that forces lookups through the proxy.
Fault-finding
| Symptom | What to do |
|---|---|
| The credential box keeps reappearing | Re-enter the login slowly, accept the offer to remember it, and check for a missing region or session suffix. |
| No program can connect | Compare host and port with the dashboard and test the pair in our proxy checker to rule out a typo or an unreachable endpoint. |
| One program ignores the proxy | Not every app reads the Windows setting. Configure that app's own proxy fields instead. |
| Certain websites refuse the connection | Some sites turn away datacenter ranges. Use residential or mobile proxies for those, as their addresses come from home broadband and mobile carriers. |
| The proxy is still on after disabling it | If PowerShell set it up, set ProxyEnable back to 0 with the second script, or turn the switch off in Settings. |
Keeping costs predictable
Because everything on the machine uses the proxy, keep the research PC lean: pause file-sync clients and remove software it does not need, so your data goes on research rather than background downloads. For general browsing and light regional access, datacenter proxies are the economical choice. For demanding sites that are selective about the traffic they accept, residential premium proxies are the type to test. The proxies overview sets the four types side by side, and the pricing page lists what each costs per GB.
Use the machine for legitimate research on public pages, within each site's terms and the law that applies to your business.
