Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Windows: Capture One can't start due to VC++ runtimes

Implemented

Comments

12 comments

  • Macon Leiper

    Is this the same bug? 

    I've pulled the diagnostic data from Windows if it helps:

    CaptureOne

    Description
    Faulting Application Path: C:\Program Files\Capture One\Capture One\CaptureOne.exe
    Creation Time: 12/15/2024 10:51:08 AM
    Problem: Stopped working
    Status: Report sent

    Problem signature
    Problem Event Name:           APPCRASH
    Application Name:             CaptureOne.exe
    Application Version:          16.5.2.2623
    Application Timestamp:        666b0000
    Fault Module Name:            coreclr.dll
    Fault Module Version:         8.0.1124.51707
    Fault Module Timestamp:       67115e10
    Exception Code:               c0000005
    Exception Offset:             00000000001c7b0e

    Extra information about the problem
    Bucket ID: e8f2c0c1dc3a2163f10fdbf8ad447abf (1229443084400753343)

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Could be.

    0
  • Miles Lee

    I also cannot run c1 now. coreclr.dll Exception Code: c0000005

    0
  • Bartosz Maciejewski

    For 2 weeks I have not been able to start Capture One version 16.3. First I got an error that the catalog cannot be opened and that I do not have a license for this type of document. Then an error that it is impossible to connect to the activation server. I followed the instructions above and after reinstalling the program starts until I enter the license and after entering it turns off. What should I do ? And when can I expect a repair because i need C1 for work ?

    0
  • Walter Rowe
    Moderator
    Top Commenter

    open a support case

    0
  • Bill Coley

    It's amazing to me that 5-1/2 months after I first posted in these forums about my experience with this issue, CO can only say that a solution is "in the works." I am STILL stuck with version 16.4.3, which I downloaded at the end of July 2024. So to-date, thanks to this unresolved problem, I've received NO benefit from my $190 CO subscription that I renewed in mid-October 2024, during which time I believe versions 16.4.4/5/6 have been released.  I intend to ask CO to extend my subscription by the number of days/weeks/months between my subscription renewal date and the release that fixes the issue. At the moment, that period of time is about ten days short of three months.

    Truly disappointing.

    2
  • Miles Lee

    hello everyone,

    I already fix it.

    I instal a software which install below package, then I can run C1 now. i don't know which one is useful.you can find it in ms offical website.

    Hope it can help.

    0
  • Sergi Salillas
    Admin

    Bill Coley Hello, thank you for your feedback. This fix is included in 16.4.5. 

    If you can't access that build, please follow the workaround mentioned in the first message on top of this thread. Thank you! 

    0
  • Sergi Salillas
    Admin

    Hello Miles Lee Thank you for your input and good catch! That is the workaround we explained in our first message on top of this thread. 

    0
  • Bill Coley

    Hi, Sergi,

    The fix(es) implemented in any CO version stamped 16.4.x did not work for me; nor did version 16.5 as late as 16.5.1.2546, which I downloaded in mid-November. Today I downloaded version 16.5.4.2682 and it worked! For the first time since last July I am able to use the latest version of CO. Wow. That was a LONG, LONG wait.

    0
  • Johannes Schiller

    Not working for me, I have installed captureOne 16.5.4.2682 I get a ton of c++ errors in the error log. I can't use the current version of capture one, and the previously installed one also does not work. 
    Always kills itself after i log in in the browser window it opens in the beginning. 
    I have submitted this in the error handler. 

    0
  • Sergi Salillas
    Admin

    "FirstName LastName" Thanks for writing and sorry to hear this doesn't seem fixed on your end. Let's continue the conversation through the support ticket. Thank you! 

    0

Post is closed for comments.