How to Set Up a Proxy for Windows 11 System Including UWP Apps and Microsoft Store

The standard proxy setup in the browser only partially solves the problem — most system applications, the Microsoft Store, and UWP programs (those installed from the Windows Store) operate under their own rules and ignore the usual settings. If you manage accounts in an anti-detect browser, work with advertising cabinets, or simply want all traffic to go through one IP — a full system setup is necessary. In this guide, we will break everything down step by step: from the built-in tools of Windows 11 to solving the problem with "stubborn" UWP applications.

Why a system proxy setup is needed — and not just in the browser

Most people set up proxies only in the browser — Chrome, Firefox, or in anti-detect browsers like Dolphin Anty or AdsPower. This works for web surfing, but outside the browser, traffic still goes from your real IP. This creates serious problems in several scenarios:

• Traffic arbitrage: if you work with multiple Facebook Ads or TikTok Ads accounts, some system requests may "leak" your real IP and link accounts together.
• SMM agencies: auto-posting applications, notifications, synchronization — all of this bypasses the browser proxy.
• Microsoft Store and UWP: standard Windows applications — Mail, Calendar, Xbox, Store apps — operate in an isolated environment and ignore browser proxy settings.
• Price monitoring and parsing: desktop clients for parsers and monitoring programs for Wildberries or Ozon require a system proxy.
• Security: a system proxy provides centralized control over all traffic from the machine.

In short: if it is important for you that all traffic from the computer goes through one IP — browser settings won't help. A system configuration is needed, and that is what we will address now.

What type of proxy to choose for Windows 11

Before proceeding to the setup, it is important to understand: Windows 11 natively supports only HTTP/HTTPS proxies through the built-in "Settings". SOCKS5 — a more flexible protocol — requires additional tools. Here is a brief comparison:

For tasks related to social media and advertising cabinets, the optimal choice is residential proxies: they have real IPs of home users, making them virtually indistinguishable from a regular internet connection. For parsing marketplaces and technical tasks, faster and more affordable datacenter proxies will suffice.

Setting up a proxy through Windows 11 "Settings" (HTTP/HTTPS)

This is the simplest way — built into the system. It is suitable for HTTP and HTTPS proxies. Most browsers and some system applications will automatically use these settings.

Step-by-step instructions:

1. Press Win + I — the Windows 11 "Settings" will open.
2. Go to "Network & Internet" → "Proxy".
3. Make sure the "Automatically detect settings" option is enabled — this allows the system to apply the proxy to all compatible applications.
4. In the "Manual proxy setup" section, click "Setup".
5. Toggle the switch to "On".
6. In the "Proxy server address" field, enter the IP address of your proxy (for example: 185.220.101.45).
7. In the "Port" field, enter the port number (for example: 8080 or 3128).
8. If the proxy requires authentication — enable the "Use a proxy server for local addresses" switch and enter the username/password upon first connection (Windows will prompt for them automatically).
9. Click "Save".

After saving the settings, Edge, Internet Explorer, and most Win32 applications will start using the proxy. However, UWP applications (Microsoft Store, Mail, Weather, Xbox) will not. More on this in the section below.

Setting up via PAC file: flexible traffic management

A PAC file (Proxy Auto-Configuration) is a small script that tells Windows which traffic to route through the proxy and which to send directly. This is convenient if you want, for example, to route only foreign sites through the proxy while accessing Russian sites directly.

How to set up a PAC file in Windows 11:

1. Create a text file with the extension .pac, for example proxy.pac, and save it on your disk, for example at C:\proxy\proxy.pac.
2. The content of the file for a simple "all traffic through proxy" scenario:

function FindProxyForURL(url, host) {
    // Local addresses — direct
    if (isPlainHostName(host) || 
        shExpMatch(host, "*.local") || 
        isInNet(host, "192.168.0.0", "255.255.0.0") ||
        isInNet(host, "10.0.0.0", "255.0.0.0")) {
        return "DIRECT";
    }
    // Everything else — through proxy
    return "PROXY 185.220.101.45:8080";
}

3. Open "Settings" → "Network & Internet" → "Proxy".
4. In the "Automatic proxy setup" section, click "Setup".
5. Enable the "Use setup script" switch.
6. In the "Script address" field, enter the path to the file in the format: file:///C:/proxy/proxy.pac
7. Click "Save".

