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

Crash on entering activation key

Comments

2 comments

  • Walter Rowe
    Moderator
    Top Commenter

    There are some threads here on the forums regarding Capture One crashing on Windows. In one of those threads someone discoverer some Windows developer libraries were conflicting with each other and they had to manually remove / re-install them. Once those were cleaned up Capture One ran well. This has been reported to Capture One. I recommend looking for the threads about Capture One crashing on Windows to see how those users fixed it, or opening a support case to see if Capture One can provide you some directions.

    0
  • Philip Bishop

    I opened a support case for this.  Capture One have fixed the problem, so I'm posting the help they gave me in case anyone has the same problem.

     

    This it has to do with the Windows registry problem where Capture One needs to access value for CPU.

    Windows Management Instrumentation (WMI) is a set of specifications from Microsoft for consolidating the management of devices and applications in a network from Windows computing systems. WMI provides users with information about the status of local or remote computer systems.

    We rely on local system functionality of Windows for the application to work, and most likely Win32_Processor is missing on your computer in order for this to work.

    To check the status of WMI, go to start-run and type in wmimgmt.msc

    In the opened window, go to More actions>Properties:

    You will see this dialog open:

    This means that WMI is consistent or not corrupted. Otherwise, you will receive an error message (there is a variety of errors, which it's not the scope of this reply to cover).

    You can also quickly check if the repository is corrupted or not by running the following command from command prompt with admin rights: winmgmt /verifyrepository

    If it is corrupted, the returned result will be “Repository is inconsistent”. If it comes back as consistent, then repository is not corrupted. Do not rebuild repository at this point.

    Finally, in some cases you can face a consistent WMI, still Capture One won't launch. Please, reset the repository by running winmgmt /resetrepository command.

     

    Running winmgmt /resetrepository command fixed it for me.

    0

Please sign in to leave a comment.