Material checked on 2026-11-14. Error strings are quoted verbatim so you can match them against your own log.
What this page is about
On Windows, starting Clash Verge Rev sometimes logs core IPC pipe did not become ready within 15s on the first attempt, while the next attempt succeeds and the proxy works afterwards. The right order is to confirm the final core state first, then deal with the first-attempt warning. The first red line alone does not justify concluding that the service is not installed, that the nodes are broken, or that TUN routing is at fault.
This page covers the startup sequence in Windows service mode. If every retry fails, or the service cannot be installed at all, go to service install failed. If the core and the system proxy are fine and only TUN breaks connectivity, go to no internet after enabling TUN.
Evidence and scope
Material checked 2026-11-09 (Beijing time). Official issue #8480 records a Windows 10 x64 case on the 2.5.8 stable client: configuration validation succeeded, the first service core start waited 15 seconds for the IPC pipe and then errored, and the client automatically retried and started the core within about two seconds. The reporter states that the proxy worked after the retry and that no pre-release build was tested. The issue remains a user report: it does not prove that every 2.5.8 installation shares the same root cause, and it is not a confirmed fix announcement.
Issue #8474 shows a different state that is easy to confuse with it: the interface says the core has started, but the control API does not respond, the latency test keeps spinning and traffic is not forwarded; restarting the core with the same configuration restores it. That case was Windows 11 in service mode with TUN enabled.
"First attempt timed out but the retry succeeded" and "the interface says started but the core is stuck" cannot share one conclusion. This site has not reproduced either case on these system combinations.
Judge the next step by the result, not the first line
| What the log and state show | What it can mean for now | Next step |
|---|---|---|
First attempt reports the 15-second IPC timeout, then Service started the core successfully appears and proxy requests work | The first attempt failed but that startup recovered | Record both attempt times and the version; do not uninstall the service or change nodes |
| The timeout is followed by repeated failures and the core stays down | No usable core baseline yet | Check service state, configuration validation and later errors; move to the service or core-start branch |
The interface shows the core running, but the latency test spins and /configs or rule-provider requests fail | "Process exists" is not the same as a working control API or forwarding | Save redacted GUI and core logs; work the stuck-control-API branch |
| Core and system proxy work, only TUN breaks connectivity | Core startup is no longer the prime suspect | Fix nodes and rules, then check the TUN service, interface, routes and DNS |
Check in order — one change at a time
1. Let the automatic retry finish. Look for the next Service started the core successfully after the first error, or for clear repeated failures. Do not keep clicking "restart core" during the retry window; that mixes up the timeline you are trying to read.
2. Confirm a real request. Keep the existing node and rules, disable TUN, use the system proxy to open an ordinary HTTPS page you normally reach, and check whether the client's connection list shows that request. If there is no entry, check whether the system proxy was actually written or whether the application bypasses it. A green interface indicator is not proof that proxying works.
3. Save one timeline. Record the Windows version, the Clash Verge Rev and Mihomo versions, the start mode (Service or Sidecar), how long configuration validation took, the time of the first error, and the time of the later success or failure. Keep only the redacted log lines adjacent to the fault; do not publish the subscription URL, tokens, node passwords or device paths.
4. Separate a cold start from a persistent failure. Quit the client and observe one more startup with the same configuration. If it happened once and the retry recovered, keep the evidence and watch the official issue. If it fails repeatedly, verify that the service runs, that versions match and that the configuration validates — and do not read "Windows cannot find the file" as "the subscription file is gone".
5. Branch only when the symptom matches. If the interface reports success but neither the control API nor traffic works, compare the GUI and core logs against the observation list in issue #8474. If only TUN fails, use the existing TUN decision table.
For a proxy that is still working, it is not worth deleting the service directory, clearing system certificates by hand or running repair scripts of unknown origin just to silence one startup warning that already recovered. If you report it upstream, a minimal reproducible sequence and a redacted timeline are far more useful than a screenshot of the dialog.
What cannot be concluded from here
- The 15-second value is the specific log line in that issue, not a fixed threshold for all versions. Wording and retry behaviour can change between builds.
- An automatic retry succeeding proves that this particular core start finished. It does not prove that every website, every rule or TUN itself works.
os error 2appears alongside the IPC pipe not being ready in that log. Those few words alone do not establish that a subscription file, a Geo data file or an antivirus product removed the core.- Issue #8480 does not provide a verified universal fix. If the problem keeps reproducing, keep the original configuration and version and follow the official issue instead of turning one machine's experience into everyone's solution.
Sources and verification date
Material checked 2026-11-09. Primary sources:
- Clash Verge Rev official repository, issue #8480 — first service core start waiting 15 seconds for the IPC pipe, then succeeding on retry.
- Clash Verge Rev official repository, issue #8474 — interface reports a running core while the control API and forwarding fail.
This article was assembled with AI assistance and edited by this site against a verifiable boundary. Neither report was reproduced here, and neither is presented as an official fix.
Frequently asked questions
The proxy works after the first error. Do I still need to reinstall the service?
Not yet. Confirm that the following log lines really show the core started, then verify with one real HTTPS request and the client's connection list. If it keeps working, keep the timeline and observe. Only check the service install and version if it fails repeatedly.
The log says Windows cannot find the specified file. Does that mean my profile was deleted?
You cannot infer that. In this case the complete error is that the core IPC pipe did not become ready within the wait window, and the retry then succeeded. Read the full context instead of quoting the second half of a Windows error string.
The interface says the core is running but pages still will not open. Why?
Core process state, control API response, system proxy settings and actual forwarding are separate checks. Confirm the connection list and the system proxy first; if control API requests also fail, work the stuck-core branch rather than switching nodes.
Is this always caused by TUN?
No. The report in issue #8480 happened with both TUN and the system proxy disabled. Only when the core and system proxy are verified working and connectivity fails after TUN is enabled does the TUN branch apply.
Can upgrading to a pre-release build fix it?
There is not enough evidence to recommend that. The original report did not test pre-release builds and the issue has no confirmed universal fix. Before upgrading, read the release notes, back up the configuration and record results under the same conditions.
Continue reading
the service will not install · no internet after enabling TUN · the full error-string index