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

Capture one doesn't start

HP

Hello,

I bought a licence for capture one pro and dowload the software on my new XPS 15 (window 10). 

When I try to open the program it doesn't run at all. Nothing happen.

I have never used capture one before. I have updated everything I can (dell and window), doesn't help.

If someone can help...

I am very disapointed.

Thanks

 

 

0

Comments

5 comments

Date Votes
  • SFA

    What happened when you ran the installation process?

    Did it install correctly?

     

    Be aware that this is a User to User forum not an official Support service but people here will try to help you.

    0
  • HP

    hello, thanks for your answer. Yes the installation process seems normal. At the end, I can chose to launch the software but nothing happen.

    0
  • HP

    here is solution I found :

     

    For anyone else looking to resolve an issue with Capture One 20 not starting on Windows (Win 10 1909 build 18363.836 for me), open Programs and Features, sort by column 'Installed On' (right click column heading and add the column if it's not shown) and look for a version of C++ that was installed the same time Capture One 20 was installed. Double click the Redistributable, walk through the repair process and try to launch the app again. 

    0
  • Mark Witherington

    You may want to try some basic diagnostics, like having task manager up and seeing if the application is there, try starting and then see it it pops up in the applications list. You could have a look at the windows event viewer and see if any errors related to Capture One are seen there. 

    I would also submit a request using the button at the top of the page. 

    There are some capture one logs you can look at under c:\users\user name\appdata\local\captureone\

    Some of which may indicate what the problem is. 

    0
  • SFA

    @HP

    That's interesting.

    Perhaps some conflict between the Windows 10 release and the C1 distribution or some sort of conflict that made some part of the installation not work quite as intended.

    I still use Win 7 at the moment so the "interesting" experiences of Win 10 are so far not part of my life.

    I expect that may have to change shortly.

    As long as you now have a good solution that is all that matters!

     

    0

Post is closed for comments.