Canon has corrected a bug in firmware v1.4.0 for the Canon EOS R3 and have released v1.4.1. If you haven't upgraded to 1.4.0, this new firmware will add the following features and fixes.

Firmware Version 1.4.1 incorporates the following enhancements and fixes:

  1. Adds support for Speedlite EL-5.*
    *The automatic light intensity adjustment of the AF-assist beam is not supported.
  2. Adds [Register people priority] to the camera menu.
    Pre-registered people can now be detected and tracked with priority.**
    ** This feature may not operate if faces are too small to detect, in profile or turned at an angle or partially hidden; for scenes where the subject is moving; or due to certain shooting environments.
  3. Adds [Save/load comm. settings on card] to the camera menu.
    Network settings can now be transferred between cameras of the same model.
  4. Adds [Panning Assist] to the camera menu. When a compatible lens is used for panning shots, image stabilization and subject blur correction are applied during the exposure.
  5. Improves the Auto White Balance (AWB) setting to reduce the time it takes for the AWB result to be reflected in the camera’s viewfinder's display when looking through the viewfinder.
  6. Adds Protect Images During [FTP Transfer] to the camera menu. Images transferred via FTP can now be automatically protected. The user can determine if images have already been transferred via FTP.
  7. Fixes an issue in which Error 70 may occur when using the camera with certain EF lenses after having updated the camera firmware to Version 1.4.0.
  8. Fixes an issue in which the original tracking performance of Servo AF cannot be attained depending on shooting conditions when performing high-speed continuous shooting using the electronic shutter after having updated the camera firmware to Version 1.4.0.
  9. Fixes minor issues.

Download firmware v1.4.1 for the Canon EOS R3

Some of our articles may include affiliate links. If you purchase through these links, we may earn an affiliate commission at no extra cost to you.

Go to discussion...

Share.

