CO1 6.2.2 corrupting output files/folders
I have already made a support case, but haven't received any reply as yet. I had just installed 6.2.2 and processed a number of P45+ files into TIFFs. At first I could open the files in Photoshop, but soon discovered I could not save them with their original name (after some editing'. I could save them under a different name in the same folder. It also turned out I could not delete those files although I had manually removed, or at least tried to remove, any protections (there weren't any). Now the entire folder/directory can no longer be accessed and seems severely corrputed. I have never had this problem before. Can anyone help? Files processed into JPG do not have these issues.
I am using Windows 7 64/bit, but my laptop with Vista 32/bit, has exactly the same problem, which leads me to believe it must be CO1 causing these problems.
Thanks
Piet Gispen Photography
http://www.pietgispen.com
I am using Windows 7 64/bit, but my laptop with Vista 32/bit, has exactly the same problem, which leads me to believe it must be CO1 causing these problems.
Thanks
Piet Gispen Photography
http://www.pietgispen.com
0
-
I have not seen this particular problem, but I have found 6.2.2 to be somewhat strange on my Win 7 system.
It seems to also have some issues with jpeg files (at times) which were created by PS Elements.
I also just got it into a memory runaway state where it was in a loop trying to build proxies.
I'm going back to 6.2.10 -
Thanks for your comment. I have just unstalled CO1, removed alle extra files etc and re-installed it. It produces exactly the same problems, causing serious trouble both on my laptop and desktop. I do hope someone at PhaseOne will look into this and respond to the support case I have made (yesterday...) soon. I will not uninstall 6.2.2 and go back to the previous version.
Piet Gispen
www.pietgispen.com0 -
After a few more tests, I found that the 6.2.2 seems to have problems with jpeg files that it produces.
I seem to get into a major "create proxie" loop.
6.2.1 has problems with the same jpeg files created by 6.2.2 -- though it does not have issues with the jpegs that it creates.0 -
Unfortunately my troubles seem to be getting worse. I have downgraded back to 6.2.1 on my desktop . Now 6.2.1 also seems to be producing corrupted TIFFs which before it did not. Some of the folders/directories get so corrupted I can no longer access or remove them. This is happening on both computer systems.
Again, I'd wish the support team of PhaseOne would look into my support case (within 8 hours??)
Piet Gispen0 -
I may have encountered similar problems.
It appears that 6.2.2 may have corrupted my Windows Explorer; at least when it looked at my folders where my photos are, or any photos inside the folders. After opening 3-4 folders, Win Explorer would shut down.
This continued even after I had uninstalled 6.2.2 and returned to 6.2.1
I think I have it fixed but - I had to do a OS system restore to a date before I installed 6.2.2
UGH !!0 -
I suppose I am fortunate, as the 32-bit update went well and the latest version is working fine for me, thus far. I am using Windows XP (with 8 GB of RAM memory) to process Olympus E-5 RAW files. 0 -
Still no response whatsoever on my support case made two days ago! I have tried a system restore to an earlier date, but even that failed. It seems I am in serious trouble. I hope that eventually PhaseOne will lend a helping hand. I am in the middle of a big assignment and can no longer work!
Piet Gispen0 -
While I still haven't received a reply from PhaseOne, I have started digging into Windows. My logbook pointed me to the possible culprit in CaptureOne. Perhaps this will help someone:
Logboeknaam: Application
Bron: Application Error
Datum: 22-7-2011 9:12:53
Gebeurtenis-id:1000
Taakcategorie: (100)
Niveau: Fout
Trefwoorden: Klassiek
Gebruiker: n.v.t.
Computer: Photography-PC
Beschrijving:
Naam van toepassing met fout: WISPTIS.EXE, versie: 6.1.7601.17514, tijdstempel: 0x4ce7a4e0
Naam van module met fout: P1.WIC.NativeComWrapper.dll, versie: 0.0.0.0, tijdstempel: 0x4ddbce83
Uitzonderingscode: 0xc0000005
Foutoffset: 0x0000000000001124
Id van proces met fout: 0x165c
Starttijd van toepassing met fout: 0x01cc483ec5787c37
Pad naar toepassing met fout: C:\Windows\SYSTEM32\WISPTIS.EXE
Pad naar module met fout: C:\Program Files\Phase One\Capture One 6\WIC\WIC64\P1.WIC.NativeComWrapper.dll
Rapport-id: 038900e3-b432-11e0-bb9e-00235482126e
Gebeurtenis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-07-22T07:12:53.000000000Z" />
<EventRecordID>8011</EventRecordID>
<Channel>Application</Channel>
<Computer>Photography-PC</Computer>
<Security />
</System>
<EventData>
<Data>WISPTIS.EXE</Data>
<Data>6.1.7601.17514</Data>
<Data>4ce7a4e0</Data>
<Data>P1.WIC.NativeComWrapper.dll</Data>
<Data>0.0.0.0</Data>
<Data>4ddbce83</Data>
<Data>c0000005</Data>
<Data>0000000000001124</Data>
<Data>165c</Data>
<Data>01cc483ec5787c37</Data>
<Data>C:\Windows\SYSTEM32\WISPTIS.EXE</Data>
<Data>C:\Program Files\Phase One\Capture One 6\WIC\WIC64\P1.WIC.NativeComWrapper.dll</Data>
<Data>038900e3-b432-11e0-bb9e-00235482126e</Data>
</EventData>
</Event>
Piet Gispen0 -
@Piet12
IIRC, CO6 from 6.2 onwards use the WIC (Windows Imaging Components), a Windows component for coding/decoding image files. It seems the P1 wrapper dll has issues with the WIC. I suggest you update your support case with your log (login to website) and maybe you'll find a response which did not make it to your mailbox.
A quick fix you could try is to uninstall 6.2.x and revert to the latest 6.1.x. You can download it from Phase One download page, software archive.0 -
Dear Paul,
Thanks for your advice. I have made my support case with PhaseOne two days ago (support team DK), and have updated it four times with my latest findings. I have received NO reaction whatsoever from Phase. In the past I would receive a reply within a couple of hours. So I wonder what is going on. I have uninstalled 6.2.2, removed all related files etc, and then re-installed 6.2.1. Unfortunately this has not helped, now 6.2.1 presents the same problems. I even could no longer use Photoshop because of the corrupted Windows Explorer files. My work-around now is to use Lightroom instead. CaptureOne, very much to my regret, in no longer on my computer, until a fix becomes available. I am not getting the maximum quality from my P45+ files, but at least I can continue my work.
I do hope PhaseOne will respond and can help to solve these problems.
Thanks again.
Piet Gispen0 -
Hi Piet,
A couple of thoughts.
Since Lightroom works ( and so did mine), it implies to me that the files themselves, and probably the folders, are not corrupted. My problems were evident with Win Explorer. They even existed on my backup drives which CO did not access.
Perhaps the order you do things in is important. I first uninstalled 6.2.2, then reinstalled 6.2.1. I still had the problems. Then I did a system restore to a date before I put 6.2.2 on. The Win Explorer problem was fixed.
Question - when you browse your photo folders with Win Explorer, does the app shut down? When you browse non photo folders, does it continue to run? (mine did). I would guess that the WIC was badly effected.
I would try another restore now that CO is uninstalled. Good luck
Jim0 -
Dear Piet,
I think you should not try to revert to 6.2.1, but to 6.1.1 as I suggested in my previous post here. Have you tried that?0 -
Thanks, no I hadn't tried that, but I will. In the meantime I have received a very short note from PhaseOne stating that they are aware of the problem and working on it. No suggestions as to how I can resolve my problems. I appreciate your help all the more.
Regards,
Piet0 -
Belive me only restore to the point before update will worke. I have the problem weeks ago with update v 6.2 to v 6.2.1 . But i have disable the restorpoints. So i have not this chance. Only when i move from the wic64 folder a dll file it works but my workstation was sine the update crazy. I have think the hardware have problems ore virus. Blueescreens, usb problems, slower, and other problems. I buy a new machine clean install v 6.2.1 work. 3 days ago i make update to v 6.2.2. . Problem raw .cr2 no possible to move - no possible to delete with windows explorer ore other program. I uninstall all von c1. But wic64 folder was no possible to delete. In save mode it was possible. So i install v 6.2.1 again. All work ok. Cr2 was possible to delet and move. After restart no possible to copy files von cf card with windows explorer and no possible open folder with cr2 files. . Windows explorer crash allways. I have learn and have enable restorpoints and so i go back to the point bevor update. No i think all work...
Ps: support answer my a lot of times. After 2 times clean uninstall and disable opencl the problem with crash windows explorer was gone at the old workstation. But my system not like bevor update.
PPS: Windows 7 32 bit no problems only 64 bit
Sorry the bad english0 -
Thanks Alex, so far my only solution is to compeletely remove CaptureOne from my computer. Re-in stalling version 6.1 as Paul suggested hasn't helped either, the program now crashes upon starting.
It is quite cynical: after having had endless trouble with the 32-bit version (all memory related, costing me weeks and lots of money), at the suggestion of PhaseOne I upgraded to Windows 7 64-bit as this should solve my problems with CO1 Pro. Now I can no longer have the program --for which I paid-- on my computer! I am now using Lightroom even to process my expensive P45+ files.
I do hope PhaseOne will hurry up: this is the rather uninspiring answer I received from the support team (which I received after two days):
[quote]
Hi,
thanks for writing us - we have been able to reproduce what you describe to us on WIN7 - 64 bit - the issue is mostlikely related to the Windows Explorer. If this is terminated you can save. However we recommend that you use the "save as..." option.
We have reported this issue to R&D of they will adress this into a future release of Capture One if possible without violating the Windows Copyright.
[end quote]
Piet0 -
dont uninstall and go back to older version. you have some other problems. (i have do this) Only a sytemrestor on the point bevor update have worke. Belive me i spent on one computer more than one week with all thinks are possible. So i buy a new computer and after the new 6.2.2. problems. only restorpoint worke. 0 -
Hi,
A restore to the last snapshot of my system is okay, and was the way for me to continue to work. Note : It is impossible, except a bug from Microsoft, to have restoration points not solving problems, except if there is no backward compatibility (data). I had the luck to find one of two days old, with a system Windows Update.
Maybe I'll do a snapshot for next release. Most often, softwares updated or installed do that before modifying customer disk. Can it be implemented ?
Best Regards,0 -
For some (most unfortunate) reason I have no more restore points, only two just made after I had installed that wretched upgrade to 6.2.2. Otherwise my systems works without any problems or hitches, it is just CO1 Pro causing all these troubles.
Piet0 -
Piet12,
It means that the system is not corrupt in itself. The (radical) restore allow to retrieve the real preceding state, registry variables included. That's the big undo we do not have in the life...
To get snapshots again, you can (I translate from my french OS):
- press "Windows key" + "Pause key", then on the left panel something like Advanced System Parameters, then select tab which looks like "System Protection".
Or just press "windows key", release it, then enter with keyboard some key words like "restoring system" or else.
Best Regards0 -
Gilles,
Thank you for your advice; I have tried this, but I have no more restore points from before installing the update. At first they were there, but they got deleted for some reason when trying to get back to them, which led to a failed system restore. After these failures (Itried twice) they were gone. Without CaptureOne Pro on my computer everything at least seems normal, enabling to do my work, albeit without CO1.
Thanks again,
Piet0 -
Here the very short answer from Phaseonesupport:
Hi - we are sorry to inform we have also found this bug in out software - this is reported to R&D and they will fix in a comming release of Capture One.
BR and thanks for writing 😊
Phase One0 -
Well this is the answer I got from the Danish Support Team, which I think is self-explanatory, and, alas, not very encouraging:
"Hi - the issue is not releated to version 6.2.2, 6.2 or even 6.1 - it is related to the way your explorer works - try with for example Paint proggram - it is the same issue! But since it apperas to be Capture One we will try to see what we can adjust in the programming to avoid the explorer to keep hanging the files developped from Capture One.I cannot tall when we can have that fixed since it's not only a Capture One issue but also a Windows issue we need to respect.
The workaround is to save as.....
Phase One"
They seem to have forgotten that as of version 6.1 CO1 works differently with Windows (WIC). Moreover I fail to see how may explorer would work differently form any other computer with the same Windows version. Also Paint (for whatever it may be worth) is working just fine... I also happen to have these problems on both computer systems (Windows 7 64-bit and Vista 32-bit). It is causing me a lot of trouble, and to be honest it is becoming more than just annoying.
Piet0 -
[quote="Piet12" wrote:
Well this is the answer I got from the Danish Support Team, which I think is self-explanatory, and, alas, not very encouraging:
"Hi - the issue is not releated to version 6.2.2, 6.2 or even 6.1 - it is related to the way your explorer works - try with for example Paint proggram - it is the same issue! But since it apperas to be Capture One we will try to see what we can adjust in the programming to avoid the explorer to keep hanging the files developped from Capture One.I cannot tall when we can have that fixed since it's not only a Capture One issue but also a Windows issue we need to respect.
The workaround is to save as.....
Phase One"
Piet
This statement really concerns me. The failures I encountered with CO 6.2.2 were present on any photo file I found with Explorer - not just those that were processed with CO.
This did not occur with 6.2.1, nor with any of the Adobe products that I have. This is not an Explorer problem.
It might occur with Paint AFTER 6.2.2 is installed, but I'll bet it did not occur with Paint with 6.2.1 or before.
Does anybody at PO really use their software, and other software on a Windows machine?
Or do they just write code?0 -
Jim,
I am quite agree with what you write: CO1 really seems to be the culprit. In addition I had the misfortune that for some reason Windows 7 had deleted my restore point from before the upgrade. I now no longer have CO1 on my computer... I have no idea how long it will Phase One take to do something about this. I am not optimistic... It is really affecting my business.
Piet0 -
[quote="Piet12" wrote:
..In addition I had the misfortune that for some reason Windows 7 had deleted my restore point from before the upgrade.
Piet
Piet,
If you have a Win 7 install disk, you might try to insert that and do a Windows repair. It might just fix up the WIC files for you.
Jim0 -
Piet,
Take a look at this site
http://www.filerepair.ca/DLL-EXE-downlo ... u.exe.html
This might help.0 -
Hello Jim and Piet,
I think that PhaseOne had not understood the issue, or me, or us.
May be we must describe again what happened.
For my part, just after installing and running a little (10 minutes) CO 6.2.2, I was unable to delete any CR2 files, even after closing CO. I did try that after reading about this bug in this forum, because I quite never delete a CR2, but I cam move them. I have made a reboot, then all was okay. Then, 30 minutes later, after running again CO 6.2.2, a lot of CR2 (and NOT xmp) in many directories was locked. So, do not panic Gilles. Here I decided to reboot, update my photos data backup, then launch a restore at a recent snapshot. With a little scary issue with W7 who gaves me a black screen after login, but solved.
I can say clearly that since I returned to 6.2.1 through a system restore, I have no more problem with explorer at all, after almost 6 working hours on this W7 64 bits OS.
Right now, I just played with mspaint. No problem, I can even remove a file opened simultaneously by CO, MP1 (in WIC mode) and MSPaint (not a CR2 😉 ). CO tells me with an exclamation mark in the preview that there is no more file, that's all. I restore it, CO is happy again. After closing all that, still no problem, I can manipulate all files
I am not sure to speak about the same bug. Tell me please,
Best Regards0 -
[quote="Gilles" wrote:
Hello Jim and Piet,
I think that PhaseOne had not understood the issue, or me, or us.
May be we must describe again what happened.......
I am not sure to speak about the same bug. Tell me please,
Best Regards
Gilles,
I encountered two major problems with 6.2.2.
1. It got it into a memory runaway state where it was in a loop trying to build proxies. The only way out was to move folders, which sometimes stopped it.
2. It appears that 6.2.2 may have corrupted my Windows Explorer (or the part that used WIC); at least when it looked at my folders where my photos are, or any photos inside the folders. After opening 2-4 folders, Win Explorer would simply shut down.
This continued even after I had uninstalled 6.2.2 and returned to 6.2.1
Note, however, that Lightroom continued to function properly, as did PS Elements.
Note - I did not encounter some of the problems that both of you mentioned - in large part because I did not use CO 6.2.2 very much before I got rid of it.
I think I have the Explorer problem fixed but - I had to do a OS system restore to a date before I installed 6.2.2
So far I have had no more problems with Explorer or CO 6.2.10 -
Jim,
did you reboot after reinstalling the 6.2.1 ?0 -
[quote="Gilles" wrote:
Jim,
did you reboot after reinstalling the 6.2.1 ?
Probably not. However, I did reboot after I did a system restore.0
Post is closed for comments.
Comments
53 comments