Windows Store Apps Not Using the Clash Proxy? Remove the UWP Loopback Restriction with CheckNetIsolation

Before installing: check the build and download source

Clash Verge Rev is a desktop interface for managing profiles, proxy groups, and connection settings. The interface and the proxy core are separate parts: the core reads the active configuration, applies its rules, and makes outbound connections. Installing the interface is only the first step. To confirm that the setup works, you will also need a compatible profile, a running core, and a request that actually uses the proxy.

Start by checking the Windows edition and processor architecture. Open Settings → System → About. Most Windows 11 PCs with Intel or AMD processors use x64 software. A Windows on ARM device needs an ARM64 build if one is offered for the current release. Do not choose an installer solely because its filename contains “Windows”; compare the architecture and package notes with your device. If the release does not provide a build for your architecture, do not try to force-install a different one.

Get the installer from a source you can verify, and check its release information before running it. File formats and package names can change between releases, so do not assume that a particular extension or version number is always current. If a download page offers more than one Windows package, use the project’s release notes to identify the intended installer. Avoid repackaged installers from file-sharing sites, and do not treat a search result or an unfamiliar mirror as proof of authenticity.

Before updating an existing installation, note which profile is active and whether you have local overrides. An application update and a profile update are different operations: reinstalling the interface does not necessarily refresh a subscription, while replacing a profile can overwrite local changes. Keep a recoverable copy of any configuration you have edited yourself.

If you need an installation entry point, use the site’s download page and check the package details for your device before continuing. The listed package is an entry point, not a substitute for checking the release notes or the publisher shown by Windows.

Install Clash Verge Rev on Windows 11

Close older Clash interfaces before installing the new client. Two applications may compete to set the Windows system proxy, use the same local port, or start separate cores. If you have another proxy tool running, turn off its system proxy and TUN routing for the initial test. You can re-enable other software later, one application at a time, if you know how the tools are meant to coexist.

1. Locate the downloaded installer. Open File Explorer and go to the folder where your browser saves downloads, usually Downloads. Check that the filename and file type match the package described by the release information. If the browser reports an incomplete download, download it again rather than opening a partial file.
2. Review the Windows publisher prompt. If User Account Control asks whether the installer can make changes, check the app name and publisher information. Continue only when the prompt matches the software you intended to install and you trust the download source. A request for administrator permission does not, by itself, prove that a file is legitimate.
3. Follow the installer’s prompts. Choose the installation options presented by that release. If Windows offers an installation location or shortcut option, select what suits your account and device. Avoid adding unrelated software or changing security settings just to complete setup.
4. Launch the application once installation finishes. If the app asks to update a component, enable a service, or install a driver, read what that component does before approving. Core service and TUN-related permissions are not required merely to open the interface or import a profile.
5. Confirm that the window opens normally. Check the client’s About or settings page for the installed application and core information where available. Do not assume that a visible window means a core is running or that an imported profile has been activated.

Windows may show different prompts depending on the installer, account permissions, and security configuration. If the installation requires elevation, use an administrator account or contact the device administrator; do not disable User Account Control. On a managed work or school PC, application installation may be restricted by policy, and an administrator may need to approve the software.

Choose a simple first-run configuration

Keep the first test small: one client, one profile, and one selected proxy group. Leave advanced options such as TUN mode, LAN access, startup services, and custom DNS changes disabled until the basic profile works. This reduces the number of possible causes if the connection fails. Record the local listening port shown by the active configuration or client settings; example port values should not be mistaken for universal defaults.

Import a profile and select it

A profile can be a remote subscription URL, a downloaded configuration file, or a configuration created for a provider. These formats are not always interchangeable. Some subscriptions return a complete YAML configuration with proxy definitions, groups, and rules. Others provide a list of nodes that needs a compatible client template or provider-specific setup. Use the format supplied for Clash-compatible clients, and ask the provider if its instructions do not identify the supported format.

1. Open profile management. In Clash Verge Rev, locate the Profiles or configuration-management area. Interface labels can differ between releases, but profile import and update controls are normally grouped together.
2. Choose the appropriate import method. For a subscription, select the URL-based import option and paste the complete URL. For a local file, use the file import control and select the configuration you intend to use. Check for accidental spaces or missing characters if the link was copied from a message.
3. Wait for the import or download to finish. Read any error text rather than repeatedly clicking update. A sign-in error such as HTTP 401 or 403 may indicate invalid credentials, an expired link, an account restriction, or a provider-side access rule. A 404 can mean that the address is wrong or no longer available.
4. Select the imported profile. A successful download does not necessarily activate that profile. Click or otherwise select it in the profile list, then check that the client identifies it as the current configuration.
5. Open the proxy group view. Confirm that expected groups or nodes appear. Choose a usable proxy in the group that handles the traffic you intend to test. If the list is empty, review the import result and configuration format before changing Windows networking settings.

