How to Upgrade to FlClash 0.8.97: Helper, VPN, and Rollback Guide

FlClash v0.8.97 was released as an official stable version on 2026-9-10. When reviewing the official changes, check the interface and localization, application window layer, desktop packaging, Android VPN, Helper plugin, and core IPC and process lifecycle separately.

When upgrading from v0.8.96 or an earlier stable release, check the new interface entries, TUN, Android VPN, window and core state. Helper is a background component that assists desktop system operations; IPC is how the app communicates with the core. If the old version will not start, first restore a state where configuration can be exported.

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.

In the old version, temporarily disable automatic subscription updates for the current Profile. Record the Profile, policy groups, operating mode and system proxy or VPN/TUN state. Complete a real HTTPS request and confirm direct networking returns after quitting FlClash. Use these records for comparison after upgrading.

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.

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.

When this article was written, this site's verified backup was v0.8.96; check the download page for the current backup version. This guide covers upgrading to and rolling back from v0.8.97, not a claim that it is still the latest stable release. If you need that version, open the official chen08209/FlClash v0.8.97 Release and verify the tag, filename, and SHA256SUMS.

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.

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.

Early official issues after v0.8.97 reported Windows core restarts, Android settings not saving, script overrides, and empty proxy groups.

The author of the script-override report later said that declaring variables with const or let resolved the problem and closed the issue. The reports differ in status and evidence. They do not establish defects affecting everyone, nor does an author’s workaround establish a common fix confirmed by the maintainers.

v0.8.98 explicitly includes only two fixes: keeping the Core running during Windows Modern Standby and refreshing Geo file details. It does not establish that other reported problems are resolved.

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.

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. For rollback, select an official version that you confirmed worked on this device before the upgrade, then import the pre-upgrade backup. The site's current download backup may not be the older version you need; verify its version and source before rolling back.

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.