wont start
Have installed capture one 12 and at first it did work. after quiting the software and tried again a little later the program wont start, not even coming up that little box saying capture is starting. Have tried both unistall and install it again. still nothing is working for me.
0
-
I'm facing the same exact problem.
I've installed Capture One 12 last Thursday (Nov 29th) and used it for about 4 hours. Everything went smoothly and images were exported correctly with selected recipes. Although every went ok in the first usage, today when returning to continue the work, Capture One 12 does not start, and dont even show start screen. If I click a second time on CO icon, system reports that an instance is already running. I've uninstalled, and reinstalled it with no success.
I still have Capture One 11 installed and there is no problem with it... the thing is tha I cant use capture one to continue what I've started in version 12...
I'll contact support.
Kind regards,
Bruno0 -
Bruno,
If you are getting the "already running message" then have you tried re-booting your PC?
Or, if you don't with to do that, start up the Windows Task Manager, go to Applications and see if you can see anything that looks like "Capture One" running. Or just "Capture". (I will assume that if you had been using V11 you will already have close that.
If you can try to close it. Then re-try V12.
If that does not work or if you cannot see anything like "Capture ...." running as an application go to the Processes Window and look for the same and also anything starting "P1".
If you find anything, end the process.
(Obviously re-booting would also do this!)
Then try V12 again to see what happens.
When you close C1 there are a couple of processes that may take a while to complete even after the scree suggests that the application is closed. If you are using catalogue backup for example or sometimes just writing the final changes out of cache memory back to disk somewhere. If, somehow, those processes are interrupted or delayed it is possible that, now and again, they end up hanging until the system is re-booted or maybe leave an "in use" flag on a file that need to be unused when the application opens.
The log files would probably provide some clues about what is going on under the hood but if you don't wish to get involved reading and interpreting those try the above and see what happens.
If it still fails you may need to create a Support Case.
HTH.
Grant0 -
Everything I tried with doesn't work. I already did a support case but there most be a problem among others outthere to.. I tried everything possible to try to make it work. 0 -
[quote="NNN636791211828885711" wrote:
Everything I tried with doesn't work. I already did a support case but there most be a problem among others outthere to.. I tried everything possible to try to make it work.
Are you clicking on an icon to start the process? If so have you checked how the link is defined?
Have you tried starting C1 from the .exe file in the installation folder?
Would you feel comfortable about looking at log files to try to interpret what happens when you start the process?
Grant0 -
Tried that to.. Nothing seems to work for me, how to make a logfile, I don't know really how. But everything I tried doesn't seems to work. 0 -
[quote="NNN636791211828885711" wrote:
Tried that to.. Nothing seems to work for me, how to make a logfile, I don't know really how. But everything I tried doesn't seems to work.
That all sounds very odd.
Log files can be found at:
C:\Users\[User Name]\AppData\Local\CaptureOne\Logs
in Win 7 and I believe much the same for later Windows versions.
They can be opened with Notepad.
See what you make of them. (Are you used to looking at things like Log files?)
Grant0 -
I did find out something after you told me to lock in the logs. instead of folder capture one I went to phase one instead and removed a configfile and thereafter it start to working again. see down to which folder..
not sure whats gonna happen when i turn of my pc if I have to remove the config.file
C:\Users\Admin\AppData\Local\Phase_One\CaptureOne
.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn\12.0.0.2910 -
[quote="NNN636791211828885711" wrote:
I did find out something after you told me to lock in the logs. instead of folder capture one I went to phase one instead and removed a configfile and thereafter it start to working again. see down to which folder..
not sure whats gonna happen when i turn of my pc if I have to remove the config.file
C:\Users\Admin\AppData\Local\Phase_One\CaptureOne
.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn\12.0.0.291
No, you only have to remove the user.config file once, in general. It is the file that contains the main settings for the program and when it becomes corrupt, the program can start behaving erratically. Deleting the file solves that.0 -
[quote="NNN636791211828885711" wrote:
I did find out something after you told me to lock in the logs. instead of folder capture one I went to phase one instead and removed a configfile and thereafter it start to working again. see down to which folder..
not sure whats gonna happen when i turn of my pc if I have to remove the config.file
That sounds like the result you needed.
Hopefully that was just a really unlucky glitch cause by an unknown event.
In over 10 years of using C1 and 5 years with this PC (My config file folders go back to 7.1.0) I have never had to delete a config file.
Maybe I have been lucky.
Grant0 -
Now it has happen again, a corrupt config file. Have to remove it everytime I want to start the program. Really know what I can do more... 0 -
In case you had previous version installed, you have older config files in the respective folders under C:\Users\Admin\AppData\Local\Phase_One
Remove them all. Make the ..\Phase_One\.. folder empty.0 -
This just happened to me with a fresh installation of a few days ago on a new machine. Deleting the file at C:\Users\myUser\AppData\Local\Phase_One fixed it for now at least. 0
Post is closed for comments.
Comments
13 comments