Keep the profile’s original purpose in mind. A provider may supply only proxy nodes, while the client needs groups and rules to decide where traffic goes. If a profile imports but the expected groups are missing, do not invent a replacement configuration without understanding the provider’s format. A malformed or incomplete YAML file can fail validation even when the subscription link itself downloads successfully.

After selecting the profile, check the client’s logs or status area for parsing errors. Errors about an unsupported proxy type or configuration field may indicate that the running core is too old for the profile, or that the subscription was designed for a different client. Updating the profile repeatedly will not fix a feature mismatch. Check the core information and the provider’s compatibility notes first.

Verify the core, proxy, and connection

First confirm that the core is running and that the selected configuration has loaded. Open the client’s logs and look for a startup or configuration-parsing error. If the client shows a core status or version, note it when troubleshooting. The GUI manages settings and displays activity; the core performs the configuration-dependent routing. A profile that uses a protocol or field unsupported by the active core may not work even though the profile is visible in the interface.

Next, check the selected proxy group and mode. In Rule mode, the configuration’s rules decide whether a connection is direct or uses a proxy policy. Selecting a node in one group does not mean every application or destination will use that node: the matching rule may send the request to another group or to DIRECT. For an initial test, choose a proxy group and node you recognize, and inspect the connection or log entry for the destination you test.

Then verify the local listener and Windows system proxy separately. The system proxy usually points applications that honor Windows proxy settings to a local address and port. The address and port must match a listener that is actually enabled in the active configuration. Do not copy a port from an online example without checking your client’s current settings. Also note that some programs ignore the Windows system proxy or use their own proxy settings, so a working browser does not prove that every application is configured to use the client.

For a controlled test, enable the client’s system proxy only after the core and profile are ready. Open a site that can confirm the route you intend to test, then inspect the client’s connection list or logs. Check the matched rule, policy group, and outbound route where those details are available. If the request is marked direct, it is not a valid test of the selected proxy node. If no request appears, the application may not use the system proxy, or its connection may not be reaching the local listener.

Leave LAN access disabled for a personal first-run setup unless another device specifically needs to connect through your PC. Enabling LAN listening can expose a local proxy service to other devices on the network, depending on the bind address and firewall rules. TUN mode is also a separate networking setup: it can route traffic from apps that ignore system proxy settings, but it may require elevated permissions and a compatible driver. Add it only after the ordinary proxy path is understood.

Fix security prompts and startup problems

If Windows SmartScreen says it protected your PC, pause and verify the file before taking action. Check that you downloaded the intended release from a source you trust, that the filename and publisher information are consistent with the release notes, and that the download completed. A warning can occur when Windows has limited reputation information for an application, but that is not a reason to ignore the warning for an unverified file. If you cannot establish where the installer came from, cancel it and obtain a trusted copy.

If the installer is blocked by an organization’s policy, do not try to bypass device management controls. Ask the administrator to review the package. On a personal device, check Windows Security’s protection history for the specific event and read the detection name. If Windows quarantined a file, verify the source and file identity before considering any restore action. Do not turn off real-time protection as a routine installation step.

If the app does not open after installation, restart Windows once and try launching it from the Start menu. Check whether another instance is already running in the notification area or Task Manager. If a previous proxy client is still active, turn off its system proxy and exit it before starting Clash Verge Rev again. If the interface opens and then closes, record any visible message and inspect the client logs or Windows Event Viewer’s application logs rather than repeatedly reinstalling without a diagnosis.

If the interface opens but the core does not start, confirm that a profile is selected and look for YAML parsing, unsupported-field, or port-binding errors. A port conflict can occur when another application already listens on the same local port. Close the competing application or change the listening port in the appropriate configuration, then make sure the Windows system proxy points to the new port. Do not edit a provider-managed profile if its updates will overwrite your changes; use the client’s supported override mechanism or consult the provider’s instructions.

If the core starts but there is no connection, test one layer at a time:

• Profile: Confirm that it is current, selected, and free of parsing errors. If nodes or groups are missing, check the subscription format and provider status.
• Proxy selection: Choose an available node in the policy group used by the test. A timeout can also reflect an unreachable server, invalid credentials, DNS failure, or a blocked destination.
• System proxy: Check that it is enabled in the client and points to the active listener. If the port changed, update the corresponding setting rather than assuming Windows followed it automatically.
• Routing rule: Inspect the connection entry to see whether the destination was sent to the selected group, another group, or DIRECT. Change the test route only when you understand which rule is responsible.
• Other network software: Temporarily disable overlapping VPN or proxy routing for diagnosis, then restore tools individually. Multiple programs changing proxy settings or routes can make results inconsistent.

Use the client’s normal exit and uninstall controls when removing it. Before uninstalling, save any configuration you need and turn off the system proxy from the client if it is still running. Removing the application does not necessarily revoke a subscription URL or erase a copy of a configuration saved elsewhere; handle those separately if the device is shared.