If Capture One fails to launch, there are several common causes and solutions to consider. This guide walks you through each possible case and provides links to tools and resources to help you get back up and running.
Contents
Case 1: Incompatible Operating System
If you're running an unsupported OS, such as macOS 10.14.6 (Mojave) with Capture One 16, the application will not open.
To resolve this, you can either:
- Upgrade to a compatible macOS version
- Downgrade to a compatible version of Capture One
Check compatibility here: Capture One system requirements and OS support
To view upgrade options for your license key, visit: https://www.captureone.com/en/store/upgrade
Case 2: OpenCL Crash
OpenCL issues can cause crashes during startup. For more information, check these articles:
To disable OpenCL:
- Windows: Download and run DONOT_useopencl.reg. Restart Capture One. To restore OpenCL later, use useopencl.reg from the same package.
- Mac: Download AdjustOpenCL_External.zip, run the application, disable OpenCL, then restart Capture One.
Case 3: Missing .NET Core & VC++ (Windows Only)
Some users report that reinstalling .NET runtimes and Visual C++ libraries can fix unexpected crashes:
Verify .NET Core Installation
- Go to Control Panel Programs and Features.
- Uninstall all existing .NET Core runtimes (e.g. “Microsoft Windows Desktop Runtime - [version]”).
- Download and install the latest .NET 8.0 Core runtime from the official .NET website.
Update Visual C++ Redistributables
- In Control Panel Programs and Features, locate all Visual C++ Redistributables.
- Download the latest versions from the Microsoft website.
- Install them to overwrite existing versions. If issues persist, use the Repair option.
- If the problem continues, try disabling your onboard graphics card before launching Capture One.
Case 4: Missing Full Disk Access (Mac Only)
Capture One may be blocked from starting if it lacks Full Disk Access. To grant access follow this guide.
Case 5: Damaged or Corrupt Database
If your database is corrupt, hold down the Option key (Mac) or Alt key (Windows) while launching Capture One. This opens a window allowing you to select a different database or create a new one.
Case 6: Application Running in the Background
- Windows: Press Ctrl + Alt + Delete, open Task Manager, and end any Capture One processes.
- Mac: Press Command + Option + Esc, select Capture One, then click Force Quit. Alternatively, right-click on the Dock icon and select Force Quit.
Comments
13 comments
"Connection is invalid.
Capture One 20 got an error: Connection is invalid. (-609)"
Thank you and have a nice Sunday evening ;-)
I have checked the compatibility with my laptop, after installation, still cannot launch capture one 13.1.1.
Zenbook UX430UN, core i7 8th Gen U, RAM 16GB, MX150 Nvidia, 1080p, Windows 10 v1909.
I have tried above solutions, still cannot launch.
I have encountered this issue.
None of the above worked. After I've installed redistributable C++ 2015-2019 package from Miscrosoft the problem is gone.
Hi Mikhail,
Thank you for your comment.
Your suggestion was also added to this article.
We stuck in the "Capture One 21 got an error: Connection is invalid. (-609)" error (High Sierra)… and also the "AdjustOpenCL_External.app" freezes and hardly can complete its USELESS task!
What to do? Even the crash report can't be sent!
Nothing works. Can not open C1 21 with a catalog generated by C1 21 on Big Sur
I had Capture 22 15.4.19 installed on my windows 11 machine and it had been running fine until a couple days ago when I wanted to import a job and it would not load the program I got an error message saying I need to install .Net Runetme 6.0.1 and I download it and I nothing happend I could not get the program to load. So I uninstalled the Capture 22 15.4.19 and loaded 15.2.1.9 and it loaded up and ran fine. I contacted Victor at tech support and he sent me a .Net Runtime 6.0.8 file to install I did that and uninstalled the 15.2.19 and tried reinstalling the 15.4,19 and I got the same error message as before I'm really at my wits end and pulling the little bit of hair out of my head because I just brought a Nikon Z-9 and wanted to import the lossless raw files and can't untill I get the new update! Can someone please advise i really can't afford to loss anymore hair:-(
thanks,
Mel
Please help!
Just upgraded to Ventura 13.0.1 on a macbook M1 max with 64 mb. Capture one 22 keeps crashing. Holding Option and starting the app, and granting full access also crashes...
The application that supposedly disables OpenCL also does not work
Please see below.
I'm also having the same issue as Luis Sayo. I purchased the full license for Capture One 22 Pro and expect the software to work as long as I need it to. What is going on. Also, the support site layout is extremely unfriendly with respect to finding related issues or logging a complaint. I have current paying clients waiting on work. Need help ASAP - but I don't intend or need to upgrade to 23!!!
Luis Sayo
I had to go to my account page and selected download capture one:
When you arrive on the next screen to download, scroll down to get to the Download Previous Version:
The command prompts then direct you to the most recent update to Capture One 22. Reloading the app fixed the error. Hope this helps!!!
Eric
I have a problem capture one 22 nov realease will not tether l can see and iv
ixCapture is the most unreliable software we operate. It constantly crashes in the air, gives in air trigger errors, and now WON'T LOAD on any laptop.
We've read through all the comments, tried everything, and still nothing. Any other suggestions?
Mine stopped launching but I was able to fix it without support, I am not sure what happened. I tried everything listed.
1. Updated graphics driver
2. I downloaded the NetFxRepairTool, search "Microsoft .NET Framework Repair Tool" and make sure you are on an official site, not some scam SEO site.
This fixed the issue. My guess is my .NET somehow got corrupted. Uninstalling and reinstalling would not work, disabling OpenCL did not do anything. Hope this helps someone. Nearly 2 hours wasted trying to fix this.
Please sign in to leave a comment.