Clash Verge Rev Service Mode Failed on Windows 11

Service Mode is not required for ordinary system proxy use

The Clash Verge Rev official terminology guide gives Service Mode a narrow purpose. An elevated clash-verge-service process launches the proxy core, allowing TUN to run while the visible Clash Verge Rev application is opened as a normal user. The service is independent of the interface process and may continue in the background after the interface exits.

This distinction prevents a great deal of unnecessary repair work. If you use only system proxy and applications can already reach the local proxy port, a failed Service Mode installation does not prove that the subscription, nodes, profile, or Mihomo core is broken. Service Mode becomes important when you specifically need TUN and do not want to launch the full interface with administrator rights on every start.

Define the desired outcome before making changes. If the requirement is only to restore browser access, disable TUN and prove system proxy first. If the requirement is non-administrator TUN, continue with the service checks below. That one decision keeps network troubleshooting separate from operating-system permission troubleshooting.

Preserve the original error and complete four preflight checks

Installing a service changes Windows system state. Before retrying, record the Clash Verge Rev version, Windows edition and build, package architecture, and the exact original error. Take a screenshot only after hiding usernames and subscription details. Repeatedly pressing Install can create overlapping elevation prompts, a stale interface status, and a service that is still stopping, making the sequence harder to understand.

• Package and source: confirm that the application came from the official Windows release and that its x64 or ARM64 architecture matches the PC. Avoid mixing a portable folder, an old installed copy, and a shortcut to a third location.
• Running processes: exit Clash Verge Rev normally, check the notification area, and make sure another Windows user session is not running a second interface copy.
• Elevation: service installation requires approval through Windows User Account Control. A denied, expired, or organization-blocked prompt cannot be completed silently by the interface.
• Security events: inspect Microsoft Defender Protection History and any managed security product for a quarantined service executable or Mihomo core.

The official Windows FAQ also distinguishes package and display failures from service failures. A wrong architecture can produce “This app can't run on your PC,” while a missing or disabled WebView2 runtime can prevent the interface from appearing. Fix those prerequisites before diagnosing the service button, because an application that never loaded correctly cannot report service state reliably.

On a company-managed PC, a local account may see a UAC prompt but still be blocked from registering services by policy. Preserve the error code and official executable path for the administrator. Disabling all endpoint protection is neither a safe nor a reliable substitute for authorization.

Reinstall the service once, with a reversible sequence

After the preflight, use only the service-management entry bundled with the current official installation. Labels can differ slightly between releases, but the sequence should remain controlled: record state, remove a stale registration, restart Windows, install once, and verify. Do not alternate between the UI and unrelated scripts whose version and origin cannot be established.

1. Back up Clash Verge Rev settings, record the current Service Mode and TUN status, and turn TUN off.
2. Use the application's own Service Mode area to uninstall or repair the service. If the current official installation directory explicitly includes its service uninstaller, use only that matching copy.
3. Restart Windows normally so a service pending deletion and any locked binaries are fully released.
4. Launch Clash Verge Rev from the current official installation, press the service Install action once, and complete the UAC prompt.
5. Wait for the status to refresh, exit normally, then reopen the interface as a standard user and check Service Mode again.

If the application's own removal action reports failure, stop and keep the exact message instead of manually deleting arbitrary registry entries or service files. A partial manual cleanup can erase the evidence needed to distinguish a permissions failure from a version conflict.

Let the failed stage determine the next check

“Installation failed” is an outcome, not a cause. Preserve the dialog text and the time it occurred, then use the stage of the failure to narrow the evidence. The official issue tracker, including issue #4957, shows that service installation has failed in particular version and environment combinations. An issue report is useful comparison material, but it cannot replace the log and version from your own machine.

When submitting a new report, include the application version, package architecture, Windows build, reproducible steps, and the first concrete error after the service action. State whether the interface was installed or portable, whether a previous fork existed, and whether UAC appeared. Remove subscription URLs, proxy server details, Windows account names, and unrelated log history.

A closed report does not necessarily mean every later symptom has the same fix. Compare exact error strings and affected versions. If they differ, treat your case as a new observation rather than copying commands written for an older binary layout.

Verify the service, core, and TUN as separate checkpoints

After the status changes to installed, do not enable every networking option at once. Reopen Clash Verge Rev as a standard user with TUN off, start the core, and confirm that the Proxies and Logs views load. This proves that the ordinary configuration and core path work independently of TUN. Next, enable only TUN and generate traffic from one test program that does not normally follow system proxy. Look for that request in the connection list.

If Service Mode remains installed but TUN cannot be created, the investigation has moved away from service registration. Check the Mihomo core error, firewall rules, virtual adapters, route conflicts, and other VPN software. The official terminology guide notes that the relevant Mihomo executables need firewall allowance; use the filenames from the current official build rather than copying an old path literally.

A useful success test has three results: Service Mode remains installed after a reboot; Clash Verge Rev opens without administrator elevation; and TUN traffic appears in the connection view while the selected profile is active. A green switch without traffic verifies only the interface state, while successful system-proxy browsing verifies a different path.

If service installation cannot be authorized yet, turn TUN off and continue with system proxy where appropriate. Temporarily running the verified official client as administrator can help determine whether the remaining issue is purely permission-related, but it is not a reason to ignore package provenance or logs, and it should not silently become the permanent workaround.

Official sources and version scope

• github.com/clash-verge-rev/clash-verge-rev.github.io/blob/main/docs/guide/term.md
• github.com/clash-verge-rev/clash-verge-rev.github.io/blob/main/docs/faq/windows.md
• github.com/clash-verge-rev/clash-verge-rev/releases/tag/v2.5.2
• github.com/clash-verge-rev/clash-verge-rev/issues/4957