A PAC file is a powerful tool, but like manual setup, it does not solve the problem for UWP applications. A different approach is needed for them.

Why UWP applications and the Microsoft Store do not see the proxy

This is one of the most common questions when setting up a proxy on Windows 11. You did everything right, the browser works through the proxy — but the Microsoft Store still loads with your real IP. Why?

UWP applications (Universal Windows Platform) are programs from the Microsoft Store: Mail, Calendar, Xbox, Photos, Movies & TV, as well as many third-party applications. They operate in an isolated "sandbox" with limited permissions and do not have access to the system's WinINet proxy settings — the ones you set in "Settings".

Technically, this is because UWP applications use their own network stack WinRT/AppContainer, rather than WinINet, which is used in classic Win32 applications (Chrome, Firefox, regular programs). Microsoft specifically isolated them for security reasons — but this creates a headache when setting up a proxy.

How to make UWP applications work through a proxy: 3 methods

The good news: a solution exists. There are three working methods — from simple to advanced.

Method 1: CheckNetIsolation — Microsoft's official tool

Windows 11 includes a built-in command-line tool CheckNetIsolation, which allows you to remove network isolation from a specific UWP application and allow it to use the system proxy.

1. Open PowerShell as Administrator (right-click on the Start menu → "Terminal (Administrator)").
2. First, find out the Package Family Name of the desired application. For the Microsoft Store, run:

Get-AppxPackage | Select-Object Name, PackageFamilyName | Sort-Object Name

3. Find the desired application in the list and copy its PackageFamilyName.
4. Run the command to remove isolation (example for Microsoft Store):

CheckNetIsolation LoopbackExempt -a -n="Microsoft.WindowsStore_8wekyb3d8bbwe"

5. Restart the application. It should now use the system proxy.
6. To remove isolation from all UWP applications at once (less secure, but convenient):

foreach ($app in (Get-AppxPackage)) { 
    CheckNetIsolation LoopbackExempt -a -n="$($app.PackageFamilyName)" 
}

Method 2: Proxifier — complete control over traffic

Proxifier is a paid application (there is a trial period) that intercepts all network traffic at the system level and routes it through a proxy. This includes UWP applications, system services, and everything else. This is the most reliable way for a full system proxy.

1. Download and install Proxifier from the official website.
2. Open the program, go to Profile → Proxy Servers → Add.
3. Enter the proxy details: address, port, select the protocol (HTTPS or SOCKS5).
4. If authentication is required — enter the username and password.
5. Click "Check" to test the connection.
6. Go to Profile → Proxification Rules. By default, there is a Default rule — set your proxy for it.
7. Click OK. Proxifier will start intercepting all traffic, including UWP.

Method 3: Clash for Windows / Mihomo — for advanced users

Clash for Windows (or its fork Mihomo) is an open-source application that works as a system proxy client. It can operate in TUN mode, which intercepts all traffic at the network adapter level — including UWP and any other applications.

1. Install Clash for Windows.
2. In the program settings, enable "System Proxy" — this will cover standard applications.
3. For full coverage, enable "TUN Mode" — it creates a virtual network adapter and intercepts all system traffic.
4. Add your proxy details to the configuration file in YAML format.
5. Select the desired profile and activate the connection.

Clash is a free tool, but it requires a bit more technical knowledge for initial setup. However, once configured, it works reliably and covers 100% of the traffic.

System SOCKS5 proxy: setup through third-party tools

Windows 11 does not natively support SOCKS5 in the "Settings" section. However, SOCKS5 is a more universal protocol: it works with any type of traffic (not just HTTP), making it preferable for arbitrage tasks and social media work. Here’s how to connect it system-wide.

Option A: through Proxifier

When adding a proxy in Proxifier, select the SOCKS5 type instead of HTTPS. Everything else is similar to what has been described above. Proxifier works great with SOCKS5 and routes it to all applications, including UWP.

Option B: through a local HTTP tunnel

Another way is to use a local proxy converter that takes SOCKS5 and outputs it as HTTP on a local port. The program Privoxy or 3proxy can handle this task:

1. Install Privoxy or 3proxy.
2. In the configuration, specify your SOCKS5 proxy as upstream.
3. The program will create a local HTTP proxy, for example at 127.0.0.1:8118.
4. Specify this local address in the Windows 11 system settings as the HTTP proxy.
5. Now all traffic goes: application → local HTTP → SOCKS5 → internet.

This method is a bit more complex, but it works without third-party paid programs. For most tasks of arbitrage specialists and SMM professionals, it is easier to use Proxifier — it resolves everything in a few clicks.

How to check that all traffic is going through the proxy

After setting up, make sure that the proxy is working correctly. Here are a few ways to check:

Method 1: Check IP in the browser

Open any browser and go to the site 2ip.ru or whatismyip.com. If the IP of your proxy is displayed instead of your real one — everything is working.

Method 2: Check via PowerShell

Open PowerShell and run the command. It will show which IP the external service sees when making a request from the command line:

Invoke-WebRequest -Uri "https://api.ipify.org" | Select-Object -ExpandProperty Content

If the result matches the IP of your proxy — the system proxy works for PowerShell and Win32 applications.

Method 3: Check UWP via Microsoft Store

Open the Microsoft Store and try to update an application or go to the "Library" section. If the update goes through and you see traffic from the Store in Proxifier (or another tool) — UWP applications are also working through the proxy.

Method 4: Wireshark — complete traffic check

For advanced checking, use Wireshark — a free traffic analyzer. Start packet capture and ensure that all outgoing connections go to the IP of your proxy, not directly to the end servers.

System proxy + anti-detect browser: how to combine

If you are using anti-detect browsers — Dolphin Anty, AdsPower, GoLogin, Multilogin, or Octo Browser — it is important to understand how they interact with the system proxy. Incorrect configuration can lead to conflicts or leaks of your real IP.

Scenario 1: System proxy + anti-detect for different tasks

This is the most common scenario for arbitrage specialists. The system proxy is used for "background" tasks (updates, Microsoft Store, system notifications), while in the anti-detect browser, each profile has its own proxy for a specific account.

In this case, do not use Proxifier to intercept the traffic of the anti-detect browser — it should manage its proxies independently. In Proxifier settings, create an exclusion rule for the executable files of Dolphin Anty or AdsPower, setting the action to "Direct".

Scenario 2: One proxy for everything

If you need both system traffic and the anti-detect browser to work through the same proxy — set up the proxy in both the system and in each profile of the anti-detect browser separately. Duplication does not create problems: the browser will use its settings, and the system will use its own.

Important point: DNS leaks

When using a system proxy, it is important to ensure that DNS requests also go through the proxy, not directly from your real IP. This is especially critical for arbitrage specialists: Facebook and TikTok analyze not only IP but also DNS patterns. Proxifier and Clash in TUN mode solve this problem automatically.

For most tasks — arbitrage, SMM, price monitoring — the optimal solution is: system setup HTTP + CheckNetIsolation for UWP + Proxifier for complete control. This covers 99% of scenarios without unnecessary complexity.

For working with Facebook Ads and TikTok Ads, where maximum trust in the IP is important, it is worth using mobile proxies — they mimic the traffic of real mobile users and raise fewer suspicions among platform algorithms.

Conclusion

Setting up a proxy for the entire Windows 11 system is a task that is solved step by step. The built-in "Settings" cover most browsers and Win32 applications, but UWP programs and the Microsoft Store require additional actions. Use CheckNetIsolation for targeted solutions or Proxifier — if you need complete control over all traffic without exceptions.

Key takeaways from this guide:

• The standard setup in "Settings" works for browsers and Win32 applications, but not for UWP.
• UWP applications (Microsoft Store, Mail, Xbox) need to be unlocked via CheckNetIsolation or Proxifier.
• SOCKS5 is not natively supported in Windows 11 — use Proxifier or Clash.
• Always check for DNS leaks: it is not enough to route HTTP through a proxy; it is important that DNS does not reveal the real IP either.
• When working with anti-detect browsers (Dolphin Anty, AdsPower, GoLogin), set up proxies both in the system and in each profile separately.

If you are setting up a system proxy for working with advertising cabinets, managing social media accounts, or monitoring marketplaces — we recommend paying attention to residential proxies: they provide a high level of trust from platforms, minimal risk of bans, and stable operation both in the browser and at the system level.