30 comments

  1. Firmware 1.4.0 bricked my R3. It's currently at service centre... Big fail for Canon. Canon doesn't have any testing departament before firmware is released to public?
  2. Firmware 1.4.0 bricked my R3. It's currently at service centre... Big fail for Canon. Canon doesn't have any testing department before firmware is released to public?
    I'm sorry to hear that.

    OK it could be the firmware that bricked your camera, or it could be coincidental, or it could be that you inadvertently bricked it yourself by not following Canon's instructions precisely.

    Did you:

    Check the size of the downloaded file against the correct size, to check for a corrupted file?
    Fit a freshly charged battery?
    Remove the lens and all other accessories?

    Is it possible that you:

    Panicked when the update stalled, and turned the camera off?
    Accidentally or deliberately touched a button or dial during the install process?

    Not criticising - just trying to be helpful ;)
  3. I'm sorry to hear that.

    OK it could be the firmware that bricked your camera, or it could be coincidental, or it could be that you inadvertently bricked it yourself by not following Canon's instructions precisely.

    Did you:

    Check the size of the downloaded file against the correct size, to check for a corrupted file?
    Fit a freshly charged battery?
    Remove the lens and all other accessories?

    Is it possible that you:

    Panicked when the update stalled, and turned the camera off?
    Accidentally or deliberately touched a button or dial during the install process?

    Not criticising - just trying to be helpful ;)
    Update itself was ok. About 1 week after upgrade I wanted to check "panning assist" - the new option. Somehow I couldn't turn it off later. I tried different shooting modes, reset of settings - all failed. It ended up on body locked in 'bulb' mode and no signal from sensor (no image in in EVF). Btw, I've just got reply from service centre - they fixed it by loading new 1.4.1. After this situation I will not be too fast with trying new firmware. Better to wait few weeks if possible...
  4. Update itself was ok. About 1 week after upgrade I wanted to check "panning assist" - the new option. Somehow I couldn't turn it off later. I tried different shooting modes, reset of settings - all failed. It ended up on body locked in 'bulb' mode and no signal from sensor (no image in in EVF). Btw, I've just got reply from service centre - they fixed it by loading new 1.4.1. After this situation I will not be too fast with trying new firmware. Better to wait few weeks if possible...
    Glad to hear that the new firmware fixes it! :D
  5. This morning I just updated my R3 camera from firmware 1.4.0 to 1.4.1.

    A couple of things I noticed:

    1) I could not get the Canon app on my phone to update it so I had to download the 1.4.1 to my card
    2) I had to format my card before installing the new firmware to the card to be able to get the camera to detect the new firmware.

    This is the last firmware I will be installing until I finish my two summer photography trips by the end of August.

    I learned my lesson; wait a month after Canon release a 1.X.0 firmware because likely there will be a 1.X.1 version to fix a bug.
  6. This morning I just updated my R3 camera from firmware 1.4.0 to 1.4.1.

    A couple of things I noticed:

    1) I could not get the Canon app on my phone to update it so I had to download the 1.4.1 to my card
    2) I had to format my card before installing the new firmware to the card to be able to get the camera to detect the new firmware.

    This is the last firmware I will be installing until I finish my two summer photography trips by the end of August.

    I learned my lesson; wait a month after Canon release a 1.X.0 firmware because likely there will be a 1.X.1 version to fix a bug.
    NEVER NEVER install firmware updates until at least a month after release. You may be lucky, most people are, but there's nothing worse than bricking a camera just before an important shoot. Don't take chances. Let others be the guinea pigs.
  7. A Canon "Oops" moment?
    Not defending Canon here, but I wonder how they compare with Sony, Nikon and Panasonic regarding "technical oversights". It's a very competitive market, where goods have to be rushed out and are increasingly complex, so I'd imagine that the other brands have similar issues.
  8. Not defending Canon here, but I wonder how they compare with Sony, Nikon and Panasonic regarding "technical oversights". It's a very competitive market, where goods have to be rushed out and are increasingly complex, so I'd imagine that the other brands have similar issues.
    SW is tough to get right. It will be interesting to see how AI can help debug it. One thing to miss a function/issue but another to brick a camera. You don't forget that.
  9. SW is tough to get right. It will be interesting to see how AI can help debug it. One thing to miss a function/issue but another to brick a camera. You don't forget that.
    Bricking seems pretty rare, though. Possibly coincidental, as well, e.g. chip failure.
  10. SW is tough to get right. It will be interesting to see how AI can help debug it.
    AI is a wonderful thing, so yes I can't see any reason why it can't be used for debugging.

    AI will provide so many opportunities for improving subject recognition, AF, metering, stacking, noise elimination, blur-control, hi-res, HDR, stabilisation and many other things that haven't even been thought of yet. As long as I can easily override it (or certain aspects of it), I welcome it. It would be nice to be able to customise cameras and choose which aspects I want AI to help with, and which ones I'd prefer to have total control of myself.
    One thing to miss a function/issue but another to brick a camera. You don't forget that.
    I find it crazy that *bricked* cameras can't be reset to the "out of box" settings, so that people can reinstall an older firmware version that works properly. If I bricked a camera, the first thing I'd do would be to remove and replace the battery, and attempt to install a previous version.

    @PawelW seems to have encountered a genuine firmware-induced bricking, but I'd place bets that a lot of the bricking that gets reported is down to user error, i.e. not following Canon's instructions *precisely*. It's easy to panic and start pressing buttons when an installation appears to have frozen, but is just very very s-l-o-w.
  11. [...]I find it crazy that *bricked* cameras can't be reset to the "out of box" settings, so that people can reinstall an older firmware version that works properly. If I bricked a camera, the first thing I'd do would be to remove and replace the battery, and attempt to install a previous version.
    [...]
    If pulling the battery works, it wasn't bricked, but 'crashed', 'hung', 'confused', 'on strike' or something like that. But not bricked.

Leave a comment

Please log in to your forum account to comment