This one wastes days because of a single word. The subscription is already in the list, the nodes preview fine, updates succeed — and the profile still will not select. The log says:
An attempt was made to access a socket in a way forbidden by its access permissions
People read "subscription", delete the profile, re-import it, reset the network stack, reinstall the client. None of that touches the actual failure, because the failure is not in fetching the subscription. It is in selection, and selection crosses a Windows service boundary.
Locate the stage before you touch anything
Five stages exist between "I have a URL" and "traffic goes through". A different error string belongs to each:
| Symptom | Stage | Next step |
|---|---|---|
| Profile card will not select, socket permission error in the log | Windows HNS / socket permissions | Record the error, check and restart HNS |
Import shows client error(Connect)
|
Remote subscription fetch | Check import method, certificate, network reachability |
| Update succeeds, node list is empty | Profile content, override, parsing | Investigate empty-node handling |
| Selection works, but you end up offline | Nodes, rules, system proxy | Move to the system-proxy layer |
Deleting a profile acts on stage 2 and 3. The socket error lives at stage 4. That is the whole mistake, and it costs a reinstall every time.
Why a socket error points at a service
Clash Verge Rev on Windows runs its core as a service so that TUN and system proxy can work without an elevated UI. That means socket creation happens under the service's identity and its network namespace, not under your user account.
When the Windows Host Network Service (HNS) is not running correctly, socket creation inside that boundary is denied even though your account has every permission it needs. The client reports the denial verbatim, which is why the message mentions permissions — but the permissions being enforced are not yours to grant.
The fix the official FAQ actually describes
The project's Windows FAQ attributes this exact string to Host Network Service not running properly, and prescribes a restart rather than a reinstall:
- Quit Clash Verge Rev — fully, including the tray icon.
- Do not delete the subscription. It is not the problem and you will need the URL again.
- Open Windows Services and find Host Network Service.
- If it is stopped, start it. If it is running, restart it once.
- Reopen the client and try selecting the existing profile again.
If the error reproduces after that, keep the error line and stop changing things. Reinstalling the client is not a next step here; the client is the thing reporting a service-state problem.
The four pieces of evidence worth collecting first
If you are going to ask for help — or file an issue — these four turn a vague report into something diagnosable:
- Full client version and Windows build number. This failure is version-sensitive on both sides.
- Whether the subscription still updates, whether nodes preview, and whether only selection fails. That single sentence separates three of the five stages.
- The complete error line from the log with its timestamp, with the subscription URL, token, username and node passwords removed. Truncated error strings are the reason half of these threads go nowhere.
- Current state of Host Network Service: running or stopped. Nothing more.
What not to conclude
- "The client is broken, I need an older version." Possible, but a service state explains the identical error string far more often.
- "My subscription is dead." Test that separately: can it update? do nodes preview? If both work, the subscription is alive.
- "Windows permissions are wrong, let me take ownership of something." Do not start changing ACLs on service directories. The boundary being enforced is not an ACL you should be editing.
One detail that trips up the retest
After restarting HNS, the client may still hold a stale handle. Quit and reopen it before retesting, and retest by selecting the existing profile. Importing a fresh copy introduces a new variable and makes a success ambiguous — you will not know whether the restart fixed it or the re-import did.
The full write-up, including the verbatim error strings across the five stages and the evidence checklist in copyable form, is here: Clash Verge Rev cannot select a profile: socket permission error.
If instead the profile selects fine and the internet is what disappears, you are one stage further along — that case is the system-proxy one, and the check order there is completely different.
Top comments (0)