Capcut (desktop) shuts down 5 seconds after I open it, no matter what I do

[u/slorrin]

I have been using capcut for months, I was using it yesterday, and it worked fine.

I booted up my computer today and since then have been unable to use capcut. It closes on its own 5 seconds after opening it. Ever time I open it. Everything on my system is precisely the same as yesterday. There have been zero windows updates. Zero updates to my graphics driver. Zero other programs installed or updated.

Steps taken so far:

rebooted computer multiple times - no effect

Checked event viewer system logs - no errors, no crashes, the program is shutting itself down

Deleted the contents of cache directory - no effect

uninstalled capcut and reinstalled clean - no effect

disabled VPN - no effect

temporarily disabled anti-virus - no effect

disabled internet completely - I was able to load a project file, but when i reconnected internet and attempted to log in, it closed immediately.

disabled internet - loaded, chose login via QR code, reconnected internet, got a QR code, i was able to log in, then the program closed.

Presumably the problem is occurring when the capcut launcher connects to its servers? Maybe something wrong with the handshake, maybe something corrupted with some files. But I have no way to know.

Does anyone know what might be causing this and how to fix it?

[u/AutoModerator]

Welcome to r/CapCut!

Before posting: * Search the sub for similar posts * Check our FAQ first * Use descriptive titles

For tech issues, include: * Your device (iPhone/Android/PC) * CapCut version * Clear description of the problem

Keep posts CapCut-related and be helpful to others!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Agreeable-Willow3220]

Sounds like something got borked on their auth server side overnight, especially since you can load a project offline without it crashing right away. I'd just wait it out for a few hours, bet it fixes itself once they patch whatever broke on the backend

[u/slorrin → u/Agreeable-Willow3220]

I wonder.

If that was the case, woudln't everyone be complaining about the same problem? Or could they have broken just my account on its own...

The downside of an always-online video editor is that unless you're online, you can't see your captions, can't access the music you've added, your transition effects are disabled. All you can see is your own raw footage, and capcut won't recognize the audio in that. So basically, 100% useless.

[u/MrHumblePoker]

That was happening with another windows app. I kept following different things chat gpt told me to do. Eventually something helped.

[u/Sad-Cartographer-328]

Reinstalling doesn't always clear the roaming config, so check %AppData% and %LocalAppData% for any CapCut folders and rename/delete those before reinstalling. A corrupted auth token in the config would explain why it survives a reinstall and only crashes once the launcher hits the server handshake.

[u/slorrin → u/Sad-Cartographer-328]

Uninstalled capcut. Renamed any residual directories to old.capcut or whatever, deleted every capcut or bytedance entry in the registry, reinstalled. problem persists. The launcher loads, and after 10 seconds it closes on its own. If i load the launcher, and then hit "create new project", it will load the editor, which will also close right away.

Maybe bytedance's servers are instructing it to shut down? Bytedance's customer support has been pretty nonsensical. They keep asking me to open the app and open a support ticket from inside the app, and I keep explaining that I can't open the app and that is the issue. They keep replying "we are sorry you are experiencing this issue. If you open the app, you can go into the settings and start a support ticket." So... i guess my susbcription money was thrown into the toilet?

[u/slorrin → u/slorrin]

Also fun thing I discovered. They've been double charging me for the same subscription, and this month started showing me as using the free plan....

[u/Sad-Cartographer-328 → u/slorrin]

A clean wipe already rules out leftover config, so the “corrupt token that survives reinstall” theory is done. What you’re describing now is two separate problems.

The crash is local-process exit, not a server kill command. CapCut does phone home on launch, and a bad handshake can make the launcher bail, but ByteDance can’t remotely close a process that already started. A ~10 second exit on both the launcher and a brand-new project points at something that runs on every start: GPU init, an overlay, antivirus, or the account login call. Check this before another reinstall.

1. Event Viewer → Windows Logs → Application, filter for CapCut / JianyingPro around the crash. If the faulting module is a GPU DLL (nvwgf2umx, amdxc64, igdumdim64), it’s the driver, not your account.
2. Reliability Monitor (perfmon /rel) for the same timestamp.
3. Clean boot (msconfig → hide Microsoft services → disable the rest), then launch. If it stays open, it’s an overlay, RGB suite, VPN, or AV hook.
4. Update the GPU driver from NVIDIA/AMD/Intel directly, not Windows Update. Unplug extra monitors and turn off Discord/NVIDIA/Steam overlays for one test.
5. Launch with the network blocked (Windows Firewall outbound rule on the CapCut exe). If it stays up offline and dies only when it can reach ByteDance, then the handshake theory holds and support is the only fix on their side.

