Windows users should prioritize a maintained client that supports their system and common protocols. Clash for Windows is discontinued and is better used as a historical configuration reference than as the default for a new device. For everyday use, install one maintained client. When migrating an old configuration, verify the subscription, rules, TUN, and system proxy one by one, and do not run the old client alongside it.
Eliminate unsuitable clients first
On the download page, compare project maintenance status, Windows architecture, core version, and required features. Remove discontinued projects from consideration for a new device.
- Is the project still maintained?
- Does it support your Windows version and system architecture?(See Clash for Windows details)
- Is the core Clash, Mihomo, or Clash Meta?
- Do you need TUN, subscription updates, and rule management?
Choose for daily needs
- Start on the client download page and review maintenance status by platform(See Windows downloads)
- For a new device, prefer a client that is still maintained
- When migrating an old configuration, confirm that the new core supports its protocol fields
- After installation, record the client and core versions for troubleshooting
Clash for Windows has extensive documentation, but its project status must be clearly stated
Clients use different interface labels and configuration entry points
Do not run multiple clients that compete for the system proxy