Node HandbookNODE HANDBOOK中文
Hiddify · Windows

Hiddify on Windows: “requires elevation” when TUN starts

The error names a helper binary and a Windows permission check. That places the failure on this machine, at the moment the client tries to start a process — before any question about the remote node has been asked.

Node Handbook editorial team ·

First: is this the same fault?

What you seeWhat it establishesNext step
The same configuration connects in system-proxy mode; VPN mode shows HiddifyCli.exe and requires elevationA local process needed for TUN was blocked by a Windows permission check; nothing about the remote node has been evaluatedSave version, dialog text and log; review the Windows elevation prompt and the install state
VPN mode fails without requires elevationCould be the virtual adapter, routing, DNS, or another core errorFind the first specific error; do not apply the permission conclusion here
Both system proxy and VPN mode failNode, subscription, core start and network are all still openRun the connection checklist first
After an update, the app shows CreateProcess failed; code 740 and will not reopenThis is the app restart stage, not the moment of starting HiddifyCli.exe on connectTreat it as a separate updater case and keep the installer and connection logs apart

The public report behind this page

Hiddify issue #2501 records one Windows case on Hiddify 5.5.5: the same configuration worked in system-proxy mode, VPN mode produced the HiddifyCli.exe error above, and the interface then reported a connection failure. As of 14 November 2026 the issue remained open. The reporter speculated that the app did not request elevation correctly and proposed “run as administrator” as a test to be verified — that is a hypothesis under test, not a confirmed root cause or an official fix.

Microsoft's system error reference defines 740 as ERROR_ELEVATION_REQUIRED: the requested operation requires elevation. The wording matches the report, but your own complete log still decides whether your case is the same one.

A second, easily confused record: issue #2402 describes setting Hiddify.exe to always run as administrator, after which the installer could not restart the application at all. That is an updater path. Do not apply this page's connection steps to it, and do not permanently tick the compatibility-page administrator option just to diagnose something.

Work through it in order, keeping a way back

  1. Protect the working path. Note the Hiddify version, the Windows build, the configuration name and the current proxy mode. If system-proxy mode works, do not delete the configuration or rewrite the subscription — you may need to switch back.
  2. Capture the first complete error. Retry VPN mode once; record the local time, the dialog text and the application log. Publish only masked logs: mask the subscription URL, token, account and node credentials. Confirm the text actually names HiddifyCli.exe rather than only a generic failure.
  3. Review the elevation step. Confirm the current session is allowed to approve a UAC prompt, and whether a prompt appeared, was declined, or was intercepted by security software. On a corporate device without administrator rights, contact the device administrator; do not work around the policy.
  4. Run one controlled contrast. Where you own the device and trust the installer source, close the app and reopen Hiddify via “Run as administrator”, then test VPN mode with the original configuration. Record whether the dialog and log change. This tests the permission difference only: success does not prove every version shares a program defect, and failure means returning to the original mode with the evidence kept.
  5. Rule out the updater variant of 740. If the error appears while the app restarts after an upgrade rather than when you click connect, check the updater scenario described in issue #2402. It is not a solution for this connection failure.
  6. Verify an actual connection. Only when the app reports a stable connection, the affected application completes an HTTPS request, and an exit-IP check shows the expected exit is the connection usable. If it still fails, add a masked log and version details to the upstream issue and wait for confirmation on that version.

Check the install and elevation state before changing anything

Three facts decide whether a permission error is plausible, and all three can be read without modifying the system:

  • Where the app lives. A client installed under a per-user directory and one installed under a machine-wide directory can inherit different launch contexts. Record the executable path from the shortcut or the process properties rather than guessing.
  • How the helper is launched. The error names a separate executable (HiddifyCli.exe), so the question is not whether Hiddify itself is elevated but whether the process it spawns at connect time is allowed to request elevation. A client running as a standard user can still normally trigger a UAC prompt — a refusal or a silent block is the interesting part.
  • What the policy layer says. On a domain-joined machine, AppLocker, Software Restriction Policies, or an endpoint-protection rule can block a helper binary without any visible prompt. In that case the dialog shows nothing about elevation because the request never reached the consent step.

A fourth signal is quieter: whether the same configuration ever worked in VPN mode on this machine. If it did and stopped after an update, the permission conclusion is weaker than the version-change conclusion, and the version is the variable to examine first.

EvidencePermission explanation plausibleWhat to check first
UAC prompt appears and is declinedYesWho can approve prompts on this device
No prompt appears at all, log still says elevation requiredNot establishedPolicy or security software blocking the helper before consent
Worked before, broke after an updateWeakVersion behaviour and the installer path
Never worked in VPN mode on this machinePossibleInstall location and the launch context of the helper

None of these entries proves a cause. They only tell you which single test is worth running next, which is the difference between a diagnosable case and a sequence of reinstalls.

Boundaries of this page

This site has not reproduced issue #2501 on a Windows machine running Hiddify 5.5.5, and there is no evidence that it affects every Windows user or every version. Running as administrator, reinstalling, disabling security software and downgrading are all unverified as general fixes — and disabling device protection to silence a TUN dialog is a bad trade regardless.

If you only need a browser or software that follows the system proxy, system-proxy mode is a legitimate temporary path. Its capture scope differs from VPN/TUN, so the two modes are not equivalent, and a working proxy mode does not mean TUN is healthy.

What to send upstream

  • Hiddify version, Windows build, and whether the device is domain-managed.
  • The complete first error line, including the executable name.
  • Whether the same configuration works in system-proxy mode.
  • UAC outcome: prompt shown and approved, prompt declined, no prompt, or blocked by security software.
  • The result of the “run as administrator” contrast, stated as a test result rather than a fix.
  • Whether the failure appears on a normal relaunch after the test.

Mask subscription URLs, tokens, UUIDs and account identifiers. A permission error is one of the few failures that can be reported completely without exposing a credential.