imgcoredll.dll can't start
Capture one 20 is unable to start. it says, fatal error imgcoredll.dll can't start. i reinstalled it, latest version, rebooted, but its still impossible to open up C1. 3 days ago everything was fine. anyone has the same problem?
-
its working again! i installed the new , free, C1 21 for fuji express. then i reinstalled the last version of C1 v20 and it worked.
hope it helps people with the same problem.
cheers
0 -
Hi Serge,
I'm having a very similar problem - I also can't start C1 v20:
"Fatal Error ImgCoreDll.dll can't start the crash handler. Try restarting... "
Previously my antivirus (Bitdefender) flagged one of the C1 files (OpenCoreDll.dll) as infected and moved it to quarantine...Any chance you are running Bitdefender as well?
No idea if it was a false positive or an actual infection...The fact that you had the same(?) problem at roughly the same time could mean it's a false positive(?)
Anyway - right now I can't start Capture One - would be great to find a fix...
cheers,
Tilman0 -
Thank you Tilman, I have the same problem and am running Bitdefender. My concern is that over the Christmas period, could Capture One have been attacked with a virus inserted in their download software?
0 -
I've sent a request to Bitdefender to check if it's a false positive or not.
No idea how fast they act/reply, but will keep you posted!0 -
Thank you. I've just tried again, reloading the software and it has worked!!!
Irritatingly it has loaded build 13.1.4, saying I can download 14.0.1 which they state may be payable. I would like to know if it is payable, is it Capture One 21 or just a patched Capture One 20? Poor information can result in mistrust and a loss of goodwill.
0 -
I repeated the same procedure today (uninstall of C1 v20 and re-install) - and this time it worked.
Maybe Bitdefender pushed out an update in the meantime - scanning the freshly installed C1 folder doesn't prompt an issue anymore...
The 'update to 14.01'-prompt is just Phase One teasing you to update to v21... I got that as well...
I would think/hope it was a Bitdefender false positive which got fixed with one of their steady updates...0
Post is closed for comments.
Comments
6 comments