Reminder to update the firmware on your R6 Mark II camera...

[JFG]

Hello R6 Mark II owners,

I just updated my R6 Mark II with the latest firmware eosr62-v170 ver. 1.7.0 75.77mb  that was posted yesterday 5-13-2026, and want to remind all that updating your "Canon Camera's firmware" is one of the easiest ways to to make your R6 Mark II literally a better camera overnight.  When you update your firmware, you get better autofocus, better stability, new features, bug fixes, and improved lens compatibility.  All for free.  

Should you update your firmware when there is trouble with your R6 Mark II?  Yes, updating your firmware is one of the first things you should do when your canon R6 Mark II starts acting weird. 

Updating firmware won't help when there's  Physical damage (Shutter, IBIS, bent pins), Dirty lens contacts, Bad SD card and Wrong settings (like Servo AF disabled).  This are user-side or hardware issues, not firmware problems.

[justadude]

"I always wait a few weeks before updating f/w... Always have 🙂"

I'm not doubting your reason for waiting, so file this as more of a curiosity than anything. While I've owned many (too many) cameras since digital cameras became popular in the 90's, and have owned quite a few brands, and also personally know a lot of other photographers who are like me and update on day one... I have never known anyone to have problems with a firmware update. 

But that being said, I do know a few others who wait a week or so like you do. Is there any particular reason? I ask only because you often hear others say "You can brick your camera doing a firmware update" ... yet no one I've talked to has ever known someone to do that. 

So I'm just curious... do you wait because of the chance of bricking the camera? Or simply to make sure there are no further bugs?

[FloridaDrafter]

---

@justadude wrote:

"I always wait a few weeks before updating f/w... Always have 🙂"

So I'm just curious... do you wait because of the chance of bricking the camera? Or simply to make sure there are no further bugs?

---

No further bugs. It goes way back to my time in IT as a systems admin. I can't count the number of BIOS updates I performed on various systems, Win, Mac, Unix, that failed or required a dive into the deep end to repair. I've just always been cautious when it comes to this type of thing.

IIRC, at least two of my R firmware updates were recalled almost immediately, I don't remember which ones, but it seems that there was one for the R5 and one for the R6. X.0.0 was released and changed overnight to X.0.1.

I'll add that my cameras are working fine, so no need to rush 🙂

Newton

[justadude]

Considering your background, this makes very good sense. Maybe I need to rethink my usual "update right away" thinking.  Thanks for the info, Newton!

[FloridaDrafter]

Gary, don't sweat the firmware "out of the gate" habit as odds are in your favor. Things have changed since my days in IT, I haven't had a BIOS update go wonky for many years. But in those days, I was managing hundreds of users and five servers. Now I'm just having to occasionally update the four that my wife and I use at home and that is for security purposes. Hackers will often go for systems with outdated software or BIOS where a vulnerability on the users part may have been neglected, that is why software, like Acrobat Reader and other utilities, should be kept up to date. BIOS is often overlooked, even by OEM. I still keep in touch with folks who are in the biz. Dell is the most secure and keep their BIOS up to date, even though it's a PIA to sometimes have to reset certain features on my laptop, like the keyboard lights and sometimes my sound system.

It's still hard to break old habits 🙂

Newton

[JFG]

Hi Gary and Newton,

I agree with Newton, Canon did pull back (suspended) Firmware Version 1.1.0 for the EOS R5 Mark II (and EOS R1) because of a critical bug affecting: Video recording using Pre-Recording; When using a CFexpress cards larger than 2TB; Result: Video files could not be played back on the camera or a PC. Canon publicly acknowledged the issue and halted the firmware download.  Canon has since released Firmware Version 1.3.0,   Firmware v1.3.0 it's the first fully stable, post-pullback release for the  R5 Mark II and it fixes everything that caused Canon to yank the earlier firmware.  Takeaway: With the v1.3.0 you get:

• Stability restored - no more playback corruption issues
• Improved AF behavior (especially tracking consistency)
• Better Thermal management in long video sessions
• Bug fixes across EVF behavior, HDMI output, and card compatibility
• General performance polish Canon didn't fully detail but is noticeable in responsiveness.

Having said that, Canon almost never pulls firmware a day after release.  What happened with R5 Mark II (and R1) was unusual, even by Canon standards.  Canon's typical firmware behavior is:

• Slow, Cautious release cycle.  Canon usually releases firmware every 6-18 months, unless a major bug or new lens requires support.
• Small incremental updates:  Most updates are: 1. Lens compatibility  2. Minor AF tweaks  3. Bug fixes  4. Stability improvements 

Canon rarely push big feature updates like Sony or Fuji..  

Should you worry if you updated?   If you did not install v.1.1.0 you are safe.

If you did install v.1.1.0 (like I did):  The bug only affects video + pre-recording + >2 TB cards.  If you don't use that combination, you won't see the issue.  Updating to v. 1.3.0 resolves the situation entirely.

I always update firmware when I receive an email from Canon informing of a new update release for my cameras and lenses.  Usually I do it when I have the time and sometimes it could be a a day to a week after the new firmware update has been released.  Not because I purposely wait a week or two out of caution, but because I don't have available time.  I updated the Firmware on my R5 Mark II and R6 Mark II on 5-14-2026 the day after the new Firmware v. 1.3.0 came out (5-13-20026).

I use to wait a week or two after a new BIOS (Firmware update) was release to update my equipment (PC, Laptop, Camera gear etc..).   But I haven't done that for at least the last 18 years or more.  I agree with Newton when he states "Gary, don't sweat the firmware "out of the gate" habit as odds are in your favor. Things have changed since my days in IT, I haven't had a BIOS update go wonky for many years."  Also, technology has advance so much so fast that the days of BIOS updates turning gear into bricks are gone.  I was one of the first to receive the R5 Mark II and have updated the firmware on it as soon as it is released and downloaded the v. 1.1.0 and my camera didn't turn into a brick.  I downloaded the new firmware version v. 1.3.0 and resolved the situation entirely. However, it is a personal decision and one needs to do what makes one comfortable and happy.