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 preferences cannot be read

richard neal
Every time I restart my PC and open up capture one I get this message. This has only been happening since I upgrade to version 11, ive never had this issue with previous versions.

Any idea what could be causing it as its becoming annoying as all my settings are reset to default, including the license key!

https://i.imgur.com/jE0ubjS.png
0

Comments

5 comments

Date Votes
  • SFA
    First guess would be a glitch in the installation process.

    Have you already tried reinstalling?



    Grant
    0
  • richard neal
    Hi grant, yes tried that. Even went to the extreme of resetting my whole PC. Installed the older version and it's fine, still only happening with 11.
    0
  • SFA
    No idea unless you have something in the preferences set by an old version that is no longer supported because of V11 changes.

    I would guess it would have to be a very old version or something quite specific. It's not a message that I have seen.

    Presumably each time you proceed C1 resets the Preferences and the new preferences are overridden after a restart. When you exit C1 how do you do that? Might it simply be the case that the new preference options are not being saved back as the preferred "last time used" values and so the "old" ones are not replaced?

    Have you created a Support Case?


    Grant
    0
  • richard neal
    Not yet, thought I'd come to the forums first in case it's a known issue or had an easy fix. I'll get onto the support team , thanks
    0
  • Ian Leslie
    One possibility is that your user account does not have permission to write over the corrupt settings file. Which means each time you start it tries to read the old file and fails - telling you that it needs to reset - and then cannot replace it with a new copy. Another reason might be a problem with the file itself. A bit of speculation on my part. You could try a check disk command to see if any repairs are needed in the file system and then launch the app as administrator to up its permissions. Unless that resolves things for the way you regularly launch things I would recommend contacting support.
    0

Post is closed for comments.