Since I like to keep the original name rename the file twice once by adding a ‘-’ suffix to the file name before the extension and then I wait for the PhotoLab to remove the sidecar file and then rename it back. dop sidecar file and detect the renamed file correctly.

And the workaround is to rename the file while PhotoLab is still open since then PhotoLab will remove the. I have been encountering this error message and it seems to happen in my case when I’m complying files into a folder I have open in PhotoLab. The files are not corrupted - (a) because I can view them in other programs and (b) because if I make another copy of them PL can read them.Īs I say, although the photos are on Onedrive, they are all available on my local drive and so there is no reason I can think of for them suddenly refusing to display.īut if someone can explain the behaviour (or give me a fix) then I would be grateful. It’s not on every file but on over 50% of them and I cannot find a difference between those which display ok and those which don’t. I’ve been storing my photos like this for a couple of years and never a problem until today when I get the message I’ve just mentioned. But that is no concern - I just like to have two local and one cloud copy of all my photos. Photolab always downloads a copy of the files to my local C drive when I start to edit them. I keep a copy of all my photos on my D drive and then make a copy of all my RAWs on OneDrive. It may be corrupted or in an unsupported format.’ As of today, I have started to receive the message ‘this image cannot be processed because of an unknown error.

DxO PhotoLab 7.0.1.76 downloading