Capture One not starting
Capture One (16.4.1 – pro) has stopped working since last Thursday. The days before I faced not a single problem with the software when processing a sport event (1700+ photo’s - raw).
Mouse-clicking the short-cut or the executable in the capture one map does not result in starting Capture One anymore. The splash screen is not popping up and messages are not appearing. I’ve re-installed Capture one (16.4.1) but the issue remains (even after deleting the map #appdata/capture one).
My laptop is running on Windows 10 pro and Wednesday evening it has been updated with the cumulative update for W10 KB5039211. Could that be the cause? I’ve submitted a technical request to CO support on Thursday but no reaction yet. I’m getting quite desperate. Any ideas to solve this?
-
I’ve re-installed CO 16.4.1 on my old laptop (also Windows 10 (pro), but not updated with the latest cumulative Windows update, and CO started normally. My guess is that the Windows update might be the cause. The log file gives me the following information:
Faulting application name: CaptureOne.exe version: 16.4.1.2127
Faulting module name: Coreclr.dll version 8.0.23.53103
The coreclr.dll is part of Microsoft.net. I really hope CO technical support will address the issue with the highest priority. At this moment I would not recommend W10 users to install the latest cumulative update KB5039211.
1 -
FWIW, I'm running Windows 10 Home with KB5039211 installed and I have no problems with CaptureOne 16.4.1.2127 starting. However, I upgraded to 16.4.1 after the patch was installed.
1 -
Yesterday I encountered the same issue and lost a lot of time to figure it out. It seems that the reason was KB5040427 update which updated .NET framework (KB5041081). I managed to revert it by installing previous version of .NET (8.0.6 - https://github.com/dotnet/core/blob/main/release-notes/8.0/8.0.6/8.0.6.md - runtime installer) and CO started to work again. Thanks for emotional roller coaster, Capture One.
1 -
Open a support case with Capture One and provide all the details.
0 -
Same problem here with the Fuji version
1 -
Same problem here with Windows 11 - happened two days ago, which was day 28 of my 30 day trial, lol. I tried deleting the logs (%localappdata%/capture*), since the exception is in the logger start up. I also uninstalled and re-downloaded from this site and reinstalled and no change, C1 still does not start. How can I get notified when they hot fix the .net update?
This kind of exception is very bad on a managed language like C#:
Faulting application name: CaptureOne.exe, version: 16.4.4.2244, time stamp: 0x666b0000
Faulting module name: coreclr.dll, version: 8.0.123.58001, time stamp: 0x65684720
Exception code: 0xc0000005Application: CaptureOne.exe
CoreCLR Version: 8.0.123.58001
.NET Version: 8.0.1
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at <Module>.P1.ModelCore.Logger.Start(std.basic_string<char,std::char_traits<char>,std::allocator<char> >*)
at <Module>.P1.ModelCore.Logger.Start(std.basic_string<char,std::char_traits<char>,std::allocator<char> >*)
at P1.ModelCoreWrapper.McSettingsPersistency.StartLogger(System.String)
at P1.C1.Core.ImagePersistency.InitializeMCLogging(System.String)
at P1.C1.StartupClass+<>c.<InitializeApplicationLogging>b__3_0()1 -
My C1 also does not load. Event viewer:
Faulting application name: CaptureOne.exe, version: 16.4.4.2244, time stamp: 0x666b0000
Faulting module name: coreclr.dll, version: 8.0.824.36612, time stamp: 0x6696b815
Exception code: 0xc0000005
Fault offset: 0x00000000001c2090
Faulting process id: 0x3edc
Faulting application start time: 0x01daf596f6a46589
Faulting application path: C:\Program Files\Capture One\Capture One\CaptureOne.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.8\coreclr.dll
Report Id: 247f87cb-d1aa-4ffc-a7a6-1752e2f6ab6b
Faulting package full name:
Faulting package-relative application ID:
Application: CaptureOne.exe
CoreCLR Version: 8.0.824.36612
.NET Version: 8.0.8
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at <Module>.P1.ModelCore.Logger.Start(std.basic_string<char,std::char_traits<char>,std::allocator<char> >*)
at <Module>.P1.ModelCore.Logger.Start(std.basic_string<char,std::char_traits<char>,std::allocator<char> >*)
at P1.ModelCoreWrapper.McSettingsPersistency.StartLogger(System.String)
at P1.C1.Core.ImagePersistency.InitializeMCLogging(System.String)
at P1.C1.StartupClass+<>c.<InitializeApplicationLogging>b__3_0()
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(System.Threading.Thread, System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread)
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()
My dotnet version is installed with Visual Studio, so I cannot uninstall it.1 -
Search the forums. There is another thread about this. Someone there provides the steps to address this with updated .NET and Visual C++ libraries.
1 -
Could you kindly link to the solution?
0 -
Walter Rowe
Could you kindly link to the solution?0
Post is closed for comments.
Comments
11 comments