When Clash looks fine everywhere except UWP

You already flipped the system proxy toggle in your Clash-class client on Windows 11. Win32 browsers pick up 127.0.0.1 and traffic flows. Then you open the Microsoft Store, an inbox Xbox companion app, or another packaged app from the Store, and the story falls apart: endless loading, sign-in failures, or downloads that never start. Nothing in the Clash log looks obviously wrong, because the traffic never reaches the local listener in the first place.

This pattern is frustrating precisely because it feels like random breakage. In practice it is usually one of two things: the app is still trying to use the OS proxy but cannot complete the handshake to localhost, or the app ignores WinINET-style proxy settings entirely and goes direct—loopback fixes only the first family of issues. This article focuses on the localhost / loopback wall that sandboxes UWP traffic, and how to align it with Clash without turning your machine into a research project.

Why UWP blocks localhost by default

Universal Windows Platform applications run with tighter network isolation than classic desktop programs. Microsoft separates “internet-facing” sockets from the loopback interface to reduce the blast radius if a Store app is compromised: a malicious package should not silently probe services you run on 127.0.0.1. The side effect is legitimate: when your proxy listens on localhost—as Clash typically does for mixed HTTP and SOCKS—the sandbox may refuse the connection unless you explicitly allow it.

That policy is implemented through loopback isolation. Unless an app is on the exemption list, outbound calls that resolve to loopback can fail at the platform layer even when user-mode code believes it configured a proxy correctly. This is different from forgetting to enable system proxy; it is different from a bad remote node; it is the operating system saying “this AppContainer may not talk to that address.” Bridging that gap is what administrators call a loopback exemption, sometimes shortened to “loopback” in casual forum posts about UWP proxy troubleshooting.

What must be true on the Clash side first

Before you touch isolation settings, confirm the basics so you do not chase the wrong failure mode. Your client should expose a mixed port (or distinct HTTP and SOCKS ports) on loopback, and the system proxy option should point Windows at that listener—usually 127.0.0.1 with the mixed port number. If you use a GUI such as Clash Verge Rev, walk the first-run checklist in our Clash Verge Rev Windows setup guide so profiles, modes, and firewall prompts are settled.

DNS still matters: if Store endpoints resolve oddly because of fake-ip or aggressive rules, you can see symptoms that resemble loopback failure. A quick sanity check is to reproduce the issue with a narrow rule that forces the Store hostname through a known-good proxy group while watching the core log. If nothing ever hits the log when the Store tries to update, loopback is a prime suspect. If connections appear but TLS fails, pivot to rules and nodes instead.

The built-in tool: CheckNetIsolation

Windows ships CheckNetIsolation.exe for developers who need to test loopback scenarios. The relevant subcommand is LoopbackExempt. You will run it elevated, because you are changing a machine-wide exemption table that applies to AppContainer sandboxes.

The identifier you pass is not the friendly app name from the Start menu; it is the Package Family Name (PFN), a stable string that looks like Microsoft.WindowsStore_8wekyb3d8bbwe. PFNs can change between major OS refreshes, so treat examples in older blog posts as hints, not gospel. The reliable workflow is always: query the PFN on your PC, add the exemption, then verify.

Step 1: Find the Package Family Name in PowerShell

Open Windows Terminal or PowerShell as a normal user first—querying packages does not require elevation. To hunt the Store:

Get-AppxPackage *WindowsStore* | Select-Object Name, PackageFamilyName

For Xbox-related packages, widen the filter:

Get-AppxPackage *Xbox* | Select-Object Name, PackageFamilyName

Copy the PackageFamilyName for the app you care about into Notepad. If you see multiple entries, match the Name column to the specific experience you are fixing—there are several Xbox modules, and you may need more than one exemption.

Step 2: Add a loopback exemption (elevated)

Now open PowerShell as Administrator. Add an exemption with:

CheckNetIsolation LoopbackExempt -a -n="YOUR_PACKAGE_FAMILY_NAME_HERE"

Replace the placeholder with the PFN you copied. The -a switch adds an allow rule. If the command succeeds, Windows updates the exemption store immediately; rebooting is usually unnecessary for testing.

To inspect what the system thinks is exempt, you can list entries:

CheckNetIsolation LoopbackExempt -s

If you add the wrong PFN, you can remove a specific entry with -d using the same -n value, then re-add carefully. Keeping a short note of which PFNs you changed makes rollback painless when you rebuild a machine.

Scope consciously. Loopback exemptions broaden what a sandboxed app may reach on localhost. Grant them to packages you recognize, and remove ones you no longer need. This is standard developer hygiene, not paranoia.

Step 3: Verify with Microsoft Store and updates

Close the Store completely using Task Manager if it refuses to exit politely, then relaunch it. Trigger a small action that previously failed: app updates, a free app install, or library refresh. Watch your Clash or Mihomo log for new flows to the appropriate policy group. Success looks boring: ordinary HTTPS entries, no mysterious instant timeouts to the local proxy address.

If the UI still stalls, capture whether any traffic hits the core at all. Silence usually means either the wrong PFN was exempted—add adjacent Xbox or Store helper packages—or the app is not using the system proxy path you think it is. Some components talk direct to CDNs by design; rule tuning becomes relevant again.

GUI helpers and bulk exemption scripts

Community tools exist that wrap the same underlying APIs with checkboxes instead of PFN typing. If you prefer a visual list of installed packages, search for reputable “loopback exemption” utilities built for Windows 10 and 11. Read the publisher notes carefully; you are granting localhost access broadly when you select many entries at once.

Automating exemptions across dozens of PFNs is attractive on lab machines, risky on personal laptops. A lighter pattern is to exempt only the Store and the Xbox modules you actively use, then expand if a secondary app complains. Document anything you script, because Windows feature updates occasionally rename or split packages.

When loopback is the wrong layer: TUN mode

Loopback fixes AppContainer restrictions around localhost listeners. It does not force every binary to honor WinINET proxy settings. If you have confirmed exemptions and still see stubborn direct traffic, consider TUN mode, which moves interception to the IP layer and can cover binaries that bypass traditional proxy configuration entirely. Our Clash TUN mode guide walks through prerequisites, DNS alignment, and realistic limits.

TUN is not a moral upgrade; it is a different contract with the OS. You will deal with adapter priority, driver prompts, and coexistence with corporate VPNs. On Windows 11 many users run system proxy plus selective loopback exemptions for Store apps, then enable TUN only when a specific game launcher or IDE refuses both patterns. Layer solutions instead of enabling everything at once.

Troubleshooting checklist

  • Double-check PFN spelling: One mistyped character and the exemption silently targets nothing useful.
  • Match architecture and scope: Some experiences span multiple packages; exempt each participant you identify in logs.
  • Firewall prompts: Windows Defender can block the Clash executable even when loopback is fine. Confirm outbound rules for your client.
  • Corporate policy: Managed PCs can restrict Store behavior independent of proxies. Loopback cannot override domain policy.
  • Conflicting VPNs: Another filter driver may reorder interfaces after sleep. A quick disable-test helps isolate the culprit.
  • DNS split-brain: If Store endpoints resolve to unexpected regions, revisit fake-ip and rule order before another round of isolation tweaks.

If your symptom is “Clash says connected but pages do not load,” start with log-first triage in our connected-but-no-Internet troubleshooting article. It complements this piece: loopback fixes a Windows platform edge case, while DNS and rule ordering fix a different class of silent failures.

When you want step-by-step menus beyond isolation commands, the Clash documentation hub collects tutorials that align with maintained clients, so you can confirm mixed ports and modes before spending another hour inside CheckNetIsolation output.

Closing: platform rules, not mystery bugs

Seeing Microsoft Store failures while Chrome works is disorienting, but the explanation is usually mundane: UWP sandboxes enforce loopback policy, Clash listens on localhost, and those two facts meet at the system proxy hop. Granting a narrow loopback exemption restores the handshake path without abandoning your profile. Compared with constantly swapping nodes, that diagnosis saves hours.

When you want a maintained installer path and documentation that stays aligned with modern Mihomo-based clients, browse the Clash official home page for context, then keep daily downloads on our curated channel rather than chasing random mirrors. A stable client plus a clear mental model of Windows networking beats superstition every time.

→ Download Clash for free and experience the difference

Download Clash from this site