How to Fix FlClash 0.8.96 Not Launching

This article covers two recent reports of FlClash 0.8.96 failing to launch at all after installation on Windows. In the first, a pop-up says that MSVCP140.dll or VCRUNTIME140.dll is missing; the original report also mentions VCRUNTIME_1.dll, so use the exact filename shown in your own pop-up.

In the second, the interface opens, but the core fails to start and displays DesktopCoreFailure. Both can look like a broken installation, but their troubleshooting paths differ.

Official issue #2370 documents DLL pop-ups after installing v0.8.96 on Windows 11 25H2; issue #2367 documents Smart App Control blocking the core, with Code Integrity events 3077 and 3089.

Neither report had received maintainer confirmation when this article was published. They are used only as evidence of the symptoms; this article does not claim that v0.8.96 has one confirmed installation defect behind both.

If FlClash starts and the only problem is node Timeout, TUN disconnects, or a failed subscription, this article does not apply. Do not install runtimes, disable security features, and reinstall the client all at once when there is no DLL pop-up or Code Integrity evidence.

First close any repeatedly opening FlClash processes; do not keep installing over the existing copy. Record the Windows version, system type, FlClash installer filename, and a screenshot of the first pop-up or DesktopCoreFailure. The official v0.8.96 Release provides both amd64 and arm64 Windows installers and archives, so the filename can confirm which one was actually installed.

If system proxy or TUN was enabled earlier, disable the system proxy in Windows network settings and confirm ordinary webpages work over a direct connection. Leaving a local proxy enabled while the client cannot start mixes a launch failure with a system-wide network outage. Do not delete Profiles, subscriptions, or the app data directory; neither troubleshooting path requires clearing user configuration first.

Use this path only when the pop-up explicitly names MSVCP140.dll, VCRUNTIME140.dll, or a similar v14 runtime file. Microsoft distributes these files with the Visual C++ v14 Redistributable.

Microsoft's official page provides stable download links for x64, x86, and ARM64. Current FlClash Windows Release assets target amd64 and arm64, so first install the x64 or ARM64 runtime that matches the official asset target; consider x86 only if the official guidance or a dependency check explicitly identifies a 32-bit component.

The amd64 installer corresponds to Microsoft's x64 runtime; the arm64 installer can use the ARM64 runtime. Microsoft currently also notes that the x64 installer contains both x64 and ARM64 binaries, but the easiest approach to verify is still to match the FlClash installer architecture with the runtime download.

If there is no DLL pop-up but the interface displays DesktopCoreFailure, first open Windows Security and check the Smart App Control status under App & browser control.

An On status alone does not prove a block. You must also match the failure time to events in the Microsoft-Windows-CodeIntegrity/Operational log.

Microsoft documents event 3077 as recording a file actually blocked by an enforced policy, while event 3089 provides signature information. First use 3077 to confirm the blocked file, then use the Correlation ActivityID to find one or more 3089 events associated with the same decision.

Matching only by nearby timestamps can incorrectly pair a signature event from other software. In the #2367 report, both event types point to the FlClash core executable.

If the log has no matching path and ActivityID, do not automatically attribute DesktopCoreFailure to Smart App Control.

Microsoft currently states that Smart App Control has no allow switch for individual apps; ordinary Defender exclusions also cannot override a Code Integrity trust decision. After confirming event 3077, do not keep adding directory exclusions or look for a supposedly unlocked core on third-party repackaging sites.

A safer sequence is to preserve redacted evidence from the official installer, event 3077, and event 3089 entries under the same ActivityID, report it to FlClash, and then check whether the project has provided a newer official build with a verifiable signature or clearly established reputation.

While waiting, you can return to an official FlClash version that you have previously confirmed launches on this computer, or temporarily use another maintained client from a verifiable source. If the rollback is still blocked, stop repeatedly downgrading.

Disabling Smart App Control entirely reduces system-level protection, not just protection for FlClash. Microsoft's FAQ has also changed the conditions for re-enabling it in recent years, so this article does not present disabling it as a fixed repair step. If you must consider it, first read the official guidance for the Windows version on your device, understand the device-wide impact, and then make your own decision.

After completing the DLL path, restart FlClash and confirm that the original pop-up no longer appears and that both the interface and core load normally. After completing the Smart App Control path, confirm both that DesktopCoreFailure is gone and that no new event 3077 near the current launch time points to the FlClash core. Seeing the window open is not enough; the core and configuration must load successfully too.

For the first recovery test, keep TUN off, select a known working node in the original Profile, enable the system proxy, and make one ordinary HTTPS request. This lets you verify “the application can finally launch” separately from “the network configuration still works.”

If the same DLL pop-up remains after repairing the runtime, first check the architecture of Microsoft Visual C++ v14 Redistributable under Installed apps; its display name may change between versions. Then run Repair again.

Then redownload the installer that matches your system from the official FlClash v0.8.96 Release. You can also test the official archive for the same architecture to determine whether the problem occurs only during installation.

If the archive reports the same DLL, continue troubleshooting the runtime instead of repeatedly installing FlClash over itself. If the DLL error disappears but becomes DesktopCoreFailure, you have entered the other path and should inspect Code Integrity events. When a Smart App Control block remains, reinstalling the same file without any change to its trust state usually produces the same result.