Those who didn't have any problems in the first place: did you have registered battery info?

Why access registered battery info during a lens update when all you should be concerned with is the current battery charge? As a software developer I think this is one crazy bug. (Not that I code bug free )

I find it a little annoying that they come out with a firmware fix for this lens which apparently sold in huge amounts, but can only be updated by the people who have the very newest cameras, which is probably a fraction of owners. I just sent a buch of lenses back and forth to Canon to get them adjusted right, and I'm kind of tired of spending money on shipping...

NickCat

Same result here with the battery registration delete after a failed update.

<snip>

Canon... really... REALLY? That's just lazy.

I would guess less "lazy" and more "we have a bug with battery info registration we didn't know about and didn't see (on the new cameras) in our testing lab".

The "lazy" was more referring to QC on the firmware by obviously not testing the update on enough different body/scenarios to ensure it would work. I do realize they can't test every scenario though, but a body with registered batteries seems like a fairly common one.

But, yes... I see new body firmwares coming soon!

Logged

jsbraby

The "lazy" was more referring to QC on the firmware by obviously not testing the update on enough different body/scenarios to ensure it would work. I do realize they can't test every scenario though, but a body with registered batteries seems like a fairly common one.

But, yes... I see new body firmwares coming soon!

I don't think it's happening to every body with battery information registered; my 5d3 has battery info registered and the STM upgrade went through first try. But it is clearly happening to some combination of battery, body and battery information registration. I wouldn't rule out an unforeseen interaction between some custom setting and the battery registration.

I haven't been following this closely enough, but I wonder if maybe the issue is with battery information registered from counterfeit or third party batteries? Maybe the people who had the issue and then succeeded after deleting the battery registration information can chime in on that.

Logged

aZhu

The "lazy" was more referring to QC on the firmware by obviously not testing the update on enough different body/scenarios to ensure it would work. I do realize they can't test every scenario though, but a body with registered batteries seems like a fairly common one.

But, yes... I see new body firmwares coming soon!

I don't think it's happening to every body with battery information registered; my 5d3 has battery info registered and the STM upgrade went through first try. But it is clearly happening to some combination of battery, body and battery information registration. I wouldn't rule out an unforeseen interaction between some custom setting and the battery registration.

I haven't been following this closely enough, but I wonder if maybe the issue is with battery information registered from counterfeit or third party batteries? Maybe the people who had the issue and then succeeded after deleting the battery registration information can chime in on that.

All of my batteries are legit but I had the issue. It can be due to other factors like you said but I also posed the idea that it could be earlier releases of the lens? I pre-ordered and got it pretty much on the week of release.