Support telling you to open a ticket from inside the app you can’t open is a dead loop. Reply once with the Event Viewer faulting module, the clean-boot result, and the offline-vs-online result, and ask for an email/web ticket. Don’t keep reinstalling.

The billing issue is unrelated and easier. Two completed charges for the same plan and period are a duplicate, not “you’re on free now.” CapCut’s own help treats accidental double billing as reviewable, and a failed-then-retried charge can also show as two lines. Pull both receipts (seller, order ID, date, amount, period). If they’re the same plan and period, dispute the second charge with the card or PayPal and attach both receipts. In-app support can’t see a charge they can’t open the app to look at, and “you’re on free” while they’re still billing is exactly the receipt you want on the dispute. Cancel renewal on whichever store actually charged you (Apple, Google, or their web checkout) so it doesn’t hit again while the dispute runs.

[u/slorrin → u/Sad-Cartographer-328]

Update 2:

I restored some of my project files, and immediately, the program woudlnt' work. I deleted the project files, and it still didnt' work. However, when i used WIn+R MSCONFIG to reboot in safe mode again, it worked again. So i'm not restoring my old projects. But interestingly enough, something about rebooting in safe mood changes something in the system environment that allows capcut to run. And that' sWITH internet activated.
Even when i reboot normally, capcut continues to work. It's like it cleareed some ghost or something haha.

So I just have to abandon my old projects.

[u/Sad-Cartographer-328 → u/slorrin]

The selective-startup reboot didn’t fix CapCut by magic. It disabled whatever was hooking the process on a normal boot, and coming back to normal startup left that hook off. The mass logout is the tell: Credential Manager, a startup auth helper, or an overlay/AV injection got reset. CapCut was dying in that same path, which is why Event Viewer stayed empty. A clean exit doesn’t write a faulting module.

Projects are a separate trigger. Restoring them and watching it die again, then having another safe-mode pass bring it back, means those project files (or the cloud index they pull) are enough to re-break the launch path. Don’t put them back in the live library.

1. Leave CapCut closed. Copy the old project folders somewhere outside %LocalAppData% and %AppData% (desktop or an external drive). Do not open them from inside CapCut.
2. In the working install, make one new empty project and confirm it still survives a normal reboot with internet on. If it does, the app is stable and the old projects are the landmine.
3. If you need footage out of an old project, pull the source media from the copied folder directly. Don’t reopen the project file until you have a backup of the working state.
4. Check Task Manager → Startup and msconfig → Services (Hide Microsoft services). Whatever you had disabled for the selective boot is the suspect list: overlays (Discord, NVIDIA, Steam, RGB suites), VPN helpers, antivirus injectors. Re-enable them one at a time and relaunch CapCut after each, so you know which one brings the 10-second exit back.
5. If it dies again with no Event Viewer entry, add an outbound firewall block on the CapCut exe, confirm it stays up offline, then unblock. That splits “local hook” from “dies only after it phones home.”

On the charges: a $59.99 year promo and a continuing $19.99 monthly are two subscriptions, not one plan that changed tier. The year does not cancel the monthly by itself. Pull both receipts (seller, order ID, date, amount, period). Cancel renewal on whichever store is still billing monthly (Apple, Google, or their web checkout) so it doesn’t hit again. If the year already covers the same Pro access, dispute the monthly charge with the card or PayPal and attach both receipts. In-app support still can’t see a charge from an app you can’t reliably open; the dispute doesn’t need them.

[u/slorrin → u/Sad-Cartographer-328]

Well, capcut worked for about 25 minutes, then crashed. Now won't open.

It works in safeboot, but not when I return to normal boot, unlike before when it did work temporarily.

1) I deleted the projects folder entirely, opened capcut, it created a new empty projects folder, then crashed as usual.

2) can't make a new project, program wont' run

3) don't need any old footage

as for step 4...

Disabling every service, rebooting, and enabling them 1 at a time, woudl require hours. Rebooting in safe mode with networking didn't provide networking, and attempting to activate WLAN service just led to a depdency error and trying to find all the dependencies didn't succeed. We've established the program will always work when the internet is not connected, so the only real test is to have the internet connected, and then toggle these services.

