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. ⚠️

Unable to launch 14.4.1 in Windows 10

Michael Woods

I installed the latest version 14.4.1 and now Capture One does not launch, either from the desktop shortcut or by clicking on the executable in Windows Explorer.  I don't even see any of the Capture One processes appear in Task Manager when I attempt to start it.  I'm running Windows 10 Pro build 19043.1288

After several reboots and reinstallation attempts, I decided to roll back to 14.4.0 which was working fine for me before - now it won't launch either.

Any ideas what could be happening here?

Thanks in advance,

Mike 

 

 

1

Comments

10 comments

Date Votes
  • OddS.

    > Michael Woods: Any ideas what could be happening here?

    Try a PC restart, or at least a Windows restart. You can also look for a capture one process in your Windows process (task) list (Alt+Ctrl+Delete), select and stop the listed capture one process(es). You may have to expand the list to see all processes/tasks on the system. A stale leftover application process that should have died last time Capture One exited, can block the next startup. (The phenomena is not limited to Capture One.)

     

    0
  • Michael Woods

    Thanks OddS - I had already tried everything you've suggested, with no success. 

    I have since done a complete uninstall of C1 following the instructions on the C1 support page, reinstalled 14.4.0 (which used to work fine for me), rebooted numerous times, and I still get the same result - the program does not start, and none of its associated processes/tasks show up in Task Manager.  

    So I'm now paying a subscription fee for a program that won't even launch - great.  

    Any other advice or suggestions from the C1 community would be much appreciated.

    1
  • SFA

    Michael,

    That sounds very odd indeed. 

    Have you checked your C1 account to see what Activations you have registered there?

    I would expect C1 to at least start before checking for activations but there may be some strange control cookie or something for a subscription license that might be a factor. I cannot think what it would be though, or what it would be for.

    0
  • Tim van der Leeuw

    In Windows 10, when you "click on the executable", where exactly do you click? From "Start" menu, or by going to the folder where the application is installed?

    I'm wondering if the shortcut-links are somehow invalid.

     

    0
  • OddS.

    Tim van der Leeuw: ...wondering if the shortcut-links are somehow invalid

    Good point, but I would expect Windows to throw an error message. If I understood M.W correctly, he (double) clicked on the executable in Windows Explorer. I would still expect an error message if Windows could not start the application.

    It is normally also possible to start C1 via Windows' file associations by double-clicking a session's database file (sessionname.cosessiondb), but Windows should emit an error message if the application start fails.

    It could be that the executable starts and terminates before showing signs of life. That is why I suggested a stale application process. I would restart the computer, then do nothing for a few minutes, note the computer time* and try to start C1, then wait for a few minutes and investigate the C1 log and the Windows event logs for clues.

    * Knowing the computer time is key when investigating logs.

     

    0
  • Tim van der Leeuw

    Yes I would have expected that too, but still wanted to know exactly how the app was started. :)

    One thing to try would be to run the app from a terminal (dos-prompt) instead of double-clicking. Perhaps it emits some printed debug-statements?

    I don't know what kind of log-files CaptureOne produces when it is running normally.

     

    0
  • Michael Woods

    Thanks to all of you who chimed in with suggestions - I've since been able to get Capture One running again.

    I found that Capture One had created a log file on every failed launch attempt it would add an entry that included (among many other things) this line:

    "Could not load file or assembly 'P1.AppCore.dll' or one of its dependencies."

    After searching around for some time, I found that another Capture One user had encountered the same error message about a year ago after he installed C1 20 and it would not launch. 

    The solution was to install the latest version of the Visual C++ Redistributable  package from the Microsoft found site here: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-160 

    I would have assumed that the missing .dll would be included in the C1 installer package... perhaps it is, but just didn't install for some reason.  For anyone else who encounters this "no launch" condition the fix is to uninstall C1, install the latest Visual C++ Redistributable package, and then reinstall C1.  This what worked for me.

    2
  • SFA

    Michael,

    One thing that would throw us off the scent for a potential WIndows Visual C++ issue would be that you seem to have had 14.4.0 working previously but that stopped as well.

    Very odd. 

    Is there any possibility that you had a Windows update applied that just happened to coincide with your 14.4.1 update? It's the only thing I can think of that might make a change of some sort that could lead to the both a new release and a previously working earlier release appear to stop working unless something unusual happened when you applied your update process.

     

    Very unusual.

    0
  • Michael Woods

    SFA,

    I checked my Windows Update history, there were no updates that align with the date/time when my troubles started.

    My best guess at this point is that there was a zombie C1 process still running in the background at the time that I ran the update to 14.4.1 and that caused a failed write or possibly some file corruption - I had noticed on a few previous attempts to shut down my machine that there were often one or two processes that had to be force quit, with names that looked suspiciously like they might belong to C1. 

    I don't know if this is related to the new Visual C++ installation, but with hardware acceleration set to "Auto" for both display and processing, I no longer get a corrupted output image on the first export (which was a constant problem before, the only workaround was to set the processing option to "Never" in the Preferences panel).

    0
  • Permanently deleted user

    Большое спасибо,  Майкл Вудс, за помощь в решении проблемы! Я потратил неделю на безуспешные запуски C1 , пока не нашел ваш комментарий! Не хватало последнего обновления Visual C++

    0

Post is closed for comments.