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?
-
Capture One is aware of the issue and developers are aware of this forum topic.
2 -
I had this issue with V16.4.4 and V16.4.5 not launching and reverted to V16.4.3 which worked fine. After finding this thread I re-installed Visual C++ 2015-2022 both x86 and 64bit and CO V16.4.5 worked fine. Two weeks on I went use CO and it would not launch again. It was ok yesterday but not today. I did a repair in both Visual C++ 2015-2022 and all is fine again. Not sure what is going on.
0 -
Same issues here on windows 10 pro. Capture one will not run on my windows 10 pro after the recent September 10, 2024—KB5043064 (OS Builds 19044.4894 and 19045.4894). Capture one attempts to run for about 20 seconds then nothing, no UI opens. No issues ever with CO in the many years i am using it. I have tried to uninstall, reinstall while rebooting between. I have tried the two most recent versions of capture one. I have had to go back to CaptureOne.Win.16.4.3.2158.exe to get a functioning CO. Going to stay with this version until its fixed
1 -
I am also having the same problem.
I had the problem a couple of weeks ago and had a project that was due and finally just reset windows and installed CO to get the project done. Here I am several weeks later, rebuilt my computer installed the latest CO which I figured probably addressed the previous issue and it worked fine. Used it two days ago. Worked great.
Now this morning, same problem. Same messages in the event log.
The most frustrating part is the last time I contacted customer support I included the messages out of the Event Log that showed the version of CO I was using and showed the dotNET version it was failing on and all I got back was boiler plate response, asking for the version number and steps to reproduce. All of which was included in my original report and the event log messages that I cut and pasted into the report.
I provided the information again as requested.
Got back more boilerplate, about trying to install the software on the same machine as a different user. Problems with user environment most common cause of issues, etc.
Did as I was instructed. Same problem.
Today I searched on the exact error message in the event log and see this has been going on for two months now!
I am still making my monthly payments for the subscription, but now I am spending time debugging software that should never have been released two months ago, or should have been fixed by now.
I will probably have to do todays shoot with NX Studio (The free Nikon app) since Capture One is dead for the second time in the last month.
And before anyone tells me to start a case, I would want to hear how this time will be different then the last time.
PS I tried the suggestion in this thread and here is where I got:
PowerShell 7.4.5
PS C:\Users\richarr> winget uninstall "Microsoft Visual C++ 2015-2022 Redistributable (x64)"
Found Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.40.33810 [Microsoft.VCRedist.2015+.x64]
Starting package uninstall...
Successfully uninstalled
PS C:\Users\richarr> winget uninstall "Microsoft Visual C++ 2015-2022 Redistributable (x86)"
Found Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.40.33810 [Microsoft.VCRedist.2015+.x86]
Starting package uninstall...
Successfully uninstalled
PS C:\Users\richarr> winget install "Microsoft.VisualCpp.Redist.2015-2022.x64"
No package found matching input criteria.
PS C:\Users\richarr> winget install "Microsoft.VisualCpp.Redist.2015-2022.x64"
No package found matching input criteria.
PS C:\Users\richarr>0 -
Robert Richardson, go back two versions of CO. see if CaptureOne.Win.16.4.3.2158 runs for you. if so , wait for a fix for the current version.
it worked for me.
0 -
Seems like that is what I am going to do to get by today. The thing I worry about is the next time CO comes out with an update that requires the database to be upgraded. The other thing that is sort of disconcerting is that no one who actually works for CO is here. It's just us users trying to help each other out while our tickets get handled by bots. (Although I did get a notification that my new ticket from today,
"Your request [248590] "Re: Capture One won't start" is now on its way to one of our friendly (and very much human) Support staff members."
So that gives me hope.
0 -
I am surprised that we have seen no public mention of this issue from Capture One. I just looked through the issues they are aware of and this issue isn't listed that I could see.
I had this same issue a month ago. Ending up resetting windows to get C1 to work again. Applied the update that had broken it and seemed fine until this week. Another update, worked fine for a couple of days and not it crashes again.
My favorite part? The original ticket I entered a month ago was closed and marked as SOLVED. Support did nothing and marked it as solved.
I wonder if Windows users are in the minority here and that is why we aren't getting any traction. The idea of paying a subscription which supposedly includes "Priority Support" and only every getting back automated responses seems like a waste of money.
0 -
Have you tried 16.4.5?
0 -
Yes. That was the second update that crashed on me after a few days of working fine. It pointed to the same culprit .NET 8.0.
0 -
Meanwhile, CaptureOne.Win.16.4.3.2158 still runs fine. I am not going to reset windows machine again to fix this problem.
0 -
It's been working fine for me since reinstalling the latest .net 9 release, haven't had any issues
0 -
I normally use C1 on my desktop computer but when away from home I use my laptop. Initially version 16.4.5 worked fine but when I tried it the other day, I found it failing to launch. I fixed this just be doing a repair on "Microsoft Visual C++ 2015-2022 Redistributable (x64)" without the need to re-install it of any other software.
0 -
Same here. v16.4.5 doesnt't load. installing v16.4.3 does
0 -
Thank you, vultures at private equity. I'm done with C1.
0 -
I just got burned by this issue! I had upgraded all the way to 16.5.0 with out issue and had last run 16.5.0 on Oct 26th just fine. Then, for some reason, it no longer opens. It crashes in a .Net module with an unhandled exception, System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
I've tried uninstalling and re-installing 16.5.0, .Net 8, downgrading to 16.4.6, 16.4.5 but that error persists. Only installing 16.4.3 works. Of course, I can't open most of my catalogs because they were upgraded to the 16.5.0 format. So unless the developers can fix the problem with 16.5.0 and allow the fix to read the 16.5.0 format catalogs, I will be very displeased! Fortunately, I was not dumb enough to import the raw files only into the catalog. So I could go back and re-import the original raw files into a new catalog and re-edit them.
BTW, this is on Windows 10 and a case was opened with CaptureOne Support.
0 -
Jeff Gottloeb, I feel for you, especially since at one point you had successfully upgraded to 16.5.0. I hope the CO people finally get around to fixing this issue. A CO support person told me in an August 22 email that they were "building some sort of fix for this and will be included in the coming release," but that obviously hasn't happened yet.
I've not ever been able to upgrade past 16.4.3, which makes my recent $190 annual renewal of my subscription seem less and less like a wise purchase.
This is a VERY frustrating.
0 -
I did a repair on "Microsoft Visual C++ 2015-2022 Redistributable (x64)" without the need to re-install it of any other software and that fixed the problem for me. Since then I have updated CO a couple of time since without any more issues. I hope this works for you.
0 -
Just updated today to C1 16.5.1 from CaptureOne.Win.16.4.3.2158.exe having had the same issues as everyone else here.
I dont know if the issue for me was sorted out by C1 update or Windows update on Microsoft Visual C++ 2015-2022 Redistributable (x64) which updated on the 10th of Oct.
I did a repair on the Microsoft Visual C++ 2015-2022 Redistributable (x64) anyway and rebooted and then updated to C1 16.5.1, rebooted again and all is good for now.
0 -
Well Well, i am back with the same issue, see my previous comments. I had got C1 back and running on the most recent version but this evening C1 wont launch again.
So been running the latest version for a month now no issues, having been plagued before that with C1 not launching and having to revert back to version CaptureOne.Win.16.4.3.2158 to get a running version. Now this eve C1 will not launch.
No changes to windows, the only change was that yesterday C1 did some minor upgrade to do with "studio" whatever that was about. I rebooted this eve and now back to the will not launch.
So i am back to version CaptureOne.Win.16.4.3.2158 to get a running version.
Super furstrating. Really love this software but seriously looking at lightroom, i am all ready paying for it with photoshop subscription so may well just save on the Capture one subscription and see if cancelling my yearly sub to C1 registers with them.
BTW its hard to believe only a few of us C1 users are affected. Odd really.
0 -
michael mulcaire: BTW its hard to believe only a few of us C1 users are affected. Odd really.
I'm sorry to hear about your renewed struggles with C1 16.5.xx, Michael. I wish I could offer you encouragement!
I haven't been able to run anything newer than 16.4.xx for more than four months now, so I understand at least a bit of where you're coming from. (A lot of good my $190 subscription is doing me.) For what seem to be access- and permission issues, I'm not able to uninstall, install, or modify any of the C++ Resdistributables, including the one that I think matters the most, for 2015-22, so I am locked out. Next month I plan to upgrade to Windows 11 in hopes that that will resolve my issues.
As for your point that it's odd so few of us have been stricken by this issue, I agree. Who knows?
0
Post is closed for comments.
Comments
50 comments