EOS R5 Mark II - Adobe Lightroom errors

[mdougc]

In processing my photos in Adobe Lightroom Classic, some photos are rejected with the error message, "The file appears to be unsupported or damaged".

The Canon DPP app also rejects the photos, but the message only pops up for 2 seconds, so I can't exactly quote it.

What's happening?

[March411]

Are you running Canon DPP latest release - dppw4.19.10

https://app.ssw.imaging-saas.canon/app/en/dpp.html

[mdougc]

I checked before downloading photos. Every Canon and Adobe app is up to date.

[p4pictures]

Check the version of DPP you have.The version that is needed to support EOS R5 Mark II is 4.19.10 or later. 

I have seen a situation where an older version of DPP didn't find any updates eve though I knew this new v4.19.10 was available and I was using 4.18 at the time.

[mdougc]

You are right! I wish Canon would fix the bugs in that web site.

Anyway, the newer version did not help.

[ebiggs1]

Agree my first guess is the R5 Mk II is new enough you need to have the latest software from Adobe and Canon DPP4. Adobe may be a little behind updating the raw file converter. If that's the problem they will soon I have no doubt.

[mdougc]

If so, Canon is also behind.

[Stephen]

Please check your EOS Utility & DPP again. The current versions very specifically mention support for the R5 Mark II

[mdougc]

You are right! The "Check for update" in the app did not find an update. I wish Canon would fix the bugs in that web site. This is one of several.

Anyway, the newer version did not help.

[mdougc]

You are labeled "Moderator", so I am guessing that means you are somehow officially connected to Canon. Therefore I am posting my update to you.

I downloaded the photos again, but instead of using the EOS Utility, I plugged the memory card directly to the computer. The corrupted photos loaded to Lightroom with no corruption error messages.

This leaves me with several possibilities for faults:
1. the cable is bad - but I have had no problems at all with other cameras.
2. the camera firmware - the read/write/xmit may be bad.
3. the EOS Utility - handler bug

Can you suggest a next step? Note that there is another post on this site with someone else reporting a similar experience.