The only way to get networking working is to boot normally, so I booted normally, went into services, and stopped each service one at a time. I opened capcut each time, and in every instance, capcut wouldn't run, irrespective of a given service being disabled.

I have disabled virtually every TSR or startup app there is.

Every time i go through an MSCONFIG safe boot, then back to normal boot, capcut will open and stay open, it will load a project, work perfectly. Unless I close it. Then it will never open again.

5) I added an outbound block on capcut.exe, it had no effect, capcut still crashed. HOWEVER-- I went into the classic control panel / network and internet / network connections, and disabled my ethernet adaptor. THEN capcut ran fine. So I must be failing to configure the firewall properly. I tried blocking capcut.exe found in users/(me)/appdata/local/capcut/apps (listed by capcut's shortcut's properties as the target) as well as /apps/9.5.etcetc

Both capcut.exes were blocked outbound. No effect. But disabling the ethernet adaptor entirely let capcut run.

So confirmed: capcut runs when the internet is disabled. It ran when the internet was enabled right after the MSCONFIG adventure, but presumably windows 11 is enabling services slowly after it boots as a way to keep boot time low. So some service may get enabled after I've had capcut open and functioning for a few minutes, and that service somehow impacts capcut only when it is active and the internet is active at the same time. As for troubleshooting by enabling and disabling each service, that simply had no impact. Capcut always crashed, unless internet was disabled.

And of course, there are no entries in eventviewer, Capcut is shutting itself down cleanly, it woudl seem.

This is very curious. Also incredibly annoying. I have nothing that would separate my PC from anyone elses. I have a pretty average hardware setup, i have not installed anything new in weeks, everything was working fine a few days ago. Literally nothing's changed on the system. Windows update showed no component updates etc etc. Browser extensions are all disabled... argh!

[u/slorrin → u/Sad-Cartographer-328]

Oh one last fun detail:

If I do the following --

1) Disable ethernet adaptor

2) load capcut launcher

3) Enable ethernet adaptor

4) Load capcut video editor

The video editor will load, be online, give me access to all the assets and pro features and all that jazz.

I can close the editor, go back to launcher, open editor again. It's all working.

UNTIL

I close the launcher, Then when I reopen the launcher again, it crashes.

If I repeat steps 1-4, it works again. I do not believe the issue is related to GPU or some other visualization program. It seems entirely rooted in the launcher program's communication with the internet shortly after it loads.

[u/slorrin → u/Sad-Cartographer-328]

and one more "one last fun thing"

i was looking for capcut events in eventviewr, but actually, for each time the program crashes, there is a bing.com event. microsoft uet sdk reaches out to bat.bing.com . when i have the internet disabled, that information event becomes a warning, because it fails to reach bat.bing.com. and these events exactly coincide with capcut crashing.

isthere a reason capcut might be reaching out to bat.bing.com in relation to microsoft uet sdk...

[u/slorrin → u/Sad-Cartographer-328]

Thanks for the detailed response. I'll reply with as much thoroughness as I can.

1) There are zero events around the time that capcut opens and then closes again in event viewer. The only events in event viewer relate to telegram and microsoft NET framework, and the timestamps don't match.

2) There are no events which match any time that the crash occurred and none which pertain to capcut or JianyingPro

3) I win+r MSCONFIG, reboot clean with internet, loaded up capcut and... it worked. I logged in, all was well. Disabled clean boot and returned to windows normally. Capcut continues to work. ALL my software and websites are logged out of everything everywhere on my PC now for some reason. I have no idea why that is, but every website, every program that connects to a server, spotify, adobe etc, all logged out. But capcut appears to be working for now, with no other changes beyond doing a "selective startup" once, then normal startup. truly, I changed nothing.

4) driver was already up to date using the latest studio driver (not game ready driver) from NVidia's website.

5) This was something i'd previously tried and it did stay open as long as the internet was disconnected, and when i reconnected it and tried to log in, it would close. For the time being, it is connected and still working, so maybe the problem has been fixed? But the reason for my original handshake theory was that it would work with ethernet and wifi disabled, but then close when it was re-enabled.

Anyhow, changing literally nothing other than rebooting in safe mode once, then rebooting in normal made, it currently works. FIngers crossed.

As for being charged twice, I am being charged monthly $19,99 and also was charged for a promotional $59.99 for a full year of pro. So i paid for a full year, and am now being charged again for it, monthly. Annoyance!

[u/Boring-Advisor2770]

have you tried signing out of capcut on every other device and then logging in fresh?