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

"ImgCoreSocket error - An invalid argument was supplied"

Permanently deleted user
With the CO 6.0 Pro running, starting CO Pro 5.2.1 produces the following error message. I believe the reverse is also true. With the CO 5 Pro running, starting CO 6.0 Pro can cause the same error.

ImgCoreSocket error

An invalid argument was supplied.

Has anyone seen this? Should I open a support case?
0

Comments

9 comments

Date Votes
  • Paul Steunebrink
    Installing different version of CO on one computer, goes very well on Windows. But running them simultaneously is - probably - not supported. I just tried it, it runs, but get the same error.

    You can open a case, see what's happening.
    0
  • Drew Altdo
    The two software's are competing for the same resources. Running two versions at the same time is not possible, supported, recommended or practical.
    0
  • Paul Steunebrink
    [quote="Drew " wrote:
    The two software's are competing for the same resources. Running two versions at the same time is not possible, supported, recommended or practical.

    ... and therefore can be fun sometimes. 😂
    0
  • Permanently deleted user
    [quote="Paul_E" wrote:
    [quote="Drew " wrote:
    The two software's are competing for the same resources. Running two versions at the same time is not possible, supported, recommended or practical.

    ... and therefore can be fun sometimes. 😂


    That makes sense. CO 4.5 and 5.0 can co-exist because CO 4.5 uses Settings45, I believe. CO 5 and 6 use the same Settings50 folder. The cache folder seems to be shared among all versions.

    It looks like CO 5 and 6 are sharing quite bit, the image engine, perhaps?
    0
  • Drew Altdo
    Quite a bit.
    0
  • NN634868609841693662UL
    I am using Phase One Capture One PRO v6.4.3.58953. I installed Phase One Capture One PRO v7 as a demo. I then uninstalled v.7 and now v6.4.3 won't run. I uninstalled and reinstalled several times but I get the ImgCoreSocket error and the program just freezes, I have to use task manager to close it. How can I fix this problem?

    All help appreciated..
    Thanks
    0
  • SFA
    [quote="NN634868609841693662UL" wrote:
    I am using Phase One Capture One PRO v6.4.3.58953. I installed Phase One Capture One PRO v7 as a demo. I then uninstalled v.7 and now v6.4.3 won't run. I uninstalled and reinstalled several times but I get the ImgCoreSocket error and the program just freezes, I have to use task manager to close it. How can I fix this problem?

    All help appreciated..
    Thanks



    As it's the weekend and support may not be around to help you out ...

    3 long shots.

    Run a windows update to check for .NET updates.

    Turn off OPENGL (just in case ....) or check for updates (or downdates ?) of your graphics drivers.

    Are you using an INTEL or an AMD processor? A very quick Google search for the message text earlier today turned up a couple of old references that mentioned AMD specifically. Thought it might be worth having the information available should you still need to talk to support.


    Grant
    0
  • NN634868609841693662UL
    INTEL i3, .... all .NET updates installed, 16G memory, big hard drives ....v6.4.3 ran fine until I tried v7... after I uninstalled v7 and went back to my v6.4.3, it started doing that freeze thing..?? I am thinking that v7 installed a driver or .dll that did not uninstall as it should have... but I don't know what to look for... I have gone through the registry looking for v7 entries as well as C:\Program Data and everywhere else I could think of, but can't find anything..? but trying v7 is what messed up v6.4.3...

    Thanks for your reply...
    0
  • SFA
    [quote="NN634868609841693662UL" wrote:
    INTEL i3, .... all .NET updates installed, 16G memory, big hard drives ....v6.4.3 ran fine until I tried v7... after I uninstalled v7 and went back to my v6.4.3, it started doing that freeze thing..?? I am thinking that v7 installed a driver or .dll that did not uninstall as it should have... but I don't know what to look for... I have gone through the registry looking for v7 entries as well as C:\Program Data and everywhere else I could think of, but can't find anything..? but trying v7 is what messed up v6.4.3...

    Thanks for your reply...

    Hmm.

    Might be worth trying to re-install 6.4.3 (or 6.4.4) and re-check .NET updates. Beyond that ... no idea, sorry.


    Grant
    0

Post is closed for comments.