CapCut knocks on server addresses your PC memorised weeks ago - and some of those addresses no longer exist. This page clears the stale records, shows how to change the DNS servers Windows uses, and keeps the heavy network reset for where it belongs: last.
DNS problems wear a perfect disguise: the error says no internet connection, but the connection is fine - only the phone book is out of date. CapCut servers move and change like any large service, and a Windows PC can hold on to a dead address for a long time. The fixes here are ordered from a five-second flush to a full stack reset, so stop at the first one that works.
Before CapCut can talk to its servers, your PC must look up their addresses - that lookup is DNS. Your PC caches the answers to save time, and providers change server addresses over time. A cached answer can point at an address CapCut retired, so the app knocks on a door nobody answers and reports no internet - while your browser, asking for different and more stable addresses, works fine. Two fixes exist: empty the cache, or change who answers the questions.
ipconfig /flushdns and press EnterThat is the whole first fix. It deletes nothing important - the cache rebuilds itself from fresh lookups within minutes.
Still failing? Your provider DNS itself may resolve CapCut servers badly. Switch the PC to a large public DNS: open Settings, Network and internet, your connection, DNS server assignment, Edit, Manual - and enter 1.1.1.1 as preferred and 8.8.8.8 as alternate (Cloudflare and Google public DNS). Save, run the flush command again, and retest CapCut. Note what the original values were, so you can put them back if your office network ever requires its own DNS.
If DNS changes change nothing, the Windows network stack itself may be damaged - usually by old VPN or filter software. The reset is netsh winsock reset in an administrator Command Prompt, followed by a restart. Honest warning: this also removes custom network settings some VPN and security tools installed, and those tools may need a repair or reinstall afterwards. That is why it sits last in this page and not first - try the flush and the DNS change before reaching for it.
Watch the DNS flush and server change done live in the video, with the exact commands typed on screen.
Watch Full VideoYes, for a home PC. Public DNS services like Cloudflare (1.1.1.1) and Google (8.8.8.8) are widely used and the change is fully reversible - set DNS server assignment back to Automatic (DHCP) and your provider defaults return.
A returning stale record usually means the DNS server itself is handing out the bad answer. Move to step two and change the DNS servers - that changes who answers, not just how long the answer is kept.
No. It resets network configuration catalogues, not your files or saved Wi-Fi networks. But VPN and security software that plugged into the network stack can stop working until repaired or reinstalled, which is why it is the last step on this page.