The only method that works for me is to format my computer and delete all files. Which is very hassle to do.

This issue strongly points to a server/verification check that is failing when CapCut reaches the network.

Below we have complied targeted, advanced steps which you can try until CapCut developers fix this issue:

Quick checks to do..

1. Make sure Windows time/date is exact and set to automatic (Settings → Time & language → Date & time). Many TLS / verification failures happen when the system clock is wrong.

2. Disable any system-wide adblockers / Pi-hole / router DNS-blocking temporarily (these can hide CapCut/TikTok endpoints). These checks are fast and resolve server-verification errors.

Advanced network / system fixes to try:

Check & clean your hosts file

Open Notepad as Administrator, then open:

C:\Windows\System32\drivers\etc\hosts

Remove any lines that reference capcut, tiktok, bytedance, or any suspicious entries that redirect hosts to 127.0.0.1 or 0.0.0.0. Save file.

• a hosts entry can silently block/redirect verification servers and trigger a security notice.

Flush DNS, reset Winsock and TCP/IP stack

Open Command Prompt as admin and run these three commands:

ipconfig /flushdns netsh winsock reset netsh int ip reset

Restart computer afterwards.

• corrupt DNS cache or Winsock issues can make app-to-server handshakes fail even when browser works. CapCut network errors can be resolved through resets.

Use a public DNS as a test

Temporarily set your NIC DNS to Cloudflare or Google:

• IPv4 DNS: 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google).

• Reboot and test CapCut while online.

  • sometimes local ISP/resolver blocks or misroutes CDN endpoints.

Disable proxy & VPN & any “network filtering” apps

• Settings → Network & internet → Proxy → make sure everything is OFF.

• Temporarily uninstall/disable VPN/third-party network/security tools (including system-level ad-blockers, Fiddler, and loopback proxy apps).

If CapCut PC is working offline a proxy/VPN/region filter interferes with verification.

Reset Microsoft Store / Store licensing if Store version also failed:

1. Run wsreset.exe (Start → type wsreset, Run as admin).

2. If that does not help, re-register Store packages (PowerShell as admin):

Get-AppxPackage -allusers Microsoft.WindowsStore | 
Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

3. Reinstall CapCut from the Store after doing the above.

The Store cache or package registration can block Store apps from performing license/online checks.

Add CapCut to Windows Firewall / AV allowlist and create outbound rule

• If you use third-party antivirus, temporarily disable it.

• Add an Outbound firewall rule to allow CapCut (CapCut.exe) full network access (or just remove restrictions).

• Alternatively block CapCut’s network access as a test if it then no longer shows the Security Notice, the error is indeed coming from a specific verification call and you can work from there.

• AV/firewall can interfere with the verification handshake.

Inspect what domains your CapCut app tries to contact

• Use Resource Monitor (resmon.exe) → Network tab → launch CapCut and watch Network Activity to see the hostname/IP CapCut connects to.

• Or use a simple tool like TCPView from Sysinternals to see active connections when you start CapCut.

That will show the endpoint that triggers the popup (example: CDN / verification host tied to ByteDance/TikTok). Once you have that hostname, you can:

• Temporarily allow it through firewall, or

• Search the hostname online to see if it’s blocked by your ISP/region.

This is how you find the exact failing endpoint rather than guess.

Update Windows Root Certificates & make sure TLS is enabled

• Run Windows Update fully (sometimes root CA updates are required).

• Ensure TLS 1.2 is enabled (most modern apps require it). You can check Internet Options → Advanced → ensure “Use TLS 1.2” is checked.

• server verification requires valid certificate chains; expired/missing root certs or disabled TLS versions can break verification.

Workarounds for immediate continuity:

1. Offline-first workflow — launch CapCut while offline, create your project, save it, then connect to the Internet only when necessary. This avoids the pop-up when you connect online but is not ideal long-term solution.

2. Sandbox / VM — run CapCut inside a clean Windows VM or different user profile to test whether something in your main profile is causing the verification failure.

3. Try a different network — tether to mobile data (phone hotspot) and test; if hotspot works, it's likely your router/ISP blocking endpoints.

If none of the above works

Please send us the results of quick diagnostic you can run now:

1. Open an admin Command Prompt and run:

2. While CapCut is running and connected, open Resource Monitor (resmon) → Network and list any remote hostnames that show for CapCut.exe (or take a screenshot of that Resource Monitor output).

Mainly this issue is primarily a network/verification failure and the next best step is to identify the endpoint.

If your CapCut works offline but errors when online, it is almost certainly failing a server/TLS/host verification which can be fixed by checking/cleaning the hosts file, flushing DNS + Winsock, disabling proxies/VPNs, resetting Microsoft Store cache, and either allowing or blocking the app in your firewall while you inspect which remote host is being contacted.

i did everything (except VM) and still appear. 
https://imgur.com/a/HDNr3V5
https://imgur.com/a/Ufwy8xp