Fix Windows TUN when FlClash is already elevated - #2380
Closed
cakeni wants to merge 9 commits into
Closed
Conversation
chen08209
force-pushed
the
dev
branch
4 times, most recently
from
September 1, 2026 01:44
7748c64 to
e17fe6d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #2368.
On Windows, an already-elevated FlClash still preferred the Helper service, which moved FlClashCore into Session 0. That defeats the user-session elevation path and matches the TUN/service-mode failure reproduced on Windows 11 25H2.
This keeps the existing Helper flow for normal unelevated launches, but when the GUI is already elevated it starts Core directly so the child inherits the elevated token and remains in the interactive user session.
A resolver regression test covers the elevated Windows path and verifies that the Helper is not probed.
Validation:
git diff --check. The local machine does not currently have a Flutter SDK available, so the Flutter test suite was not run locally.