Capture One won't launch after installing 16.4.4
Today I installed the latest CO service release (16.4.4). It installed as expected, with the usual sequence of advisories and options displayed to the screen. But since completion of the release's installation, CO no longer opens.
- It didn't open even though during the installation process I ticked the launch-after-installation box.
- It didn't open when, 20 minutes later, I clicked the CO icon.
- It didn't launch after I restarted Windows then clicked the CO icon.
- After clicking the CO icon, no reference to the application shows at any time, on any tab, of the "Task Manager" page in Windows 10.
I used CO without incident last night, before today's installation. I have installed many, many service releases on this PC over the years, always without issue. I don't understand why it's not opening now.
Ideas?
-
You can download 16.4.3 from Capture One and install it, test it, then try the upgrade again.
0 -
Thanks for the suggestion, Walter. I will try your suggestion when I get the time, then report back.
0 -
UPDATE: I downloaded and installed 16.4.3 from CaptureOne.com. The app installed AND launched (via ticking the "Launch" box available at the installation's completion) without issue.
At the end of the successful launch, Capture One asked whether I wanted to download the available update, 16.4.4. I accepted the offer.
Upon completion of the download, CO asked whether I wanted to install. I said yes. The installation process proceeded without issue, culminating in another "Launch" box to tick, which I did. . . . And then nothing. As when I installed 14.4.4 yesterday, I saw no CO splash screen and no evidence of CO activity on any Task Manager tab. Nothing. I then clicked the desktop CO icon, and again, nothing.
So 16.4.3 downloaded, installed, and launched without issue. 16.4.4 downloaded and installed apparently successfully, but has yet to launch, whether after downloading from within 16.4.3 or from the CO website.
Thanks for your continued interest in this matter.
1 -
Open a support case. They will probably ask for all kinds of logs from your system.
0 -
Will do. Thank you again.
0 -
I am also having this exact issue. 16.4.3 ran just fine without any issues. updated to 16.4.4 per the pop-up prompt, and now it's bricked. Ive uninstalled 16.4.4 and reinstalled to no avail. It's a shame because I'm on the 30-day trial because I am done with Adobe, and now I cant even use my capture one trial. I submitted a ticket. In the mean time, ill be using V16.4.3 as it works without any issues.
3 -
Exact same issue here. I'm contacting support right now.
3 -
Until V16.4.4 gets fixed, Just use 16.4.3. That works for me without any issues. I submitted a ticket and am awaiting a response.
2 -
Thank you, Ian and Charles, for posting about your experience with 16.4.4. I'm sorry for the inconvenience you've encountered, but am grateful for the company.
I too have submitted a support ticket (as well as log files), and returned to 16.4.3 until the fix is in.
Now that three of us have reported the issue, perhaps there will be some additional speed to CO's response. (Has anyone else had issues launching 16.4.4?)
1 -
Same issue for me, Windows 11 with the latest updates, AMD CPU, Nvidia GPU.
0 -
FIXED!!!!!!!!This is what i did:Verify .NET Core Installation:
- Ensure all .NET Core runtimes are correctly installed. Sometimes, corrupt installations can cause issues.
- Go to
Control Panel
->Programs and Features
and uninstall all existing versions of the .NET Core runtime. - Download and install the latest .NET Core runtime from the official .NET website.
AND:Update Visual C++ Redistributables:- Go to
Control Panel
->Programs and Features
and look for all instances of Microsoft Visual C++ Redistributable. - Download the latest versions from the Microsoft website and install them.
After I repaired my Visual C++ Redistributables it works!!!! V16.4.4 is running just fine now.5 -
This is a great find! You should get a bounty from Capture One! Definitely add this info to your support case.
1 -
Haha thanks! I've updated my support ticket and told them I have fixed the issue for my system. I just hope this helps out other people who are experiencing issues. I wouldn't mind a discount for a Capture One Pro License! :)
0 -
I'm glad that the process you detailed resulted in 16.4.4 running as expected on your system, Ian. Well done! Unfortunately, that process has not made a difference on my system; 16.4.4 still does not launch for me. But there was a complication, which might explain at least part of my issue.
I successfully updated the Visual C++ files, but after I uninstalled the existing .NET Core application, the latest version from the Microsoft site will not install. When I click the file, Windows asks whether I will allow the installer to make changes to my system - as expected - but after I consent, nothing happens and no new .NET Core app is installed.
The CO support team has responded to my support ticket, asking for additional information from me. I will pursue a solution through them.
Thanks for posting the solution that worked for you. I hope you get that discount!
0 -
I can confirm that .NET Core is not needed as I don't have it installed and I still managed to make the new version work. I however have .Net Runtime 8.0, .Net Desktop Runtime 8.0 and ASP.NET Core Runtime 8.0 installed.
The trick to get 16.4.4 to launch for me was indeed to reinstall Visuall C++ 2015-2022. I had it installed already, but the 16.4.4 installer triggers and install of the redist Visual C++ package, so it might be corrupting stuff there. Reinstalling the Visual C++ packages on top of Capture One fixed the issue. I personnally use Winget for that. I just forced uninstall + reinstall of these the x86 and x64 packages with the Uniget tool.
1 -
Thank you for your contribution to this thread, Charles.
I can't figure out how to download, let alone use, the Uniget tool to uninstall/install the Visual C++ 2015-2022 package. Could you please advise?
0 -
No Problem Bill.
I prefer to use Uniget as a visual tool that can automate installing and uninstalling packages (programs) from various repositories. It's not obligatory though, you can just use Winget (a package manager included with Windows). For that open a Terminal/Powershell window as administrator and paste the following:winget uninstall "Microsoft Visual C++ 2015-2022 Redistributable (x64)"
winget uninstall "Microsoft Visual C++ 2015-2022 Redistributable (x86)"This will only work if Visual C++ 2015-2022 was properly registered in the system’s list of installed applications. If that's not the case, you can follow the usual manual route of using the control panel or the Windows 11 Apps menu to uninstall those.
Then no need of navigating the Microsoft website and download stuff manually, you can simply paste the following to use Winget to fetch the latest version of Visual C++ 2015-2022 and install it.
winget install "Microsoft.VisualCpp.Redist.2015-2022.x64"
winget install "Microsoft.VisualCpp.Redist.2015-2022.x86"Voilà!
1 -
Same issue on my side, still trying the .NET and reinstalling the Visual C++ methods posted above. Anyone had any luck yet?
0 -
Neither uninstalling nor uninstalling . . . anything . . . has helped me get 16.4.4 to run. In fact, I am unable, either through Winget or Control Panel, to uninstall the 2015-2022 redistributable. It's all quite frustrating.
I am pursuing my ticket with the CO support people (after a delay on my end!)
0 -
Same issue here: updated to 16.4 and no launch but pressing the launch again informs me that Capture One is already running... but not according to Task Manager. Windows 11 user. Very frustrating!
0 -
David, you win today's prize for latest variation on the theme. Wow. There MUST be something in the code that the developers can correct.
0 -
Thanks Charles! I've been racking my brain to fix this issue. I can confirm that adding/updating to .Net 8.0 and uninstalling and reinstalling the Visual C++ components worked for me.
0 -
Installing the latest 9.0 .net framework worked for me. I'm not sure what happened but I updated Visual Studio yesterday and it must've corrupted whatever version of .net Capture One is targeting as it would no longer start today...
0 -
I am also pursuing my ticket and am disappointed that it is taking many days to receive a response. I'm using 16.4.3 for the time being as I don't really want to be uninstalling/installing programs to accommodate Capture One's coding.
0 -
For version 16.4.4 - Installing the latest .NET 8.0.8 runtime and latest Visual C++ 2022 redist did the trick for me on Windows 11 using AMD Ryzen 7 8845HS w/ Radeon 780M Graphics.
0 -
For those who have updated the Windows components .. does Microsoft not keep those updated for you? As a macOS user I don't have experience with this.
0 -
.NET 8.0.8 runtime and latest Visual C++ 2022 Redistributable worked for me on Win 11, I'm also on a Ryzen System 5900x, Nvidia 3080. Those are a bit hard to find and figure out the right ones since there are so many options on the download pages so here are the direct links to what I downloaded and installed.
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-8.0.8-windows-x64-installer0 -
For the record, my problem was fixed by uninstalling and reinstalling the Visual C++ files: Windows 11 OS.
0 -
This problem is most likely a problem with the Capture One Windows installer as it appears to not be installing the right version of the libraries or making sure that they are already present. Someone who has experienced this problem should file a bug report.
The v16.4.4 installer actually does trigger a Visual C++ Redist installer package, but there is no way to know what version it is exactly without decompressing the installer and manually check for it. It does appear as though it's indeed not the right version needed by Capture One, or some files in it are corrupted, because uninstalling and reinstalling Visual C++ redist after updating Capture One fixed the issue for me.
I did file a ticket as soon as I encountered the issue almost three weeks ago, I also explained what would likely cause it at length with the support team, but they closed my ticket after I found a solution without ever acknowledging that there was an issue with the v16.4.4 installer in the first place.
-1 -
Capture One is aware of the issue and developers are aware of this forum topic.
1
Please sign in to leave a comment.
Comments
43 comments