What staying on it actually costs

The repository is archived and read-only, so no further releases are coming. The interface itself is not broken; the problem is the core bundled with it, frozen at an old version, which means everything added since then passed it by.

  • Newer protocols your provider has adopted are simply unrecognised, so half the nodes vanish on import or the whole profile fails to load.
  • Security fixes have stopped. This is a program that runs in the background all day and handles all of your traffic, which matters more than any missing feature.
  • Nothing gets fixed when it breaks, and the community has largely stopped discussing CFW errors.
SponsoredWhere does the subscription link come from?Our partner provider gives you 1 GB of high-speed Hong Kong data at signup — import it in one click.Get high-speed nodes

Take the right things with you

  1. Copy the URL of every subscription out of the profile list and save it somewhere. That is the one thing that genuinely matters.
  2. Write down what you changed yourself: rules you added, proxy groups you edited, DNS settings, anything you wrote in Parsers.
  3. Use the open-config-folder entry in the interface and copy that whole directory somewhere safe, untouched.
  4. Check that your provider dashboard can still issue the subscription link, so a mistyped copy is not fatal.

What sits in that folder is already-converted YAML, not the original subscription and not a format meant for a current core. Keep it as a reference for remembering your own edits, but it is not something to reuse directly.

Re-add the subscription, do not carry the YAML across

Create a new profile in Clash Verge Rev, Mihomo Party or FlClash, paste the URL and let the new client fetch it once itself. The current core reconverts everything using its own field set, which is exactly how the legacy baggage gets dropped. After the import, check three things: node count, whether the proxy groups were generated, and whether the rule count looks plausible.

Switches that do not move with you

  • The port. Both sides often default to 7890, but do not assume it — confirm mixed-port in the settings.
  • allow-lan. If phones or a TV box used this machine as their gateway, turn it back on deliberately.
  • TUN. The new client has its own implementation and will ask for admin rights or install its own service the first time you enable it.
  • Launch at login, start minimised, enable the system proxy on startup — all of these live in the new client and none of them carry over.
  • Anything you did with Parsers maps to the merge or override profile in a current client, usually through prepend and append style fields, and has to be written again.

What the uninstaller leaves behind

An uninstaller only removes what it installed. The system proxy line lives in the OS, so it can outlive the app, and the symptom is a browser complaining that the proxy server refuses connections. If you used TUN, the background service and its virtual adapter may still be registered too. Turning the system proxy and TUN off inside CFW before uninstalling avoids most of this; the deeper cleanup has its own guide.

Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' | Select ProxyEnable, ProxyServer
netsh winhttp show proxy
Do not delete the CFW data folder the moment the migration looks fine. Give it a week or two. What you should not do is run both clients at once: they compete for the same port and the same system proxy setting, whoever writes last wins, and debugging that is time you will not get back.