On this page
Decide whether this upgrade fits your needs
FlClash v0.8.97 was released as a stable version on 9/10/2026. The official notes describe more than a small patch: they cover the interface and localization, app and window layer, desktop packaging, Android VPN, Helper plugins, and the core IPC and process lifecycle.
This guide is for users on v0.8.96 or an earlier stable release who plan to upgrade, or who notice changed interface entry points, TUN, Android VPN, window behavior, or core state after upgrading. If the old version no longer starts, first restore it to a state where you can export the configuration.
The project does not claim that v0.8.97 fixes every node, subscription, or DNS problem. There is no need to upgrade only for a newer version number; update when you need proxy authentication or the new cross-platform interface, or when you can complete the regression checklist.
Decide from your current state
| Current situation | Recommendation | Why |
|---|---|---|
| v0.8.96 works reliably and you do not need new features | Wait for now | The broad rework makes a known-good baseline especially valuable |
| You need the proxy authentication added in v0.8.97 | Back up, then upgrade | The official release notes explicitly list this new capability |
| You are ready to test the new interface, Helper, or Android VPN | Upgrade one platform at a time | Test only one traffic-capture path at a time |
| The old version already has node Timeout or subscription failures | Diagnose the existing failure first | An upgrade cannot replace node, configuration, and DNS diagnosis |
Save your Profile, settings, and working baseline before upgrading
The most important preparation is not a screenshot of the version number but a recoverable network path. In the old version, temporarily disable automatic subscription updates for the current Profile, then record the current Profile, policy group, mode, system proxy or VPN/TUN state, and complete one real HTTPS request.
Use FlClash's built-in backup or export feature to save the Profile and app settings, then copy that backup outside the app data directory. A subscription URL, node passwords, and WebDAV credentials are sensitive and should not appear in a public cloud drive, issue, or screenshot.
On desktop, also record the current package architecture and whether a system-level service is in use. On Android, record the system version, battery restrictions, and VPN permission state. This lets you separate app changes from existing device limitations after the upgrade.
Pre-upgrade baseline
- Recorded the current FlClash version and operating-system architecture
- Saved an external copy of the Profile, overrides, and app settings
- Recorded the active policy group and one known-good node
- Recorded the original system proxy, TUN, or Android VPN state
- Completed one real HTTPS request on the old version and kept its connection record
- Know how to restore direct connectivity after exiting FlClash
Choose the correct package from the official Release
The official v0.8.97 Release provides Windows installers and ZIP files for amd64 and arm64, macOS DMG files for amd64 and arm64, three Android ABI packages, and Linux AppImage, DEB, and RPM packages for amd64 and arm64.
This site's verified local backup is still v0.8.96 and must not be mistaken for v0.8.97. To upgrade to the new stable release, open the official chen08209/FlClash Release and verify the tag, filename, and SHA256SUMS.
Before installing, fully exit FlClash from the tray or app menu and confirm that the old core has stopped. Do not let two desktop clients change the system proxy at the same time, and on Android do not repeatedly relaunch immediately after installing over an active VPN.
Package label
| Platforms | Typical device | v0.8.97 package |
|---|---|---|
| Windows | Intel or AMD PC | windows-amd64-setup.exe |
| Windows | ARM Windows device | windows-arm64-setup.exe |
| macOS | Apple M-series | macos-arm64.dmg |
| macOS | Intel Mac | macos-amd64.dmg |
| Android | Most modern phones | android-arm64-v8a.apk |
| Linux | Choose by distribution and uname -m | AppImage, DEB, or RPM matching the architecture |
Replace only the app; do not change the configuration at the same time
Download the official stable release
Confirm that the page tag is v0.8.97 and select the asset matching your system and CPU architecture.
Verify the checksum list
Match the filename against SHA256SUMS from the same Release; do not use a renamed or repackaged file from someone else.
Fully exit the old version
Turn off the system proxy, TUN, or Android VPN first, then exit through the app and wait for the old core to stop.
Install over the existing app
Keep the existing configuration directory, and do not import a new subscription, change DNS, or switch nodes during the upgrade.
Verify the desktop interface, core, and Helper separately
v0.8.97 reworks the desktop runners, plugins, Helper, Rust bridge, and core IPC together. An open window proves only that the interface started; also confirm that the Profile loads, the core keeps running, and the system proxy or TUN captures real requests.
On the first launch, use only the pre-upgrade Profile and fixed node. Enable the system proxy, complete a browser request, and inspect the connection record. If you normally use TUN, wait until the system-proxy path is stable before enabling TUN separately.
Proxy authentication is a new capability, not a switch everyone must enable. Configure it only when the local proxy endpoint truly requires a username and password, then verify that wrong credentials are rejected while correct credentials can connect.
The window opens, but proxy groups are empty or the core keeps restarting
Read the first app or core error; do not re-import the subscription or reinstall the service yet.
The system proxy works, but enabling TUN breaks connectivity
The failure is in the Helper, permissions, DNS, or TUN path. Restore the system proxy and keep using that path.
The browser fails and there is no connection record
Confirm that the system proxy points to the current FlClash port, and exit other proxy clients.
A connection record exists but the node shows Timeout
Pin another known-good node instead of attributing a normal node failure to v0.8.97.
Every app fails after you enable proxy authentication
Revert the new authentication setting, then confirm whether the app can send credentials to the local proxy.
Desktop acceptance criteria
- The app shows v0.8.97, and the pre-upgrade Profile and policy selection remain available
- The core stays running and the interface does not repeatedly show IPC or process errors
- A real HTTPS request succeeds through the system proxy and appears in the connection record
- When TUN is needed, enabling it separately lets previously uncaptured apps connect
- After a full exit, the system proxy or TUN is removed and the device returns to direct connectivity
- After one restart, the Profile, window state, and traffic-capture method still work
Test one complete VPN lifecycle on Android
The Android build reworks the VPN service and lifecycle in v0.8.97. Start from a stopped state, launch the VPN once with the original Profile, test foreground access, lock-screen recovery, and switching between Wi-Fi and mobile data, then stop it manually.
A VPN icon in the status bar does not prove that the proxy works. You must also see a connection record and a successful real HTTPS request. If the icon disappears after locking the screen, suspect background restrictions; if it remains but requests show Timeout, continue with node, DNS, and rule checks.
Android regression sequence
Confirm the original Profile
After opening the app, confirm the Profile, policy group, and fixed node without immediately refreshing every subscription.
Start the VPN once
Accept the system VPN request for FlClash and confirm that a foreground request appears in the connection record.
Test network transitions
Test Wi-Fi, mobile data, and lock-screen recovery in sequence, observing the same target site each time.
Stop it manually
Disconnect from FlClash or the system VPN page and confirm that normal connectivity returns immediately.
Use early post-release reports only to define what to watch
After v0.8.97 was released, early official issues reported Windows core restarts, Android settings not saving, script overrides, and empty proxy groups. They still lack a shared reproduction, maintainer conclusion, or formal fix, so they cannot be treated as confirmed defects affecting every user.
If your device fails, preserve the version, platform, package name, first error, and minimal reproduction. Comparing v0.8.97 with the pre-upgrade version using the same Profile is more useful than deleting data, switching nodes, and changing DNS at the same time.
Layer where the failure occurs
| Symptom | Evidence to retain | Safe action |
|---|---|---|
| The app does not open | System version, architecture, package name, and first error | Restore direct connectivity and verify the official package |
| The Profile or settings differ from expectations | Before-and-after backups and the exact fields | Do not keep saving changes over the old copy |
| The core or proxy groups malfunction | App log, core log, and the same Profile | Disable traffic capture, then compare versions |
| Only real connections fail | Domain, matched rule, outbound route, and node result | Continue with node, DNS, or rule troubleshooting |
Roll back on failure and preserve upgrade evidence
If v0.8.97 cannot reliably start, capture traffic, or stop on your device, first disable the system proxy, TUN, or Android VPN, confirm direct connectivity, and then fully exit the app. Do not overwrite the configuration directory while old and new processes are both running.
After saving redacted v0.8.97 logs and a copy of the current data, uninstall or remove the new app, reinstall the official version that definitely worked before the upgrade, and import the pre-upgrade backup. This site's v0.8.96 backup is suitable only as a clearly labeled older rollback source.
After rollback, repeat the verification with the same Profile, node, and network. Only when the old version recovers and v0.8.97 consistently fails do you have a useful version comparison. When reporting to the project, do not upload a subscription URL, node password, or complete configuration.
Upgrade or rollback completion criteria
- The running version and package source can be verified
- The Profile, overrides, and policy selection match the backup
- A real request succeeds through the system proxy or Android VPN
- When TUN is needed, permissions, DNS, and connection records have been verified separately
- After a full exit, the device returns to direct connectivity with no leftover traffic capture
- Any upgrade failure has a minimal reproduction, first error, and version comparison preserved
- Subscription links, passwords, log paths, and personal information are all redacted
References
- FlClashFlClash v0.8.97 stable release notes
- FlClashOfficial FlClash v0.8.97 changelog
- FlClashEarly report #2405 on v0.8.97 Windows core and proxy behavior
- FlClashEarly report #2407 on v0.8.97 Android settings not saving
- FlClashEarly report #2409 on script overrides in v0.8.97
- FlClashEarly report #2411 on empty proxy groups in v0.8.97